01-OptiX RTN 900 LAG Special Topic

OptiX RTN 900 LAG
Special Topic
www.huawei.com
Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:
 Master the basic concepts of LAG
 Master the features of LAG
 Master the basic configuration of LAG
Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved. Page1
Contents
1. Definition of LAG
2. Features of LAG
3. Cases of LAG fault analysis
4. Configuration Example of LAG
LAG Definition
 Link aggregation allows one or more links connected to the
same equipment to be aggregated to form a link
aggregation group (LAG). For MAC users, a LAG works as
a single link.
Purpose
 Increased bandwidth
 A LAG provides users with a cost-effective method for

increasing link bandwidth. Users obtain data links with higher
bandwidth by aggregating multiple physical links into one
logical link without upgrading the existing equipment. The
bandwidth provided by the logical link is equal to the total
bandwidth provided by the multiple physical links.
 Increased availability
 Members in a LAG provide dynamic backup for one another.

When a link fails, the other links in the LAG quickly take over.
LAG Establishment Process
 Exchanging LACPDUs Between Both Ends
 As shown in Figure,users need to create a static LAG on NE1
and NE2 and add member ports to the LAG. The member ports
are enabled with LACP, and therefore NE1 and NE2 can send
LACPDUs to each other.
LAG Establishment Process(Cont.)
 Determining the Actor
 As shown in Figure 2, devices at both ends receive LACPDUs

from each other. This section uses NE2 as an example. When
NE2 receives LACPDUs from NE1, NE2 checks and records
information about NE1 and compares system priorities. If the
system priority of NE1 is higher than that of NE2, NE1 acts as the
Actor.
LAG Establishment Process(Cont.)
 Selecting Active Ports
 As shown in Figure 3, after devices at both ends select the Actor,

both devices select active port based on the priorities of ports on
the Actor.
Types of Aggregation
 Manual aggregation
 In manual aggregation, a user creates a LAG; the link aggregation control
protocol (LACP) is not started.
 A port can be in the up or down state. The system determines whether to
aggregate a port according to its physical state (up or down), working
mode, and rate.
 Static aggregation
 In static aggregation, a user creates a LAG; the LACP is started.
 By running the LACP, a LAG determines the status of each member port.
A member port can be in the selected, standby, or unselected state.
 Static aggregation has more accurate and effective control over link
aggregation than manual aggregation.
Load Sharing Modes
 Load sharing mode
 Each member link in a LAG carries traffic. That is, the member links in
the LAG share the load. In load sharing mode, the bandwidth of the
link increases. When a member in a LAG changes or a certain link
fails, the traffic is re-allocated automatically.
Load Sharing Modes(Cont.)
 Load non-sharing mode
 Only one member link in a LAG carries traffic and the other
links in the LAG are in the standby state. This is equivalent to
the hot standby mechanism. This is because when an active
link in a LAG fails, the system selects a link among the standby
links in the LAG as an active link to replace the failed link.
Port Types
 Main port
 A main port represents the logical port aggregated by ports in a
LAG.
 Slave Port
 In a LAG, the ports except for the main port are slave ports.
LAG priority
 LAG priority includes system priority and port priority.
Priority setting allows negotiation of aggregation information
between LAGs at two ends and real-time maintenance on
link status.
 System priority
 Indicates the priority of a LAG.
 Port priority
 Indicates the priority of a port in a LAG.
Procedure of a LAG Switching
 In the case of a load non-sharing LAG, when the NE detects
that a certain port in the LAG is in the link down state or that
the conditions for triggering a LAG switching are met, the
following operations are performed:
 The faulty port at the local end is shut down.
 The link with highest priority among the backup links is

selected to replace the faulty link among the active links.
 The LACP packet is sent to the NE at the opposite end.
 According to the LACP packet, the NE at the opposite end

