I've got an question about ACE modules in HA, when one of the switch is reloaded a couple of the ACE contexts come up in cold standby. I've check the config in the contexts to confirm that they match and the same ft interface is used by all contexts. When I do a switchover them come up in hot standby, has anybody seen this before ? I've looked at a couple of bugs in the standby area but can't see one to match.
Giles, I've only a basic config on the context that's I'm faulting. No SSL certs/keys or script files but I'll double check. I've seen it a couple of times in testing so I should be able to reproduce it.
I have a similar issue, I had been working on an ssl config and did not have the keys/certs on both modules. Now I have all of the ssl configuration removed, removed the keys/certs, and it is still stuck in FSM_FT_STATE_STANDBY_COLD
We have compared configs, and even erased the offending context configuration and reloaded standby module -- same thing.
After working with TAC , it looks like my configuration stopped synching from an probe that was configured with bad syntax. Apparently the original version of the ACE code did not care, and now it did. We found this from looking
at the output of a sh tech and looking for errors with cfgmgr. You could see the sync failing and what part of the config it was having problems with.
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...