split brain 1000v

[Dragomir]

I think I have a pair of 1000v that are not connected anymore together, one does not recognize the other

one should be active and one should be secondary

sh system redundancy status

Redundancy role

---------------

      administrative:   secondary

         operational:   secondary

Redundancy mode

---------------

      administrative:   HA

         operational:   None

This supervisor (sup-2)

-----------------------

    Redundancy state:   Active

    Supervisor state:   Active

      Internal state:   Active with no standby               

Other supervisor (sup-1)

------------------------

    Redundancy state:   Not present

Mod     Status          UUID                                    License Status

---     -----------     ------------------------------------    --------------

3       absent          c6456f3e-2aa1-11e2-1100-00000000002f    licensed

4       absent          c6456f3e-2aa1-11e2-1100-00000000000e    licensed

5       absent          c6456f3e-2aa1-11e2-1100-00000000003e    licensed

6       powered-up      c6456f3e-2aa1-11e2-1100-00000000005d    licensed

7       powered-up      c6456f3e-2aa1-11e2-1100-00000000002d    licensed

8       powered-up      c6456f3e-2aa1-11e2-1100-00000000003d    licensed

9       powered-up      c6456f3e-2aa1-11e2-1100-00000000004f    licensed

10      powered-up      c6456f3e-2aa1-11e2-1100-00000000003f    licensed

11      powered-up      c6456f3e-2aa1-11e2-1100-00000000000f    licensed

12      powered-up      c6456f3e-2aa1-11e2-1100-00000000001f    licensed

13      powered-up      c6456f3e-2aa1-11e2-1100-00000000004e    licensed

14      powered-up      3e6f45c6-a12a-e211-1100-00000000000e    licensed

15      powered-up      3e6f45c6-a12a-e211-1100-00000000003e    licensed

In vsphere, The 1000v dvs keeps keeping reconfiguing distributed switch tasks on the 1000v

any idea?

[Joe LeBlanc · Accepted solution]

Hi Tony,

It looks like this VSM is secondary. You need to go to the console window of the other VSM VM and verify the system redundancy role with 'show system redundancy status'. My guess is that the other VSM is configured for 'Standalone' and we need to change the role to 'Primary' in order for the VSMs to pair.

Once we reconfigure the other VSM as primary, the two VSMs should see each other (given they have L2 connectivity)

Nexus1000v# show system redundancy status
Redundancy role
---------------
      administrative:  standalone
        operational:  standalone

Redundancy mode
---------------
      administrative:  HA
        operational:  None

This supervisor (sup-1)
-----------------------
    Redundancy state:  Active
    Supervisor state:  Active
      Internal state:  Active with no standby

Other supervisor (sup-2)
------------------------
    Redundancy state:  Not present
Nexus1000v# con
Nexus1000v(config)# system redundancy role primary

After this change, the VSMs will negotiate and the secondary will reboot. When the secondary comes back up, we should see that they have paired.

Nexus1000v(config)# show redundancy status
Redundancy role
---------------
      administrative:  primary
        operational:  primary

Redundancy mode
---------------
      administrative:  HA
        operational:  HA

This supervisor (sup-1)
-----------------------
    Redundancy state:  Active
    Supervisor state:  Active
      Internal state:  Active with HA standby

HTH,

Joe