You need to be running Enhanced Device Alias for the zone change to be automatic. In enhanced mode, the zone process tracks the device alias database and if s PWWN changes as a result of a device alias update, it will be reflected in the zones. The zoneset must still be reactivated manually for the new PWWN to be distributed as part of the zoneset. This mode was put into place to make is easier to update many zones if a single hba needs to be replaced.
The step when using enhanced mode device alias
-update the device alias database to remove failed pwwn
-update device alias database to add new pwwn (alias name must be the same)
-issue device aliase commit to make the change effective
-reactivate the currently active zoneset for the vsan where the new pwwn resides
If the fabric is running device alias in basic mode, you will need to manully edit the zones to remove then add in the device alias once it has been changed, and then reactivate the zoneset.
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...