Some weeks ago, we decided to do a connectivity test with our nexus equipment. The topology was fairly simple, only one Nexus 5548UP, no vPC domain configured. 2 Nexus 2248TP Fabric Extenders connected to the 5548UP. Finally, a server, doing NIC teaming, ACTIVE-ACTIVE in a PortChannel config, one link to each Nexus 2248TP Fabric Extender. Topology attached below.
My understanding was that the FEXs were remote line cards, so what we are doing here is like adding 2 linecards to a moludar switch like a 6500 and creating a PortChannel using 1 link to 1 linecard, and 1 link to another linecard.
To my surprise, this was not allowed.
I tried to find and explanation why this could not be configured, but nothing found.
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...