(Optional) Configuring the System Parameters

This topic describes how to configure the system parameters including the overseas version flag and message waiting indication (MWI) mode according to the local standards to ensure that the response of the user terminal complies with the local standards. Thunder-link where you can buy OLT, DSLAM there.

Procedure

1. Run the system parameters command to configure the system parameters.
2. Run the display system parameters command to check whether the system parameters are the same as those in the data plan.

Example

To configure the overseas version flag (system parameter 1) to Hong Kong (parameter value 1), do as follows:

huawei(config)#system parameters 1 1                      
huawei(config)#display system parameters 1
  ----------------------------------------------------------------------------- 
  Parameter name index: 1     Parameter value: 1                                
  Mean: Overseas version flag, 0:China, 1:HongKong, 2:Brazil, 3:Egypt, 4:       
Singapore, 5:Thailand, 6:France, 7:Britain MSFUK, 8:Britain ETSI, 9:Bulgaria,   
10:Reserved, 11:Austria, 12:Hungary, 13:Poland                                  
  ----------------------------------------------------------------------------- 

Parent topic: 

When Prewarning on Service Unavailability of H806GPBH & H806GPBD Boards of MA5600T

When Display Change of Service Ports and Service Failure in the MA5600T?

What Is the Calculation Method for Load Balancing of the Upstream Aggregation Ports of the MA5680T?

Huawei OLT Cascading Capability

This topic describes the cascading capability of the MA5680T/MA5683T, which can be
implemented by the OPGD or ETHB board.
NE Convergence
The MA5680T/MA5683T features powerful access and convergence capability. In the
downstream direction, it supports cascading to other devices through the GE or 10GE port. In
the upstream direction, it supports connection to the IP/MPLS network through the GE or 10GE
port. It also supports dual homing to the BRAS through direct connection.
Unique ATM DSLAM Cascading Function
The MA5680T/MA5683T supports cascaded ATM DSLAM devices and finally migrates the
ATM convergence network to the Ethernet convergence network.
l The MA5680T/MA5683T can inherit all the ATM services, including the ATM STM-1
port, PPPoA/IPoA, and high speed Internet (HSI) line services.
l The MA5680T/MA5683T supports the IPoA and PPPoA access services on the subscriber
side, which are converted into the IPoE and PPPoE modes inside the device and then
accessed to the IP network.
l The MA5680T/MA5683T supports upstream transmission in the Ethernet, ATM PWE3,
or ETH PWE3 mode.

More blog:

When Prewarning on Service Unavailability of H806GPBH & H806GPBD Boards of MA5600T

How to enable the operation of log forwarding server on the U2000?

How to Use the Multimeter to Check Whether the A32 Board Is Faulty?

Forwarding Framework on the Device

For OLT device

NOTE:

The difference among the following forwarding tables is the first-level and second-level indexes. For example, the first-level and second-level index in the GPON multicast forwarding table (VLAN+GIP) is VLAN+GIP.

GPON Multicast Forwarding Table (VLAN+GIP) [OLT]

Figure 1 GPON multicast forwarding table (VLAN+GIP)

The OLT supports a distributed 2+1-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GIP" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GIP" index, the service board duplicates multicast data to the GPON port interested in the multicast program in an as-per-requirement manner, effectively saving the downstream bandwidth of the GPON port. Then the service board encapsulates and transmits the multicast data on the GPON port in the mode of multicast GEM port (system-level parameter, configurable, default value 4095).
• The third-level duplication is implemented on the ONT. By using the "VLAN+GMAC" white list, the ONT filters out unneeded multicast data to avoid bandwidth overflow at the downstream ingress (ONT only supports that in olt-control mode). Then, by using the "VLAN+GMAC" index, the ONT duplicates the multicast data to the ONT ports in an as-per-requirement manner (only supports forwarding by using GMAC in snooping mode).

NOTE:

1. This forwarding mode applies to ASMSSM and ASM ONLY group filter modes (for details, see "Group Filter Mode").
2. The ONT that implements the third-level duplication is recommended to use the chip that supports VLAN+GIP forwarding. If the ONT does not use such a chip, program GIP-to-GMAC mapping must be a one-to-one mapping. Without the one-to-one mapping on the same ONT, garbled images will occur.

