Guest

Preview Tool

Cisco Bug: CSCur39065 - DAO.1: "DVS: Not connected" on restart of vCenter or VC crash

Last Modified

Mar 19, 2018

Products (1)

  • Cisco Nexus 1000V Switch for VMware vSphere

Known Affected Releases

5.2(1)AJ(1.0.669) 5.2(1)SV3(1.1.57)

Description (partial)

Symptom:
"sh vmware vem upgrade status" command shows the ouput as "DVS: Not connected" in the VSM.

Conditions:
If the VSM and DVS bundle ID are in mixed mode like below, then an restart or crash of vCenter leads to  "DVS: Not connected" state. In this state any new configuration will not pushed to vCenter and also upgrade of VEM using VUM cannot be done.

Before vCenter restart/crash: VSM and VEM are in mixed mode:
Upgrade Bundle ID:
    VSM: VEM500-201410171177-BG
    DVS: VEM500-201408170101-BG
After vCenter restart/crash:
Upgrade Bundle ID:
    VSM: VEM500-201410171177-BG
    DVS: Not connected

So follow the workaround mentioned below.
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.