Users Guide
• Understanding VLAN Support
• Viewing Or Editing Hypervisor Proles
• Duplicating Hypervisor Proles
• Renaming Hypervisor Proles
• Deleting Hypervisor Proles
• Refreshing Hypervisor Proles
VLAN Support
The OpenManage Integration for VMware vCenter supports hypervisor deployment to a routable VLAN. Congure VLAN support in
the Deployment Wizard. In this portion of the Deployment Wizard, there is an option to specify use of VLANs and to specify a VLAN
ID. When a VLAN ID is provided, it is applied to the hypervisor's management interface during deployment and tags all trac with
the VLAN ID.
Make sure that the VLAN provided during deployment communicates with both the virtual appliance and the vCenter server. The
deployment of a hypervisor to a VLAN that cannot communicate to one or both of these destinations causes the deployment to fail.
If you have selected multiple bare-metal servers in a single deployment job and want to apply the same VLAN ID to all the servers
then on the Server Identication portion of the Deployment Wizard, under Default Settings, use the Apply settings to all selected
servers button. This option lets you apply the same VLAN ID along with the other network settings to all the servers in that
deployment job.
NOTE: The OpenManage Integration for VMware vCenter does not support a multi-homed conguration. Adding a
second network interface to the appliance for communication with a second network causes problems for the work ows
involving hypervisor deployment, server compliance, and rmware updates.
Figure 4. Example VLAN network.
In this example network, the OpenManage Integration for VMware vCenter is on VLAN 5, while the vCenter and the VMkernal of
the ESXi hosts being deployed are on VLAN 10. Because the OpenManage Integration for VMware vCenter does not support multi-
VLAN homing, VLAN 5 must route to VLAN 10 for all systems to communicate to each other correctly. If routing is not enabled
between these VLANs, then the deployment fails.
55