Reference Guide

Impact Description
dynamically created by FIP snooping on server-
facing ports in ENode mode.
MTU auto-configuration MTU size is set to mini-jumbo (2500 bytes) when a
port is in Switchport mode, the FIP snooping
feature is enabled on the switch, and FIP snooping
is enabled on all or individual VLANs.
Link aggregation group (LAG) FIP snooping is supported on port channels on
ports on which PFC mode is on (PFC is
operationally up).
STP If you enable an STP protocol (STP, RSTP, PVSTP,
or MSTP) on the switch and ports enter a blocking
state, when the state change occurs, the
corresponding port-based ACLs are deleted. If a
port is enabled for FIP snooping in ENode or FCF
mode, the ENode/FCF MAC-based ACLs are
deleted.
FIP Snooping Restrictions
The following restrictions apply when you configure FIP snooping.
The maximum number of FCoE VLANs supported:
on an S5000 NPIV proxy gateway is 12.
on an S5000 switch not configured as an NPIV proxy gateway is eight.
The maximum number of FCFs supported on a FIP snooping-enabled VLAN:
on an S5000 NPIV proxy gateway is 12.
on an S5000 switch not configured as an NPIV proxy gateway is 12.
The maximum number of FIP snooping sessions (including NPIV sessions) supported per ENode
server is 64 and is user-configurable.
In a full FCoE NPIV configuration, 64 sessions (one FLOGI + 63 NPIV sessions) are supported per
ENode server.
Links to other FIP snooping bridges on a FIP snooping-enabled port (bridge-to-bridge links) are not
supported on the S5000 switch.
The DCBx version that you configure on an interface determines the server CNA traffic that FIP
snooping supports on the interface:
CEE-DCBX supports T11-compliant Gen-2 CNAs.
CIN-DCBX supports Gen-1 CNAs.
IEEE 802.1Qaz (Draft 2.5) supports Gen-2 CNAs.
You can also configure an interface to operate using the DCBx version received from a peer (the auto-
configure
option). In this case, the S5000 switch detects the capabilities of a CNA and auto-configures
the interface to the correct DCBx mode.
364
FCoE Transit