shuts down the corresponding port and switches the port.
Switching Conditions
Switching Condition Description
The Ethernet port is in the If the member port of a LAG is an Ethernet port and
link down state. is in the link down state, the ETH_LOS alarm is
reported.
The microwave port is in the If the member port of a LAG is a microwave port and
link down state. when the MW_LOF, MW_LIM, MW_BER_EXC, or
MW_BER_SD alarm is reported, the NE considers
that the microwave port is in the link down state and
then LAG switching is triggered.
NOTE:The MW_BER_SD alarm is an optional
condition.
A link failure is detected when If the protocol packets are not received for three
the LACP is run. consecutive periods (3s), the LACP considers that
the link is unavailable and then LAG switching is
triggered.
The port priority or system LAG switching occurs if the port priority or system
priority of a member port is priority of a member port is changed.
changed.
E-LAG
 E-LAG is a mechanism that implements multi-chassis link
aggregation using the Link Aggregation Control Protocol
(LACP). It enhances Ethernet link reliability from the port
level to the equipment level.
Contents
2. Features of LAG
LAG Application
 As shown in Figure, NE1 and NE2 are adjacent stations.
The Ethernet boards at the stations are connected to the
client equipment through four links. To increase link
capacity and improve link reliability, the four links are
aggregated as a LAG.
Availability
 Hardware Requirements on packet plane
Feature Name Board Type (Port Type)
LAG IFU2/IFX2/ISU2/ISX2/ISV3 (IF port)
EM6T/EM6F/EM6TA/EM6FA/EG4/EG4P(Ethernet
port)
EFP8 (PORT 10)
EMS6 (PORT 8)
 Hardware Requirements on EOP/EOS plane
Feature Name Board Type (Port Type)

LAG EFP8 (PORT 1 to PORT 8)
EFP8 (VCTRUNK 1 to VCTRUNK 16)
EMS6 (PORT 1 to PORT 6)
EMS6 (VCTRUNK 1 to VCTRUNK 8)
Specifications on packet plane
Item Specification
Maximum number of supported 20
LAGs
Type of supported ports in a LAG FE/GE port
Integrated IP radio port
Load sharing Sharing
Non-sharing
Number of slave ports in a LAG 7 (Sharing)
1 (Non-sharing)
LAG type Manual aggregation
Static aggregation
Load sharing type (only applicable Algorithm auto-sensing
to the load sharing mode)a Based on source MAC addresses
Based on destination MAC addresses
Based on source MAC addresses plus destination MAC
addresses
Based on source IP addresses
Based on destination IP addresses
Based on source IP addresses plus destination IP address
Based on MPLS labels
Revertive mode (in load non- Revertive
sharing mode only) Non-revertive
Specifications on EoP/EoS plane
Item Specifications
EFP8 EMS6
Maximum number of LAGs 12 8
Type of port in a LAG FE port FE/GE port
VCTRUNK VCTRUNK
Load sharing mode Load sharing

Load non-sharing
Maximum number of slave 7 (load sharing mode, FE 3 (load sharing mode, FE port)
ports port) 1 (load sharing mode, GE port)
7 (load sharing mode, VCTRUNK)
15 (load sharing mode,
1 (load non-sharing mode)
VCTRUNK)
1 (load non-sharing mode)
LAG type Manual aggregation
Static aggregation
Load sharing type IP address-based load sharing
(applicable only to the load MAC address-based load sharing
sharing mode)
Revertive mode (applicable Revertive
only to the load non-sharing Non-revertive
mode)
Feature Dependencies and
Limitations
 Self-limitations
Item Description
Member sharing A member cannot be configured in two LAGs.
NOTE:This limitation does not work for a manual load-
sharing LAG formed by two 1+1 HSB/FD/SD protection
groups.
IF port An IF port on the can be configured into a LAG for air
interfaces. The AM attribute, channel spacing, modulation
scheme, and preset number of E1s must be consistently
set for all IF ports in a LAG.
Ethernet port The rate must be consistently set for Ethernet ports in a
LAG.
Disabling port You can disable either the master port or the slave port in a
LAG.
DLAG configured using Only Ethernet ports with the same rate on the following
Ethernet ports boards can be configured into a distributed link
aggregation group (DLAG)
Feature Dependencies and Limitations(Cont.)
 Limitations Between LAG and Other Features
