i would like two know what the best practices are regaring keeping profiles on multiple UCS environments in sync? I have two rooms in a DC and in each room there is a UCS system. I would like to keep the nic templates/hba templates/service profiles in sync so I can easily deploy a system in room A or B. I understand the content of the MAC/WWN/IP/UUID pools need to be unique per system but all the other stuff can be the same.
I think it can be done manually by exporting the XML of all the various objects in the gui and then do a merge on the other system but I am not sure if this is the best way to do it.
Unfortunately right now, exporting XML, or using a 3rd party scripting app is the only way to keep multiple systems in sync. That being said there is development being done on a UCS Enterprise Manager, that will be able to manage multiple UCS systems and do exactly what you're asking.
There is no commit date for this yet, but I would guess it would be avaiable closer to the end of the year.
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...