I would for sure using 4.1.1a code if upgrading. I would delete your CIFS configuration before upgrading and then upgrade and then re-enable.
The only real issue that I ran into while doing this was that one device for some reason during upgrade lost its policies. No big deal. I just went to the central manager and set the policies back to default and it pushed them down to that device.
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...