We are wondering about a vPC peer-switch setup whis states to be non-operational!
We are running a Cisco Nexus 7010 vPC pair against a Cisco 6500 VSS setup.
The VSS system is the root of the MST (STP).
We have enabled vPC peer-switch feature on the N7ks.
The two N7ks show the following STP states:
nex7010-1# sh spanning-tree summary Switch is in mst mode (IEEE Standard) Root bridge for: none
Port Type Default is disable
Edge Port [PortFast] BPDU Guard Default is enabled Edge Port [PortFast] BPDU Filter Default is disabled
Bridge Assurance is enabled
Loopguard Default is disabled
Pathcost method used is long
PVST Simulation is enabled
vPC peer-switch is enabled (non-operational)
STP-Lite is enabled
Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
MST0000 0 0 0 2 2
MST0001 0 0 0 2 2
---------------------- -------- --------- -------- ---------- ----------
2 msts 0 0 0 4 4
nex7010-2# sh spanning-tree summary Switch is in mst mode (IEEE Standard) Root bridge for: none
Port Type Default is disable
Edge Port [PortFast] BPDU Guard Default is enabled Edge Port [PortFast] BPDU Filter Default is disabled
Bridge Assurance is enabled
Loopguard Default is disabled
Pathcost method used is long
PVST Simulation is enabled
vPC peer-switch is enabled (non-operational)
STP-Lite is enabled
Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
MST0000 0 0 0 2 2
MST0001 0 0 0 2 2
---------------------- -------- --------- -------- ---------- ----------
2 msts 0 0 0 4 4
What could be the reason for that vPC peer-switch feature to be enabled but (non-operational)?!
Thank you for any hint!
