Fip Snooping Prerequisites; Fip Snooping Restrictions - Dell PowerEdge M IO Aggregator Command Reference Manual

FIP Snooping Prerequisites

On an Aggregator, FIP snooping requires the following conditions:
• A FIP snooping bridge requires DCBX and PFC to be enabled on the switch for lossless Ethernet
connections (refer to
is recommended but not required.
DCBX and PFC mode are auto-configured on Aggregator ports and FIP snooping is operational on the
port. If the PFC parameters in a DCBX exchange with a peer are not synchronized, FIP and FCoE
frames are dropped on the port.
• VLAN membership:
• The Aggregator auto-configures the VLANs which handle FCoE traffic. You can reconfigure
VLAN membership on a port (
• Each FIP snooping port is auto-configured to operate in Hybrid mode so that it accepts both tagged
and untagged VLAN frames.
• Tagged VLAN membership is auto-configured on each FIP snooping port that sends and receives
FCoE traffic and has links with an FCF, ENode server, or another FIP snooping bridge.
The default VLAN membership of the port should continue to operate with untagged frames. FIP
snooping is not supported on a port that is configured for non-default untagged VLAN member-
ship.

FIP Snooping Restrictions

The following restrictions apply to FIP snooping on an Aggregator:
• The maximum number of FCoE VLANs supported on the Aggregator is eight.
• The maximum number of FIP snooping sessions (including NPIV sessions) supported per ENode
server is 16.
In a full FCoE N port ID virtualization (NPIV) configuration, 16 sessions (one FLOGI + fifteen NPIV
sessions) are supported per ENode. In an FCoE NPV configuration, only one session is supported per
ENode.
• The maximum number of FCFs supported per FIP snooping-enabled VLAN is four.
• Links to other FIP snooping bridges on a FIP snooping-enabled port (bridge-to-bridge links) are not
supported on the Aggregator.
Data Center Bridging (DCB)). Dell recommends that you also enable ETS; ETS
vlan tagged
command).
FIP Snooping | 99