FIP Snooping | 99FIP Snooping PrerequisitesOn an Aggregator, FIP snooping requires the following conditions:• A FIP snooping bridge requires DCBX and PFC to be enabled on the switch for lossless Ethernetconnections (refer to Data Center Bridging (DCB)). Dell recommends that you also enable ETS; ETSis recommended but not required.DCBX and PFC mode are auto-configured on Aggregator ports and FIP snooping is operational on theport. If the PFC parameters in a DCBX exchange with a peer are not synchronized, FIP and FCoEframes are dropped on the port.• VLAN membership:• The Aggregator auto-configures the VLANs which handle FCoE traffic. You can reconfigureVLAN membership on a port (vlan tagged command).• Each FIP snooping port is auto-configured to operate in Hybrid mode so that it accepts both taggedand untagged VLAN frames.• Tagged VLAN membership is auto-configured on each FIP snooping port that sends and receivesFCoE 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. FIPsnooping is not supported on a port that is configured for non-default untagged VLAN member-ship.FIP Snooping RestrictionsThe 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 ENodeserver is 16.In a full FCoE N port ID virtualization (NPIV) configuration, 16 sessions (one FLOGI + fifteen NPIVsessions) are supported per ENode. In an FCoE NPV configuration, only one session is supported perENode.• 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 notsupported on the Aggregator.
