Configuration manual

Bridge-to-FCF Links

A port directly connected to an FCF is auto-configured in FCF mode. 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

FIP snooping affects other software features on an Aggregator 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 in 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 the 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).

FIP Snooping Prerequisites

On an Aggregator, FIP snooping requires the following conditions:

• 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. DCBX and PFC mode are auto-configured on Aggregator ports and

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.

• VLAN membership:

– The Aggregator auto-configures the VLANs which handle FCoE traffic. You can reconfigure VLAN

membership on a port (vlan tagged command).

– Each FIP snooping port is auto-configured to operate in Hybrid mode so that it accepts both

tagged and untagged VLAN frames.

– Tagged VLAN membership is auto-configured on each FIP snooping port that sends and receives

FCoE traffic and has links with an FCF, ENode server or another FIP snooping bridge.

– 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

membership.

FIP Snooping Restrictions

The following restrictions apply to FIP snooping on an Aggregator:

• The maximum number of FCoE VLANs supported on the Aggregator is eight.

• The maximum number of FIP snooping sessions supported per ENode server is 32. To increase the

maximum number of sessions to 64, use the fip-snooping max-sessions-per-enodemac

command. This is configurable only in PMUX mode.

• In a full FCoE N port ID virtualization (NPIV) configuration, 16 sessions (one FLOGI + 15 NPIV sessions)

are supported per ENode. In an FCoE NPV confguration, only one session is supported per ENode.

• The maximum number of FCFs supported per FIP snooping-enabled VLAN is 12.

• Links to other FIP snooping bridges on a FIP snooping-enabled port (bridge-to-bridge links) are not

supported on the Aggregator.

FIP Snooping