Now the DC's are connected have L2 and also L3 IP connectivity. I was wondering if we could run OTV on the N7ks.
I realise that they are not connected directly edge to edge. However is there a possibility to encapsulate them in EoMPLS or some way on the 6k's and transport them across. we dont have EoMPLS yet but if we can OTV on top of it then we can look at it.
I understand that L2Tpv3 is not supported on the 6k's. Can someone confirm that as wel for me thanks.
If you have any other suggestions, I would apprecate that.
If I understand correctly, your N7K is strictly L2. You will have to create another VDC to create both OTV internal and joint interface. The internal interface will be L2 only, the joint interface will be L3 running IGMP version 3 (not PIM).
Your correct. The N7K is strictly a L2 switch at the moment. So if I understand you correct,you are suggesting 2 portchannels 1x L2 for internal interface that connects to the 6k and 1x L3 port channel for the join-interface to the 6k. and put them in a seperate VDC say VDC_JEYE would I be right?
Now should the internal interface be a 10G or can I use 1 Gig as well if I dont have spare 10G ports on the 6k. for the L3 port channel i can use a gig interface right?
And the intra DC traffic can use the default VDC right?
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...