Preview Tool

Cisco Bug: CSCtc68140 - IVR2: ivr switch stuck in advertisiing after upgrade

Last Modified

Jun 12, 2013

Products (1)

  • Cisco MDS 9000 Series Multilayer Switches

Known Affected Releases


Description (partial)

In large customer setup, the IVR switch was stuck in advertising shortly after a zoneset activation was received by IVR. the zoneset activation is completed but IVR is always stuck in advertising state.

In a large setup, issue a IVR zoneset activation request in one IVR switch. According to the activation sequence, this initiate switch could only start its local IVR zoneset activation after receiving all the peer switches' success response for this req. During the waiting period, some peer switch might already process the IVR zoneset activation request and start the corresponding regular zoneset activation in the fabric. So when the initiate switch received the peer switch's regular zoneset activation req, IVR in the initiate switch will start a pacing period for current active IVR zoneset members. During the pacing period, all the responses from peer switch reached and IVR started its local IVR zoneset activation. At this time the zone FSM state will become stuck at advertising state and cannot escape (because IVR will assume the regular zoneset activation never complete). From the implementation, we find the pacing period is not needed for regular zoneset activation (because there is no IVR zone member changes when receiving regular zoneset activation). So the fix is not to start the IVR pacing for regular zoneset activation

1. Created a dummy zone in the local zoneset and activated it on the switch that was stuck in the advertising state. this notified IVR and brought it out of the advertising state as the zoneset activation went through successfully 
after this to try and confirm that ivr zoneset activation worked successfully we added a dummy ivr zone and reactivated the ivr zone successfully
3. Upgrade to 4.2.3, 5.0.1 or higher version

Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.