Users Guide

Configure a Port for a Bridge-to-FCF Link
If a port is directly connected to an FCF, configure the port mode as FCF. Initially, all FCoE traffic is blocked;
only FIP frames are allowed to pass.
NOTE: FCoE-Trusted Port mode used to connect to another FIP snooping bridge (bridge-bridge link) is
not supported on the S5000 switch.
FCoE traffic is allowed on the port only after a successful fabric login (FLOGI) request/response and
confirmed use of the configured FC-MAP value for the VLAN.
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 27. 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 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.
FCoE Transit 398