The devices should work fine together, however the 4.1.1c devices won't have the ability to use the SSL (HTTPS) AO or any of the other bug fixes that are in 4.1.3b. It is also important that the CM is upgraded to the newest version that is on the network, so it should also be upgraded to 4.1.3b if you have that version on the network.
I would recommend that they attempt to stay at the same code version Enterprise-wide, and I would definitely recommend the 4.1.3b version over the 4.1.1c if they have a choice.
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...