Link Aggregation Status - Cisco ASR 5500 Administration Manual

Asr 5500 system administration guide, staros release 19
Table of Contents

Advertisement

Link Aggregation Status

Important
To achieve redundancy you must configure a second non-redundant LAG. You can use a higher layer load
balancing mechanisms such as ECMP (Equal Cost Multiple Path) routing to uniformly distribute the traffic
across two LAG groups.
When one MIO/UMIO fails, half the ports from both the LAG groups will be available for distribution of the
traffic from the other MIO/UMIO.
Figure 11: Non-Redundant LAG Configuration with ECMP
Configuring a second LAG group is not mandatory, but is the usual approach for achieving redundancy with
this mode of LAG.
However, if the aggregating ports are loaded with more than 50% of their capacity and an MIO/UMIO
failure/switchover occurs, the ASR 5500 configured port capacity is oversubscribed and an indeterminate
amount of sessions are dropped and traffic lost.
Link Aggregation Status
To check the status of link aggregation, use the following commands:
• show port table
• show port info slot/port
A single character is used to display LAG physical port status in the output of the show port table command.
See the table below.
Table 6: LAG Port Status
Display
LA+
LA-
LA~ (tilde)
LA*
ASR 5500 System Administration Guide, StarOS Release 19
60
With this mode operation, automatic ASR 5500 port redundancy is lost.
Description
Port is actively used for distributing (transmit nd recieve data).
Port failed to negotiate LACP.
Port negotiated LACP but another peer was selected.
Port is (re)negotiating LACP.
System Settings

Advertisement

Table of Contents
loading

Table of Contents