cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1099
Views
0
Helpful
2
Replies

different VEM state in same cluster

Hi,

I am currently upgrading the virtualisation environment. vCenter and VSM is updated and it's all running fine.

For upgrading the VEM's and the ESX's I moved some VM's to another ESX and the VM's lost connection. I found that the problem ist that one of my ESX doesn't get every Vlan and every PortProfile which is very strange.

As you can see with the vemcmd show dr command I am missing vlan100 on my second ESX. On my TestCluster I could fix this with deleting the vlan and recreate it, but i don't want to do this in this highly productive environment. So did anybody see this issue as well or do i have to fix this on a weekend?

!Log from my first ESX

N1000v# mod vem 3 execute vemcmd show dr

BD 1, vdc 1, vlan 1, 9 ports, DR 0, multi_uplinks TRUE

Portlist:

     16     vmnic0

     18     vmnic2

     19     vmnic3

     20     vmnic4

     21     vmnic5

     22     vmnic6

    304    

    305    

    306    

BD 100, vdc 1, vlan 100, 5 ports, DR 305, multi_uplinks TRUE

Portlist:

     20     vmnic4

     21     vmnic5

     58     ServerA.eth1

     79     ServerB.eth1

    305  DR

BD 106, vdc 1, vlan 106, 3 ports, DR 305, multi_uplinks TRUE

Portlist:

     20     vmnic4

     21     vmnic5

    305  DR

BD 300, vdc 1, vlan 300, 8 ports, DR 305, multi_uplinks TRUE

Portlist:

     20     vmnic4

     21     vmnic5

     51     ServerC.eth2

     52     ServerD.eth1

    305  DR

!Log from my second ESX

N1000v# mod vem 4 execute vemcmd show dr

BD 1, vdc 1, vlan 1, 9 ports, DR 0, multi_uplinks TRUE

Portlist:

     16     vmnic0

     18     vmnic2

     19     vmnic3

     20     vmnic4

     21     vmnic5

     22     vmnic6

    304    

    305    

    306    

BD 106, vdc 1, vlan 106, 3 ports, DR 306, multi_uplinks TRUE

Portlist:

     20     vmnic4

     21     vmnic5

    306  DR

BD 300, vdc 1, vlan 300, 3 ports, DR 306, multi_uplinks TRUE

Portlist:

     20     vmnic4

     21     vmnic5

    306  DR

2 Replies 2

Robert Burns
Cisco Employee
Cisco Employee

Chris,

Version of 1000v?

Version of ESX (affected host)?

From affected host "vemcmd show trunk"

Can you also paste (or send me privately) your running config.

Thanks,

Robert

Hi Robert,

Thanks for your reply. By now the problem is fixed. After upgrading both VSM somehow the vlans were faulty. I figured this out with the comparison of "show vlan" and "show system internal l2fm info detail". The system command didn't show every vlan therefore, the VEM didn't get every vlan they needed.

After a reload of the VSM and not just a reload of module 1 and module 2 the system command knew every vlan and after a vem restart it worked fine again.

This happend during upgrading from version 4.0(4)SV1(2) to version 4.0(4)SV1(3b).

Thanks,

Chris