Feature Description
1+1 HSB, 1+1 FD, and 1+1 When a 1+1 HSB, 1+1 FD, or 1+1 SD protection group is
SD being created for an Integrated IP radio link on an NE, the
NE automatically creates a non-load sharing LAG. This LAG
can neither be displayed on the NMS nor be configured
manually.
N+1 protection When a standard N+1 protection group is being created for
an Integrated IP radio link on an NE, the NE automatically
creates a load-sharing LAG. This LAG can neither be
displayed on the NMS nor be configured manually.
IGMP Snooping A LAG member can be a member of an Internet Group
Management Protocol (IGMP) Snooping multicast group.
MSTP A LAG member can be a member of an MSTP port group.
Layer 2 switching A LAG can function as a logical port that is mounted to a
bridge.
A LAG can be a member of an IGMP Snooping multicast
group.
STP/RSTP A LAG can function as a logical port of a bridge to participate
in the spanning tree computation.
PLA A LAG conflicts with the PLA
Contents
2. Features of LAG
Case1:LAG sharing fails
 Problem Description
 When enabling LAG on an XPIC link, by using sharing between
V and H polarizations. Only the H polarization was carrying the
traffic.
LAG
site A site B
Case1:LAG sharing fails (Cont.)
 Handling procedure
 Check LAG configuration: LAG configuration was checked
from both sites, and both sites have the correct configuration.
 Check capacity license on all ports: the capacity license for

all ports was the same and was correct.
 Check the load sharing algorithm: after all above steps were
checked, the LAG load sharing algorithm was checked. And we
found that one site was making sharing according to IPaddress
and the other site was making automatic sharing.
Case1:LAG sharing fails (Cont.)
 Root Cause
 After making the above troubleshooting steps, it was clear that
the cause of the problem was due to misconfiguration between
the two, since each site is using different sharing algorithm.
 Solution
 After the cause was clear, the LAG algorithm was changed
from site B, to make both site’s sharing algorithm the same
“source and destination IP address”
Case2:RTN LAG fail
 when configuring LAG between RTN and PTN, the LAG is always
fail.
 Using Manual+revertive+no-sharing.
 when deploy the configuration: RTN 22-1 and PTN 5-1 in

service,the service is outage.
22-1 6-1
22-2 5-1
RTN
LAG PTN
Case2:RTN LAG fail (Cont.)
 Handling Process
 Change the connection of the board like 22-1 to 5-1 and 22-2
to 6-1 the service is normal
 Change the connection like 22-1 to 6-1 and 22-2 to 5-1 and set
the 22-1 and 6-1 as high port priority the service is fail
 Disable the 5-1 port at PTN side and deploy the service is
normal at begin but after the WTR the service is outage again.
Case2:RTN LAG fail (Cont.)
 Root Cause
 when deploy the LAG between the RTN and PTN，and use
the model of Mannual+revertive+no-sharing ,no matter how
you set the port priority the service will auto select the small
port number !
 if you connect the small RTN port number with the large PTN
port number which means the service will always outage
Case3:Wrong parameter lead to LAG
configuration failure
 XXX customer feedback a failure faced when creating LAG on main

board of 2 microwave 1+1 protection group, NMS U2000 report "The
resource has been occupied".
configuration failure (Cont.)
 Product document confirm that this
version(RTN900V1R5C00SPC100) support configure LAG on
main board of 2 microwave 1+1 protection group.
 Check the service configuration on main and standby port of
microwave 1+1 group, no service configured.
 Check the QoS configuration on main and standby port of
microwave 1+1 group, only default QoS policy there.
 Check each port attributes, all attributes are default value.
 Check the parameter of LAG, found that the LAG set to manual +
non-sharing, which is not correct and result in configuration failure.
configuration failure (Cont.)
 Root Cause
 From version RTN900V1R5C00SPC100, RTN could deploy
LAG on main board of 2 microwave 1+1 protection group, but
the parameter of LAG is restirct, only manual + sharing LAG
allowed.
 Solution
 In case of making up of LAG with main board of 2 microwave
1+1 protection group, the LAG attribute must be manual and
sharing.
Case4：Transmission LAG cause
packet drop
 All traffic are carried by fiber link, the microwave work as
