I am still confused by the option of being creating a Fabric dual/VSAN rather than my referred way of creating a SEPARATE VSAN for Fabric A (VSAN33) and B (VSAN44) using of course a different FCoE VLAN for the 2 VSAN-FCoE VLAN (33) & FCoE VLAN (44),
Q1. which is the preferred option or Cisco's Best Practices with FC Uplink to a pair of MDS? FI-A via Expansion Module to MDS-A and FI-B to MDS-B?
Pro & Con
Q2. For the Fabric dual/VSAN setup, how does it work as I only see a Single VSAN and a Single FCoE VLAN at customer setup?
I have checked it via GUI and command line and I am very sure that I only see 1 VLAN and 1 FCoE VLAN.
Q3. Is that still a pre-requsite to create a FCoE VLAN in this case as I do not the VSAN's FCoE VLAN being created in customer setup? I remember the older UCS firmware imposed still requirement or I am wrong!!!
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...