Vnic Groups - Lenovo RackSwitch G8264CS Application Manual

vNIC Groups

242
G8264CS Application Guide for ENOS 8.4
vNICs can be grouped together, along with uplink ports and LAGs, as well as
other ports that were defined as server ports but not connected to vNICs. Each
vNIC group is essentially a separate virtual network within the switch. Elements
within a vNIC group have a common logical function and can communicate with
each other, while elements in different vNIC groups are separated.
ENOS 8.4 supports up to 32 independent vNIC groups.
The VLAN configured for the vNIC group will be automatically assigned to
member vNICs, ports, and LAGs must not be manually configured for those
elements.
Note: Once a VLAN is assigned to a vNIC group, that VLAN is used only for vNIC
purposes and is no longer available for configuration. Likewise, any VLAN
configured for regular purposes cannot be configured as a vNIC group VLAN.
Other vNIC group rules are as follows:
vNIC groups may have one or more vNIC members. However, any given vNIC

can be a member of only one vNIC group.
 All vNICs on a given port must belong to different vNIC groups.
 Uplink ports which are part of a LAG may not be individually added to a vNIC
group. Only one individual uplink port, one static LAG (consisting of multiple
uplink ports), or one dynamic LAG may be added to any given vNIC group.
 In dedicated mode, for any switch ports or port LAG connected to regular
(non‐vNIC) devices:
These elements can be placed in only one vNIC group (they cannot be

members of multiple vNIC groups).
Once added to a vNIC group, the PVID for the element is automatically set to

use the vNIC group VLAN number, and PVID tagging on the element is
automatically disabled.
By default, STP is disabled on non‐server ports or LAGs added to a vNIC

group. STP cannot be re‐enabled on the port.
 Because regular, inner VLAN IDs are ignored by the switch for traffic in vNIC
groups, following rules and restrictions apply:
The inner VLAN tag may specify any VLAN ID in the full, supported range (1

to 4095) and may even duplicate outer vNIC group VLAN IDs.
Per‐VLAN IGMP snooping is not supported in vNIC groups.

The inner VLAN tag is not processed in any way in vNIC groups: The inner

tag cannot be stripped or added on egress port, is not used to restrict
multicast traffic, is not matched against ACL filters, and does not influence
Layer 3 switching.
For vNIC ports on the switch, because the outer vNIC group VLAN is

transparent to the OS/hypervisor and upstream devices, configure VLAN
tagging as normally required (on or off) for the those devices, ignoring any
outer tag.