If my UCS servers are running ESX, and I go to that server in my UCSM, then click on the virtual machines tab, I do not see anything. How does this process work? Is there a way that the UCS needs to know about the VM guests inside of the ESX host?
VM-FEX in hardware. The Palo VIC adaptor uses dynamic vNICs which get assigned directly to VMs. This allows you to create port profiles in UCSM which have VLAN and QoS attributes assigned.
It's a similar concept to the 2248 FEXs in regard to how the interfaces are managed, but the 2200 FEXs are not involved in this respect here. Just as a 2200 FEX's interfaces are managed by a parent N5K, a VM-FEX's (virtual) interfaces are managed by UCSM.
There is a good video series here which detail how to deploy VM-FEX, worth a watch.
1. You'll need the Enterprise Plus license in VMware
2. Your blades need the Cisco M81KR VIC network adaptor
Everything else included with UCSM by default.
It may not give a performance boost for VM - VM communication, but you can easily set and assign QoS policies directly from UCSM for your VMs. Greatly simplifies QoS configuration found on legacy switches.
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
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...