I'm not really sure that I understood you correctly , but e.g. in ft peer configuration you have such options :
heartbeat interval X
heartbeat count Y
It means that device sends heartbeats with interval Xms and if Y heartbeats are missing from peer device, it will assume that it's down and take over. So, it should take around X*Yms to declare second device dead.
If you have query interface configured it will increase failover time, as device will try to check if peer is alive via this additional interface (
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...