UFP Limitations
412
G8264 Application Guide for ENOS 8.4
The following limitations apply when configuring UFP:
For Emulex NICs, FCoE must be configured only on vPort 2 of the physical NIC.
UFP port in FCoE mode cannot operate with FIP auto‐VLAN feature.
VLANs that have member vPorts configured in trunk‐, access‐, or auto‐modes
cannot have member vPorts configured in tunnel mode or FCoE.
vPorts on a physical port must be members of separate VLANs.
VLANs 4002‐4009 are reserved for outer tagging.
VLAN translation is not applied on egress ports that have UFP enabled but no
vPorts configured in trunk‐, access‐, or auto‐modes.
UFP bandwidth is guaranteed lossless only for unicast traffic.
VMready is supported only on a vPort which is configured in auto‐VLAN
mode. When a vPort is in auto‐VLAN mode, it can support up to 32 VMGroups.
EVB is supported only on a vPort which is configured in auto‐VLAN mode.
VMready and EVB cannot be configured on the same physical port.
UFP vPorts can support up to 1024 VLANs in trunk mode and auto mode.
UFP can be enabled only on ports connected to servers and defined as server
ports
When CEE is turned on, FCoE vPort must be used for lossless priority traffic. For
loss‐tolerant priority traffic, a non‐FCoE UFP vPort must be used. The lossless
property of FCoE vPort is not guaranteed, if lossless and loss‐tolerant traffic are
combined.
When the vPort is enabled and the channel link state is up, the system does not
support changing vPort VLAN type from private/non‐private to
non‐private/private.
When integrating with private VLANs, UFP is not supported in stacking mode.
A maximum of eight vPorts can be configured for each physical switch port.
UFP and vNIC cannot be configured at the same time on a switch.
VMReady Local Group configuration is not supported by UFP.