DF16 7362 Introduction

1 © Nokia 2016
 Section 3
GPON Configuration

2 © Nokia 2016 Nokia Internal Use

GPON Configuration

• “gpon” mode is the default mode of DF-16.

• To change from ngpon mode to gpon mode, use “configure equipment shelf 1/1 mode gpon”.
• Warning:
- If the mode is changed, then PON side of provisioning, including ONTs/bridgeports/vlanports, will be
removed.
- VLAN and qos profiles will not be removed.
- The uplink port side configuration will not be removed.
- Mode change will result in automatic reboot of the OLT.
• 16 PON ports are supported. Given there are only 8 physical PON ports, a dual GPON OLT XFP
(3FE56402 variants) should be used in which each XFP can connect up to two fibers. In other
words, each XFP supports up to two PON ports.
- “show pon sfp-inventory” to view SFP vendor detail.
- “show equipment diagnostics sfp lt:1/1/1:sfp:x detail” to view SFP stats.

3 © Nokia 2016 Nokia Internal Use

GPON Configuration – CLI Provisioning

• The GPON mode configuration follows standard 7360 GPON configuration from PON standpoint.
The following CLI example creates Bridgeport 1/1/1/3/1/1/1 and two VLAN ports. The steps are
identical to what we do in a 7360 GPON:
• configure equipment ont interface 1/1/1/3/1 sernum ALCL:FAE233B8 sw-ver-pland disabled
• configure equipment ont interface 1/1/1/3/1 admin-state up
• configure equipment ont slot 1/1/1/3/1/1 planned-card-type ethernet plndnumdataports 4 plndnumvoiceports 0
• configure ethernet ont 1/1/1/3/1/1/1 admin-state up
• configure qos interface 1/1/1/3/1/1/1 upstream-queue 0 bandwidth-profile name:test_bw
• configure bridge port 1/1/1/3/1/1/1 max-unicast-mac 128
• configure bridge port 1/1/1/3/1/1/1 vlan-id 101
• configure bridge port 1/1/1/3/1/1/1 vlan-id 102
• configure bridge port 1/1/1/3/1/1/1 pvid 101

4 © Nokia 2016 Nokia Internal Use

GPON Configuration – Traffic Forwarding

• With a bridgeport and two vlanports created on the PON side, we are now forming a forwarding
module like the one illustrate below, and traffic will flow through the two link-agg groups and
bridgeport/vlanport on the PON side, following certain rules.

5 © Nokia 2016 Nokia Internal Use

GPON Configuration – Traffic Forwarding

• The forwarding rules are the same for CC VLAN and RB VLAN on the upstream direction, but vary
a bit on the downstream direction currently. In our example, VLAN 101 is a CC VLAN. VLAN 102 is
a RB VLAN.
• Upstream traffic forwarding rules on a CC VLAN, or a RB VLAN:
- Packets from ONT side will be sent to both link-agg groups, if the destination mac is not learned anywhere.
- If the destination mac is already learned on one of the link-agg group, then packets from ONT side will only
be sent to that group.
- In other words, upstream direction forwarding follows mac-based forwarding rule.

6 © Nokia 2016 Nokia Internal Use

GPON Configuration – Traffic Forwarding

• Downstream traffic forwarding rules on a CC VLAN:

- Packet from one link-agg group will only be sent towards the ONT side, but not to the other uplink
port/group. This is regardless if the destination mac is learned on ONT side or not.
- The only scenario packet going to the other link-agg group is when ONT side has no matching vlan port.
• Downstream traffic forwarding rules on a RB VLAN:
- If destination mac is not learned on the ONT side, the packets will be sent to the other uplink port/group but
not to the ONT side. This is due to RB VLAN on PON side doesn’t forward packet if mac is not learned.
- If destination mac is learned on the ONT side, then the packet will be sent to the ONT side, but not to the
other uplink port/group.

7 © Nokia 2016 Nokia Internal Use