Does anyone know a way to re-number the interfaces on a VEM, so they're sequential? My VEMs have 4 interfaces that I'm using as uplinks, and they're all sequential starting at 1. However, my VEM 7 has a mis-order going on. Truncated output from show interface status is shown below.
Eth5/1 -- up trunk full unknown --
Eth5/2 -- up trunk full unknown --
Eth5/3 -- up trunk full unknown --
Eth5/4 -- up trunk full unknown --
Eth7/1 -- up trunk full unknown --
Eth7/4 -- up trunk full unknown --
Eth7/6 -- up trunk full unknown --
Eth7/7 -- up trunk full unknown --
The disparity in numbering is messing up some automation.
The interface number in the Nexus 1000V are taken from the vmnic numbers in the ESXi host that the VEM resides. So going into /etc/vmware/esx.conf (be careful, of course) I was able to renumber the interfaces there. After a reboot, I had to change the port groups on the newly numbered interfaces in vCeneter DVS, and voila. Interfaces are back to normal.
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...