IGMP
© Copyright Lenovo 2018
Private‐VLAN mode is promiscuous:
Allows only primary VLAN.
There can be multiple Private VLAN domains.
The Private VLAN domains must be unique for vPorts belonging to the same
UFP port.
Private‐VLAN mode is host:
Allows only ONE secondary VLAN. In the case of a vPort is in network trunk
mode, there will be multiple VLANs assigned to the vPort, but there will still
be only ONE secondary VLAN. The other VLANs will be in a different
private VLAN domain.
Warns if no primary VLAN is associated with the secondary VLAN assigned
to a vPort.
UFP with private VLANs is supported under the following limitations:
vPorts from the same physical port cannot belong to the same private VLAN
domain.
vPorts cannot be configured with a primary VLAN as a default VLAN, only
with secondary VLANs.
UFP ports cannot have switchport mode private‐VLAN enabled on them.
Private VLAN is supported only on vPorts configured with trunk or access
mode.
UFP cannot be configured on promiscuous ports.
For more information on private VLANs, see "Private VLANs" on page
A vPort is able to learn and configure IGMP entries (IGMP/IPMC groups and
Mrouters.). The IPMC traffic will always be forwarded according to the IGMP
entries, regardless of the location of the IGMP entries (on physical or logical ports)
and the RX port type.
For an example configuration, see "Example 6: UFP with IGMP Configuration" on
page
300.
Note: Double tagged IGMP related packets will not be forwarded to tagged VMs
based on inner tag when tagpvid‐ingress is enabled or UFP vPorts are configured
in tunnel mode.
151 .
Chapter 19: Unified Fabric Port
293