I'll have SANs directly attached to the N5k's, with UCS/FI where we are planning to utilize FCoE downstream to the UCS/FI environment.
Now, what I am curious about, is why in the above document (Which was updated in June 2013) there is a seperate FCoE port channel and another ethernet vPC. I am curious behind the reasoning behind this. Is there a limitation with FCoE over vPC links or is just a matter of keeping the traffic from fabric A away from fabic B?
Also I am assuming the document has an FCoE port-channel as opposed to a san-port-channel is for the additional throughput of 10Gb FCoE as opposed to the 8Gb FC links.
I see the disclaimer note about the 2x seperate links and the FI operating in NPIV mode from the FC perspective that just isn't not helping me.
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...