I'm facing some problems and I'd like to share with you to check if my understand is correct or not.
I'm attaching the topology to help with the understanding.
In normal situation, traffic is able to pass from the 5K to the 6500. However, if the active uplink goes down I was also expecting traffic to pass over the link that connects the two 5Ks, but this is not happening.
In other words, if the traffic goes through from SRV-B- -> N5k2 -> 6k5-2 -> SRV-C everything works fine.
If the traffic goes through SRV-A -> N5k1 -> N5k2 -> 6k5-2 -> SRV-C or SRV-B -> N5k2 -> N5k1 -> SRV-A we face the problem. On both directions.
If I change the root priority for 6k1, traffic SRV-A- -> N5k1 -> 6k5-1 -> 6k5-2 -> SRV-C works fine.
My understanding is that the traffic that throughout the vPC Peer Link isn’t completing.
We are testing from a server on the Enclosure to a Server outside of Nexus ambient. On both directions the problem persists.
If I change the root priority to a vlan doing the traffic go “ahead” without pass by the vPC Peer link, works.
If I removed the vPC Peer link configuration and configure a simple trunk between both N5k, everything works.
According to this document, Orphan ports can communicate between vPC Peer Link.
According to the Orphan Ports traffic.png that I attached from a Cisco document, 2 orphan devices can communicate using the vPC peer link. My both enclosure are "orphans" and they are trying to use this link to communicate.
I'm not able to connect the enclousure to the other Nexus in this moment, so my intention is understand how is this scenario's behavior or if it's impossible to use this design.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...