03-13-2012 07:30 PM
We have 2 nexus 5548UP running Layer 2. I have setup vPC between both nexus switches and have a few questions on how vPC failover works. Below is partial snippets of what I have configured for vPC,etc. During testing, I reload nx-1 and what I am seeing is that the vPC peer-link goes down as expected but all vpc port-channels are in a failed state on nx-2 until nx-1 is back online once vPC is formed and functioning everything looks good. I then reload nx-2 and the vPC port-channels go into fail state, etc. Am I missing something in my configuration?
NX-1
feature tacacs+
feature udld
feature lacp
feature vpc
feature fex
feature vtp
cfs eth distribute
no ip domain-lookup
vtp mode transparent
vpc domain 300
role priority 200
peer-keepalive destination 10.100.5.12 source 10.100.5.11
int po12
description NETAPPA
switchport mode trunk
vpc 12
switchport trunk allowed vlan 5,6,7,8
spanning-tree port type edge trunk
int po13
description NETAPPB
switchport mode trunk
vpc 13
switchport trunk allowed vlan 5,6,7,8
spanning-tree port type edge trunk
int po250
description nx-2
switchport mode trunk
vpc peer-link
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
spanning-tree port type network
int e1/27
description vpc peer link
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
channel-group 250 mode active
int e1/28
description vpc peer link
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
channel-group 250 mode active
int e1/1
description netappa:e1a
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
channel-group 12 mode active
int e1/2
description netappb:e1a
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
channel-group 13 mode active
NX-2
feature tacacs+
feature udld
feature lacp
feature vpc
feature fex
feature vtp
cfs eth distribute
no ip domain-lookup
vtp mode transparent
vpc domain 300
role priority 300
peer-keepalive destination 10.100.5.11 source 10.100.5.12
int po12
description NETAPPA
switchport mode trunk
vpc 12
switchport trunk allowed vlan 5,6,7,8
spanning-tree port type edge trunk
int po13
description NETAPPB
switchport mode trunk
vpc 13
switchport trunk allowed vlan 5,6,7,8
spanning-tree port type edge trunk
int po250
description nx-1
switchport mode trunk
vpc peer-link
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
spanning-tree port type network
int e1/27
description vpc peer link
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
channel-group 250 mode active
int e1/28
description vpc peer link
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
channel-group 250 mode active
int e1/1
description netappa:e1b
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
channel-group 12 mode active
int e1/2
description netappb:e1b
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 5,6,7,8
channel-group 13 mode active
Solved! Go to Solution.
03-14-2012 06:27 AM
What Nexus OS are you running.. You could be seeing this bug
03-14-2012 06:27 AM
What Nexus OS are you running.. You could be seeing this bug
03-14-2012 01:31 PM
I am running 5.1.3.N1.1. I just upgraded to the .1a NX-OS and this fixed it. Thank you for your support.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide