We use (by default) the source/destination/OXID id loadbalancing. The OXID is the exchange identifier in a fibre channel frame. Most of the time, a new exchage ID will be used when a device goes and gets a different set of data...whether that is a block of data or recognizes it as a different file, whatever depending on the driver in the initiator. So, then we will spread these sessions across the portchannel. We don't do a per-packet LB like CEF can be configured to do on the IP side. If you want to compare it to IP, we LB each TCP session down a different physical path.
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...