FIP Snooping | 193
Configuring 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.
FCoE traffic is allowed on the port only after a successful 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 as follows:
• 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.
FIP Snooping Prerequisites
Before you configure FIP snooping on an MXL switch, ensure that the following conditions are met:
• A FIP snooping bridge requires DCBX and PFC to be enabled on the switch for lossless Ethernet
connections (refer to Data Center Bridging (DCB)). Dell recommends that you also enable ETS; ETS
is recommended but not required.
If you enable DCBX and PFC mode is on (PFC is operationally up) in a port configuration, FIP snoop-
ing is operational on the port. If the PFC parameters in a DCBX exchange with a peer are not synchro-
nized, FIP and FCoE frames are dropped on the port after you enable the FIP snooping feature.
• VLAN membership:
• You must create the VLANs on the switch which handles FCoE traffic (
interface vlan command).
• You must configure each FIP snooping port to operate in Hybrid mode so that it accepts both
tagged and untagged VLAN frames (
portmode hybrid command).
• You must configure tagged VLAN membership on each FIP snooping port that sends and receives
FCoE traffic and has links with an FCF, ENode server, or another FIP snooping bridge (
tagged
port-type slot/port command).
The default VLAN membership of the port should continue to operate with untagged frames. FIP
snooping is not supported on a port that is configured for non-default untagged VLAN member-
ship.
To Next Page
Loading...
