We would like to be able to use the same management network for the UCSM management interfaces and as the management network for VMs running on our blades. For example, we'd like to have the management pool for UCSM from 188.8.131.52 and the VM ESXi management network also be on 184.108.40.206.
From what I can tell, the mangement network on UCSM is physically separate in chassis from the traffic needed to reach the blade mezzanine cards, correct? So being able to route to the UCSM management network doesn't mean we'll be able to route to the mezzanine interfaces if they use that same network.
Since our management network (220.127.116.11) is on physically different infrastructure than our data network (18.104.22.168), we're trying to have our 6120 uplink to switches with different views of the network, two for data and one for mgmt. However, the 6120 wants to allow all vlans created on all uplinks, and this isn't working.
A picture of what we're trying to do would look like this.
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...