This topic describes only the forwarding framework in the most common single-copy duplication mechanism. For the hardware forwarding framework in the multi-copy duplication mechanism, see "GPON Multi-Copy Duplication."

GPON Multicast Forwarding Table (VLAN+GIP+SIP) [OLT]

Figure 2 GPON multicast forwarding table (VLAN+GIP+SIP) 

The OLT supports a distributed 2+1-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GIP+SIP" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GIP+SIP" index, the service board duplicates multicast data to the GPON port interested in the multicast program in an as-per-requirement manner, effectively saving the downstream bandwidth of the GPON port. Then the service board encapsulates and transmits the multicast data on the GPON port in the mode of multicast GEM port (system-level parameter, configurable, default value 4095).
• The third-level duplication is implemented on the ONT. By using the "VLAN+GMAC" white list, the ONT filters out unneeded multicast data to avoid bandwidth overflow at the downstream ingress (ONT only supports that in olt-control mode). Then, by using the "VLAN+GMAC" index, the ONT duplicates the multicast data to the ONT ports in an as-per-requirement manner (only supports forwarding by using GMAC in snooping mode).

NOTE:

1. This forwarding mode applies to the SSM ONLY group filter mode.
2. Due to hardware limitations, only the difference in the least significant 20 bits can be differentiated between source IP addresses (SIPs). For example, 1.1.1.1 and 2.1.1.1 are the same SIP for the device; 1.1.1.1 and 1.1.1.2 are different SIPs for the device.
3. The ONT that implements the third-level duplication is recommended to use the chip that supports VLAN+GIP forwarding. If the ONT does not use such a chip, program GIP-to-GMAC mapping must be a one-to-one mapping. Without the one-to-one mapping on the same ONT, garbled images will occur.

Multicast Forwarding Table (VLAN+GMAC) [DSLAM]

Figure 3 DSLAM multicast forwarding table (VLAN+GMAC) 

 

The DSLAM supports a distributed two-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GMAC" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GMAC" index, the service board duplicates multicast data to the multicast user (usually corresponding to the first port) interested in the multicast program in an as-per-requirement manner.

NOTE:

This forwarding mode applies to boards that do not support Layer 3 multicast forwarding chip.

Multicast Forwarding Table (VLAN+GIP) [DSLAM]

Figure 4 DSLAM multicast forwarding table (VLAN+GIP)

The DSLAM supports a distributed two-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GIP" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GIP" index, the service board duplicates multicast data to the multicast user (usually corresponding to the first port) interested in the multicast program in an as-per-requirement manner.

NOTE:

This forwarding mode applies to ASMSSM and ASM ONLY group filter modes.

Multicast Forwarding Table (VLAN+GIP+SIP) [DSLAM]

Figure 5 DSLAM multicast forwarding table (VLAN+GIP+SIP)

The DSLAM supports a distributed two-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GIP+SIP" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GIP+SIP" index, the service board duplicates multicast data to the multicast user (usually corresponding to the first port) interested in the multicast program in an as-per-requirement manner.

NOTE:

1. This forwarding mode applies to the SSM ONLY group filter mode.
2. Due to hardware limitations, only the difference in the least significant 20 bits can be differentiated between SIPs. For example, 1.1.1.1 and 2.1.1.1 are the same SIP for the device; 1.1.1.1 and 1.1.1.2 are different SIPs for the device.

More related:

How to Control Board Failure After an MxU Service Port Is Bound to a Rate Unlimited

What’s the Service Interruption on the MA5616?

How to Upgrade the LSW Chip of the H801SCUN Board

How to Join Flow

This section considers IGMPv2 proxy as an example to describe the Join Flow.

Join Flow [OLT]

Figure 1 Join flow

1. The multicast user switches a channel and sends a join message for demanding a new program GIP1.
   
2. After receiving the join message, the service board enters the IGMP protocol stack of the multicast user. After multicast control is implemented (for details, see "Multicast CAC"), the following group membership table is generated on the service board.
   

   Index	Online Member
   MVLAN1+GIP1	Multicast user 1

   • At the same time, the following multicast forwarding table is generated on the service board (for details on how to map GIP1 to GMAC1, see "Basic Concepts").

   Index	Duplication Destination
   MVLAN1+ GMAC1	GPON port 1

   • According to MVLAN1 corresponding to the program, the service board serves as the proxy of multicast user 1 and sends a join message to the control board.
