Role Priority in VCP
i want to ask why we use role priority in vcp. do we achive load balancing for access layers switches in below scenario? or have to configure HSRP or GLPB?
As far as I know, therre is no such feature.
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
Similar Messages
-
Influence the sequence of Roles in IllumLoginRoles
Hi all,
is there a possibility to influence the sequence in which MII orders the roles which are assigned to a user?
For example, user A has roles IllumLoginRoles="'SAP_JAVA_NWADMIN_LOCAL','XMII Administrators','XMII Users', 'My new Role' ". How can I manage to get the role 'My new Role' to be the first role in the list?
This is important, because the Content Display Tabs on the MII Portal are displayed in the sequence of the roles in the IllumLoginRoles list. And the first Content Display Tab is loaded on login. So if I want the Content Tab of role 'My new Role' to be loaded when user A logs in, it must be the first role in the list.
I think it doesn't matter when the role was created, and surely the roles are not ordered by name.
Michael
Edited by: Michael Otto on Nov 4, 2008 9:15 AMMichael,
The order of your role names has no bearing on how it is showed in the Content Display Tabs or Navigation Items. Under System Management -> Custom Attribute Mapping -> Roles Tab, there is an option for priority. The lowest number has the highest priority so most likely XMII_Administrators would have a priority of '0' and XMII_Users would have one of '100'.
Content tabs are added, modified, and deleted in a similar manner to the navigation tree items. The tab item hierarchy is one dimensional. Tabs may be ordered within a user or role. Tabs are inherited from the user level first and then the role level. The order of inherited roles is determined by the role priority. The user's first tab, whether it be from the user or role level becomes the default home page in the main content area. The target window radio buttons behave the same way as the navigation tree items.
When the attributes are read, roles are added lowest priority to highest priority. Profile properties can be created at the role or the user level. A user will inherit properties from the roles that they are a member of. If more than one role has the same property name, the role with the highest priority will pass its property value to the user. If the user has the same property name defined in their profile, the user value always takes precedence. -
Hello team ,this is my requirement .. Through customizing..
When call center Team creates Service Request/Service Order/ Complaints it should be set as High Priority by default...we need to set only interaction agent bussiness role priority only HIGH..only for this bussiness role.through customizing how to do it..what are the steps..through customizing only please.. helpBy customizing, you can set a default priority to a given transaction type.
But this does not depend on the business role.
But as you are talking about IC agents, maybe you can check IDI for this purpose, because there are actions like "Set Problem Priority", "Set Service Request Priority" or "Set Service Order Priority".
Best regards,
Sylvain AGUETTAZ -
Nexus 4001i and MST tons of log errors
Went looking through my Nexus 4001i logs today, and started noticing a bunch of STP role and port change messages:
2013 Jul 5 14:40:31 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/1 instance MST0000 role changed to designated
2013 Jul 5 14:40:31 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port port-channel2 instance MST0000 role changed to alternate
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port port-channel1 instance MST0000 role changed to root
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/14 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/14 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/13 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/13 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/12 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/12 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/11 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/11 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/10 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/10 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/9 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/9 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/8 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/8 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/7 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/7 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/6 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/6 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/5 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/5 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/4 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/4 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/3 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/3 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/2 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/2 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/1 removed as MST Boundary port
After going through a variety of configuration validations, spanning-tree root and priority validations as well as making sure the instances and revisions between the various MST speaking switches (all of the Nexus gear including Nexus 5596 which are vPC peers, 4001i's which connect via vPC's to the 5596's, and Catalyst 3110X's which also use MST, but only have one uplink at this time to the 5596's not in a vPC setup).
None of the other devices appear to be experiencing this problem.
I am quite confused as to what is going on, and cannot figure out why the 4001i is wigging out like this.
A quick output of MST::
N4k-SLOT7-SW1# show spanning-tree mst
##### MST0 vlans mapped: 801-3109,3111-4094
Bridge address 6073.5c8d.7e82 priority 24576 (24576 sysid 0)
Root address 0023.04ee.be03 priority 16384 (16384 sysid 0)
port Po1 path cost 0
Regional Root address 0023.04ee.be03 priority 16384 (16384 sysid 0)
internal cost 500 rem hops 19
Operational hello time 2 , forward delay 15, max age 20, txholdcount 6
Configured hello time 2 , forward delay 15, max age 20, max hops 20
Interface Role Sts Cost Prio.Nbr Type
Po1 Root FWD 500 32.4096 P2p
Po2 Altn BLK 1000 64.4097 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
##### MST1 vlans mapped: 2-499,600-800,3110
Bridge address 6073.5c8d.7e82 priority 24577 (24576 sysid 1)
Root address 0023.04ee.be03 priority 16385 (16384 sysid 1)
port Po1 cost 500 rem hops 19
Interface Role Sts Cost Prio.Nbr Type
Po1 Root FWD 500 128.4096 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
##### MST2 vlans mapped: 1,500-599
Bridge address 6073.5c8d.7e82 priority 24578 (24576 sysid 2)
Root address 0023.04ee.be03 priority 16386 (16384 sysid 2)
port Po2 cost 1000 rem hops 19
Interface Role Sts Cost Prio.Nbr Type
Po2 Root FWD 1000 128.4097 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
N4k-SLOT7-SW1# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3:48:09 ago
from port-channel1
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3:48:07 ago
from port-channel1
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3:48:07 ago
from port-channel2
(topology change was due to testing rapid-PVST for this switch, and then putting it back, the previous change occured 555 hours ago).
N4k-SLOT9-SW2# show spanning-tree
MST0000
Spanning tree enabled protocol mstp
Root ID Priority 16384
Address 0023.04ee.be03
Cost 0
Port 4096 (port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 24576 (priority 24576 sys-id-ext 0)
Address 2c54.2ded.b704
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Root FWD 500 128.4096 P2p
Po2 Altn BLK 1000 128.4097 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
MST0001
Spanning tree enabled protocol mstp
Root ID Priority 16385
Address 0023.04ee.be03
Cost 500
Port 4096 (port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 24577 (priority 24576 sys-id-ext 1)
Address 2c54.2ded.b704
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Root FWD 500 128.4096 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
MST0002
Spanning tree enabled protocol mstp
Root ID Priority 16386
Address 0023.04ee.be03
Cost 1000
Port 4097 (port-channel2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 24578 (priority 24576 sys-id-ext 2)
Address 2c54.2ded.b704
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po2 Root FWD 1000 128.4097 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
N4k-SLOT9-SW2# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 18758 last change occurred 4:01:03 ago
from port-channel1
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 45742 last change occurred 4:01:02 ago
from port-channel1
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 21007 last change occurred 599:47:47 ago
from port-channel2
N4k-SLOT9-SW2#
N5596-DC-SW1# show spanning-tree
MST0000
Spanning tree enabled protocol mstp
Root ID Priority 16384
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16384 (priority 16384 sys-id-ext 0)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Desg FWD 1000 128.4096 P2p
Po2 Desg FWD 200 128.4097 (vPC) P2p
Po3 Desg FWD 200 128.4098 (vPC) P2p
Po57 Desg FWD 200 128.4152 (vPC) P2p
Po100 Desg FWD 1000 128.4195 (vPC peer-link) Network P2p
Eth1/15 Desg FWD 2000 128.143 Edge P2p
Eth1/16 Desg FWD 2000 128.144 Edge P2p
MST0001
Spanning tree enabled protocol mstp
Root ID Priority 16385
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16385 (priority 16384 sys-id-ext 1)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po2 Desg FWD 200 128.4097 (vPC) P2p
Po3 Desg FWD 200 128.4098 (vPC) P2p
Po57 Desg FWD 200 128.4152 (vPC) P2p
Po100 Desg FWD 1000 128.4195 (vPC peer-link) Network P2p
MST0002
Spanning tree enabled protocol mstp
Root ID Priority 16386
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16386 (priority 16384 sys-id-ext 2)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Desg FWD 1000 128.4096 P2p
Eth1/15 Desg FWD 2000 128.143 Edge P2p
Eth1/16 Desg FWD 2000 128.144 Edge P2p
N5596-DC-SW1# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 44578 last change occurred 4:11:57 ago
from port-channel2
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 98707 last change occurred 4:11:55 ago
from port-channel2
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 4 last change occurred 4:11:55 ago
from port-channel1
N5596-DC-SW2# show spanning-tree
MST0000
Spanning tree enabled protocol mstp
Root ID Priority 16384
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16384 (priority 16384 sys-id-ext 0)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Desg FWD 1000 128.4096 P2p
Po2 Desg FWD 200 128.4097 (vPC) P2p
Po3 Desg FWD 200 128.4098 (vPC) P2p
Po57 Desg FWD 200 128.4152 (vPC) P2p
Po100 Root FWD 1000 128.4195 (vPC peer-link) Network P2p
Eth1/9 Desg FWD 20000 128.137 P2p
Eth1/15 Desg FWD 2000 128.143 Edge P2p
Eth1/16 Desg FWD 2000 128.144 Edge P2p
MST0001
Spanning tree enabled protocol mstp
Root ID Priority 16385
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16385 (priority 16384 sys-id-ext 1)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po2 Desg FWD 200 128.4097 (vPC) P2p
Po3 Desg FWD 200 128.4098 (vPC) P2p
Po57 Desg FWD 200 128.4152 (vPC) P2p
Po100 Root FWD 1000 128.4195 (vPC peer-link) Network P2p
Eth1/9 Desg FWD 20000 128.137 P2p
MST0002
Spanning tree enabled protocol mstp
Root ID Priority 16386
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16386 (priority 16384 sys-id-ext 2)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Desg FWD 1000 128.4096 P2p
Eth1/9 Desg FWD 20000 128.137 P2p
Eth1/15 Desg FWD 2000 128.143 Edge P2p
Eth1/16 Desg FWD 2000 128.144 Edge P2p
N5596-DC-SW2# show spanning-tree | i occur|from|exec
N5596-DC-SW2# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 44234 last change occurred 4:12:45 ago
from port-channel100
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 97804 last change occurred 4:12:43 ago
from port-channel100
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 49801 last change occurred 599:58:06 ago
from Ethernet1/9
Except from MST configs:
Nexus 4001i switches:
vlan 1,301-499
vlan 500
fip-snooping enable
vlan 600-800
spanning-tree mode mst
spanning-tree pathcost method long
spanning-tree mst 0-2 priority 24576
spanning-tree mst configuration
revision 1
instance 1 vlan 2-499,600-800,3110
instance 2 vlan 1,500-599
Nexus 5596 switches:
N5596-DC-SW1
spanning-tree mode mst
spanning-tree pathcost method long
spanning-tree mst 0-2 priority 16384
spanning-tree pseudo-information
mst 0-2 root priority 16384
mst 0-2 designated priority 16384
spanning-tree mst configuration
revision 1
instance 1 vlan 2-499,600-800,3110
instance 2 vlan 1,500-599
N5596-DC-SW2
spanning-tree mode mst
spanning-tree pathcost method long
spanning-tree mst 0-2 priority 16384
spanning-tree vlan 3110 priority 24576
spanning-tree pseudo-information
mst 0-1 designated priority 20480
mst 2 designated priority 16384
vlan 1-499,501,600-800 designated priority 20480
spanning-tree mst configuration
revision 1
instance 1 vlan 2-499,600-800,3110
instance 2 vlan 1,500-599
5596's vPC configs
N5596-DC-SW1
vpc domain 3
peer-switch
role priority 100
peer-keepalive destination 192.168.92.223 source 192.168.92.222
auto-recovery
N5596-DC-SW2
vpc domain 3
peer-switch
role priority 200
peer-keepalive destination 192.168.92.222 source 192.168.92.223
auto-recovery
Quick rundown of connections between devices:
Nexus 4001's connect to Nexus 5596's for ethernet data via twinax cables in a four port vPC between both Nexus 5596's.
Nexus 4001's connect to one Nexus 5596 a piece for FCoE two port LACP port channel. (hence the two instances, and vlan 1,500-599 in the same instance)
Catalyst 3110X connects via one Fiber-Optic connection to the N5596-DC-SW2, eventually will have two in a port-channel
Also keep in mind I corrected a priority conflict between the 3110X and Nexus 5596's earlier last month, which would explain all of the topology changes.
I can provide any other information if it is useful. I am just confused!I identified the problem.
Refer to
http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_2/nx-os/interfaces/configuration/guide/if_vPC.html
for more information.
The problem I encountered was self-inflicted.
Using the spanning-tree pseudo-information command creates a psuedo priority setup that if implemented after the global spanning-tree commands sits alongside the spanning-tree priority and vlan definitions. This is intended to allow for non-vPC VLANs to have their own spanning-tree definitions separate of the spanning-tree environment for the vPC vlans. I am not sure the best way to describe it, but if you are not running a hybrid vPC setup (where you have vPC member VLANs and non-vPC VLANS with a separate link between the 5596's for the non-vPC VLANs) this setup would help you ensure you have a stable spanning-tree and prevent unnecessary blocking.
When I enabled this command, I applied it to the vPC VLAN's as well, and that caused the Nexus 4001i's vPC links to constantly change port role, and update all of the edge ports subsequently. While I didn't see a performance impact to end hosts (not much traffic is on the Nexus DataCenter environment yet), I did get a torrent of logs as shown above.
Once I removed the spanning-tree pseudo-information, the switches quieted down and spanning-tree stabilized on the Nexus 4001i's.
I will revisit the configuration though for trunks not using vPC if it is needed. -
How to replace Nexus5596 with dual-homing N2K
What is the correct process to replace a FEX parent switch with dual-homing fex?
Traffic should not be interrupted.Hi
Do you have VPC between Parent Switches & are you running VPC on dual homed FEX fabric ports. ?
If yes Below is the procedure,
1) boot the replacement switch without VPC, peer-links & FEX ports connected to it.
2) Make sure it has same Software version matches with the peer switch.
3) enable Pre-Provisioning for slots with appropriate FEX model.
, here find the guide:
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus5000/sw/system_management/521_n1_1/b_5k_System_Mgmt_Config_521N11_chapter_0100.html#task_05BB53AD7AFB49CF9A8E4A5C6C37CB38
So, on the replacement switch you will pre-provision the Fabric Extender and configure the ports so it will be ready when you add the module to the RMA SW.
Please make sure you put the appropriate FEX model on the provision slot, otherwise, when connected it will not come Online
Example, FEX 110:
N5K(config)# slot 110
N5K(config-slot)#provision model N2K-C2248T
4) Now keep all ports at Shut down state Then Configure Entire switch that includes FEX host ports, FEX Fabric Ports & VPC peer-link, VPC Domain Configuration.
keep FEX host ports in shut state.
5) keep VPC Role priority on existing switch lower than , new switch
6) Connect Peer-link ports to Peer switch & wait till VPC Comes up-
7) Then connect Fabric ports from FEX to the pre-configured ports on replacement switch
After it comes online Unshut FEX host ports.
I got similar steps here as well
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/operations/n5k_vpc_ops.html#wp425197
NOTE: I followed same process however, few ping drops were seen....arnd ( 5- 6 ping loss) only on few hosts...
Mazhar -
Nexus 6004 EIGRP Relationship between the two switches
Hi All,
I will try to explain this as best as I can. In our current TEST LAB we have a Pair of Cisco ASA5585x running in Active/Passive mode. We use a VRF transit to connect the 10 GB interface to a Pair of Cisco Nexus 6004 (L3) switches running vPC between them. Downstream we also have a pair of Cisco 9372 switches (L2) also running vPC between the two.
As of right now we have EIGRP neighbor relationship formed between the two N6K's and the ASA.
ASA
ciscoasa# sh eigrp neighbors
EIGRP-IPv4 neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 172.16.230.9 Te0/8.451 12 01:30:25 1 200 0 52
0 172.16.230.10 Te0/8.451 12 01:30:25 1 200 0 48
The ASA formed relationship with both N6K's
SWITCH1
Nexus6-1# sh ip eigrp neighbors vrf inside
IP-EIGRP neighbors for process 100 VRF Inside
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 172.16.8.3 Vlan680 11 01:28:28 1 50 0 45
1 172.16.230.10 Vlan451 13 01:28:28 1 50 0 46
2 172.16.230.11 Vlan451 10 01:28:00 4 50 0 13
Nexus6-1#
SWITCH2
Nexus6-2# sh ip eigrp neighbors vrf Inside
IP-EIGRP neighbors for process 100 VRF Inside
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
2 172.16.8.2 Vlan680 14 01:30:11 23 138 0 48
0 172.16.230.9 Vlan451 13 01:30:11 480 2880 0 50
1 172.16.230.11 Vlan451 13 01:29:48 1598 5000 0 13
Nexus6-2#
Both Nexus Switches formed EIGRP neighbors using the vPC Peer-Link. There is enough documentation out there that strongly suggest not to use vPC Peer-Links for EIGRP anything.
We do have additional interfaces available on the 6K's that we can use as a cross connect for EIGRP. What we are having trouble understanding how we can force EIGRP traffic over those ports?
Here is a complete Switch config:
Switch1
Nexus6-1# sh run
feature telnet
cfs eth distribute
feature eigrp
feature interface-vlan
feature lacp
feature vpc
feature lldp
vlan 1
vlan 451
name P2P_VRF_SVI
vlan 652
name Management
vlan 680
name Inside
vrf context Inside
vrf context management
ip route 0.0.0.0/0 172.16.52.1
vrf context peer-keepalive
vpc domain 99
role priority 1
peer-keepalive destination 10.200.50.2 source 10.200.50.1 vrf peer-keepalive
delay restore 120
interface Vlan1
interface Vlan451
description Inside p2p to ASA
no shutdown
vrf member Inside
ip address 172.16.230.9/29
ip router eigrp 100
no ip passive-interface eigrp 100
interface Vlan651
interface Vlan680
description Inside Network
no shutdown
vrf member Inside
ip address 172.16.8.2/22
ip router eigrp 100
interface port-channel99
switchport mode trunk
spanning-tree port type network
vpc peer-link
interface port-channel102
switchport mode trunk
vpc 102
interface Ethernet1/1
description vPC Peer Link 1.1
switchport mode trunk
speed auto
channel-group 99
interface Ethernet1/6
interface Ethernet1/7
description vPC Peer Link 1.7 to Nexus 9372 PRI
switchport mode trunk
speed auto
channel-group 102 mode active
interface Ethernet1/8
interface Ethernet1/9
interface Ethernet2/1
description vPC Peer Link 2.1
switchport mode trunk
speed auto
channel-group 99
interface Ethernet2/2
interface Ethernet2/7
description vPC Peer Link 2.1 to Nexus SEC
switchport mode trunk
speed auto
channel-group 102 mode active
interface Ethernet2/8
interface Ethernet8/1
description keep-alive peer-link to ALNSWI02
no switchport
vrf member peer-keepalive
ip address 10.200.50.1/30
interface Ethernet8/2
description Uplink to ASA
switchport mode trunk
interface Ethernet8/3
interface mgmt0
vrf member management
ip address 172.16.52.3/23
line console
line vty
boot kickstart bootflash:/n6000-uk9-kickstart.7.0.1.N1.1.bin
boot system bootflash:/n6000-uk9.7.0.1.N1.1.bin
router eigrp 100
passive-interface default
default-information originate
vrf Inside
autonomous-system 100
default-information originate
poap transit
Nexus6-1#
Nexus6-1# sh ip eigrp neighbors vrf inside
IP-EIGRP neighbors for process 100 VRF Inside
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 172.16.8.3 Vlan680 11 01:28:28 1 50 0 45
1 172.16.230.10 Vlan451 13 01:28:28 1 50 0 46
2 172.16.230.11 Vlan451 10 01:28:00 4 50 0 13
Nexus6-1#
Nexus6-1# sh ip eigrp topology vrf Inside
IP-EIGRP Topology Table for AS(100)/ID(172.16.8.2) VRF Inside
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 172.16.8.0/22, 1 successors, FD is 2816
via Connected, Vlan680
P 172.16.230.8/29, 1 successors, FD is 2816
via Connected, Vlan451
Nexus6-1# sh vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 99
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : primary
Number of vPCs configured : 1
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Disabled
vPC Peer-link status
id Port Status Active vlans
1 Po99 up 1,451,652,680
vPC status
id Port Status Consistency Reason Active vlans
102 Po102 up success success 1,451,652,6
80
Nexus6-1# sh spanning-tree
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 32769
Address 1005.caf5.88ff
Cost 2
Port 4197 (port-channel102)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 8c60.4f2d.2ffc
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Root FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
Eth8/3 Desg FWD 2 128.1027 P2p
VLAN0451
Spanning tree enabled protocol rstp
Root ID Priority 33219
Address 8c60.4f2d.2ffc
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33219 (priority 32768 sys-id-ext 451)
Address 8c60.4f2d.2ffc
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Desg FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
VLAN0652
Spanning tree enabled protocol rstp
Root ID Priority 33420
Address 1005.caf5.88ff
Cost 2
Port 4197 (port-channel102)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33420 (priority 32768 sys-id-ext 652)
Address 8c60.4f2d.2ffc
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Root FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
VLAN0680
Spanning tree enabled protocol rstp
Root ID Priority 33448
Address 1005.caf5.88ff
Cost 2
Port 4197 (port-channel102)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33448 (priority 32768 sys-id-ext 680)
Address 8c60.4f2d.2ffc
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Root FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
Nexus6-1#
Switch2
Nexus6-2# sh run
!Command: show running-config
!Time: Sat Feb 12 19:02:44 2011
version 7.0(1)N1(1)
hostname Nexus6-2
feature telnet
cfs eth distribute
feature eigrp
feature interface-vlan
feature lacp
feature vpc
feature lldp
vlan 1
vlan 451
name P2P_VRF_SVI
vlan 652
name Management
vlan 680
name Inside
vrf context Inside
vrf context P2P_Inside_VRF
vrf context management
ip route 0.0.0.0/0 172.16.52.1
vrf context peer-keepalive
vpc domain 99
role priority 2
peer-keepalive destination 10.200.50.1 source 10.200.50.2 vrf peer-keepalive
delay restore 120
interface Vlan1
interface Vlan451
description Inside p2p to ASA
no shutdown
vrf member Inside
ip address 172.16.230.10/29
ip router eigrp 100
no ip passive-interface eigrp 100
interface Vlan680
description Inside Network
no shutdown
vrf member Inside
ip address 172.16.8.3/22
ip router eigrp 100
interface port-channel99
switchport mode trunk
spanning-tree port type network
vpc peer-link
interface port-channel102
switchport mode trunk
vpc 102
interface Ethernet1/1
description vPC Peer Link 1.1
switchport mode trunk
speed auto
channel-group 99
interface Ethernet1/2
interface Ethernet1/6
interface Ethernet1/7
description vPC Link 1.7 to Nexus 9372 SEC
switchport mode trunk
speed auto
channel-group 102 mode active
interface Ethernet1/8
interface Ethernet1/12
interface Ethernet2/1
description vPC Peer Link 2.1
switchport mode trunk
speed auto
channel-group 99
interface Ethernet2/2
interface Ethernet2/6
interface Ethernet2/7
description vPC Link 2.1 to Nexus PRI
switchport mode trunk
speed auto
channel-group 102 mode active
interface Ethernet2/8
interface Ethernet2/12
interface Ethernet8/1
description keep-alive peer-link to ALNSWI01
no switchport
vrf member peer-keepalive
ip address 10.200.50.2/30
interface Ethernet8/2
description Uplink to ASA
switchport mode trunk
switchport trunk allowed vlan 1,451,652,680
interface Ethernet8/3
interface Ethernet8/20
interface mgmt0
vrf member management
ip address 172.16.52.4/23
line console
line vty
boot kickstart bootflash:/n6000-uk9-kickstart.7.0.1.N1.1.bin
boot system bootflash:/n6000-uk9.7.0.1.N1.1.bin
router eigrp 100
vrf Inside
autonomous-system 100
default-information originate
poap transit
logging logfile messages 6
Nexus6-2#
Nexus6-2#
Nexus6-2# sh ip eigrp neighbors vrf Inside
IP-EIGRP neighbors for process 100 VRF Inside
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
2 172.16.8.2 Vlan680 14 01:30:11 23 138 0 48
0 172.16.230.9 Vlan451 13 01:30:11 480 2880 0 50
1 172.16.230.11 Vlan451 13 01:29:48 1598 5000 0 13
Nexus6-2#
Nexus6-2# sh ip eigrp topology vrf Inside
IP-EIGRP Topology Table for AS(100)/ID(172.16.8.3) VRF Inside
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 172.16.8.0/22, 1 successors, FD is 2816
via Connected, Vlan680
P 172.16.230.8/29, 1 successors, FD is 2816
via Connected, Vlan451
Nexus6-2#
Nexus6-2#
Nexus6-2# sh vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 99
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : secondary
Number of vPCs configured : 1
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Disabled
vPC Peer-link status
id Port Status Active vlans
1 Po99 up 1,451,652,680
vPC status
id Port Status Consistency Reason Active vlans
102 Po102 up success success 1,451,652,6
80
Nexus6-2#
Nexus6-2#
Nexus6-2# sh spanning-tree
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 32769
Address 1005.caf5.88ff
Cost 3
Port 4194 (port-channel99)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 8c60.4f2d.777c
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po99 Root FWD 1 128.4194 (vPC peer-link) Network P2p
Po102 Root FWD 1 128.4197 (vPC) P2p
Eth8/2 Desg FWD 2 128.1026 P2p
Eth8/3 Desg FWD 2 128.1027 P2p
VLAN0451
Spanning tree enabled protocol rstp
Root ID Priority 33219
Address 8cJon,
Are you ready for the mass confusion?
when Looking at the ASA EIGRP neighbors output here is what I see.
ASA# sh eigrp neighbors
EIGRP-IPv4 neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
3 172.16.230.1 Te0/8.450 13 16:45:14 1 200 0 64
2 172.16.230.2 Te0/8.450 11 16:45:14 1 200 0 84
1 172.16.230.10 Te0/8.451 11 16:45:20 1 200 0 178
0 172.16.230.9 Te0/8.451 13 16:45:20 1 200 0 148
For simplicity sake lets just concetrate on Interface TenGigabit0/8.451 which is the SVI on the Nexus switch that is VLAN451
From the Nexus Switch 6004 that is directly connected to the ASA here is what I see
SWI01# sh ip eigrp neighbors vrf Inside
IP-EIGRP neighbors for process 100 VRF Inside
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 172.16.8.3 Vlan680 10 17:04:30 54 324 0 177
1 172.16.230.10 Vlan451 11 16:59:10 819 4914 0 178
2 172.16.230.11 Vlan451 14 16:53:48 24 144 0 20
The Inside VRF that is tied to both SVI's on the Switch vlans 451 and 680 is in EIGRP 100 on the switch
SWI01# sh run int vlan 451
interface Vlan451
description Inside p2p to ASA
no shutdown
vrf member Inside
ip address 172.16.230.9/29
ip router eigrp 100
no ip passive-interface eigrp 100
SWI01# sh run int vlan 680
interface Vlan680
description Inside Network
no shutdown
vrf member Inside
ip address 172.16.8.2/22
ip router eigrp 100
hsrp 1
authentication text test
preempt
priority 250
ip 172.16.8.1
so you with me so far?
If you are you have noticed that on the ASA neighbors the ASA sees 172.16.230.11 as a neighbor which is the Secondary Nexus SW. That is becauise they all share the same subnet.
172.16.230.8/29
Brakedown:
PRI Nexus 6004 - 172.16.230.9
SEC NEXUS 6004 - 172.16.230.10
PRI ASA 5585x - 172.16.230.11
SEC ASA 5585x - 172.16.230.12
Because the ASA EIGRP network is a /29 it learns the Secondary Nexus via the Primary Nexus.
I am not sure that the link we created between the two Nexus Switches is doing anything but consuming ports right now.
SWI01# sh run int ethernet 8/9
interface Ethernet8/9
description EIGRP PORT to Secondary Nexus
switchport mode trunk
switchport trunk allowed vlan 450-451
SWI02# sh run int ethernet 8/9
interface Ethernet8/9
description EIGRP PORT to Primary Nexus
switchport mode trunk
switchport trunk allowed vlan 450-451
So the SVI's that go up to the ASA for inspection are 450 and 451. The network SVI's are 600 and 680 all of them live on the switch, and 680, and 600 are extended over the peer links down to the 9372's.
I think that we are breaking the golden rule of vPC BUT.. I am not 100% sure. Some of the documents read that we should not be allowing network vlans over peer links, but then how do you extend the vlans down to the leaf switch?
This is giving me nightmares at the moment…
does this make sense? -
Hello,
There are two N7Ks connected with peer-link (Po1). There will be some other L2 switches connected to those N7Ks with vPC. Also, there is a separate, dedicated L2 link (Po9) between N7Ks to carry VLANs for orphan ports connected on both N7Ks. Here is configuration:
N7K-1:
spanning-tree mst configuration
name test
revision 3
instance 1 vlan 1-9,12-14,16-1005
instance 2 vlan 10,11,15
spanning-tree mode mst
spanning-tree mst 0-2 priority 4096
spanning-tree pseudo-information
mst 0-2 designated priority 4096
mst 0-2 root priority 4096
vpc domain 1
peer-keepalive destination 1.1.1.2 source 1.1.1.1 vrf peer-keepalive
system-priority 1000
role priority 1
auto-recovery reload-delay 240
peer-gateway
peer-switch
graceful consistency-check
ip arp synchronize
delay restore 30
delay restore interface-vlan 40
interface port-channel 1
vpc peer-link
switchport trunk allowed vlan remove 10,11,15
interface port-channel 9
switchport trunk allowed vlan 10,11,15
spanning-tree mst 2 cost 100
N7K-2:
spanning-tree mst configuration
name test
revision 3
instance 1 vlan 1-9,12-14,16-1005
instance 2 vlan 10,11,15
spanning-tree mode mst
spanning-tree mst 0-2 priority 4096
spanning-tree pseudo-information
mst 0-2 designated priority 8192
mst 0-2 root priority 8192
vpc domain 1
peer-keepalive destination 1.1.1.1 source 1.1.1.2 vrf peer-keepalive
system-priority 1000
role priority 1
auto-recovery reload-delay 240
peer-gateway
peer-switch
graceful consistency-check
ip arp synchronize
delay restore 30
delay restore interface-vlan 40
interface port-channel 1
vpc peer-link
switchport trunk allowed vlan remove 10,11,15
interface port-channel 9
switchport trunk allowed vlan 10,11,15
spanning-tree mst 2 cost 100
In theory, for vPC VLANs, that is those carried over peer-link, global STP configuration should be used. And, because peer-switch is used, both N7Ks will generate the same BPDU (the same Bridge ID with priority 4096), both becomming root. And, for other VLANs, carried over dedicated L2 link, the pseudo-information should be used. That is, N7K-1 should become root, and Po9 should be Designated. The N7K-2 should be backup root and Po9 should be Root port.
Unfortunately, it's not how it works. Maybe I am missing something, but BPDUs sent over dedicated L2 Po9 are exactly the same as for VPC VLANs. N7K-1 becomes root and its Po9 becomes Designated. But, N7K-2 is also a root, and since it sees the same BPDU as it generates by itself, it treats Po9 as an alternate way to itself and places that port in Alternate/Blocking state.
So, am I doing something wrong, or dedicated L2 link cannot co-exist with peer-link? I had no chance to test it, but it may work if I remove peer-switch feature (although it is recommended to have it)
Best regards,
KrzysztofWe have filed
CSCuc41076
vPC Peer Switch Hybrid Topology MST blocking in non vPC Peer Link -
Nexus 7000 - unexpected shutdown of vPC-Ports during reload of the primary vPC Switch
Dear Community,
We experienced an unusual behavior of two Nexus 7000 switches within a vPC domain.
According to the attached sketch, we have four N7Ks in two data centers - two Nexus 7Ks are in a vPC domain for each data center.
Both data centers are connected via a Multilayer-vPC.
We had to reload one of these switches and I expected the other N7K in this vPC domain to continue forwarding over its vPC-Member-ports.
Actually, all vPC ports have been disabled on the secondary switch until the reload of the first N7K (vPC-Role: primary) finished.
Logging on Switch B:
20:11:51 <Switch B> %VPC-2-VPC_SUSP_ALL_VPC: Peer-link going down, suspending all vPCs on secondary
20:12:01 <Switch B> %VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain 1, VPC peer keep-alive receive has failed
In case of a Peer-link failure, I would expect this behavior if the other switch is still reachable via the Peer-Keepalive-Link (via the Mgmt-Port), but since we reloaded the whole switch, the vPCs should continue forwarding.
Could this be a bug or are there any timers to be tuned?
All N7K switches are running on NX-OS 6.2(8)
Switch A:
vpc domain 1
peer-switch
role priority 2048
system-priority 1024
peer-keepalive destination <Mgmt-IP-Switch-B>
delay restore 360
peer-gateway
auto-recovery reload-delay 360
ip arp synchronize
interface port-channel1
switchport mode trunk
switchport trunk allowed vlan <x-y>
spanning-tree port type network
vpc peer-link
Switch B:
vpc domain 1
peer-switch
role priority 1024
system-priority 1024
peer-keepalive destination <Mgmt-IP-Switch-A>
delay restore 360
peer-gateway
auto-recovery reload-delay 360
ip arp synchronize
interface port-channel1
switchport mode trunk
switchport trunk allowed vlan <x-y>
spanning-tree port type network
vpc peer-link
Best regardsProblem solved:
During the reload of the Nexus 7K, the linecards were powerd off a short time earlier than the Mgmt-Interface. As a result of this behavior, the secondary Nexus 7K received at least one vPC-Peer-Keepalive Message while its peer-link was already powerd off. To avoid a split brain scenario, the VPC-member-ports have been shut down.
Now we are using dedicated interfaces on the linecards for the VPC-Peer-Keepalive-Link and a reload of one N7K won't result in a total network outage any more. -
VPC on Nexus 5000 with Catalyst 6500 (no VSS)
Hi, I'm pretty new on the Nexus and UCS world so I have some many questions I hope you can help on getting some answers.
The diagram below is the configuration we are looking to deploy, that way because we do not have VSS on the 6500 switches so we can not create only one Etherchannel to the 6500s.
Our blades inserted on the UCS chassis have INTEL dual port cards, so they do not support full failover.
Questions I have are.
- Is this my best deployment choice?
- vPC highly depend on the management interface on the Nexus 5000 for the keep alive peer monitoring, so what is going to happen if the vPC brakes due to:
- one of the 6500 goes down
- STP?
- What is going to happend with the Etherchannels on the remaining 6500?
- the Management interface goes down for any other reason
- which one is going to be the primary NEXUS?
Below is the list of devices involved and the configuration for the Nexus 5000 and 65000.
Any help is appreciated.
Devices
· 2 Cisco Catalyst with two WS-SUP720-3B each (no VSS)
· 2 Cisco Nexus 5010
· 2 Cisco UCS 6120xp
· 2 UCS Chassis
- 4 Cisco B200-M1 blades (2 each chassis)
- Dual 10Gb Intel card (1 per blade)
vPC Configuration on Nexus 5000
TACSWN01
TACSWN02
feature vpc
vpc domain 5
reload restore
reload restore delay 300
Peer-keepalive destination 10.11.3.10
role priority 10
!--- Enables vPC, define vPC domain and peer for keep alive
int ethernet 1/9-10
channel-group 50 mode active
!--- Put Interfaces on Po50
int port-channel 50
switchport mode trunk
spanning-tree port type network
vpc peer-link
!--- Po50 configured as Peer-Link for vPC
inter ethernet 1/17-18
description UCS6120-A
switchport mode trunk
channel-group 51 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-A
int port-channel 51
swithport mode trunk
vpc 51
spannig-tree port type edge trunk
!--- Associates vPC 51 to Po51
inter ethernet 1/19-20
description UCS6120-B
switchport mode trunk
channel-group 52 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-B
int port-channel 52
swithport mode trunk
vpc 52
spannig-tree port type edge trunk
!--- Associates vPC 52 to Po52
!----- CONFIGURATION for Connection to Catalyst 6506
Int ethernet 1/1-3
description Cat6506-01
switchport mode trunk
channel-group 61 mode active
!--- Associate interfaces to Po61 connected to Cat6506-01
Int port-channel 61
switchport mode trunk
vpc 61
!--- Associates vPC 61 to Po61
Int ethernet 1/4-6
description Cat6506-02
switchport mode trunk
channel-group 62 mode active
!--- Associate interfaces to Po62 connected to Cat6506-02
Int port-channel 62
switchport mode trunk
vpc 62
!--- Associates vPC 62 to Po62
feature vpc
vpc domain 5
reload restore
reload restore delay 300
Peer-keepalive destination 10.11.3.9
role priority 20
!--- Enables vPC, define vPC domain and peer for keep alive
int ethernet 1/9-10
channel-group 50 mode active
!--- Put Interfaces on Po50
int port-channel 50
switchport mode trunk
spanning-tree port type network
vpc peer-link
!--- Po50 configured as Peer-Link for vPC
inter ethernet 1/17-18
description UCS6120-A
switchport mode trunk
channel-group 51 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-A
int port-channel 51
swithport mode trunk
vpc 51
spannig-tree port type edge trunk
!--- Associates vPC 51 to Po51
inter ethernet 1/19-20
description UCS6120-B
switchport mode trunk
channel-group 52 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-B
int port-channel 52
swithport mode trunk
vpc 52
spannig-tree port type edge trunk
!--- Associates vPC 52 to Po52
!----- CONFIGURATION for Connection to Catalyst 6506
Int ethernet 1/1-3
description Cat6506-01
switchport mode trunk
channel-group 61 mode active
!--- Associate interfaces to Po61 connected to Cat6506-01
Int port-channel 61
switchport mode trunk
vpc 61
!--- Associates vPC 61 to Po61
Int ethernet 1/4-6
description Cat6506-02
switchport mode trunk
channel-group 62 mode active
!--- Associate interfaces to Po62 connected to Cat6506-02
Int port-channel 62
switchport mode trunk
vpc 62
!--- Associates vPC 62 to Po62
vPC Verification
show vpc consistency-parameters
!--- show compatibility parameters
Show feature
!--- Use it to verify that vpc and lacp features are enabled.
show vpc brief
!--- Displays information about vPC Domain
Etherchannel configuration on TAC 6500s
TACSWC01
TACSWC02
interface range GigabitEthernet2/38 - 43
description TACSWN01 (Po61 vPC61)
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
no ip address
channel-group 61 mode active
interface range GigabitEthernet2/38 - 43
description TACSWN02 (Po62 vPC62)
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
no ip address
channel-group 62 mode activeihernandez81,
Between the c1-r1 & c1-r2 there are no L2 links, ditto with d6-s1 & d6-s2. We did have a routed link just to allow orphan traffic.
All the c1r1 & c1-r2 HSRP communications ( we use GLBP as well ) go from c1-r1 to c1-r2 via the hosp-n5k-s1 & hosp-n5k-s2. Port channels 203 & 204 carry the exact same vlans.
The same is the case on the d6-s1 & d6-s2 sides except we converted them to a VSS cluster so we only have po203 with 4 *10 Gb links going to the 5Ks ( 2 from each VSS member to each 5K).
As you can tell what we were doing was extending VM vlans between 2 data centers prior to arrivals of 7010s and UCS chassis - which worked quite well.
If you got on any 5K you would see 2 port channels - 203 & 204 - going to each 6500, again when one pair went to VSS po204 went away.
I know, I know they are not the same things .... but if you view the 5Ks like a 3750 stack .... how would you hook up a 3750 stack from 2 6500s and if you did why would you run an L2 link between the 6500s ?
For us using 4 10G ports between 6509s took ports that were too expensive - we had 6704s - so use the 5Ks.
Our blocking link was on one of the links between site1 & site2. If we did not have wan connectivty there would have been no blocking or loops.
Caution .... if you go with 7Ks beware of the inability to do L2/L3 via VPCs.
better ?
one of the nice things about working with some of this stuff is as long as you maintain l2 connectivity if you are migrating things they tend to work, unless they really break -
Hi I have a question regarding peer-switch konfiguration on a vPC/vPC+ pair of N7K with vPC and non vPC attached switches
If I understood correctly with following configuration
for vPC attached switches (assuming the have default STP-prio) the vPC-bundle acts as one Switch with the priority of 4096
for STP non-VPC attached switches for VLAN1-1960 the N7K-A is the root-bridge and for VLAN 1961-3920 the N7K-B is the root-bridge,
N7K-A
vpc domain 20
peer-switch
role priority 1
spanning-tree pseudo-information
vlan 1-3920 root priority 4096
vlan 1-1960 designated priority 4096
vlan 1961-3920 designated priority 8192
N7K-B
vpc domain 20
peer-switch
role priority 2
spanning-tree pseudo-information
vlan 1-3920 root priority 4096
vlan 1-1960 designated priority 8192
vlan 1961-3920 designated priority 4096
Is that coorect so far ?
If yes then I have one outstandig question.
Do we need the global configuration for spanning-tree priority in this case?
spanning-tree vlan 1-3920 priority 4096
as we configure it in a pure vPC environment
N7K-A
spanning-tree vlan 1-3920 priority 4096
vpc domain 20
peer-switch
role priority 1
N7K-B
spanning-tree vlan 1-3920 priority 4096
vpc domain 20
peer-switch
role priority 2
Thanks
HubertHere is a description of the use of the Spanning-tree Pseudo-information and the Peer switch command on the Nexus 7000. Maybe this will help clarify some misunderstanding:
SETUP:
7K1 and 7K2 are vPC peers and have a higher priority than 7K3. So 7K1 and 7K2s ports to 7K3 will all be DESIGNATED.
7K3 is connected to both 7K1 and 7K2 using individual STP links.
7K4 is connected to both 7K1 and 7K2 in a vPC.
Common Points for all Scenarios:
If vPC fails for whatever reason; all links will revert to regular spanning-tree.
The root priority on 7K1 and 7K2 will be the vPC System-MAC (same on both) and the Designated priority will use the respective non-vPC System-MACs of 7k1 and 7K2
Even if the STP Priority is configured globally and lower, the Pseudo Root Priority and Designated Priorities are still used for STP calculations.
The STP Pseudo-information HACK:
Allows you to set a different root priority and different designated priority. To satisfy the requirement for the Peer switch command and still be able to perform VLAN load balancing for non-vPC dual connected links.
Root Priority: Used in Root Bridge Election
Designated Priority: Used in Designated Bridge Election
SCENARIO 1: Same STP Priority configured Globally with the Peer switch Enabled (Individual STP links)
The Root priority and Designated priority on 7K1 and 7K2 will be the same as the globally configured or default STP priority
One of the links to 7K1 and 7K2 becomes the "Root Port" and the other becomes "ALTN BLK"
Since they have the same Root Priority and the same vPC system MAC, the lower port will be selected as the root port.
SCENARIO 2: BOTH STP Pseudo-information Root and Designated Priorities Configured with Peer Switch Enabled (Individual STP links)
The Root priority may be different from the Designated Priority based on the STP Pseudo-information configuration.
VLAN traffic from 7K3 is load balanced between 7K1 and 7K2 based on the configured Pseudo-Designated Priority. So the Root port for a VLAN from 7K3 will be to the device with a lower Pseudo-Designated priority.
SCENARIO 3: ONLY STP Pseudo-information Root Priority Configured with Peer Switch Enabled (Individual STP links)
The Root priority and Designated Priority are the same as the Pseudo Root Priority.
No VLAN load balancing occurs
The Root port is the link to the vPC primary switch. The Link to the vPC Secondary is “ALTN BLK”.
SCENARIO 4: ONLY STP Pseudo-information Designated Priority Configured with Peer Switch Enabled (Individual STP links)
The Root priority will be the Globally configured or default STP Priority
The Designated priority will still be the Pseudo-Designated priority
VLAN load balancing will still occur.
SCENARIO 5: Same STP Priority configured Globally with the Peer switch Enabled (vPC links on 7K4)
The Root priority and Designated priority on 7K1 and 7K2 will be the same as the globally configured or default STP priority.
If the vPC Peer-link fails, the interface going to the secondary vPC device (7K2) will be shut DOWN.
SCENARIO 6: BOTH STP Pseudo-information Root and Designated Priorities Configured with Peer Switch Enabled (vPC links on 7K4)
The Root priority and Designated Priority are the same as the configured Pseudo-Root Priority.
If the vPC Peer-link fails, the interface going to the secondary vPC device (7K2) will be shut DOWN.
SCENARIO 7: ONLY STP Pseudo-information Root Priority Configured with Peer Switch Enabled (vPC links on 7K4)
The Root priority and Designated Priority are the same as the configured Pseudo-Root Priority.
If the vPC Peer-link fails, the interface going to the secondary vPC device (7K2) will be shut DOWN.
SCENARIO 8: ONLY STP Pseudo-information Designated Priority Configured with Peer Switch Enabled (vPC links on 7K4)
The Root priority and Designated priority on 7K1 and 7K2 will be the same as the globally configured or default STP priority.
If the vPC Peer-link fails, the interface going to the secondary vPC device (7K2) will be shut DOWN -
Hello,
We have the topology in Attachement. and we have problem with SVI and VPC
The configuration:
N5K1:
vpc domain 100
peer-switch
role priority 100
system-priority 1024
peer-keepalive destination 192.168.21.1
peer-config-check-bypass
delay restore 150
peer-gateway
auto-recovery
ip arp synchronize
vlan 801
name DEV_WAN
interface Vlan801
description IP DEV
no shutdown
no ip redirects
interface Vlan1000
no shutdown
no ip redirects
ip address 192.168.22.5/30
interface port-channel1000
switchport mode trunk
spanning-tree port type network
spanning-tree guard loop
vpc peer-link
interface port-channel401
description LACP-SRV1
switchport mode trunk
speed 1000
duplex full
vpc 401
interface Ethernet1/1
description "TRUNK VPC"
no cdp enable
switchport mode trunk
spanning-tree port type network
spanning-tree bpdufilter enable
channel-group 1000 mode active
interface Ethernet1/2
description "TRUNK VPC"
switchport mode trunk
spanning-tree port type network
channel-group 1000 mode active
interface Ethernet1/5
description SRV1_GB2
switchport mode trunk
speed 1000
duplex full
channel-group 401 mode active
interface Ethernet1/29
description Uplink N5K3
switchport mode trunk
N5K2:
vpc domain 100
peer-switch
role priority 110
system-priority 1024
peer-keepalive destination 192.168.21.2
peer-config-check-bypass
delay restore 150
peer-gateway
auto-recovery
ip arp synchronize
vlan 801
name DEV_WAN
interface Vlan801
no shutdown
ip address 202.168.72.1/29
interface Vlan1000
description VPC-N5K
no shutdown
no ip redirects
ip address 192.168.22.6/30
interface port-channel1000
switchport mode trunk
spanning-tree port type network
spanning-tree guard loop
vpc peer-link
interface port-channel401
description LACP-SRV1
switchport mode trunk
speed 1000
duplex full
vpc 401
interface Ethernet1/1
description "TRUNK VPC"
switchport mode trunk
spanning-tree port type network
channel-group 1000 mode active
interface Ethernet1/2
description "TRUNK VPC"
switchport mode trunk
spanning-tree port type network
channel-group 1000 mode active
interface Ethernet1/5
description SRV1_GB4
switchport mode trunk
speed 1000
duplex full
channel-group 401 mode active
SRV1 IP: 202.168.72.2/29
When i plug the cable from SRV1 to N5K1 and N5K2 i can't ping SRV1 from ADM
when i unplug the cable from SRV1 to N5K2 i can't ping SRV1 from ADM
when i unplug the cable from SRV1 to N5K1 i CAN ping SRV1 from ADM
between N5K1, N5K2 and N5K3 we have OSPF
Thks !n5k01# sh vpc brief
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 100
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : primary
Number of vPCs configured : 8
Peer Gateway : Enabled
Peer gateway excluded VLANs : -
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled (timeout = 240 seconds)
vPC Peer-link status
id Port Status Active vlans
1 Po1000 up 1-3,101-102,110,700-703,705,710,730,801,803,1000,3
001-3008,3400-3401
vPC status
id Port Status Consistency Reason Active vlans
1 Po1 up success success 1-3,101-102
,110,700-70
3,705,710,7
30,801,803,
1000,300....
401 Po401 down* success success -
(The cable is unplug)
n5K02# sh vpc brief
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 100
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : secondary
Number of vPCs configured : 8
Peer Gateway : Enabled
Peer gateway excluded VLANs : -
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled (timeout = 240 seconds)
vPC Peer-link status
id Port Status Active vlans
1 Po1000 up 1-3,101-102,110,700-703,705,710,730,801,803,1000,3
001-3008,3400-3401
vPC status
id Port Status Consistency Reason Active vlans
1 Po1 up success success 1-3,101-102
,110,700-70
3,705,710,7
30,801,803,
1000,300....
401 Po401 up success success 1-3,101-102
,110,700-70
3,705,710,7
30,801,803,
1000,300.... -
VPC N5k Switch Failure causes connectivity disruption
Hello,
I have configured enhanced vPC on 2 n5k and B22 FEXs (vPC from 5k to B22, and vPC from B22 to blade servers).
Everything is running smoothly, except when I power off one of the 5k, the connectivity to the blade servers is lost, comes back up for a short while, loses connectivity again, and after a few minutes comes back up for good.
From the logs I can see that all the port-channels (peer-link, to the FEXs and port-channels to other switches in network) get in down state, then fizical interfaces start coming backup in fabric mode, then port-channels, see FEXs starting to get online then all the port-channels go down again and then whole thing starts again.(all of this is hapenig with one of the 5k powerd off, same thing hapens with promary and secondary vpc).
Connectivity is lost in the same way when the 5k is started again, but just once.
I am running NX OS version 5.2.1N1.3.
I have no idea what could cause this behavior.
Any help would be appreciated.
Regards,
BogdanHi Reza,
Below you can find my run-config.
version 5.2(1)N1(3)
feature fcoe
install feature-set virtualization
feature-set virtualization
logging level feature-mgr 0
hostname N5k_1
feature npiv
feature telnet
cfs eth distribute
feature udld
feature interface-vlan
feature lacp
feature vpc
feature lldp
feature vtp
feature fex
fex 107
pinning max-links 1
description "FEX0107"
fcoe
fex 108
pinning max-links 1
description "FEX0108"
slot 1
port 31-32 type fc
vpc domain 1
role priority 1000
peer-keepalive destination 1.1.1.2
auto-recovery
vsan database
vsan 50 name "VSAN_A"
fcdomain fcid database
interface port-channel100
description Po Synch N5k
switchport mode trunk
spanning-tree port type network
logging event port link-status
logging event port trunk-status
speed 10000
vpc peer-link
interface port-channel107
switchport mode fex-fabric
fex associate 107
vpc 107
interface port-channel108
switchport mode fex-fabric
fex associate 108
vpc 108
interface port-channel111
switchport mode trunk
interface vfc111
bind interface Ethernet107/1/1
no shutdown
vsan database
vsan 50 interface vfc111
vsan 50 interface fc1/31
vsan 50 interface fc1/32
interface fc1/31
no shutdown
interface fc1/32
no shutdown
interface Ethernet1/1
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/2
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/3
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/4
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/5
switchport mode fex-fabric
fex associate 107
channel-group 107
interface Ethernet1/6
switchport mode fex-fabric
fex associate 107
channel-group 107
interface Ethernet1/7
switchport mode fex-fabric
fex associate 108
channel-group 108
interface Ethernet1/8
switchport mode fex-fabric
fex associate 108
channel-group 108
interface Ethernet107/1/1
switchport mode trunk
channel-group 111 mode active
interface Ethernet108/1/1
switchport mode trunk
channel-group 111 mode active
version 5.2(1)N1(3)
feature fcoe
install feature-set virtualization
feature-set virtualization
logging level feature-mgr 0
hostname N5k_2
feature npiv
feature telnet
cfs eth distribute
feature udld
feature interface-vlan
feature lacp
feature vpc
feature lldp
feature vtp
feature fex
fex 107
pinning max-links 1
description "FEX0107"
fex 108
pinning max-links 1
description "FEX0108"
fcoe
slot 1
port 31-32 type fc
vpc domain 1
role priority 1000
peer-keepalive destination 1.1.1.1
auto-recovery
vsan database
vsan 51 name "VSAN_B"
fcdomain fcid database
interface port-channel100
description Po Synch N5k
switchport mode trunk
spanning-tree port type network
logging event port link-status
logging event port trunk-status
speed 10000
vpc peer-link
interface port-channel107
switchport mode fex-fabric
fex associate 107
vpc 107
interface port-channel108
switchport mode fex-fabric
fex associate 108
vpc 108
interface port-channel111
switchport mode trunk
interface vfc111
bind interface Ethernet108/1/1
no shutdown
vsan database
vsan 51 interface vfc111
vsan 51 interface fc1/31
vsan 51 interface fc1/32
interface fc1/31
no shutdown
interface fc1/32
no shutdown
interface Ethernet1/1
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/2
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/3
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/4
description Synch N5k
switchport mode trunk
logging event port link-status
logging event port trunk-status
udld aggressive
channel-group 100 mode active
interface Ethernet1/5
switchport mode fex-fabric
fex associate 107
channel-group 107
interface Ethernet1/6
switchport mode fex-fabric
fex associate 107
channel-group 107
interface Ethernet1/7
switchport mode fex-fabric
fex associate 108
channel-group 108
interface Ethernet1/8
switchport mode fex-fabric
fex associate 108
channel-group 108
interface Ethernet107/1/1
switchport mode trunk
channel-group 111 mode active
interface Ethernet108/1/1
switchport mode trunk
channel-group 111 mode active -
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 activeWhat Nexus OS are you running.. You could be seeing this bug
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtw76636 -
N5k96UP connected to 6509 no VSS over 1GB
Hi there,
i have the advantage to connect 2 N5k Switches on 2 6500 without VSS over 1GB Ports (Portchannel)
I configured LACP on the port-channel interfaces, and all interfaces on the 5ks facing down to the 65 in one Port-Channel and one vPC.
Is this the right way for this issue, ore dose i need to configure different port-channels and different vPCs on the 5ks?
Now, all Ports facing to 6500b are Suspended on N5ka and N5kb.
N5ka# sh port-channel summ
Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
Group Port- Type Protocol Member Ports
Channel
10 Po10(SU) Eth LACP Eth1/43(s) Eth1/44(s) Eth1/45(P)
Eth1/46(P) Eth2/13(s) Eth2/14(s)
Eth2/15(P) Eth2/16(P)
N5kb# sh port-channel summ
Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
Group Port- Type Protocol Member Ports
Channel
10 Po10(SU) Eth LACP Eth1/43(P) Eth1/44(P) Eth1/45(s)
Eth1/46(s) Eth2/13(P) Eth2/14(P)
Eth2/15(s) Eth2/16(s)
6500a#
interface GigabitEthernet2/17
description to N5ka
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/18
description to N5ka
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/19
description to N5ka
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/20
description to N5ka
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/21
description N5kb
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/22
description N5kb
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/23
description N5Kb
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/24
descriptionN5kb
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface Port-channel10
description Po10 N5ka and N5kb
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
6500b#
interface GigabitEthernet2/17
description to N5kb
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/18
description to N5kb
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/19
description to N5kb
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/20
description to N5kb
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/21
description N5ka
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/22
description N5ka
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/23
description N5Ka
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface GigabitEthernet2/24
descriptionN5ka
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
channel-group 10 mode active
interface Port-channel10
description Po10 N5kb and N5ka
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 64
switchport mode trunk
switchport nonegotiate
N5ka:
vpc domain 99
role priority 1000
peer-keepalive destination xxxxx
interface port-channel10
description i=po10 Eth1/43 - 46, Eth2/13 - 16 6500a, 6500b Uplink VLAN64 vPC10
switchport mode trunk
vpc 10
switchport trunk allowed vlan 64
spanning-tree port type network
interface Ethernet1/43
description i=Eth1/43 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/44
description i=Eth1/44 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/45
description i=Eth1/45 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/46
description i=Eth1/46 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/47
description i=e1/47 vPCpeerLink-Domain99
switchport mode trunk
udld aggressive
channel-group 99
interface Ethernet1/48
description i=e1/48 vPCpeerLink-Domain99
switchport mode trunk
udld aggressive
channel-group 99
interface Ethernet2/13
description i=Eth2/13 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet2/14
description i=Eth2/14 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet2/15
description i=Eth2/15 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet2/16
description i=Eth2/16 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
N5kb
interface Ethernet1/43
description i=Eth1/43 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/44
description i=Eth1/44 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/45
description i=Eth1/45 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/46
description i=Eth1/46 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/47
description i=e1/47 u=e1/47 t=vPCpeerLink-Domain99
switchport mode trunk
channel-group 99
interface Ethernet1/48
description i=e1/48 u=e1/48 t=vPCpeerLink-Domain99
switchport mode trunk
udld aggressive
channel-group 99
interface Ethernet2/13
description i=Eth2/13 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet2/14
description i=Eth2/14 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet2/15
description i=Eth2/15 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet2/16
description i=Eth2/16 6500
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active!Command: show running-config
!Time: Thu Nov 17 15:31:23 2011
version 5.0(3)N2(2)
no feature telnet
no telnet server enable
cfs eth distribute
feature udld
feature lacp
feature vpc
feature lldp
feature fex
username xxx password 5 xxx role network-admin
username xxx password 5 xxx role network-admin
ip domain-lookup
radius-server key 7 xxxx
radius-server timeout 3
radius-server retransmit 2
radius-server host 10.10.8.53 auth-port 1645 acct-port 1646 authentication accounting
aaa group server radius RADAuth
server 10.10.8.53
use-vrf management
source-interface mgmt0
hostname g6-nex
logging event link-status default
ip access-list SNMP
10 permit ip 10.10.3.0/24 any
20 permit ip 10.10.8.0/24 any
30 deny ip any any
ip access-list SSHlogin
10 permit ip 10.10.3.0/24 any
20 permit ip 10.10.8.0/24 any
30 deny ip any any
class-map type qos class-fcoe
class-map type queuing class-fcoe
match qos-group 1
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type network-qos class-fcoe
match qos-group 1
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
fex 104
pinning max-links 8
description "FEX0104"
fex 105
pinning max-links 8
description "FEX0105"
fex 106
pinning max-links 4
description "FEX0106"
fex 107
pinning max-links 4
description "FEX0107"
snmp-server location xxx
snmp-server host 10.10.8.14 traps version 2c g6-nex
snmp-server host 10.10.8.14 use-vrf management
snmp-server host 10.10.8.13 traps version 2c z6-nex
snmp-server host 10.10.8.13 use-vrf management
snmp-server enable traps callhome event-notify
snmp-server enable traps callhome smtp-send-fail
snmp-server enable traps cfs state-change-notif
snmp-server enable traps cfs merge-failure
snmp-server enable traps aaa server-state-change
snmp-server enable traps zone unsupp-mem
snmp-server enable traps upgrade UpgradeOpNotifyOnCompletion
snmp-server enable traps upgrade UpgradeJobStatusNotify
snmp-server enable traps feature-control FeatureOpStatusChange
snmp-server enable traps sysmgr cseFailSwCoreNotifyExtended
snmp-server enable traps config ccmCLIRunningConfigChanged
snmp-server enable traps snmp authentication
snmp-server enable traps vtp notifs
snmp-server enable traps vtp vlancreate
snmp-server enable traps vtp vlandelete
snmp-server enable traps poe portonoff
snmp-server enable traps poe pwrusageon
snmp-server enable traps poe pwrusageoff
snmp-server enable traps poe police
snmp-server community xxx group network-operator
snmp-server community xxx group network-admin
snmp-server community xxx use-acl SNMP
snmp-server community xxx use-acl SNMP
ntp server 10.10.8.53 use-vrf management
aaa authentication login default group RADAuth
aaa authentication login console group RADAuth
aaa accounting default group RADAuth
vrf context management
ip route 0.0.0.0/0 10.10.3.202
vlan 1
vlan 64
name BDRLAN_064_Server
vlan 1950
name BDRLAN_1950_VMKERNEL
vlan 1972
name BDRLAN_1972_SMN-Srv
vpc domain 99
peer-keepalive destination 10.10.3.130
interface port-channel10
description i=po10 Eth1/43 - 46, Eth2/13 - 16 s=z6-c65, g6-c65 t=Uplink VLAN64 vPC10
switchport mode trunk
vpc 10
switchport trunk allowed vlan 64
spanning-tree port type network
interface port-channel11
switchport mode trunk
vpc 11
switchport trunk allowed vlan 64
spanning-tree port type network
interface port-channel99
description i=po99 e1/47 e1/48 s=z6-nex u=po99 t=vPCpeerLink
switchport mode trunk
vpc peer-link
spanning-tree port type network
interface port-channel1001
description i=po1001 Eth104/1/1 - Eth100/1/1 t=Port-Channel
vpc 1001
switchport access vlan 64
interface port-channel1002
description i=po1002 Eth104/1/2 - Eth100/1/2 t=Port-Channel
vpc 1002
switchport access vlan 64
interface port-channel1003
description i=po1003 Eth104/1/3 - Eth100/1/3 t=Port-Channel
vpc 1003
switchport access vlan 64
interface port-channel1004
description i=po1004 Eth104/1/4 - Eth100/1/4 t=Port-Channel
vpc 1004
switchport access vlan 64
interface port-channel1005
description i=po1005 Eth104/1/5 - Eth100/1/5 t=Port-Channel
vpc 1005
switchport access vlan 64
interface port-channel1006
description i=po1006 Eth104/1/6 - Eth100/1/6 t=Port-Channel
vpc 1006
switchport access vlan 64
interface port-channel1007
description i=po1007 Eth104/1/7 - Eth100/1/7 t=Port-Channel
vpc 1007
switchport access vlan 64
interface port-channel1008
description i=po1008 Eth104/1/8 - Eth100/1/8 t=Port-Channel
vpc 1008
switchport access vlan 64
interface port-channel1009
description i=po1009 Eth104/1/9 - Eth100/1/9 t=Port-Channel
vpc 1009
switchport access vlan 64
interface port-channel1010
description i=po1010 Eth104/1/10 - Eth100/1/10 t=Port-Channel
vpc 1010
switchport access vlan 64
interface port-channel1011
description i=po1011 Eth104/1/11 - Eth100/1/11 t=Port-Channel
vpc 1011
switchport access vlan 64
interface port-channel1012
description i=po1012 Eth104/1/12 - Eth100/1/12 t=Port-Channel
vpc 1012
switchport access vlan 64
interface port-channel1013
description i=po1013 Eth104/1/13 - Eth100/1/13 t=Port-Channel
vpc 1013
switchport access vlan 64
interface port-channel1014
description i=po1014 Eth104/1/14 - Eth100/1/14 t=Port-Channel
vpc 1014
switchport access vlan 64
interface port-channel1015
description i=po1015 Eth104/1/15 - Eth100/1/15 t=Port-Channel
vpc 1015
switchport access vlan 64
interface port-channel1016
description i=po1016 Eth104/1/16 - Eth100/1/16 t=Port-Channel
vpc 1016
switchport access vlan 64
interface port-channel1101
description i=po1101 Eth105/1/1 - Eth101/1/1 t=Port-Channel
vpc 1101
switchport access vlan 64
interface port-channel1102
description i=po1102 Eth105/1/2 - Eth101/1/2 t=Port-Channel
vpc 1102
switchport access vlan 64
interface port-channel1103
description i=po1103 Eth105/1/3 - Eth101/1/3 t=Port-Channel
vpc 1103
switchport access vlan 64
interface port-channel1104
description i=po1104 Eth105/1/4 - Eth101/1/4 t=Port-Channel
vpc 1104
switchport access vlan 64
interface port-channel1105
description i=po1105 Eth105/1/5 - Eth101/1/5 t=Port-Channel
vpc 1105
switchport access vlan 64
interface port-channel1106
description i=po1106 Eth105/1/6 - Eth101/1/6 t=Port-Channel
vpc 1106
switchport access vlan 64
interface port-channel1107
description i=po1107 Eth105/1/7 - Eth101/1/7 t=Port-Channel
vpc 1107
switchport access vlan 64
interface port-channel1108
description i=po1108 Eth105/1/8 - Eth101/1/8 t=Port-Channel
vpc 1108
switchport access vlan 64
interface port-channel1109
description i=po1109 Eth105/1/9 - Eth101/1/9 t=Port-Channel
vpc 1109
switchport access vlan 64
interface port-channel1110
description i=po1110 Eth105/1/10 - Eth101/1/10 t=Port-Channel
vpc 1110
switchport access vlan 64
interface port-channel1111
description i=po1111 Eth105/1/11 - Eth101/1/11 t=Port-Channel
vpc 1111
switchport access vlan 64
interface port-channel1112
description i=po1112 Eth105/1/12 - Eth101/1/12 t=Port-Channel
vpc 1112
switchport access vlan 64
interface port-channel1113
description i=po1113 Eth105/1/13 - Eth101/1/13 t=Port-Channel
vpc 1113
switchport access vlan 64
interface port-channel1114
description i=po1114 Eth105/1/14 - Eth101/1/14 t=Port-Channel
vpc 1114
switchport access vlan 64
interface port-channel1115
description i=po1115 Eth105/1/15 - Eth101/1/15 t=Port-Channel
vpc 1115
switchport access vlan 64
interface port-channel1116
description i=po1116 Eth105/1/16 - Eth101/1/16 t=Port-Channel
vpc 1116
switchport access vlan 64
interface port-channel1201
description i=po1201 Eth106/1/1 - Eth102/1/1 t=Port-Channel
vpc 1201
switchport access vlan 1972
interface port-channel1202
description i=po1202 Eth106/1/2 - Eth102/1/2 t=Port-Channel
vpc 1202
switchport access vlan 1972
interface port-channel1203
description i=po1203 Eth106/1/3 - Eth102/1/3 t=Port-Channel
vpc 1203
switchport access vlan 1972
interface port-channel1204
description i=po1204 Eth106/1/4 - Eth102/1/4 t=Port-Channel
vpc 1204
switchport access vlan 1972
interface port-channel1205
description i=po1205 Eth106/1/5 - Eth102/1/5 t=Port-Channel
vpc 1205
switchport access vlan 1972
interface port-channel1206
description i=po1206 Eth106/1/6 - Eth102/1/6 t=Port-Channel
vpc 1206
switchport access vlan 1972
interface port-channel1207
description i=po1207 Eth106/1/7 - Eth102/1/7 t=Port-Channel
vpc 1207
switchport access vlan 1972
interface port-channel1208
description i=po1208 Eth106/1/8 - Eth102/1/8 t=Port-Channel
vpc 1208
switchport access vlan 1972
interface port-channel1209
description i=po1209 Eth106/1/9 - Eth102/1/9 t=Port-Channel
vpc 1209
switchport access vlan 1972
interface port-channel1210
description i=po1210 Eth106/1/10 - Eth102/1/10 t=Port-Channel
vpc 1210
switchport access vlan 1972
interface port-channel1211
description i=po1211 Eth106/1/11 - Eth102/1/11 t=Port-Channel
vpc 1211
switchport access vlan 1972
interface port-channel1212
description i=po1212 Eth106/1/12 - Eth102/1/12 t=Port-Channel
vpc 1212
switchport access vlan 1972
interface port-channel1213
description i=po1213 Eth106/1/13 - Eth102/1/13 t=Port-Channel
vpc 1213
switchport access vlan 1972
interface port-channel1214
description i=po1214 Eth106/1/14 - Eth102/1/14 t=Port-Channel
vpc 1214
switchport access vlan 1972
interface port-channel1215
description i=po1215 Eth106/1/15 - Eth102/1/15 t=Port-Channel
vpc 1215
switchport access vlan 1972
interface port-channel1216
description i=po1216 Eth106/1/16 - Eth102/1/16 t=Port-Channel
vpc 1216
switchport access vlan 1972
interface port-channel1217
description i=po1217 Eth106/1/17 - Eth102/1/17 t=Port-Channel
vpc 1217
switchport access vlan 1950
interface port-channel1218
description i=po1218 Eth106/1/18 - Eth102/1/18 t=Port-Channel
vpc 1218
switchport access vlan 1950
interface port-channel1219
description i=po1219 Eth106/1/19 - Eth102/1/19 t=Port-Channel
vpc 1219
switchport access vlan 1950
interface port-channel1220
description i=po1220 Eth106/1/20 - Eth102/1/20 t=Port-Channel
vpc 1220
switchport access vlan 1950
interface port-channel1221
description i=po1221 Eth106/1/21 - Eth102/1/21 t=Port-Channel
vpc 1221
switchport access vlan 1950
interface port-channel1222
description i=po1222 Eth106/1/22 - Eth102/1/22 t=Port-Channel
vpc 1222
switchport access vlan 1950
interface port-channel1223
description i=po1223 Eth106/1/23 - Eth102/1/23 t=Port-Channel
vpc 1223
switchport access vlan 1950
interface port-channel1224
description i=po1224 Eth106/1/24 - Eth102/1/24 t=Port-Channel
vpc 1224
switchport access vlan 1950
interface port-channel1225
description i=po1225 Eth106/1/25 - Eth102/1/25 t=Port-Channel
vpc 1225
switchport access vlan 1950
interface port-channel1226
description i=po1226 Eth106/1/26 - Eth102/1/26 t=Port-Channel
vpc 1226
switchport access vlan 1950
interface port-channel1227
description i=po1227 Eth106/1/27 - Eth102/1/27 t=Port-Channel
vpc 1227
switchport access vlan 1950
[K
interface port-channel1228
description i=po1228 Eth106/1/28 - Eth102/1/28 t=Port-Channel
vpc 1228
switchport access vlan 1950
interface port-channel1229
description i=po1229 Eth106/1/29 - Eth102/1/29 t=Port-Channel
vpc 1229
switchport access vlan 1950
interface port-channel1230
description i=po1230 Eth106/1/30 - Eth102/1/30 t=Port-Channel
vpc 1230
switchport access vlan 1950
interface port-channel1231
description i=po1231 Eth106/1/31 - Eth102/1/31 t=Port-Channel
vpc 1231
switchport access vlan 1950
interface port-channel1232
description i=po1232 Eth106/1/32 - Eth102/1/32 t=Port-Channel
vpc 1232
switchport access vlan 1950
interface port-channel1301
description i=po1301 Eth107/1/1 - Eth103/1/1 t=Port-Channel
vpc 1301
switchport access vlan 1972
interface port-channel1302
description i=po1302 Eth107/1/2 - Eth103/1/2 t=Port-Channel
vpc 1302
switchport access vlan 1972
interface port-channel1303
description i=po1303 Eth107/1/3 - Eth103/1/3 t=Port-Channel
vpc 1303
switchport access vlan 1972
interface port-channel1304
description i=po1304 Eth107/1/4 - Eth103/1/4 t=Port-Channel
vpc 1304
switchport access vlan 1972
interface port-channel1305
description i=po1305 Eth107/1/5 - Eth103/1/5 t=Port-Channel
vpc 1305
switchport access vlan 1972
interface port-channel1306
description i=po1306 Eth107/1/6 - Eth103/1/6 t=Port-Channel
vpc 1306
switchport access vlan 1972
interface port-channel1307
description i=po1307 Eth107/1/7 - Eth103/1/7 t=Port-Channel
vpc 1307
switchport access vlan 1972
interface port-channel1308
description i=po1308 Eth107/1/8 - Eth103/1/8 t=Port-Channel
vpc 1308
switchport access vlan 1972
interface port-channel1309
description i=po1309 Eth107/1/9 - Eth103/1/9 t=Port-Channel
vpc 1309
switchport access vlan 1972
interface port-channel1310
description i=po1310 Eth107/1/10 - Eth103/1/10 t=Port-Channel
vpc 1310
switchport access vlan 1972
interface port-channel1311
description i=po1311 Eth107/1/11 - Eth103/1/11 t=Port-Channel
vpc 1311
switchport access vlan 1972
interface port-channel1312
description i=po1312 Eth107/1/12 - Eth103/1/12 t=Port-Channel
vpc 1312
switchport access vlan 1972
interface port-channel1313
description i=po1313 Eth107/1/13 - Eth103/1/13 t=Port-Channel
vpc 1313
switchport access vlan 1972
interface port-channel1314
description i=po1314 Eth107/1/14 - Eth103/1/14 t=Port-Channel
vpc 1314
switchport access vlan 1972
interface port-channel1315
description i=po1315 Eth107/1/15 - Eth103/1/15 t=Port-Channel
vpc 1315
switchport access vlan 1972
interface port-channel1316
description i=po1316 Eth107/1/16 - Eth103/1/16 t=Port-Channel
vpc 1316
switchport access vlan 1972
interface port-channel1317
description i=po1317 Eth107/1/17 - Eth103/1/17 t=Port-Channel
vpc 1317
switchport access vlan 1950
interface port-channel1318
description i=po1318 Eth107/1/18 - Eth103/1/18 t=Port-Channel
vpc 1318
switchport access vlan 1950
interface port-channel1319
description i=po1319 Eth107/1/19 - Eth103/1/19 t=Port-Channel
vpc 1319
switchport access vlan 1950
interface port-channel1320
description i=po1320 Eth107/1/20 - Eth103/1/20 t=Port-Channel
vpc 1320
switchport access vlan 1950
interface port-channel1321
description i=po1321 Eth107/1/21 - Eth103/1/21 t=Port-Channel
vpc 1321
switchport access vlan 1950
interface port-channel1322
description i=po1322 Eth107/1/22 - Eth103/1/22 t=Port-Channel
vpc 1322
switchport access vlan 1950
interface port-channel1323
description i=po1323 Eth107/1/23 - Eth103/1/23 t=Port-Channel
vpc 1323
switchport access vlan 1950
interface port-channel1324
description i=po1324 Eth107/1/24 - Eth103/1/24 t=Port-Channel
vpc 1324
switchport access vlan 1950
interface port-channel1325
description i=po1325 Eth107/1/25 - Eth103/1/25 t=Port-Channel
vpc 1325
switchport access vlan 1950
interface port-channel1326
description i=po1326 Eth107/1/26 - Eth103/1/26 t=Port-Channel
vpc 1326
switchport access vlan 1950
interface port-channel1327
description i=po1327 Eth107/1/27 - Eth103/1/27 t=Port-Channel
vpc 1327
switchport access vlan 1950
interface port-channel1328
description i=po1328 Eth107/1/28 - Eth103/1/28 t=Port-Channel
vpc 1328
switchport access vlan 1950
interface port-channel1329
description i=po1329 Eth107/1/29 - Eth103/1/29 t=Port-Channel
vpc 1329
switchport access vlan 1950
interface port-channel1330
description i=po1330 Eth107/1/30 - Eth103/1/30 t=Port-Channel
vpc 1330
switchport access vlan 1950
interface port-channel1331
description i=po1331 Eth107/1/31 - Eth103/1/31 t=Port-Channel
vpc 1331
switchport access vlan 1950
interface port-channel1332
description i=po1332 Eth107/1/32 - Eth103/1/32 t=Port-Channel
vpc 1332
switchport access vlan 1950
interface Ethernet1/1
description i=e1/01 s=FEX104-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 104
interface Ethernet1/2
description i=e1/02 s=FEX104-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 104
interface Ethernet1/3
description i=e1/03 s=FEX104-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 104
interface Ethernet1/4
description i=e1/04 s=FEX104-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 104
interface Ethernet1/5
description i=e1/05 s=FEX104-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 104
interface Ethernet1/6
description i=e1/06 s=FEX104-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 104
interface Ethernet1/7
description i=e1/07 s=FEX104-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 104
interface Ethernet1/8
description i=e1/08 s=FEX104-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 104
interface Ethernet1/9
description i=e1/09 s=FEX105-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 105
interface Ethernet1/10
description i=e1/10 s=FEX105-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 105
interface Ethernet1/11
description i=e1/11 s=FEX105-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 105
interface Ethernet1/12
description i=e1/12 s=FEX105-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 105
interface Ethernet1/13
description i=e1/13 s=FEX105-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 105
interface Ethernet1/14
description i=e1/14 s=FEX105-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 105
interface Ethernet1/15
description i=e1/15 s=FEX105-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 105
interface Ethernet1/16
description i=e1/16 s=FEX105-10GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 105
interface Ethernet1/17
description i=e1/17 s=FEX106-1GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 106
interface Ethernet1/18
description i=e1/18 s=FEX106-1GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 106
interface Ethernet1/19
description i=e1/19 s=FEX106-1GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 106
interface Ethernet1/20
description i=e1/20 s=FEX106-1GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 106
interface Ethernet1/21
description i=e1/21 s=FEX107-1GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 107
interface Ethernet1/22
description i=e1/22 s=FEX107-1GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 107
interface Ethernet1/23
description i=e1/23 s=FEX107-1GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 107
interface Ethernet1/24
description i=e1/24 s=FEX107-1GB t=FEX-Uplink
switchport mode fex-fabric
fex associate 107
interface Ethernet1/25
interface Ethernet1/26
interface Ethernet1/27
interface Ethernet1/28
interface Ethernet1/29
interface Ethernet1/30
interface Ethernet1/31
interface Ethernet1/32
interface Ethernet1/33
interface Ethernet1/34
interface Ethernet1/35
interface Ethernet1/36
interface Ethernet1/37
interface Ethernet1/38
interface Ethernet1/39
interface Ethernet1/40
interface Ethernet1/41
description i=e1/41 s=s6-4-smn1 gi1/0/52 v=1950,1972
switchport mode trunk
switchport trunk allowed vlan 1950,1972
speed 1000
interface Ethernet1/42
interface Ethernet1/43
description i=Eth1/43 s=z6-c65 gi2/23 t=trunk v=64
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/44
description i=Eth1/44 s=z6-c65 gi2/24 t=trunk v=64
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/45
description i=Eth1/45 s=g6-c65 gi2/19 t=trunk v=64
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/46
description i=Eth1/46 s=g6-c65 gi2/20 t=trunk v=64
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet1/47
description i=e1/47 s=z6-nex u=e1/47 t=vPCpeerLink-Domain99
switchport mode trunk
channel-group 99
interface Ethernet1/48
description i=e1/48 s=z6-nex u=e1/48 t=vPCpeerLink-Domain99
switchport mode trunk
udld aggressive
channel-group 99
interface Ethernet2/1
interface Ethernet2/2
interface Ethernet2/3
interface Ethernet2/4
interface Ethernet2/5
interface Ethernet2/6
interface Ethernet2/7
interface Ethernet2/8
interface Ethernet2/9
interface Ethernet2/10
interface Ethernet2/11
interface Ethernet2/12
interface Ethernet2/13
description i=Eth2/13 s=z6-c65 gi2/21 t=trunk v=64
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet2/14
description i=Eth2/14 s=z6-c65 gi2/22 t=trunk v=64
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet2/15
description i=Eth2/15 s=g6-c65 gi2/17 t=trunk v=64
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface Ethernet2/16
description i=Eth2/16 s=g6-c65 gi2/18 t=trunk v=64
switchport mode trunk
switchport trunk allowed vlan 64
spanning-tree port type network
speed 1000
udld aggressive
channel-group 10 mode active
interface mgmt0
ip address 10.10.3.131/24
interface Ethernet104/1/1
description i=Eth104/1/1 h=ESX01a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1001
interface Ethernet104/1/2
description i=Eth104/1/2 h=ESX02a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1002
interface Ethernet104/1/3
description i=Eth104/1/3 h=ESX03a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1003
interface Ethernet104/1/4
description i=Eth104/1/4 h=ESX04a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1004
interface Ethernet104/1/5
description i=Eth104/1/5 h=ESX05a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1005
interface Ethernet104/1/6
description i=Eth104/1/6 h=ESX06a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1006
interface Ethernet104/1/7
description i=Eth104/1/7 h=ESX06a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1007
interface Ethernet104/1/8
description i=Eth104/1/8 h=ESX09a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1008
interface Ethernet104/1/9
description i=Eth104/1/9 h=ESX10a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1009
interface Ethernet104/1/10
description i=Eth104/1/10 h=ESX11a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1010
interface Ethernet104/1/11
description i=Eth104/1/11 h=ESX12a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1011
interface Ethernet104/1/12
description i=Eth104/1/12 h=ESX13a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1012
interface Ethernet104/1/13
description i=Eth104/1/13 h=ESX14a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1013
interface Ethernet104/1/14
description i=Eth104/1/14 h=ESX15a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1014
interface Ethernet104/1/15
description i=Eth104/1/15 h=ESX15a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1015
interface Ethernet104/1/16
description i=Eth104/1/16 h=ESX16a t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1016
interface Ethernet104/1/17
shutdown
interface Ethernet104/1/18
shutdown
interface Ethernet104/1/19
shutdown
interface Ethernet104/1/20
shutdown
interface Ethernet104/1/21
shutdown
interface Ethernet104/1/22
shutdown
interface Ethernet104/1/23
shutdown
interface Ethernet104/1/24
shutdown
interface Ethernet104/1/25
shutdown
interface Ethernet104/1/26
shutdown
interface Ethernet104/1/27
shutdown
interface Ethernet104/1/28
shutdown
interface Ethernet104/1/29
shutdown
interface Ethernet104/1/30
shutdown
interface Ethernet104/1/31
shutdown
interface Ethernet104/1/32
shutdown
interface Ethernet105/1/1
description i=Eth105/1/1 h=ESX01b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1101
interface Ethernet105/1/2
description i=Eth105/1/2 h=ESX02b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1102
interface Ethernet105/1/3
description i=Eth105/1/3 h=ESX03b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1103
interface Ethernet105/1/4
description i=Eth105/1/4 h=ESX04b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1104
interface Ethernet105/1/5
description i=Eth105/1/5 h=ESX05b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1105
interface Ethernet105/1/6
description i=Eth105/1/6 h=ESX06b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1106
interface Ethernet105/1/7
description i=Eth105/1/7 h=ESX07b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1107
interface Ethernet105/1/8
description i=Eth105/1/8 h=ESX08b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1108
interface Ethernet105/1/9
description i=Eth105/1/9 h=ESX09b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1109
interface Ethernet105/1/10
description i=Eth105/1/10 h=ESX10b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1110
interface Ethernet105/1/11
description i=Eth105/1/11 h=ESX11b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1111
interface Ethernet105/1/12
description i=Eth105/1/12 h=ESX12b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1112
interface Ethernet105/1/13
description i=Eth105/1/13 h=ESX13b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1113
interface Ethernet105/1/14
description i=Eth105/1/14 h=ESX14b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1114
interface Ethernet105/1/15
description i=Eth105/1/15 h=ESX15b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1115
interface Ethernet105/1/16
description i=Eth105/1/16 h=ESX16b t=Port-Channel
switchport access vlan 64
spanning-tree port type edge
channel-group 1116
interface Ethernet105/1/17
shutdown
interface Ethernet105/1/18
shutdown
interface Ethernet105/1/19
shutdown
interface Ethernet105/1/20
shutdown
interface Ethernet105/1/21
shutdown
interface Ethernet105/1/22
shutdown
interface Ethernet105/1/23
shutdown
interface Ethernet105/1/24
shutdown
interface Ethernet105/1/25
shutdown
interface Ethernet105/1/26
shutdown
interface Ethernet105/1/27
shutdown
interface Ethernet105/1/28
shutdown
interface Ethernet105/1/29
shutdown
interface Ethernet105/1/30
shutdown
interface Ethernet105/1/31
shutdown
interface Ethernet105/1/32
shutdown
interface Ethernet106/1/1
description i=Eth106/1/1 h=ESX01a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1201
interface Ethernet106/1/2
description i=Eth106/1/2 h=ESX02a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1202
interface Ethernet106/1/3
description i=Eth106/1/3 h=ESX03a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1203
interface Ethernet106/1/4
description i=Eth106/1/4 h=ESX04a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1204
interface Ethernet106/1/5
description i=Eth106/1/6 h=ESX05a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1205
interface Ethernet106/1/6
description i=Eth106/1/6 h=ESX06a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1206
interface Ethernet106/1/7
description i=Eth106/1/7 h=ESX07a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1207
interface Ethernet106/1/8
description i=Eth106/1/8 h=ESX08a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1208
interface Ethernet106/1/9
description i=Eth106/1/9 h=ESX09a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1209
interface Ethernet106/1/10
description i=Eth106/1/10 h=ESX10a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1210
interface Ethernet106/1/11
description i=Eth106/1/11 h=ESX11a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1211
interface Ethernet106/1/12
description i=Eth106/1/12 h=ESX12a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1212
interface Ethernet106/1/13
description i=Eth106/1/13 h=ESX13a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1213
interface Ethernet106/1/14
description i=Eth106/1/14 h=ESX14a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1214
interface Ethernet106/1/15
description i=Eth106/1/15 h=ESX15a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1215
interface Ethernet106/1/16
description i=Eth106/1/16 h=ESX16a t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1216
interface Ethernet106/1/17
description i=Eth106/1/17 h=ESX1a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1217
interface Ethernet106/1/18
description i=Eth106/1/18 h=ESX2a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1218
interface Ethernet106/1/19
description i=Eth106/1/19 h=ESX3a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1219
interface Ethernet106/1/20
description i=Eth106/1/20 h=ESX4a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1220
interface Ethernet106/1/21
description i=Eth106/1/20 h=ESX5a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1221
interface Ethernet106/1/22
description i=Eth106/1/22 h=ESX6a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1222
interface Ethernet106/1/23
description i=Eth106/1/23 h=ESX7a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1223
interface Ethernet106/1/24
description i=Eth106/1/24 h=ESX8a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1224
interface Ethernet106/1/25
description i=Eth106/1/25 h=ESX9a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1225
interface Ethernet106/1/26
description i=Eth106/1/26 h=ESX10a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1226
interface Ethernet106/1/27
description i=Eth106/1/27 h=ESX11a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1227
interface Ethernet106/1/28
description i=Eth106/1/28 h=ESX12a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1228
interface Ethernet106/1/29
description i=Eth106/1/29 h=ESX13a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1229
interface Ethernet106/1/30
description i=Eth106/1/30 h=ESX14a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1230
interface Ethernet106/1/31
description i=Eth106/1/31 h=ESX15a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1231
interface Ethernet106/1/32
description i=Eth106/1/32 h=ESX16a t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1232
interface Ethernet106/1/33
shutdown
interface Ethernet106/1/34
shutdown
interface Ethernet106/1/35
shutdown
interface Ethernet106/1/36
shutdown
interface Ethernet106/1/37
shutdown
interface Ethernet106/1/38
shutdown
interface Ethernet106/1/39
shutdown
interface Ethernet106/1/40
shutdown
interface Ethernet106/1/41
shutdown
interface Ethernet106/1/42
shutdown
interface Ethernet106/1/43
shutdown
interface Ethernet106/1/44
shutdown
interface Ethernet106/1/45
shutdown
interface Ethernet106/1/46
shutdown
interface Ethernet106/1/47
shutdown
interface Ethernet106/1/48
shutdown
interface Ethernet107/1/1
description i=Eth107/1/1 h=ESX1b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1301
interface Ethernet107/1/2
description i=Eth107/1/2 h=ESX2b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1302
interface Ethernet107/1/3
description i=Eth107/1/3 h=ESX3b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1303
interface Ethernet107/1/4
description i=Eth107/1/4 h=ESX4b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1304
interface Ethernet107/1/5
description i=Eth107/1/5 h=ESX5b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1305
interface Ethernet107/1/6
description i=Eth107/1/6 h=ESX6b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1306
interface Ethernet107/1/7
description i=Eth107/1/7 h=ESX7b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1307
interface Ethernet107/1/8
description i=Eth107/1/8 h=ESX8b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1308
interface Ethernet107/1/9
description i=Eth107/1/9 h=ESX9b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1309
interface Ethernet107/1/10
description i=Eth107/1/10 h=ESX10b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1310
interface Ethernet107/1/11
description i=Eth107/1/11 h=ESX11b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1311
interface Ethernet107/1/12
description i=Eth107/1/12 h=ESX12b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1312
interface Ethernet107/1/13
description i=Eth107/1/13 h=ESX13b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1313
interface Ethernet107/1/14
description i=Eth107/1/14 h=ESX14b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1314
interface Ethernet107/1/15
description i=Eth107/1/15 h=ESX15b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1315
interface Ethernet107/1/16
description i=Eth107/1/16 h=ESX16b t=Port-Channel
switchport access vlan 1972
spanning-tree port type edge
channel-group 1316
interface Ethernet107/1/17
description i=Eth107/1/17 h=ESX01b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1317
interface Ethernet107/1/18
description i=Eth107/1/18 h=ESX02b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1318
interface Ethernet107/1/19
description i=Eth107/1/19 h=ESX03b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1319
interface Ethernet107/1/20
description i=Eth107/1/20 h=ESX04b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1320
interface Ethernet107/1/21
description i=Eth107/1/21 h=ESX05b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1321
interface Ethernet107/1/22
description i=Eth107/1/22 h=ESX06b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1322
interface Ethernet107/1/23
description i=Eth107/1/23 h=ESX07b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1323
interface Ethernet107/1/24
description i=Eth107/1/24 h=ESX08b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1324
interface Ethernet107/1/25
description i=Eth107/1/25 h=ESX09b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1325
interface Ethernet107/1/26
description i=Eth107/1/26 h=ESX10b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1326
interface Ethernet107/1/27
description i=Eth107/1/27 h=ESX11b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1327
interface Ethernet107/1/28
description i=Eth107/1/28 h=ESX12b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1328
interface Ethernet107/1/29
description i=Eth107/1/29 h=ESX13b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1329
interface Ethernet107/1/30
description i=Eth107/1/30 h=ESX14b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1330
interface Ethernet107/1/31
description i=Eth107/1/31 h=ESX15b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1331
interface Ethernet107/1/32
description i=Eth107/1/32 h=ESX16b t=Port-Channel
switchport access vlan 1950
spanning-tree port type edge
channel-group 1332
interface Ethernet107/1/33
shutdown
interface Ethernet107/1/34
shutdown
interface Ethernet107/1/35
shutdown
interface Ethernet107/1/36
shutdown
interface Ethernet107/1/37
shutdown
interface Ethernet107/1/38
shutdown
interface Ethernet107/1/39
shutdown
interface Ethernet107/1/40
shutdown
interface Ethernet107/1/41
shutdown
interface Ethernet107/1/42
shutdown
interface Ethernet107/1/43
shutdown
interface Ethernet107/1/44
shutdown
interface Ethernet107/1/45
shutdown
interface Ethernet107/1/46
shutdown
interface Ethernet107/1/47
shutdown
interface Ethernet107/1/48
shutdown
clock timezone CET 1 0
clock summer-time CEST 5 sunday march 02:00 5 sunday october 03:00 60
cli alias name wr copy run start
line console
line vty
access-class SSHlogin in
boot kickstart bootflash:/n5000-uk9-kickstart.5.0.3.N2.2.bin
boot system bootflash:/n5000-uk9.5.0.3.N2.2.bin
ip radius source-interface mgmt0
logging server 10.10.8.30 6
logging server 10.10.8.13 6
logging monitor 6
logging monitor 6
z6-nex# sh run
Communication could not be established with the process
!Command: show running-config
!Time: Thu Nov 17 15:40:15 2011
version 5.0(3)N2(2)
no feature telnet
no telnet server enable
cfs eth distribute
feature udld
feature lacp
feature vpc
feature lldp
feature fex
username xxx password 5 xxx role network-admin
username xxx password 5 xxx role network-admin
ip domain-lookup
radius-server key 7 xxx
radius-server timeout 3
radius-server retransmit 2
radius-server host 10.10.8.53 auth-port 1645 acct-port 1646 authentication accounting
aaa group server radius RADAuth
server 10.10.8.53
use-vrf management
source-interface mgmt0
hostname z6-nex
logging event link-status default
ip access-list SNMP
10 permit ip 10.10.3.0/24 any
20 permit ip 10.10.8.0/24 any
30 deny ip any any
ip access-list SSHlogin
10 permit ip 10.10.3.0/24 any
20 permit ip 10.10.8.0/24 any
30 deny ip any any
class-map type qos class-fcoe
class-map type queuing class-fcoe
match qos-group 1
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type network-qos class-fcoe
match qos-group 1
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
fex 100
pinning max-links 8
description "FEX0100"
fex 101
pinning max-links 8
description "FEX0101"
fex 102
pinning max-links 4
description "FEX0102"
fex 103
pinning max-links 4
description "FEX0103"
snmp-server location
snmp-server host 10.10.8.14 traps version 2c z6-nex
snmp-server host 10.10.8.14 use-vrf management
snmp-server host 10.10.8.13 traps version 2c z6-nex
snmp-server host 10.10.8.13 use-vrf management
snmp-server enable traps entity fru
snmp-server enable traps callhome event-notify
snmp-server enable traps callhome smtp-send-fail
snmp-server enable traps cfs state-change-notif
snmp-server enable traps cfs merge-failure
snmp-server enable traps aaa server-state-change
snmp-server enable traps zone unsupp-mem
snmp-server enable traps upgrade UpgradeOpNotifyOnCompletion
snmp-server enable traps upgrade UpgradeJobStatusNotify
snmp-server enable traps feature-control FeatureOpStatusChange
snmp-server enable traps sysmgr cseFailSwCoreNotifyExtended
snmp-server enable traps config ccmCLIRunningConfigChanged
snmp-server enable traps snmp authentication
snmp-server enable traps vtp notifs
snmp-server enable traps vtp vlancreate
snmp-server enable traps vtp vlandelete
snmp-server enable traps poe portonoff
snmp-server enable traps poe pwrusageon
snmp-server enable traps poe pwrusageoff
snmp-server enable traps poe police
snmp-server community xxx group network-operator
snmp-server community xxx group network-admin
snmp-server community xxx use-acl SNMP
snmp-server community xxx use-acl SNMP
ntp server 10.10.8.53 use-vrf management
aaa authentication login default group RADAuth
aaa authentication login console group RADAuth
aaa accounting default group RADAuth
vrf context management
ip route 0.0.0.0/0 10.10.3.202
vlan 1
vlan 64
name BDRLAN_064_Server
vlan 1950
name BDRLAN_1950_VMKERNEL
vlan 1972
name BDRLAN_1972_SMN-Srv
vpc domain 99
role priority 1000
peer-keepalive destination 10.10.3.131
interface port-channel10
description i=po10 Eth1/43 - 46, Eth2/13 - 16 s=z6-c65, g6-c65 t=Uplink VLAN64 vPC10
switchport mode trunk
vpc 10
switchport trunk allowed vlan 64
spanning-tree port type network
interface port-channel11
switchport mode trunk
vpc 11
switchport trunk allowed vlan 64
spanning-tree port type network
interface port-channel99
description i=po99 e1/47 e1/48 s=g6-nex u=po99 t=vPCpeerLink
switchport mode trunk
vpc peer-link
spanning-tree port type network
interface port-channel1001
description i=po1001 Eth100/1/1 - Eth104/1/1 t=Port-Channel
vpc 1001
switchport access vlan 64
interface port-channel1002
description i=po1002 Eth100/1/2 - Eth104/1/2 t=Port-Channel
vpc 1002
switchport access vlan 64
interface port-channel1003
description i=po1003 Eth100/1/3 - Eth104/1/3 t=Port-Channel
vpc 1003
switchport access vlan 64
interface port-channel1004
description i=po1004 Eth100/1/4 - Eth104/1/4 t=Port-Channel
vpc 1004
switchport access vlan 64
interface port-channel1005
description i=po1005 Eth100/1/5 - Eth104/1/5 t=Port-Channel
vpc 1005
switchport access vlan 64
interface port-channel1006
description i=po1006 Eth100/1/6 - Eth104/1/6 t=Port-Channel
vpc 1006
switchport access vlan 64
interface port-channel1007
description i=po1007 Eth100/1/7 - Eth104/1/7 t=Port-Channel
vpc 1007
switchport access vlan 64
interface port-channel1008
description i=po1008 Eth100/1/8 - Eth104/1/8 t=Port-Channel
vpc 1008
switchport access vlan 64
[K
interface port-channel1009
description i=po1009 Eth100/1/9 - Eth104/1/9 t=Port-Channel
vpc 1009
switchport access vlan 64
interface port-channel1010
description i=po1010 Eth100/1/10 - Eth104/1/10 t=Port-Channel
vpc 1010
switchport access vlan 64
interface port-channel1011
description i=po1011 Eth100/1/11 - Eth104/1/11 t=Port-Channel
vpc 1011
switchport access vlan 64
interface port-channel1012
description i=po1012 Eth100/1/12 - Eth104/1/12 t=Port-Channel
vpc 1012
switchport access vlan 64
interface port-channel1013
description i=po1013 Eth100/1/13 - Eth104/1/13 t=Port-Channel
vpc 1013
switchport access vlan 64
interface port-channel1014
description i=po1014 Eth100/1/14 - Eth104/1/14 t=Port-Channel
vpc 1014
switchport access vlan 64
interface port-channel1015
description i=po1015 Eth100/1/15 - Eth104/1/15 t=Port-Channel
vpc 1015
switchport access vlan 64
interface port-channel1016
description i=po1016 Eth100/1/16 - Eth104/1/16 t=Port-Channel
vpc 1016
switchport access vlan 64
interface port-channel1101
description i=po1101 Eth101/1/1 - Eth105/1/1 t=Port-Channel
vpc 1101
switchport access vlan 64
interface port-channel1102
description i=po1102 Eth101/1/2 - Eth105/1/2 t=Port-Channel
vpc 1102
switchport access vlan 64
interface port-channel1103
description i=po1103 Eth101/1/3 - Eth105/1/3 t=Port-Channel
vpc 1103
switchport access vlan 64
interface port-channel1104
description i=po1104 Eth101/1/4 - Eth105/1/4 t=Port-Channel
vpc 1104
switchport access vlan 64
interface port-channel1105
description i=po1105 Eth101/1/5 - Eth105/1/5 t=Port-Channel
vpc 1105
switchport access vlan 64
interface port-channel1106
description i=po1106 Eth101/1/6 - Eth105/1/6 t=Port-Channel
vpc 1106
switchport access vlan 64
interface port-channel1107
description i=po1107 Eth101/1/7 - Eth105/1/7 t=Port-Channel
vpc 1107
switchport access vlan 64
interface port-channel1108
description i=po1108 Eth101/1/8 - Eth105/1/8 t=Port-Channel
vpc 1108
switchport access vlan 64
interface port-channel1109
description i=po1109 Eth101/1/9 - Eth105/1/9 t=Port-Channel
vpc 1109
switchport access vlan 64 -
Hello,
I have problem with vPC`+ in N5K. I think that all my setup it's ok but my peers are not reachables in fabricpath in the vpc domain.
n5k-del-1(config)# show vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 21
vPC+ switch id : 121
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
vPC fabricpath status : peer is not reachable through fabricpath
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : primary
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled (timeout = 240 seconds)
vPC Peer-link status
id Port Status Active vlans
1 Po1 up -
n5k-del-2(config)# show vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 21
vPC+ switch id : 121
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
vPC fabricpath status : peer is not reachable through fabricpath
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : secondary
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled (timeout = 240 seconds)
vPC Peer-link status
id Port Status Active vlans
1 Po1 up -
n5k-del-1(config)# show run int port-channel 1
!Command: show running-config interface port-channel1
!Time: Tue Mar 3 12:31:16 2009
version 6.0(2)N2(3)
interface port-channel1
switchport mode fabricpath
spanning-tree port type network
vpc peer-link
n5k-del-1(config)# show port-channel summary
Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
M - Not in use. Min-links not met
Group Port- Type Protocol Member Ports
Channel
1 Po1(SU) Eth LACP Eth1/1(P) Eth1/2(P) Eth1/17(P)
Eth1/18(P)
n5k-del-2(config)# show run int port-channel 1
!Command: show running-config interface port-channel1
!Time: Tue Mar 3 12:33:57 2009
version 6.0(2)N2(3)
interface port-channel1
switchport mode fabricpath
spanning-tree port type network
vpc peer-link
n5k-del-2(config)# show port-channel summary
Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
M - Not in use. Min-links not met
Group Port- Type Protocol Member Ports
Channel
1 Po1(SU) Eth LACP Eth1/1(P) Eth1/2(P) Eth1/17(P)
Eth1/18(P)
n5k-del-1(config)# show run fabricpath
!Command: show running-config fabricpath
!Time: Tue Mar 3 12:32:02 2009
version 6.0(2)N2(3)
install feature-set fabricpath
feature-set fabricpath
vpc domain 21
fabricpath switch-id 121
interface port-channel1
switchport mode fabricpath
interface Ethernet1/1
switchport mode fabricpath
interface Ethernet1/2
switchport mode fabricpath
interface Ethernet1/17
switchport mode fabricpath
interface Ethernet1/18
switchport mode fabricpath
fabricpath domain default
fabricpath switch-id 21
n5k-del-2(config)# show run fabricpath
!Command: show running-config fabricpath
!Time: Tue Mar 3 12:31:17 2009
version 6.0(2)N2(3)
install feature-set fabricpath
feature-set fabricpath
vpc domain 21
fabricpath switch-id 121
interface port-channel1
switchport mode fabricpath
interface Ethernet1/1
switchport mode fabricpath
interface Ethernet1/2
switchport mode fabricpath
interface Ethernet1/17
switchport mode fabricpath
interface Ethernet1/18
switchport mode fabricpath
fabricpath domain default
fabricpath switch-id 22
n5k-del-1(config)# show run vpc
!Command: show running-config vpc
!Time: Tue Mar 3 12:36:23 2009
version 6.0(2)N2(3)
feature vpc
vpc domain 21
role priority 100
peer-keepalive destination 10.0.0.22 source 10.0.0.21
auto-recovery
fabricpath switch-id 121
ip arp synchronize
interface port-channel1
vpc peer-link
n5k-del-2(config)# show run vpc
!Command: show running-config vpc
!Time: Tue Mar 3 12:36:01 2009
version 6.0(2)N2(3)
feature vpc
vpc domain 21
role priority 110
peer-keepalive destination 10.0.0.21 source 10.0.0.22
auto-recovery
fabricpath switch-id 121
ip arp synchronize
interface port-channel1
vpc peer-link
any idea?
Best RegardsHi,
The issue you have is that you don't have any VLANs configured and operating in FabricPath mode i.e.,
!vlan 100 mode fabricpath!
I just set this up using your configuration and see exactly the same behavior until a VLAN is created that then has mode fabricpath configured.
If you look at the peer-link state in the FabricPath topology and active the VLANs I think you'll see the forwarding state of the interface is DOWN and there are no active VLANs.
N5K-p10-1# sh fabricpath isis interface port-channel 101Fabricpath IS-IS domain: defaultInterface: port-channel101 Status: protocol-up/link-up/admin-up Index: 0x0001, Local Circuit ID: 0x01, Circuit Type: L1 No authentication type/keychain configured Authentication check specified Extended Local Circuit ID: 0x16000064, P2P Circuit ID: 0000.0000.0000.00 Retx interval: 5, Retx throttle interval: 66 ms LSP interval: 33 ms, MTU: 1500 P2P Adjs: 1, AdjsUp: 1, Priority 64 Hello Interval: 10, Multi: 3, Next IIH: 00:00:03 Level Adjs AdjsUp Metric CSNP Next CSNP Last LSP ID 1 1 1 20 60 00:00:35 ffff.ffff.ffff.ff-ff Topologies enabled: Topology Metric MetricConfig Forwarding 0 20 no DOWNN5K-p10-1# sh fabricpath topology interface port-channel 101Interface Topo-Description Topo-ID Topo-IF-State------------------- -------------------------------- ---------- -------------port-channel101 0 0 DownN5K-p10-1# sh fabricpath topology vlan activeTopo-Description Topo-ID Active VLAN List-------------------------------- --------- -------------------------------------0 0 --
If you then change the VLAN mode from mode ce to mode fabricpath (note that you need to exit the vlan configuration mode for the change to take effect), you should see the following SYSLOG message:
2014 Feb 3 12:50:23 N5K-p10-1 %ETHPORT-3-IF_ERROR_VLANS_REMOVED: VLANs 99-100 on Interface port-channel101 are removed from suspended state.2014 Feb 3 12:50:23 N5K-p10-1 %L3VM-5-FP_TPG_INTF_UP: Interface port-channel101 up in fabricpath topology 0
And then show vpc will indicate that the vPC fabricpath status as "peer is reachable through fabricpath"
N5K-p10-1# sh vpcLegend: (*) - local vPC is down, forwarding via vPC peer-linkvPC domain id : 21vPC+ switch id : 121Peer status : peer adjacency formed okvPC keep-alive status : peer is alivevPC fabricpath status : peer is reachable through fabricpath[snip]N5K-p10-1# show fabricpath isis interface port-channel 101
Fabricpath IS-IS domain: default
Interface: port-channel101
Status: protocol-up/link-up/admin-up
Index: 0x0001, Local Circuit ID: 0x01, Circuit Type: L1
No authentication type/keychain configured
Authentication check specified
Extended Local Circuit ID: 0x16000064, P2P Circuit ID: 0000.0000.0000.00
Retx interval: 5, Retx throttle interval: 66 ms
LSP interval: 33 ms, MTU: 1500
P2P Adjs: 1, AdjsUp: 1, Priority 64
Hello Interval: 10, Multi: 3, Next IIH: 00:00:01
Level Adjs AdjsUp Metric CSNP Next CSNP Last LSP ID
1 1 1 20 60 00:00:47 ffff.ffff.ffff.ff-ff
Topologies enabled:
Topology Metric MetricConfig Forwarding
0 20 no UP
TN5K-p10-1# show fabricpath topology vlan active
Topo-Description Topo-ID Active VLAN List
0 0 99-100
Regards
Maybe you are looking for
-
With iTunes 10.3. Startup now 40% longer. Why?
I just installed the new iTunes on my MacBook Air. Startup now takes 40% longer. It used to start up in 9 seconds from Apple logo. Now 14 secs. What happened, and how can it be remedied?.
-
Embedding a java program which requires one parameter to an applet
I have a java program which requires one parameter for running it such as; "java program.java 34" .I must use this program as an applet. How can I send this parameter during running the applet. "appletviewer program.html" ???
-
Managing Runtime Attachments Using the GP API
Hi All, I have a requirement to read the files which are attached to a process at GP Runtime, through GP API. For this i am trying to get the resolveAttachmentInfo method from IGPAttachmentSourceHandler class. I have imported both the packages GPAt
-
How do i group the columns of a table for a given row?
Hi, I have a situation where i need to display a table that has a column for every day of a given period of time. But the first two rows of the table should be grouped in such a way that each cell of the first row covers the seven columns of the row
-
How to recieve emails in imessage?
How I can recieve emails in my imessage?