I am using boot from iSCSI with the same Cisco (6248+2208+1240) hardware. Although I don't use Hyper-V instead.
As far as I can see you have configured it correctly. Only one note, you have set your CoS (Class of Service) to MTU 9216 for gold. You should keep this value the same (e.g. 9000) as your vNICs and iSCSI target.
I have this same issue now, instead of changing best effort to 9216, what should be done? should we adjust the force 10 switches to match the cos value of the expected ucs class of traffic? i'm concerned that changing best effort is like a band-aid where if we properly configured the force 10 switches, that we would still maintain our priority without sacrificing performance down to best effort priorities.
also when looking at the portchannel details on CLI on the UCS, we see that the Portchannel is still using MTU of 1500, is this normal? or is it reflecting the Best Effort policy MTU size explicitly?
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...