standby. When fiber link is down, the traffic shift to microwave
links
LAG LAG
LAG
NE40E1 NE40E2
site B
site A
packet drop (Cont.)
 Check the route in 2 PE NE40E , they have the route to each
other.
 Check BGP, BFD, IGP in PE, all protocol are normal.
 Doubt the Microwave link has some issue. test the connectivity
of NE40E1-NE40E2, find NE40E1 cannot ping NE40E2.
 Deploy policy to do statistic test, find PE1 can send out packet,
but NE40E2 cannot receive these ICPM packet. doubt
microwave link discard some packet.
packet drop (Cont.)
 Root Cause
 Only some packets are discarded by Microwave link in
transmission side.
 If LAG is deployed in microwave side as redundancy, any

member link is down , it will cause certainly IP packet is
dropped. Because LAG base on harsh algorithm, some
certain IP choice certainly one link, other choice other link
according to base harsh algorithm.
Case5：The lag configuration failure
due to the diferent port mode
 W country and C project, the front line engineer feedback
failure of lag configuration.
due to the diferent port mode (Cont.)
 Possible causes:
 Parameter of the lag is faulty
 MPLS status of the port in the lag is different
 Other attribute of main and slave port is different
due to the diferent port mode (Cont.)
 As in the picture, the port is changed to Layer 3,the lag main port
(10-isx2-1) and slave port (9-isx2-1) have different MPLS status.
And this lead to the lag configuration failure.
Contents
2. Features of LAG
Networking Diagram
 As shown in Figure , the Hybrid radio link between NE1 and
NE2 adopts the 2+0 non-protection scheme. Hence,
the Integrated IP radio ports that correspond to the radio link
need to be configured as a load-sharing LAG.
Data Preparation
Item Value in This Planning Principle
Example
Static (default value) Configure the same aggregation type at both ends. Static
LAG type aggregation is recommended.
Load sharing Non-Sharing Configure the same load sharing mode at both ends. Configure
mode a load non-sharing LAG to provide protection, and a load
sharing LAG to increase bandwidth.
Revertive Revertive If the OptiX RTN 900 and OptiX equipment are interconnected
Mode to form a load non-sharing LAG, it is recommended that the
LAG be set to revertive and the WTR time take the default
value.
If the OptiX RTN 900 and another type of equipment are
interconnected to form a load non-sharing LAG, it is
recommended that the LAG be set to non-revertive.
System 32768 (default The default value is recommended. The system priority can be
priority value) set only in static aggregation.
Master and Master port: 3-ISU2- It is recommended that you set the main and slave ports
slave ports 1 consistently for the equipment at both ends.
Slave port: 5-ISU2-1
Switching Enable It is recommended that you enable this function when a LAG is
upon air configured at air interfaces.
interface SD
Creating a LAG
Setting LAG Parameters
Querying the Protocol Information of
the LAG
Relevant Alarms-LAG_BWMM
Description LAG_BWMM is an alarm indicating the bandwidth inconsistency in the LAG group.
Alarm
Major
Severity
Parameters None
Impact on the
For a LAG group in load-sharing mode, data services may be lost.
System
Possible
Cause : In the LAG group, the license capacities of the ports differ from each other.
Causes
Relevant Alarms-LAG_DOWN
The LAG_DOWN alarm indicates that a link aggregation group (LAG) is unavailable.
Description
This alarm is reported when the number of activated members in a LAG is 0.
Alarm
Major
Severity
Parameters None
Impact on the
Services are interrupted.
System
Possible Cause 1: The opposite NE is not configured with any LAGs.

Causes Cause 2: All member ports in the LAG are unavailable.
Relevant Alarms-
LAG_MEMBER_DOWN
The LAG_MEMBER_DOWN alarm indicates that a member port in the link aggregation
Description group (LAG) is unavailable. This alarm is reported when a member port cannot be
activated and cannot work as the backup port
Alarm
Minor
Severity
Parameter 1, Parameter 2 indicates the board ID; Parameter 3 indicates the sub-board
Parameters ID ; Parameter 4, Parameter 5 indicates the port ID. Parameter 6 indicates the cause
that makes the port unavailable.
Impact on the In load-sharing mode, packet loss may occur continuously due to bandwidth insufficiency.
System In load non-sharing mode, link switching is triggered and packet loss occurs temporarily.
Cause 1: The port is unavailable or is disabled.

