Setting up iSCSI boot for the first time and had a question.
Setup: UCS blades connected to a N5K pair (vPC) with a dual-controller NetApp connected. There are 4 UCS vNICs - two for just iSCSI (as the native VLAN) and two for everything else.
The odd blades are booting from LUNs on NetApp controller A and the even blades are booting from LUNs on NetApp controller B.
So my question. When I make the iSCSI targets for an odd blade (for example), do I have both A and B "NIC"s point to controller A's IP? Or does NIC-A point to controller A's IP and NIC-B point to controller B's IP? I was not sure as, in this example, controller A would own the LUN that this odd blade is booting from.
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...