Ve Capacity; Vm Group Types; Local Vm Groups - Lenovo Flex System Fabric CN4093 Application Manual

VE Capacity

VM Group Types

Local VM Groups

242
CN4093 Application Guide for N/OS 8.2
When VMready is enabled, the switch will automatically discover VEs that reside
in hypervisors directly connected on the switch ports. Lenovo N/OS 8.2 supports
up to 4096 VEs. Once this limit is reached, the switch will reject additional VEs.
Note: In rare situations, the switch may reject new VEs prior to reaching the
supported limit. This can occur when the internal hash corresponding to the new
VE is already in use. If this occurs, change the MAC address of the VE and retry
the operation. The MAC address can usually be changed from the virtualization
management server console (such as the VMware Virtual Center).
VEs, as well as internal ports, external ports, static trunks and LACP trunks, can be
placed into VM groups on the switch to define virtual communication boundaries.
Elements in a given VM group are permitted to communicate with each other,
while those in different groups are not. The elements within a VM group
automatically share certain group‐level settings.
Lenovo N/OS 8.2 supports up to 4096 VM groups. There are two different types:
 Local VM groups are maintained locally on the switch. Their configuration is not
synchronized with hypervisors.
 Distributed VM groups are automatically synchronized with a virtualization
management server (see "Assigning a vCenter" on page
Each VM group type is covered in detail in the following sections.
The configuration for local VM groups is maintained on the switch (locally) and is
not directly synchronized with hypervisors. Local VM groups may include only
local elements: local switch ports and trunks, and only those VEs connected to one
of the switch ports or pre‐provisioned on the switch.
Local VM groups support limited VE migration: as VMs and other VEs move to
different hypervisors connected to different ports on the switch, the configuration
of their group identity and features moves with them. However, VE migration to
and from more distant hypervisors (those not connected to the CN4093, may
require manual configuration when using local VM groups).
251).