Hi there. We have nexus 5000 switches uplinked to our core VSS switches. We have recently paired up our nexus 5000 switches and enabled vPC. For example S1 and S2 are now connected via po20 which is the vPC peer link. I have noticed that spanning tree on switch S2 is now blocking on the uplink interface to the VSS, which means that all traffic destined to servers connected off the S2 has to pass through switch S1 and across the vPC link. The vPC link is 2x 10gig bundle. The uplink to the VSS is 4x10gig bundle. The VSS is the root bridge for all vlans.
I have tried changing port costs and port priority so that S2 forwards via the VSS and not over the vPC link but nothing i change can make the VSS uplink port move to forwarding state.
The VSS is running standard PVST, which is required due to legacy attached switches. Is this an interoperability issue between versions of spanning tree running on the nexus and VSS? Or is this behaviour correct due to the bridge assurance feature enabled on the nexus? Obviously this is not a good solution as we want all traffic from the core to the servers to go via the nexus that the servers are attached to.
Has anyone came across this issue before? Or can anyone please advise of a solution to this problem?