The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS commands that begin with F that are used to manage a Cisco Nexus 2000 Series Fabric Extender from a Cisco Nexus 5500 switch.
To associate a Cisco Nexus 2000 Series Fabric Extender (FEX) to a switch for pinning Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP) and FCoE traffic, use the fcoe command. To remove the association, use the no form of this command.
Specifies the VSAN status. The VSAN ID range is from 1 to 4094. |
FEX configuration mode
VLAN configuration mode
|
|
---|---|
Before you use this command, make sure that you enable the Fabric Extender (FEX) features on the switch by using the feature fex command.
You can use this command only on a Cisco Nexus 2232P Fabric Extender. When you bind an interface to a virtual Fibre Channel interface to enable FCoE traffic, you must use slot number 1. The port number can be from 1 to 32.
This example shows how to configure a FEX as FCoE enabled:
This example shows how to configure a pair of FEXs to carry FCoE traffic in a fabric virtual port channel (vPC) topology, with the host uplink ports in the FEXs configured to the same port channel:
This example shows how to configure FCoE traffic on a VLAN:
This example shows how to disable FCoE traffic on a FEX:
|
|
---|---|
To enable Fabric Extender (FEX) features on the switch, use the feature fex command. To disable FEX, use the no form of this command.
|
|
---|---|
This example shows how to enable FEX features on the switch:
|
|
---|---|
Creates a Fabric Extender and enters fabric extender configuration mode. |
|
To create a Fabric Extender and enter fabric extender configuration mode, use the fex command. To delete the Fabric Extender configuration, use the no form of this command.
Fabric Extender chassis ID. The chassis ID range is from 100 to 199. |
|
|
You can create and configure the Fabric Extender before you connect and associate it to an interface on the parent switch. Once you associate the Fabric Extender to the switch, the configuration you created is transferred over to the Fabric Extender and applied.
This example shows how to enter Fabric Extender configuration mode:
switch#
configure terminal
switch(config)#
fex 101
This example shows how to delete the Fabric Extender configuration:
switch(config-fex)#
no fex 101
To associate a Fabric Extender to a fabric interface, use the fex associate command. To disassociate the Fabric Extender, use the no form of this command.
no fex associate [ chassis_ID ]
Fabric Extender chassis ID. The chassis ID range is from 100 to 199. |
|
|
Before you can associate an interface on the parent switch to the Fabric Extender, you must first make the interface into a fabric interface by entering the switchport mode fex-fabric command.
This example shows how to associate the Fabric Extender to an Ethernet interface:
This example shows how to associate the Fabric Extender to an EtherChannel interface:
|
|
---|---|
Displays all configured Fabric Extender chassis connected to the switch. |
|
To redistribute the host interfaces on a Fabric Extender, use the fex pinning redistribute command.
fex pinning redistribute chassis_ID
Fabric Extender chassis ID. The chassis ID range is from 100 to 199. |
|
|
When you provision the Fabric Extender using the statically pinned mode (see the Cisco Nexus 2000 Series Fabric Extender Software Configuration Guide), the host interfaces on the Fabric Extender are pinned to the fabric interfaces in the order that they were initially configured. The next time that you reboot the Fabric Extender, the configured fabric interfaces are pinned to the host interfaces in an ascending order by the port number of the fabric interface.
Use the fex pinning redistribute command if you want to configure the same fixed distribution of host interfaces without restarting the Fabric Extender after your initial configuration.
This example shows how to redistribute the host interfaces on a Fabric Extender:
switch#
fex pinning redistribute 101
|
|
---|---|
Displays all configured Fabric Extender chassis connected to the switch. |
|
Displays the Fabric Extender ports pinned to a specific switch interface. |
To limit the amount of input buffer space (in bytes) allocated to each Fabric Extender port, use the fex queue-limit command. To disable the drop threshold and allow a Fabric Extender port to use all available buffer space, use the no form of this command.
Fabric Extender queue limit is available in the default configuration and is set on.
|
|
---|---|
By default, the drop threshold applies to each Fabric Extender port to limit the amount of buffer being allocated for each port. To restore the default queue limit of each Fabric Extender port, use the fex queue-limit command.
This example shows how to set the queue limit for the input buffer for each Fabric Extender port:
This example shows how to restore the default queue limit for each Fabric Extender port:
|
|
---|---|
Displays all configured Fabric Extender chassis connected to the switch. |