- 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
Converting an Ethernet Interface To a Fibre Channel Interface
When a QFX3500 acts as an FCoE-FC gateway, native Fibre Channel (FC) traffic flows between the switch and the storage area network (SAN) FC switch. When you configure a port as an FC interface, it transports only FC traffic. It does not transport Ethernet traffic.
You can configure ports xe-0/0/0 through xe-0/0/5 as fc-0/0/0 through fc-0/0/5 and ports xe-0/0/42 through xe-0/0/47 as fc-0/0/42 through fc-0/0/47 to create blocks of native FC interfaces.
Each of these blocks of ports must be configured either as all Ethernet ports or as all native FC ports. Within each block of ports, you cannot mix FC and Ethernet interfaces. This means that you can configure 0, 6, or 12 ports as native FC ports. Configuring a Physical Fibre Channel Interface describes how to configure the port blocks as physical FC interfaces.
Do not configure ports that you want to use for native FC traffic as part of an Ethernet VLAN or as Ethernet ports.
Configure a port as an FC interface when the port connects to the F_Port of an FC switch.
FC interface configuration includes:
Explicitly specifying one or more ports as an FC family interface in NP_Port mode (mandatory).
Configuring the FC interface options port speed and buffer-to-buffer credit state change number (BB_SC_N) (optional).
Configuring the interface as a loopback interface (optional).
The buffer-to-buffer state change number feature prevents the loss of buffer-to-buffer credits between the two interfaces on either end of an FC link. The state change number determines the number of frames and receiver ready (R_RDY) primitives the interfaces exchange between the state change send (BB_SCs) and the state change receive (BB_SCr) primitives used to track these transactions.
Enabling BB_SC_N by configuring BB_SC_N on both of the FC link interfaces:
Requests that 2BB_SC_N number of frames be sent between two consecutive BB_SCs primitives, and
Requests that 2BB_SC_N number of R_RDY primitives be sent between two consecutive BB_SCr primitives.
When the number of R_RDY primitives received equals 2BB_SC_N, the R_RDY counter resets to zero. When the number of frames received equals 2BB_SC_N, the frame counter resets to zero. The interfaces calculate the number of buffer-to-buffer credits lost based on counter discrepancies and take corrective action to recover the lost credits.
If you enable BB_SC_N, the recommended BB_SC_N setting is eight. Setting the BB_SC_N number to zero (0) disables the feature. If either of the two connected FC interfaces is configured with zero as the BB_SC_N value, then both interfaces disable the feature. If the two connected FC interfaces have different nonzero BB_SC_N numbers configured, both interfaces use the higher number.
For the port to transport FC traffic, you must also set the physical port as an FC port using the port-range command.
To configure an FC interface using the CLI:
After you configure one or more FC interfaces, assign them and an FCoE VLAN to an FC fabric.
