cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
14409
Views
4
Helpful
3
Replies

vm n1kv connectivity

pareshmistry
Level 1
Level 1

We have 5 uplink port channels with 2 nic each with UCS.

We were originally receiving the below error msg.

2014 Apr  4 15:53:22.780 GW-VBK1-ENT-NX1000 %VEM_MGR-SLOT8-2-VEM_SYSLOG_CRIT: VLAN_MISCONFIG : Po27 and Po26 are carrying vlans [3208-3209]. Configure a port-channel on a port-profile carrying multiple uplinks on the same VEM to avoid network loops. (Ignore if any of these ports are configured as local SPAN destination)

Noticed that 2 uplink profiles were trunking the same system vlans (control & packet) so we fixed this by removing the system vlans from the other uplink profile.

This fixed the above error msg from popping up and we don't see this error msg.

Although the issue has again popped where we see the below BLK ports/vlans on the vem;

WDC-VBK1-CTC-NX1000# module vem 5 execute vemcmd show port vlans
                          Native  VLAN   Allowed
  LTL   VSM Port  Mode    VLAN    State* Vlans
   17     Eth5/1   A          1   BLK    1
   18     Eth5/2   A          1   BLK    1
   19     Eth5/3   A          1   BLK    1
   20     Eth5/4   A          1   BLK    1
   21     Eth5/5   A          1   BLK    1
   22     Eth5/6   A          1   BLK    1
   23     Eth5/7   T          1   FWD    3204,3208-3209
   24     Eth5/8   T          1   FWD    3204,3208-3209
   25     Eth5/9   T          1   FWD    3205
   26    Eth5/10   T          1   FWD    3205
   49      Veth5   A       3204   FWD    3204
   50      Veth6   A       3205   FWD    3205
  561       Po63   T          1   FWD    3205

* VLAN State: VLAN State represents the state of allowed vlans.
WDC-VBK1-CTC-NX1000#

Any tips/cmds to check what might be causing the issue?

Thx

3 Replies 3

Joe LeBlanc
Cisco Employee
Cisco Employee

Hi Paresh,

What is the version?

Can you paste the running config of the type ethernet port-profiles?

Nexus1000v# sh run |beg "type eth"

Thanks,

Joe

This is now fixed. The root cause was two uplink profiles trunking the same control and packet vlans. Not sure why it popped up after the change but it's not appeared anymore after a reboot of the vem affected as well as the supervisor switchover.

Thanks for updating the thread Paresh!

Review Cisco Networking for a $25 gift card