I have several sets of CSS's running in box to box redundancy running version 5.03 Build 15.
My question is what causes one CSS to out of the blue go backup and the other become master? I've had this happen on just about all the ones I have configured for box to box. This one pair has been running for a little over a year without a problem and today failed over to the other CSS twice. Nothing shows up in the logs except the "transition to redundancy backup / master." Another pair did this several times about a year ago, after having ran for quite some time. I rebooted both units and they were fine for a period of about 6 months. I find this very strange and am curious if anyone else has had these same problems. I have updated the code on one set, the problem reappered about 7 months later.
I'm now deploying all new CSS installs using interface/vip redundancy.
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...