Cisco Bug: CSCum47601 - interface stuck in Negotiating state during mlacp switchover cli command
Mar 07, 2018
- Cisco 7600 Series Routers
Known Affected Releases
Symptom: One of the links takes approx 80-90 seconds to transition from STANDBY to ACTIVE when "mlacp switchover bundle-etherx" is performed. Evidence: RP/0/RSP0/CPU0:ar13.ptlelab#sh bundle bundle-e 15 Port Device State Port ID B/W, kbps -------------------- --------------- ----------- -------------- ---------- Gi0/0/0/10 Local Standby 0x016e, 0xa005 1000000 mLACP peer is active Gi0/0/0/11 Local Standby 0x016e, 0xa006 1000000 mLACP peer is active Gi0/0/0/10 22.214.171.124 Active 0x016d, 0x9004 1000000 Link is Active Gi0/0/0/11 126.96.36.199 Negotiating 0x016d, 0x9005 1000000 Partner is not Synchronized (Waiting, not Selected, or out-of-date) <<<<<< Issue Conditions: Only when we cli command "mlacp switchover bundle-etherx" Other methods of failover scenarios mentioned below, there are no issues. 1. Link Failure: The member can be removed from the bundle using any of the following events: Fiber pull at either end of the POA-DHD link. (NB: This is the most representative way of testing this scenario.) Shut down the POA-DHD link on the DHD. Shut down the POA-DHD link on the POA. Remove the bundle membership configuration on either end of the POA-DHD link. 2. Device Failure: This represents a meltdown of the router carrying the traffic; total loss of the node. The only valid test trigger for this event is a hard reset (power down) of the device, even a router reload is not truly representative as the device will tend to go down in a series of indeterminate stages.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases