Broadcasts sent from vPC secondary to the peer-link will not transmit on the vPC primary destination vPC. This is usually seen when the secondary switch has orphan ports or L3 interfaces that are up while the vPCs are suspended.
The observed impact is noticed while vPC delay restore is in effect. Traffic must be successfully forwarded across the peer-link to transmit out the primary's vPCs. Since this is not happening properly, the delay restore timer affects the length of the outage.
This problem happens specifically on Nexus 5548 and 5596, but could not occur on Nexus 5010 or 5020.
Reduce the delay restore timer to minimize impact, but tune to give enough time for routing protocols to converge:
vpc domain [id]
delay restore 10
n5k version is 5.0(3)N2(1) for us
but what i don't understand is "broadcasts sent from vPC secondary" in my opinion,vpc "secondary" only on control layer,forwarding occurs at the same time between primary and secondary n5k.
actually,i want to know the difference between the port-channel on n2k and it's on 2960.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...