VEM problem ? Dropping received frames

[born.jason]

Hi,

since december we have the nexus 1000v in our company. Everything working fine and looks good. We have a ESX cluster with two hosts and 7 NICs uplink. Today after a long time i have a look in the logging and saw this:

Dropping received frames from duplicate VSM - kernel

How could i get rid of this? This message flooding the logging.

Here is the configuration.....

sh ver:

Software
  loader:    version 1.2(2) [last: image booted through mgmt0]
  kickstart: version 4.0(4)SV1(1)
  system:    version 4.0(4)SV1(1)
  kickstart image file is:
  kickstart compile time:  4/2/2009 23:00:00
  system image file is:    bootflash:/nexus-1000v-mz.4.0.4.SV1.1.bin
  system compile time:     4/2/2009 23:00:00 [04/26/2009 13:27:23]

and here the uplink profiles and other profiles for service console and so on:

port-profile system-uplink
  capability uplink
  vmware port-group
  switchport mode trunk
  switchport trunk allowed vlan 2,51-52 (VLAN 2 is not in use at the moment)
  channel-group auto mode on sub-group cdp
  no shutdown
  system vlan 51-52
  state enabled

port-profile vm-uplink
  capability uplink
  vmware port-group
  switchport mode trunk
  switchport trunk allowed vlan 1,10,101-200
  channel-group auto mode on sub-group cdp
  no shutdown
  state enabled

port-profile nexus-control
  vmware port-group
  switchport mode access
  switchport access vlan 51
  no shutdown
  system vlan 51
  state enabled
port-profile nexus-packet
  vmware port-group
  switchport mode access
  switchport access vlan 52
  no shutdown
  system vlan 52
  state enabled

port-profile ServiceConsole
  vmware port-group
  switchport mode trunk
  switchport trunk allowed vlan 1-2 (maybe here ist the problem, this is configured from a guy before)
  no shutdown
  state enabled
port-profile VMotion
  vmware port-group
  switchport mode access
  switchport access vlan 10
  no shutdown
  state enabled

We have vlan 1 as the defaultvlan for office network, service console belongs to vlan 1 (Yes i know this is not good but at this time there is no other choice :-( )

On the uplink switch a port-channel is created with five ports for vm-uplink and another port-channel with two nics for system-uplink, which connected with the vmnic`s.

If i have to reconfigure some points please let me know if i can make this changes while the system is running.....

[lwatta]

You need VIB version 4.0.4.1.2.0.81-1.11.11 for that kernel version

Check out the campatibility guide here http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_2/compatibility/information/n1000v_compatibility.html

If you are having VUM problems make sure VUM is downloading the correct VIB versions and using the right repository for Cisco Nexus 1000V. It should be  using the following repository in VUM https://hostupdate.vmware.com/software/VUM/PRODUCTION/csco-main-index.xml

And check out this KB article that describes the problem

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013134

[born.jason]

I have the right source in VUM.

Where can i download the VIB i need?

[born.jason]

Ok, found the VIB but look:

The following problems were encountered trying to resolve dependencies:
   Requested VIB cross_cisco-vem-v110-esx_4.0.4.1.2.0.81-1.11.11 is already
   installed

[lwatta]

Sorry I have been sick the last few days.

So that looks ok.You have the right VEM module for the kernel loaded.  Does the VEM module show up on the VSM with show module?

louis

[born.jason]

Hi Louis,

hope you are fine now.

yes the VEM is up under "show module"

Maybe i have to try this -> https://communities.cisco.com/message/51333#51333

If i perform a rpm -qa | grep vem the following appears:

[root@server01 ~]# rpm -qa | grep vem
cisco-vem-v100-esx-4.0.4.1.1.31-1.11.11
cisco-vem-v100-esx-4.0.4.1.1.28-0.7.3
cisco-vem-v110-esx-4.0.4.1.2.0.81-1.11.11

[cdusio]

Ok I labbed this up and it works np..

Here's what you need to do.First, verify that the VSM (one you reinstalled) has the conrol, packet and management VLAN's correctly defined.

1. Change the secondary VSM to primary
   1. set systyem redundancy role primary
   2. copy run start
   3. reload
2. On the second VSM it probably just says (switch) at the command prompt...
   1. Make sure it is set to be secondary
   2. set system redundancy role secondary
3. Add in the domain id info.... for example
   
   1. svs-domain
        domain id 100
        control vlan 260
        packet vlan 261
        svs mode L2
4. copy run start
5. reload secondary VSM

When it comes up it shoule go into standby.. You should give the primary enough time to reboot before you do this.

lmk if this solves your issue.

-C