- play_arrow Overview
- play_arrow Storage Overview
-
- play_arrow Fibre Channel and FCoE-FC Gateways
- play_arrow Using Fibre Channel and FCoE-FC Gateways
- Understanding Fibre Channel
- Understanding an FCoE-FC Gateway
- Understanding Fibre Channel Fabrics on the QFabric System
- Configuring an FCoE-FC Gateway Fibre Channel Fabric
- Understanding FCoE-FC Gateway Functions
- Disabling the Fabric WWN Verification Check
- Understanding FCoE and FIP Session High Availability
- Understanding FIP Functions
- Understanding FIP Implementation on an FCoE-FC Gateway
- Understanding FIP Parameters on an FCoE-FC Gateway
- Configuring FIP on an FCoE-FC Gateway
- Setting the Maximum Number of FIP Login Sessions per ENode
- Setting the Maximum Number of FIP Login Sessions per FC Interface
- Setting the Maximum Number of FIP Login Sessions per FC Fabric
- Setting the Maximum Number of FIP Login Sessions per Node Device
- Monitoring Fibre Channel Interface Load Balancing
- Troubleshooting Dropped FIP Traffic
- Understanding Fibre Channel Virtual Links
- Understanding Interfaces on an FCoE-FC Gateway
- Example: Setting Up Fibre Channel and FCoE VLAN Interfaces in an FCoE-FC Gateway Fabric
- Configuring a Physical Fibre Channel Interface
- Converting an Ethernet Interface To a Fibre Channel Interface
- Configuring an FCoE VLAN Interface on an FCoE-FC Gateway
- Assigning Interfaces to a Fibre Channel Fabric
- Deleting a Fibre Channel Interface
- Troubleshooting Fibre Channel Interface Deletion
- Disabling VN2VF_Port FIP Snooping on an FCoE-FC Gateway Switch Interface
- Disabling Storm Control on FCoE Interfaces on an FCoE-FC Gateway
- Understanding Load Balancing in an FCoE-FC Gateway Proxy Fabric
- Defining the Proxy Load-Balancing Algorithm
- Simulating On-Demand Fibre Channel Link Load Rebalancing (Dry Run Test)
- Example: Configuring Automated Fibre Channel Interface Load Rebalancing
-
- 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 VLANs for FCoE Traffic on an FCoE Transit Switch
Fibre Channel over Ethernet (FCoE) transit switches transport FCoE traffic on a dedicated VLAN (it cannot be shared with any other type of traffic). You configure a VLAN for FCoE traffic using different procedures on switches that use the Enhanced Layer 2 Software (ELS) configuration style than on switches that don’t use ELS.
Considerations When Configuring FCoE VLANs
When you configure a switch as a Fibre Channel over Ethernet (FCoE) transit switch, you must configure a VLAN that transports only FCoE traffic. FCoE traffic requires a dedicated VLAN and cannot share a VLAN with any other type of traffic.
Because FCoE traffic is tagged traffic, the port (or interface) mode cannot be access mode;you must use either trunk interface-mode for ELS switches or tagged-access port-mode for switches that don’t use ELS.
However, each interface that belongs to an FCoE VLAN must not only transport the tagged FCoE traffic, it must also transport the untagged FCoE Initialization Protocol (FIP) traffic. FIP communicates with the storage area network (SAN) Fibre Channel (FC) switch to set up the FCoE session for the FCoE client.
To transport untagged traffic on a tagged-access or trunk mode interface, the interface must have a native VLAN configured on it. Therefore, each interface that belongs to an FCoE VLAN must also have a native VLAN on it.
There are slight differences in the way you configure a native VLAN on an interface depending on whether the switch uses the Enhanced Layer 2 Software (ELS) configuration style or the original non-ELS CLI.
FCoE VLANs (any VLAN that carries FCoE traffic) support only Spanning Tree Protocol (STP) and link aggregation group (LAG) Layer 2 features.
FCoE traffic cannot use a standard LAG because traffic might be hashed to different physical LAG links on different transmissions. This breaks the (virtual) point-to-point link that Fibre Channel traffic requires. If you configure a standard LAG interface for FCoE traffic, FCoE traffic might be rejected by the FC SAN.
QFabric systems support a special LAG called an FCoE LAG, which enables you to transport FCoE traffic and regular Ethernet traffic (traffic that is not FCoE traffic) across the same link aggregation bundle. Standard LAGs use a hashing algorithm to determine which physical link in the LAG is used for a transmission, so communication between two devices might use different physical links in the LAG for different transmissions. An FCoE LAG ensures that FCoE traffic uses the same physical link in the LAG for requests and replies in order to preserve the virtual point-to-point link between the FCoE device converged network adapter (CNA) and the FC SAN switch across the QFabric system Node device. An FCoE LAG does not provide load balancing or link redundancy for FCoE traffic. However, regular Ethernet traffic uses the standard hashing algorithm and receives the usual LAG benefits of load balancing and link redundancy in an FCoE LAG.
To configure an FCoE VLAN on a QFX3500 switch that you are using as an FCoE-FC gateway, you must also configure an FCoE VLAN interface as described in Configuring an FCoE VLAN Interface on an FCoE-FC Gateway. (Only the QFX3500 switch supports FCoE-FC gateway configuration.)
Configuring an FCoE VLAN includes the following steps:
Configure a VLAN to use as a dedicated FCoE VLAN
Configure the interface members of the FCoE VLAN.
Configure a native VLAN for FIP traffic.