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 on an NPIV Proxy Gateway
When you configure an S5000 as an NPIV proxy gateway and enable Fibre Channel capability, FIP
snooping is automatically enabled on all VLANs using the default FIP snooping settings.
To identify the SAN fabric to which FCoE storage traffic is sent, use an FCoE map. FIP snooping is
automatically configured on the FCoE VLAN specified in the FCoE map using the FC-MAP parameter in
the map:
• When you apply an FCoE map to a server-facing Ethernet interface in ENode port mode
• When you apply an FCoE map to a fabric-facing FC interface
NOTE: When you configure an S5000 switch as an NPIV proxy gateway, only the fip-snooping
max-sessions-per-enodemac command is supported to configure FIP snooping.
For more information, refer to NPIV Proxy Gateway.
FIP Snooping in an S5000 Stack
FIP snooping is not supported on stack units in an S5000 stack.
Impact on Other Software Features
When you enable FIP snooping on a switch, other software features are impacted. The following table
lists the impact of FIP snooping.
Table 23. Impact of Enabling FIP Snooping
Impact Description
MAC address learning MAC address learning is not performed on FIP and
FCoE frames, which are denied by ACLs
FCoE Transit
363