- 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
Disabling Storm Control on FCoE Interfaces on an FCoE-FC Gateway
Storm control is not supported on the FCoE interfaces of an FCoE-FC gateway VLAN. Enabling storm control on an FCoE-FC gateway VLAN interface may cause FCoE packet loss. Storm control is disabled by default on all interfaces. However, if you enabled storm control globally on all switch interfaces or on any interfaces that are part of the FCoE VLAN interface, you must disable storm control on the Ethernet interfaces of the FCoE VLAN.
If storm control is enabled on only a few interfaces of the
FCoE VLAN, you can disable storm control on individual interfaces
by including the delete ethernet-switching-options storm-control
interface interface-name statement in the
configuration, where interface-name is the name of the interface on which you want to disable storm
control.
If storm control is enabled globally on the switch when the switch is acting as an FCoE-FC gateway, it is often easiest to disable storm control on all interfaces, then enable storm control only on Ethernet interfaces that are not part of the FCoE VLAN interface.
If storm control is enabled globally, you can disable storm control in either of two ways:
Disable storm control on all interfaces, then enable storm control on the interfaces you want to use storm control. (From the default configuration, you cannot disable storm control on individual interfaces because the default configuration enables storm control on
allinterfaces, not on individual interfaces.)For example, if you want interfaces xe-0/0/20, xe-0/0/21, and xe-0/0/22 to use storm control, disable storm control on all interfaces, then enable storm control on those three interfaces:
Disable storm control on all interfaces:
content_copy zoom_out_mapuser@switch# delete ethernet-switching-options storm-control interface all
Enable storm control on interfaces xe-0/0/20, xe-0/0/21, and xe-0/0/22:
content_copy zoom_out_mapuser@switch# set ethernet-switching-options storm-control interface xe-0/0/20 user@switch# set ethernet-switching-options storm-control interface xe-0/0/21 user@switch# set ethernet-switching-options storm-control interface xe-0/0/22
Disable storm control for all unknown unicast traffic on all interfaces by including the following statement in your configuration:
content_copy zoom_out_mapuser@switch# set ethernet-switching-options storm-control interface all no-unknown-unicast
