Guest

Preview Tool

Cisco Bug: CSCvs42587 - Disaster Recovery: vbond registering with secondary vmanage cluster after recovering from failure

Last Modified

Jan 25, 2020

Products (1)

  • Cisco SD-WAN

Known Affected Releases

19.2.99

Description (partial)

Symptom:
When failing primary manage along with one of the two vbonds. Disaster recovery fails over to secondary vmanage cluster correctly. Upon recovering the vbond, the vbond is registering with the now secondary cluster and distributing the secondary vmanage to edge devices causing issue where some edge devices are connecting to primary vmanage cluster and some are connecting to secondary vmanage cluster

Conditions:
When failing primary manage along with one of the two vbonds. Disaster recovery fails over to secondary vmanage cluster correctly. Upon recovering the vbond, the vbond is registering with the now secondary cluster and distributing the secondary vmanage to edge devices causing issue where some edge devices are connecting to primary vmanage cluster and some are connecting to secondary vmanage cluster
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.