How do you handle overlapping vlans when using OTV between Data Centers. i.e. in Data Center 1 i have vlan 100 with ip address 10.10.100.0/24 and in Data Center 2 I have vlan 100 with ip address 10.20.100.0/24. I don't want to combine these into one network but keep them seperate when extending them between Data Centers.. Can OTV re-assign the vlans? or do i have to ensure the vlan tags are unique between the data centers?
Then you need seperated OTV edge devices for each DC which has overlapped vlans. You can increase the number up to three at this moment by using VDC feature. OTV doesn't support qinq or similar mechanisms yet.
Evan with a separate VDC the only way I can think of to translate the vlans is too connect access ports for each vlan that needs to be translated. This is not a practical solution for a large number of vlans as it would use a large number of ports on the Nexus 7K. If a trunk is used the vlan tags are passed through. Is there another way?
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...