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

show bundle
Reason
Link is Attached and has not gone Collecting (reason
unknown)
Link is Collecting and has not gone Distributing
(reason unknown)
Link is being removed from the bundle
Link is Defaulted; LACPDUs are not being received
from the partner
Link is down
Link is Expired; LACPDUs are not being received
from the partner
Link is in the process of being created
Link is marked as Standby by mLACP peer
Link is Not Aggregatable (reason unknown)
Link is not operational as a result of mLACP
negotiations
Link is Standby; bundle has more links than are
supported

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

Release 5.3.x
632
Link Bundling Commands on the Cisco ASR 9000 Series Router
Description
The link is in Negotiating state because the mLACP
peer PoA has not indicated that the link has gone
Collecting in the Mux machine. This could be because
of an issue between the mLACP peer and its LACP
partner or because this state has not been
communicated to the local system.
The link is in Negotiating state because the mLACP
peer PoA has not indicated that the link has gone
Distributing in the Mux machine. This could be
because of an issue between the mLACP peer and its
LACP partner or because this state has not been
communicated to the local system.
The link is being removed from the bundle and
remains in Configured state while this happens.
The link is in Configured state because no LACPDUs
are being received from the LACP partner device.
Either the partner is not transmitting or the packets
are getting lost.
The link is in Configured state because it is
operationally or administratively down.
The link is in Negotiating state because no LACPDUs
have been received from the LACP Partner device in
the Current-While period and the link is now marked
as Expired in the Receive machine.
The link is in Configured state because the member
configuration is still being processed.
The link is in Standby state because this has been
indicated by the mLACP peer PoA.
The link is in Configured state because it is marked
as an Individual link by the mLACP peer PoA.
mLACP negotiations with the peer have led to this
link being kept in Configured state. This is likely to
indicate a misconfiguration between the two peer
devices.
The link is in Standby state because the number of
links in Selected state has already reached the hard
platform limit on the number of active links.