By default, the IP address and certain other attributes of the IGESM are controlled by the Management Module. One consequence of this is that, if you change the IP address directly on the IGESM (via CLI or GUI), and at some later date/time, the Management Module gets reloaded, the IP address that the Management Module knows for the IGESM will be pushed back over to the IGESM, and the one that was changed via CLI/GUI will be overwritten.
The simplest way to avoid this is to only change the IP address of the IGESM from the Management Module GUI. This will ensure the address stays consistent.
Another option is to remove the control of the IGESM from the Management Module, which can be done with Protected Mode, but Protected Mode requires an Advanced Management Module be present and the IGESM must be at code level 12.1(22)EA9 or higher. A description and directions for utilizing Protected Mode can be found at the following link:
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...