Guest

Preview Tool

Cisco Bug: CSCvu82645 - Need to document the procedure to reboot the LB VM with VIP to avoid side effects

Last Modified

Jul 06, 2020

Products (1)

  • Cisco Policy Suite for Mobile

Known Affected Releases

18.5.0

Description (partial)

Symptom:
After rebooting the LB VM with the VIP address(es), the DIAMETER connections supported by its QNS processes will be disconnected. The VIP address(es) will be migrated to the other LB VM and the DIAMETER connections will eventually be reestablished in the other LB VM but some DIAMETER connection alarms may get stuck.
After the connection drop, all the SNMP traps ?Gx is down? will be sent out. The diagnostics output will show all the alarms ?Gx is down?. 
After the reestablishment, some SNMP traps ?Gx is back up? may not be sent out. And the diagnostics output will keep showing some alarms ?Gx is down? (they get stuck there).

Conditions:
1. There are active DIAMETER connections
2. The target LB VM has the VIP address(es)
3. You reboot the LB VM with the VIP address(es)
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.