3. After receiving the join message, the control board enters the IGMP protocol stack of MVLAN1 and generates the following group membership table.
   

   Index	Online Member
   MVLAN1+GIP1	Service board 1

   • At the same time, the control board generates the following multicast forwarding table.

   Index	Duplication Destination
   MVLAN1+ GMAC1	Port corresponding to service board 1

4. The control board then sends a join message to the multicast router through the multicast upstream port of MVLAN1.
   
5. After receiving the multicast stream, the device first duplicates the stream to service board 1 according to the multicast forwarding table of the control board, and then duplicates the stream to GPON port 1 according to the multicast forwarding table of the service board.

NOTE:

1. Though the SVLAN of a multicast user is different from the MVLAN, the device can still implement the mapping to the MVLAN according to the multicast member configuration relationship. In this way, cross-VLAN multicast is supported without requiring additional configuration.
2. The join flow for boards supporting the group filter mode is similar and only the forwarding entry index is different.

Join Flow [DSLAM]

Figure 2 Join flow

1. The multicast user switches a channel and sends a join message for demanding a new program GIP1.
   
2. After receiving the join message, the control board enters the IGMP protocol stack of the multicast user. After multicast control is implemented (for details, see "Multicast CAC"), the following group membership table is generated on the control board.
   

   Index	Online Member
   MVLAN1+GIP1	Multicast user 1

   At the same time, the following multicast forwarding tables are generated on the control board and the service board (for details on how to map GIP1 to GMAC1, see "Basic Concepts").
   

   Table 1 Multicast forwarding table on the control board

   Index	Duplication Destination
   MVLAN1+ GMAC1	Corresponding port on service board 1

   Table 2 Multicast forwarding table on the service board

   Index	Duplication Destination
   MVLAN1+ GMAC1	User port 1

   • According to MVLAN1 corresponding to the program, the service board serves as the proxy of multicast user 1 and sends a join message to the control board.
3. The control board then sends a join message to the multicast router through the multicast upstream port of MVLAN1.
   
4. After receiving the multicast stream, the device first duplicates the stream to service board 1 according to the multicast forwarding table of the control board, and then duplicates the stream to user port 1 according to the multicast forwarding table of the service board.

NOTE:

1. Though the SVLAN of a multicast user is different from the MVLAN, the device can still implement the mapping to the MVLAN according to the multicast member configuration relationship. In this way, cross-VLAN multicast is supported without requiring additional configuration.
2. The join flow for boards supporting the group filter mode is similar and only the forwarding entry index is different.
3. If the traffic with a high priority is suddenly overloaded and the service with a low priority is affected, IGMP packets are not discarded. The device processes and sends the IGMP packets first.

More related:

How to precaution the using problem of Huawei MA5603T product?

Some Abnormal OLT GPON CLASS B+ Optical Modules at High Temperature

Number Dialing Failures If An MxU Connects To A Special Type Of Phone Set-20131010-A

Forwarding Framework on the Device

For OLT device

NOTE:

The difference among the following forwarding tables is the first-level and second-level indexes. For example, the first-level and second-level index in the GPON multicast forwarding table (VLAN+GIP) is VLAN+GIP.

GPON Multicast Forwarding Table (VLAN+GIP) [OLT]

Figure 1 GPON multicast forwarding table (VLAN+GIP) 

 

The OLT supports a distributed 2+1-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GIP" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GIP" index, the service board duplicates multicast data to the GPON port interested in the multicast program in an as-per-requirement manner, effectively saving the downstream bandwidth of the GPON port. Then the service board encapsulates and transmits the multicast data on the GPON port in the mode of multicast GEM port (system-level parameter, configurable, default value 4095).
• The third-level duplication is implemented on the ONT. By using the "VLAN+GMAC" white list, the ONT filters out unneeded multicast data to avoid bandwidth overflow at the downstream ingress (ONT only supports that in olt-control mode). Then, by using the "VLAN+GMAC" index, the ONT duplicates the multicast data to the ONT ports in an as-per-requirement manner (only supports forwarding by using GMAC in snooping mode).

NOTE:

