The problem is that both "A-1" and "B-1" OTVs are choosen as AED for even VLANs, and "A-2" and "B-2" are AED for odd VLANs. The traffic for odd and even VLANs is not equal, so both inter-site links are not utilized equaly. If AEDs were choosed in a crossed manner (A-1, B-2 for odd, and A2, B1 for even VLANs), the traffic for odd and even VLANs would load-balance between both links. Is there any way to manualy define System ID for OTV AED? By default, the System ID is taken from SUP MAC, and unfortunately I cannot change N7Ks' places now.
Do you know if it will be possible at all in the nearest future? What are other possible ways to load-balace unequal traffic for odd and even VLANs in OTV? I have seen customers' networks where most of VLANs were odd, so the traffic is very unequal... Lack of flexible load-balancing makes OTV poor solution for many customers.. :-(
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...