I had a quick question re: importing fcaliases into the device-alias database.
We have a series of zones that were previously configured using the fcalias for the member definition.
After the successful import of fcaliases into the device-alias database, should we expect to see the running config for each zone definition get updated to using the device-alias? Or, alternately, should the newly create device-alias only get used on a go-forward basis for future zones?
The 9500 is running 3.1(2a) and we have the switch configured to device-alias mode enhanced.
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...