White Papers

● A switch stack configuration is synchronized with the standby stack unit.
● Dynamic population of the FCoE database (ENode, Session, and FCF tables) is synchronized with the standby stack unit.
The FCoE database is maintained by snooping FIP keep-alive messages.
● In case of a failover, the new master switch starts the required timers for the FCoE database tables. Timers run only on the
master stack unit.
Using FIP Snooping
After you enable FcoE transit, the configuration of FIP snooping on an S5000 switch not configured as an NPIV proxy gateway
consists of the following tasks.
For more information about FIP snooping on an NPIV proxy gateway, refer to FIP Snooping on an NPIV Proxy Gateway.
There are four steps to configure FCoE transit.
1. Enable the FCoE transit feature on a switch to maintain FIP snooping information on the switch.
2. Enable FIP snooping globally on all Virtual Local Area Networks (VLANs) or individual VLANs on a FIP snooping bridge.
3. Configure the FC-Map value applied globally by the switch on all VLANs or an individual VLAN. The FC-MAP value checks
the first 24 bits in the MAC address in incoming FCoE frames.
4. Configure the maximum number of FIP-snooping sessions supported ont eh switch for an ENode MAC address.
5. Configure FCF mode for a FIP snooping bridge-to-FCF link.
NOTE: The FCoE-Trusted Port mode used to connect to another FIP snooping bridge (bridge-bridge link) is not supported
on the S5000 switch.
For a sample FIP snooping configuration, refer to FCoE Transit Configuration Example.
Enable the FCoE Transit Feature
The following sections describe how to enable FCoE transit.
NOTE:
FCoE transit is disabled by default. To enable FCoE transit and configure FIP snooping, follow the steps in
Configuring FIP Snooping.
When you enable FCoE transit, the switch snoops FIP packets on VLANs enabled for FIP snooping and allows legitimate
sessions. FCoE and FIP packets are dropped on VLANs disabled for FIP snooping. When you disable FCoE transit, the S5000
operates as a pure Layer 2 switch that switches FCoE and FIP packets.
As soon as you enable the FCoE transit feature on a switch-bridge, existing VLAN-specific and FIP snooping configurations are
applied. The FCoE database is populated when the switch connects to a converged network adapter (CNA) or FCF port and
compatible DCB configurations are synchronized. By default, all FCoE and FIP frames are dropped unless specifically permitted
by existing FIP snooping-generated ACLs. You can reconfigure any of the FIP snooping settings.
If you disable FCoE transit, FIP and FCoE traffic are handled as normal Ethernet frames and no FIP snooping ACLs are
generated. The VLAN-specific and FIP snooping configuration is disabled and stored until you re-enable FCoE transit and the
configurations are re-applied.
NOTE:
When you configure the S5000 switch as an NPIV proxy gateway and enable Fibre Channel capability (the
feature fc command), FIP snooping is automatically enabled on all VLANs on the switch using the default FIP snooping
settings.
FIP Snooping Prerequisites
Before you enable FCoE transit and configure FIP snooping on a switch, ensure that certain conditions are met.
A FIP snooping bridge requires data center bridging exchange protocol (DCBx) and priority-based flow control (PFC) to be
enabled on the switch for lossless Ethernet connections (refer to the Data Center Bridging (DCB)chapter). Dell Networking
recommends also enabling enhanced transmission selection (ETS); however, ETS is recommended but not required.
If you enable DCBx and PFC mode is on (PFC is operationally up) in a port configuration, 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
after you enable the FIP snooping feature.
For VLAN membership, you must:
300
FCoE Transit