Guest

Preview Tool

Cisco Bug: CSCur84178 - MPE node status went to critical during VOSM failover

Last Modified

Feb 26, 2015

Products (1)

  • Cisco Videoscape Media Gateways

Known Affected Releases

2.3

Description (partial)

Symptom:
Sometime after a primary MPE controller failover the MPE devices may not get registered to new MPE controller fast enough. The MPE application thinks that they have failed and it releases them to PAM with error.

Conditions:
When the primary MPE controller is brought down a switchover to standby MPE controller happens. All MPE devices are now registered to new MPE controller. It takes some time for them to be registered successfully.  However  sometimes a device may not get registered to the new MPE controller fast enough. The MPE application queries the MPE controller to see if any device has failed. In this particular case the MPE controller thinks the device is offline. After its regular failover checks and timing interval MPE application fails the device and releases it back to PAM with error. The device is actually operational but it just hasn't registered to the MPE controller.
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)
  • 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.