This is a general question, wondering if anyone knows. Historically, VPC has had issues with creating routing adjencencies across the peer-link, due to the loop prevention logic. Now, with Fabricpath enabled, you move to VPC+ where the peer-link is a Fabricpath link. Does anyone know if, since Fabricpath has its own (superior) loop-prevention logic, the same limitation applies?
It still applies to the Fabricpath setup as well. Now in VPC if you remember we recommend you to use a seperate link for carrying vlan's and to establish routing adjacencies and not on the peer-link. Fabricpath is TRILL based and just one step ahead of VPC. VPC+ still has all those loop prevention mechanisms.
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...