Distributed Vm Groups - Lenovo CN4093 Application Manual

Distributed VM Groups

© Copyright Lenovo 2015
The following rules apply to the local VM group configuration commands:
cpu: Enable sending unregistered IPMC to CPU.

flood: Enable flooding unregistered IPMC.

key: Add LACP LAGs to the group.

optflood: Enable optimized flooding to allow sending unregistered IPMC to

the Mrouter ports without having any packet loss during the learning period;
This option is disabled by default; When optflood is enabled, the flood and cpu
settings are ignored.
port: Add switch server ports or switch uplink ports to the group. Note that

VM groups and vNICs (see
simultaneously on the same port.
portchannel: Add static port LAGs to the group.

profile: The profile options are not applicable to local VM groups. Only

distributed VM groups may use VM profiles (see
stg: The group may be assigned to a Spanning-Tree group for broadcast loop

control (see"Spanning Tree Protocols" on page
tag: Enable VLAN tagging for the VM group. If the VM group contains ports

which also exist in other VM groups, enable tagging in both VM groups.
validate: Set validate mode for the group.

vlan: Each VM group must have a unique VLAN number. This is required for

local VM groups. If one is not explicitly configured, the switch will
automatically assign the next unconfigured VLAN when a VE or port is added
to the VM group.
vmap: Each VM group may optionally be assigned a VLAN-based ACL (see

"VLAN Maps" on page
vm: Add VMs.

VMs and other VEs are primarily specified by MAC address. They can also be
specified by UUID or by the index number as shown in various VMready
information output (see
vport: Add a virtual port.

Add a virtual port to the group.
Distributed VM groups allow configuration profiles to be synchronized between
the CN4093 and associated hypervisors and VEs. This allows VE configuration to
be centralized, and provides for more reliable VE migration across hypervisors.
Using distributed VM groups requires a virtualization management server. The
management server acts as a central point of access to configure and maintain
multiple hypervisors and their VEs (VMs, virtual switches, and so on).
The CN4093 must connect to a virtualization management server before
distributed VM groups can be used. The switch uses this connection to collect
configuration information about associated VEs, and can also automatically push
configuration profiles to the virtualization management server, which in turn
configures the hypervisors and VEs. See
page 268 for more information.
"Virtual NICs" on page
271).
"VMready Information Displays" on page
"Virtualization Management Servers" on
241) are not supported
"VM Profiles" on page
151).
273).
Chapter 16: VMready
262).
261