- play_arrow Overview
- play_arrow Storage Overview
-
- play_arrow Transit Switch, FCoE, and FIP Snooping
- play_arrow Using FCoE on a Transit Switch
- Understanding FCoE Transit Switch Functionality
- Understanding FCoE
- Understanding FCoE LAGs
- Configuring an FCoE LAG
- Example: Configuring an FCoE LAG on a Redundant Server Node Group
- Understanding OxID Hash Control for FCoE Traffic Load Balancing on QFabric Systems
- Understanding OxID Hash Control for FCoE Traffic Load Balancing on Standalone Switches
- Enabling and Disabling CoS OxID Hash Control for FCoE Traffic on Standalone Switches
- Enabling and Disabling CoS OxID Hash Control for FCoE Traffic on QFabric Systems
- Configuring VLANs for FCoE Traffic on an FCoE Transit Switch
- Understanding FIP Snooping, FBF, and MVR Filter Scalability
- Understanding VN_Port to VF_Port FIP Snooping on an FCoE Transit Switch
- Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch
- Understanding VN_Port to VN_Port FIP Snooping on an FCoE Transit Switch
- Enabling VN2VN_Port FIP Snooping and Configuring the Beacon Period on an FCoE Transit Switch
- Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Directly Connected to the Same FCoE Transit Switch)
- Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Directly Connected to Different FCoE Transit Switches)
- Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Indirectly Connected Through an Aggregation Layer FCoE Transit Switch)
- Disabling Enhanced FIP Snooping Scaling
- Understanding MC-LAGs on an FCoE Transit Switch
- Example: Configuring CoS Using ELS for FCoE Transit Switch Traffic Across an MC-LAG
- Understanding FCoE and FIP Session High Availability
- Troubleshooting Dropped FIP Traffic
- Troubleshooting Dropped FCoE Traffic
-
- play_arrow Data Center Bridging (DCBX, PFC)
- play_arrow Using Data Center Bridging (DCBX, PFC)
- Understanding DCB Features and Requirements
- Understanding DCBX
- Configuring the DCBX Mode
- Configuring DCBX Autonegotiation
- Disabling the ETS Recommendation TLV
- Understanding DCBX Application Protocol TLV Exchange
- Defining an Application for DCBX Application Protocol TLV Exchange
- Configuring an Application Map for DCBX Application Protocol TLV Exchange
- Applying an Application Map to an Interface for DCBX Application Protocol TLV Exchange
- Example: Configuring DCBX Application Protocol TLV Exchange
- Understanding CoS Flow Control (Ethernet PAUSE and PFC)
- Example: Configuring CoS PFC for FCoE Traffic
- play_arrow Learn About Technology
-
- play_arrow Configuration Statements and Operational Commands
Configuring FIP on an FCoE-FC Gateway
Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP) establishes and maintains Fibre Channel (FC) virtual links between pairs of FCoE devices. A virtual link emulates the physical point-to-point link that FC requires between two FC devices.
FIP is enabled by default and uses the default FIP settings on all FCoE interfaces that are part of the gateway FC fabric. You can use the default FIP parameter values, or you can configure FIP parameters globally or on a per-interface basis. Configuring FIP on an individual interface overrides the global FIP configuration.
You can configure the following parameters globally for the fabric and per interface:
FIP keepalive message transmission interval—This interval is the time period between sending FIP keepalive messages.
Priority—If an FCoE node (ENode) connects to more than one switch, the priority value determines the switch to which the ENode connects. The switch with the lowest priority number has the highest priority.
You can only configure the following parameters globally on an FC fabric:
FC-MAP—The 24-bit FCoE mapped address prefix that identifies the attached FC switch in the SAN fabric. The FC-MAP value is used in the fabric provided MAC address (FPMA) created for each ENode that logs in. This value must be the same for the FC switch and the QFX Series.
Note:Changing the FC-MAP value causes all logins to drop and forces the ENodes to log in again.
FCoE trusted—You can globally configure all of the Ethernet ports in a specified FC fabric to be FCoE trusted. You might want to configure interfaces as FCoE trusted if the interfaces are connected to a transit switch that is performing FIP snooping. For interfaces that are directly connected to FCoE hosts, FIP snooping should be enabled, and you should not configure the fabric as FCoE trusted.
Note:Do not configure interfaces with FIP snooping enabled as FCoE trusted.
Configuring interfaces as FCoE trusted reduces system overhead by eliminating the need for filters. The total number of sessions the system can support is 2500 sessions. Sessions are defined as the combined number of VN_Port to VF_Port sessions and VN_Port to VN_Port sessions. (Although VN2VF and VN2VN sessions run in different FCoE VLANs, the session limit is a system limit, not a per-VLAN limit.)
Note:A session is a FLOGI or FDISC login to the FC SAN fabric. Session does not refer to end-to-end storage sessions. There is no limit to the number of end-to-end storage sessions.
Note:Changing the fabric ports from untrusted to trusted removes any existing FIP snooping filters from the ports. Changing the fabric ports from trusted to untrusted forces all of the FCoE sessions on those ports to log out so that when the ENodes and VN_Ports log in again, the switch can build the appropriate FIP snooping filters.
Maximum number of FCoE sessions per ENode—You can globally configure the maximum number of FCoE sessions (FLOGI plus FDISC) permitted from an ENode. The maximum number of sessions per ENode is 2000 sessions. The total number of sessions (VN2VF_Port sessions and VN2VN_Port sessions combined) cannot exceed the gateway fabric’s maximum limit of 2500 sessions.
To configure FIP options globally using the CLI:
For example, to configure all FCoE interfaces associated with an FC fabric called movieco_san with a FIP keepalive interval value of 25000 milliseconds, a priority of 70, an FC-MAP value of 0EFC01, as FCoE trusted, and with a maximum number of FCoE sessions per ENode of 200 sessions:
[edit fc-fabrics movieco_san protocols fip] user@switch# set fka-adv-period 25000 user@switch# set priority 70 user@switch# set fc-map 0EFC01 user@switch# set fcoe-trusted user@switch# set max-sessions-per-enode 200
To override the global FC fabric FIP configuration for a specific FCoE interface using the CLI:
Specify the fabric and interface on which you want to configure FIP:
content_copy zoom_out_map[edit fc-fabrics fabric-name protocols fip interface interface-name]
Configure the FIP keepalive message transmission interval and priority:
content_copy zoom_out_map[edit fc-fabrics fabric-name protocols fip interface interface-name] user@switch# set fka-adv-period milliseconds user@switch# set priority priority
