If you want a redundant (back up) Central Manager, you would need a second WAE.
Having servers at two locations might require more configuration and planning, but not necessarily a big issue. Things to think about would be: potential number of users, concurrent TCP connections at each site and the fan out ratio for DRE and CIFS (number of peer WAEs that the local WAE can optimize connections to). This would give you a good idea as to what hardware to use.
Also, since WAAS' optimization mechanisms require only two WAEs in the traffic path, intermediate WAEs would not present a problem.
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...