When setting up a Hyper-V server using VM-FEX and SR-IOV is there a way to use VLAN's other than the Native VLAN on each dynamic NIC assigned to the virtual machines?
We have setup the port profiles and created the VM-FEX virtual switches inside Hyper-V and bound the Dynamic NIC inside the guest OS to the Port Profile. We have not been able to see a way to tag the traffic leaving the VM with a VLAN tag. You can't set the VLAN at the VM Settings page while the virtual switch is setup using VM-FEX like you normally would in Hyper-V (you get an usuported feature error). The Microsoft driver inside the VM and the VF driver also don't appear to support VLAN tagging.
We ahve been told by TAC that our setup is correct and that you can only use the Native VLAN. If this is the case then why do all the VM-FEX guides for Hyper-V include how to add Named VLAN's by CLI or GUI to the Port Profiles.
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...