1. This forwarding mode applies to ASMSSM and ASM ONLY group filter modes (for details, see "Group Filter Mode").
2. The ONT that implements the third-level duplication is recommended to use the chip that supports VLAN+GIP forwarding. If the ONT does not use such a chip, program GIP-to-GMAC mapping must be a one-to-one mapping. Without the one-to-one mapping on the same ONT, garbled images will occur.

This topic describes only the forwarding framework in the most common single-copy duplication mechanism. For the hardware forwarding framework in the multi-copy duplication mechanism, see "GPON Multi-Copy Duplication."

GPON Multicast Forwarding Table (VLAN+GIP+SIP) [OLT]

Figure 2 GPON multicast forwarding table (VLAN+GIP+SIP)

The OLT supports a distributed 2+1-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GIP+SIP" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GIP+SIP" index, the service board duplicates multicast data to the GPON port interested in the multicast program in an as-per-requirement manner, effectively saving the downstream bandwidth of the GPON port. Then the service board encapsulates and transmits the multicast data on the GPON port in the mode of multicast GEM port (system-level parameter, configurable, default value 4095).
• The third-level duplication is implemented on the ONT. By using the "VLAN+GMAC" white list, the ONT filters out unneeded multicast data to avoid bandwidth overflow at the downstream ingress (ONT only supports that in olt-control mode). Then, by using the "VLAN+GMAC" index, the ONT duplicates the multicast data to the ONT ports in an as-per-requirement manner (only supports forwarding by using GMAC in snooping mode).

NOTE:

1. This forwarding mode applies to the SSM ONLY group filter mode.
2. Due to hardware limitations, only the difference in the least significant 20 bits can be differentiated between source IP addresses (SIPs). For example, 1.1.1.1 and 2.1.1.1 are the same SIP for the device; 1.1.1.1 and 1.1.1.2 are different SIPs for the device.
3. The ONT that implements the third-level duplication is recommended to use the chip that supports VLAN+GIP forwarding. If the ONT does not use such a chip, program GIP-to-GMAC mapping must be a one-to-one mapping. Without the one-to-one mapping on the same ONT, garbled images will occur.

Multicast Forwarding Table (VLAN+GMAC) [DSLAM]

Figure 3 DSLAM multicast forwarding table (VLAN+GMAC)

The DSLAM supports a distributed two-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GMAC" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GMAC" index, the service board duplicates multicast data to the multicast user (usually corresponding to the first port) interested in the multicast program in an as-per-requirement manner.

NOTE:

This forwarding mode applies to boards that do not support Layer 3 multicast forwarding chip.

Multicast Forwarding Table (VLAN+GIP) [DSLAM]

Figure 4 DSLAM multicast forwarding table (VLAN+GIP)

The DSLAM supports a distributed two-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GIP" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GIP" index, the service board duplicates multicast data to the multicast user (usually corresponding to the first port) interested in the multicast program in an as-per-requirement manner.

NOTE:

This forwarding mode applies to ASMSSM and ASM ONLY group filter modes.

Multicast Forwarding Table (VLAN+GIP+SIP) [DSLAM]

Figure 5 DSLAM multicast forwarding table (VLAN+GIP+SIP)

The DSLAM supports a distributed two-level duplication architecture:

• The first-level duplication is implemented on the control board. By using the "VLAN+GIP+SIP" index, the control board duplicates multicast data to the service board interested in the multicast program in an as-per-requirement manner, effectively saving the backplane bandwidth.
• The second-level duplication is implemented on the service board. By using the "VLAN+GIP+SIP" index, the service board duplicates multicast data to the multicast user (usually corresponding to the first port) interested in the multicast program in an as-per-requirement manner.

NOTE:

1. This forwarding mode applies to the SSM ONLY group filter mode.
2. Due to hardware limitations, only the difference in the least significant 20 bits can be differentiated between SIPs. For example, 1.1.1.1 and 2.1.1.1 are the same SIP for the device; 1.1.1.1 and 1.1.1.2 are different SIPs for the device.

More blog:

What’s the alarm on the OptiX OSN 1800II board restarts after power-off

Warning of Failed Cascading on the MA5616 Equipped with the JDSU GE Optical Module

How to Control Board Failure After an MxU Service Port Is Bound to a Rate Unlimited