Cisco Asr 9000 Series Aggregation Services Router Interface And Hardware Component Command Reference - Cisco ASR 9000 Series Command Reference Manual

Link Bundling Commands on the Cisco ASR 9000 Series Router
Reason
Link is Standby due to maximum-active links
configuration
Link is waiting for BFD session to start
Loopback: Actor and Partner have the same System
ID and Key
Not enough links available to meet minimum-active
threshold
Partner has marked the link as Not Aggregatable
Partner has not advertised that it is Collecting
Partner has not echoed the correct parameters for this
link
Partner is not Synchronized (Waiting, not Selected,
or out-of-date)
Partner is not Synchronized (Waiting, Standby, or
LAG ID mismatch)

Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Command Reference,

Description
The link is in Standby state because the number of
links in Selected state has already reached the
configured maximum active links threshold.
The link is in BFD Running state because LACP is
negotiated but the BFD session has not started from
the remote device.
The link is in Configured state because a loopback
condition has been detected on the link—two links
configured to be members of the bundle are actually
connected to each other.
The link is in Standby state because there are not
enough selectable links (i.e. links which meet the
criteria to be marked Selected within the bundle) to
meet the minimum active links/bandwidth threshold.
The link is in Configured state because it is marked
as an Individual link by the LACP partner device.
The link is in Negotiating state because the LACP
partner device has not advertised that the link is in
Collecting state in its LACPDUs.
The link is in Negotiating state because the LACP
partner device has not correctly echoed the local
system's port information in the LACPDUs it is
sending.
The link is in Negotiating state because the mLACP
peer PoA has not indicated that its LACP partner
device is Synchronized. This could be because the
devices are genuinely not Synchronized or because
this state has not been communicated to the local
system.
The link is in Negotiating state because the LACP
partner device has not indicated that it is
Synchronized in the LACPDUs it is sending. On the
partner device the link could still be waiting for the
Wait-While timer to expire, it could be held in
Standby state, or there could be a misconfiguration
leading to a LAG ID mismatch between links
configured to be within the same bundle.
show bundle
Release 5.3.x
633