Possible Cause 2: The port receives no LACP packet.
Causes Cause 3: The port works in half-duplex mode.
Cause 4: The port is looped back.
Relevant Alarms-LAG_PORT_FAIL
The LAG_PORT_FAIL is an alarm indicating that a port in the LAG fails. When a port in
Description
the LAG is unavailable, the LAG_PORT_FAIL alarm is reported.
Alarm
Minor
Severity
Parameter 1:Indicates the number of the IP port.
Parameter 2, Parameter 3:The values are always 0x00 0x01.
Parameters
Parameter 4:Indicates the cause of the protection failure.
Parameter 5:The value is always 0xff.
Impact on the The port in the LAG cannot share the service load, and the port does not transmit or
System receive any services.
Cause 1: The port is disabled or the link is faulty.

Cause 2: The port is in the half-duplex mode.
Possible
Cause 3: The port fails to receive the LCAP packets.
Causes
Cause 4: The port detects a selfloop.
Cause 5: other unknown reasons.
Relevant Alarms-
LAG_VC_PORT_FAIL
The LAG_VC_PORT_FAIL is an alarm indicating that a VCG port in the LAG fails. When
Description
the VCTRUNK is unavailable, the alarm is reported.
Alarm
Minor
Severity
Parameter 1:The value is always 0x01.
Parameter 2, Parameter 3:Indicate the number of the faulty VCG port in the LAG.
Parameter 2 indicates the most significant bits and Parameter 3 indicates the least
Parameters
significant bits.
Parameter 4:Indicates the cause of the protection failure.
Parameter 5:The value is always 0xff.
Impact on the The port in the LAG cannot share the service load, and the port does not transmit or
System receive any services.
Cause 1: The link of the port is faulty or fails.

Possible Cause 2: The port fails to receive the LCAP packets.
Causes Cause 3: The port detects a selfloop.
Cause 4: other unknown reasons
Question
 What’s the function of LAG?
Summary
 Definition of LAG
 Features of LAG
 Configuration Example of LAG
Thank you
www.huawei.com

01-OptiX RTN 900 LAG Special Topic

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

01-OptiX RTN 900 LAG Special Topic

Hochgeladen von

Copyright:

Verfügbare Formate

OptiX RTN 900 LAG

Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved.

 Master the basic concepts of LAG

 Master the features of LAG

 Master the basic configuration of LAG

3. Cases of LAG fault analysis

4. Configuration Example of LAG

 A LAG provides users with a cost-effective method for

 Members in a LAG provide dynamic backup for one another.

 As shown in Figure 2, devices at both ends receive LACPDUs

 As shown in Figure 3, after devices at both ends select the Actor,

 The link with highest priority among the backup links is

 The LACP packet is sent to the NE at the opposite end.

 According to the LACP packet, the NE at the opposite end

3. Cases of LAG fault analysis

4. Configuration Example of LAG

 Hardware Requirements on EOP/EOS plane

Feature Name Board Type (Port Type)

Load sharing mode Load sharing

3. Cases of LAG fault analysis

4. Configuration Example of LAG

 Check capacity license on all ports: the capacity license for

 when deploy the configuration: RTN 22-1 and PTN 5-1 in

 XXX customer feedback a failure faced when creating LAG on main

 Check BGP, BFD, IGP in PE, all protocol are normal.

 If LAG is deployed in microwave side as redundancy, any

 MPLS status of the port in the lag is different

 Other attribute of main and slave port is different

3. Cases of LAG fault analysis

4. Configuration Example of LAG

Possible Cause 1: The opposite NE is not configured with any LAGs.

Cause 1: The port is unavailable or is disabled.

Cause 1: The port is disabled or the link is faulty.

Cause 1: The link of the port is faulty or fails.

 Configuration Example of LAG

Das könnte Ihnen auch gefallen