Cisco UCS Manager Network Management Guide Using the CLI, Release 6.0

Port Functionality on Cisco UCS 6664 Fabric Interconnect

The Cisco UCS 6664 Fabric Interconnect is a 2-rack unit (RU) fixed-port system designed for flexible and high-performance networking. It features 64 front panel ports that support a variety of connectivity options.

Front Panel Port Configuration and Types

The UCS 6664 Fabric Interconnect supports the following possible configurations or port types for each front panel port:


Port Number	Port Hardware	Admin Port Speed	Port Type	Port Role
1-24	QSFP 28	40 Gbps/100 Gbps	Gigabit Ethernet	Server Port Ethernet/FCoE Uplink Port FCoE Storage Port Appliance Port (EHM only) Monitor Port
25-40 (Unified Ports)	SFP28	16 Gbps/32 Gbps/64 Gbps	Fibre Channel (FC)	FC Uplink Port FC Storage Port
25-40 (Unified Ports)	SFP28	10 Gbps/25 Gbps	Gigabit Ethernet	Server Port Ethernet/FcoE Uplink Port Appliance Port (EHM only) Monitor Port
41-64 Note: Ports 49–64 are MAC Security (MACsec)-capable	QSFP 28	40 Gbps/100 Gbps	Gigabit Ethernet	Server Port Ethernet/FCoE Uplink Port FCoE Storage Port Appliance Port (EHM only) Monitor Port

Note

Breakout port functionality is not supported on Cisco UCS 6600 Series Fabric Interconnects.

Unified Ports on the Cisco UCS 6500 Series Fabric Interconnects

Unified ports are ports on the Cisco UCS 6500 Series Fabric Interconnects that you can configure to carry either Ethernet or Fibre Channel traffic. A Cisco UCS domain cannot use these un-reserved ports until you configure them.

Note

When you configure a port on a Fabric Interconnect, the administrative state is automatically set to enabled. If the port is connected to another device, this may cause traffic disruption. You can disable the port after configuring it. Configurable beacon LEDs indicate which unified ports are configured for the selected port mode.

Configuring Ethernet Breakout Ports on UCS 6536 Fabric Interconnects

Procedure

Step 1

On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name.

The Fabric Interconnect General tab appears, providing at-a-glance status, actions, physical display, properties, and firmware information for the selected fabric interconnect.

Step 2

View the available port(s) to break out.

Ensure that the port overall status is up and admin status is available. Do one of the following:

In the Work pane, click the Physical Ports tab. The Ethernet Ports and FC Ports subtabs appear.
In the Work pane, click the Physical Display tab. The Physical Display shows a graphical representation of the base fabric interconnect with a legend to help you identify port admin status.
In the Navigation pane, expand Fabric_Interconnect_Name > Fixed Module > Ethernet Ports. this action displays ports in a tree view.

Step 3

Select one or more ports that you can break out. On the UCS 6536 fabric interconnect, ports 1 to 36 support breakout. Do one of the following:

On the Physical Display, click a port or Ctrl-click to select multiple ports.
On the Ethernet Ports tab, click a port or Ctrl-click to select multiple ports.
On the Ethernet Ports tree view, click a port or Ctrl-click to select multiple ports.

Step 4

Configure the selected port(s) as breakout ports.

On the Ethernet Ports tab, right-click the selected port(s) and choose Configure 4x10G Breakout Port or Configure 4x25G Breakout Port from the pop-up menu.
On the Ethernet Ports tree view, right-click the selected port(s) and choose Configure 4x10G Breakout Port or Configure 4x25G Breakout Port from the pop-up menu. You can also select ports in the Ethernet Ports tree view and select Configure Breakout Port from the Work pane Actions Area. From the drop-down list, choose whether you want to configure the breakout port as a 4x10G port or a 4x25G port.

Step 5

Click OK.

Step 6

Configure the breakout ports according to your requirements.

Right-click one or more ports and select one of the following options. This table describes the actions that occur when you select the option. If a option is disabled, the port is already configured as such.


Configure Option	Action
Configure as Server Port	You confirm your action. Configuration takes place. The system displays a successful message. Click Yes.
Configure as Uplink Port	You confirm your action. Configuration takes place. The system displays a successful message. Click Yes.
Configure as FCoE Uplink Port	You confirm your action. Configuration takes place. The system displays a successful message. Click Yes.
Configure as FCoE Storage Port	You confirm your action. Configuration takes place. The system displays a successful message. Click Yes.
Configure as Appliance Port	You confirm your action. Configuration takes place. The system displays a successful message. Click Yes.

Step 7

The confirmation dialog box displays. Click Yes.

Note

Ethernet breakout port configuration will not lead to Fabric Interconnect reboot.

Configuring Fibre Channel Breakout Ports

Converting Ethernet Ports to Fibre Channel Breakout Port

You can follow the below steps to configure ethernet ports to Fibre Channel ports using scope cabling:

Procedure

	Command or Action	Purpose
Step 1	UCS-A # scope cabling	Enters the cabling mode.
Step 2	UCS-A /cabling # scope fabric a	Enters cabling fabric mode for the specified fabric.
Step 3	UCS-A /cabling/fabric # create breakout `1 36`	Creates the breakout port on the selected slot and port.
Step 4	UCS-A /cabling/fabric/breakout* # set transport fc	Creates Fibre Channel uplink breakout ports.
Step 5	UCS-A /cabling/fabric/breakout* # commit-buffer	Commits the transaction to the server.

Example

The following example creates breakout ports on Cisco UCS 6536 Fabric Interconnect sets the breakout type, and commits the transaction:

UCS-A# scope cabling 
UCS-A /cabling # scope fabric a
UCS-A /cabling/fabric/breakout* # create breakout 1 36
UCS-A /cabling/fabric/breakout* # set transport fc

Note

This operation will change port mode from Ethernet to Fibre Channel or vice-versa. When committed, this change will require the switch to reboot.


UCS-A /cabling/fabric/breakout* # commit-buffer

Converting Ethernet Breakout Port to Fibre Channel Breakout Port

Follow the below commands to convert any existing ethernet breakout ports to Fibre Channel breakout ports using scope cabling:

Procedure

	Command or Action	Purpose
Step 1	UCS-A # scope cabling	Enters the cabling mode.
Step 2	UCS-A /cabling # scope fabric a	Enters cabling fabric mode for the specified fabric.
Step 3	UCS-A /cabling/fabric # show breakout	Shows the existing breakout ports.
Step 4	UCS-A /fc-uplink/fabric # scope breakout `1 36`	Enters the breakout port.
Step 5	UCS-A /fc-uplink/fabric/breakout # set transport fc	Creates the FC uplink breakout ports.
Step 6	UCS-A /cabling/fabric/breakout* # commit-buffer	Commits the transaction to the server.

Example

The following example creates breakout ports on a UCS 6536 Fabric Interconnect, sets the breakout type, and commits the transaction:

UCS-A# scope cabling 
UCS-A /cabling # scope fabric a
UCS-A /fc-uplink/fabric # show breakout
port breakout:
    Slot ID    Port ID    breakout type FC breakout type transport type
    ---------- ---------- ------------- ---------------- --------------
             1         36        10g 4x            Unknown           Ether
UCS-A /cabling/fabric # scope breakout 1 36
UCS-A /fc-uplink/fabric/breakout # set transport fc

Note

This operation will change port mode from Ethernet to Fibre Channel or vice-versa. When committed, this change will require the switch to reboot.


UCS-A /cabling/fabric/breakout* # commit-buffer

Converting Ethernet Breakout Port to Fibre Channel Breakout Port Using Fibre Channel Uplink

To create ethernet breakout port through Fibre Channel Uplink, the port should already be in ethernet breakout mode.

Procedure

	Command or Action	Purpose
Step 1	UCS-A # scope fc-uplink	Enters the Fibre Channel uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric a	Enters cabling fabric mode for the specified fabric.
Step 3	UCS-A /fc-uplink/fabric # create aggr-interface `slot-idport-id`	Creates the breakout port on the selected slot and port. The Slot ID ranges from 1 through 4 and the Port ID ranges from 36 through 33.
Step 4	UCS-A /fc-uplink/fabric/aggr-interface* # create br-interface `slot-id`	Creates the breakout port on the selected port.
Step 5	UCS-A /fc-uplink/fabric/aggr-interface/br-interface* # up	Sets the breakout port on the selected slot and port as FC uplink port.
Step 6	Repeat steps 4 and 5 for the remaining `slot-id` from 1 through 4.
Step 7	UCS-A /fc-uplink/fabric/aggr-interface/br-interface*# commit-buffer	Commits the transaction to the server.

Example

The following example creates breakout ports on a UCS 6536 Fabric Interconnect, sets the breakout type, and commits the transaction:

UCS-A# scope fc-uplink 
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # create aggr-interface 1 36
UCS-A /fc-uplink/fabric/aggr-interface* # create br-interface 1
UCS-A /fc-uplink/fabric/aggr-interface/br-interface* # up
UCS-A /fc-uplink/fabric/aggr-interface* # create br-interface 2
UCS-A /fc-uplink/fabric/aggr-interface/br-interface* # up
UCS-A /fc-uplink/fabric/aggr-interface* # create br-interface 3
UCS-A /fc-uplink/fabric/aggr-interface/br-interface* # up
UCS-A /fc-uplink/fabric/aggr-interface* # create br-interface 4
UCS-A /fc-uplink/fabric/aggr-interface/br-interface* # up
UCS-A /fc-uplink/fabric/aggr-interface/br-interface* # commit-buffer

Note

You must create all four breakout interfaces to proceed with commit-buffer.

Deleting Fibre Channel Breakout Port

Deleting Fibre Channel Breakout Ports

The example described in this topic describes how to delete an entire breakout interface and to convert the port to normal ethernet interface using scope cabling.

Procedure

Command or Action

Purpose

Step 1

UCS-A# scope cabling

Enters the cabling mode.

Step 2

UCS-A# /cabling # scope fabric{a | b}

Enters cabling fabric mode for the specified fabric.

Step 3

UCS-A /cabling/fabric # delete breakout slot-id port-id

Deletes the breakout for the specified ports. Slot ID ranges from 1 through 4 and Port ID ranges from 33 through 36.

Note

This operation will change the port mode (from Ethernet to FC or vice-versa). When committed, it leads to reboot.

Step 4

UCS-A /cabling/fabric* # commit-buffer

Commits the transaction to the server.

What to do next

Verify that you deleted the specified breakout port using the show command.

Deleting Fibre Channel Breakout Ports Using Fibre Channel Uplink

You can follow the below steps to delete an entire breakout interface and to convert the port to normal ethernet interface.

Procedure

Command or Action

Purpose

Step 1

UCS-A# scope fc-uplink

Enters the cabling mode.

Step 2

UCS-A# /fc-uplink # scope fabric{a | b}

Enters cabling fabric mode for the specified fabric.

Step 3

UCS-A /fc-uplink/fabric # delete aggr-interface slot-id port-id

Deletes the breakout for the specified ports. Slot ID ranges from 1 through 4 and Port ID ranges from 33 through 36.

Note

This operation will change the port mode (from Ethernet to FC or vice-versa). When committed, it leads to reboot.

Step 4

UCS-A /fc-uplink/fabric* # commit-buffer

Commits the transaction to the server.

What to do next

Verify that you deleted the specified breakout port using the show command.

Appliance Breakout Port

Configuring Breakout Appliance Ports

You can follow the below steps to configure appliance breakout ports for both Cisco UCS Fabric Interconnects 9108 100G, Cisco UCS 6500 Series Fabric Interconnect, , and Cisco UCS 6400 Series Fabric Interconnect:

Procedure

Command or Action Purpose

Step 1

UCS-A# scope eth-storage

Enters Ethernet storage mode.

Step 2

UCS-A# /eth-storage # scope fabric{a | b}

Enters Ethernet storage mode for the specified fabric.

Step 3

UCS-A# /eth-storage/fabric # enter aggr-interface slot-numaggregate-port-num

Enters the interface for the specified aggregate(main) appliance port.

Step 4

UCS-A# /eth-storage/fabric/port-channel/member-aggr-port # create br -interfacebreakout-port-num

Creates an interface for the specified breakout appliance port.

Step 5

UCS-A# /eth-storage/fabric/port-channel/member-aggr-port/br-member-port # commit-buffer

Example:

The following example creates an interface for an appliance port 1 of the aggregate port 20 on slot 1 of fabric B, and commits the transaction:


UCS-A# scope eth-storage 
UCS-A /eth-storage # scope fabric a 
UCS-A /eth-storage/fabric # enter aggr-interface 1 20
UCS-A /eth-storage/fabric/aggr-interface # create br-interface 1
UCS-A /eth-storage/fabric/aggr-interface/br-interface* # commit-buffer

Example:

Note

If the port is only connected to 100G SFP which is broken out in 25x4 breakout port then when creating an appliance port, the default speed for a breakout port would be Auto.

Commits the transaction to the server.

Modifying Speed for Breakout Port of Type 25x4Gbps

Beginning from Cisco UCS Manager release 4.2(3b), you can modify the speed for breakout port of type 25x4Gbps for Cisco UCS Fabric Interconnects 9108 100G, Cisco UCS 6500, and Cisco UCS 6400 Series Fabric Interconnects. The commands are:

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-storage	Enters Ethernet storage mode.
Step 2	UCS-A# /eth-storage # scope fabric {a \| b}	Enters Ethernet storage mode for the specified fabric.
Step 3	UCS-A# /eth-storage/fabric /aggr-interface # create aggr-interface `1 28`	Enters the interface for the specified aggregate(main) appliance port.
Step 4	UCS-A# /eth-storage/fabric/aggr-interface # scope br -interface`1`	Creates an interface for the specified breakout appliance port.
Step 5	UCS-A# /eth-storage/fabric/aggr-interface/br-interface* # set adminspeed 25gbps	Modifies the admin speed to 25Gbps.
Step 6	UCS-A# /eth-storage/fabric/aggr-interface/br-interface* # commit-buffer	Commits the transaction.

Modifying FEC Value for Breakout Port of Type 25 x 4Gbps

From Release 4.2(3p) onwards, you can modify the FEC value for breakout port of type 25 x 4Gbps. The commands are:

Procedure

Command or Action

Purpose

Step 1

UCS-A# scope eth-storage

Enters Ethernet storage mode.

Step 2

UCS-A# /eth-storage # scope fabric {a | b}

Enters Ethernet storage mode for the specified fabric.

Step 3

UCS-A# /eth-storage/fabric /aggr-interface # create aggr-interface 1 28

Enters the interface for the specified aggregate(main) appliance port.

Step 4

UCS-A# /eth-storage/fabric/aggr-interface # scope br -interface1

Creates an interface for the specified breakout appliance port.

Step 5

UCS-A# /eth-storage/fabric/aggr-interface/br-interface* # set fec cl91

Modifies the FEC value to cl91.

Step 6

UCS-A# /eth-storage/fabric/aggr-interface/br-interface* # commit-buffer

Commits the transaction to the server.

Note

You cannot modify FEC value for any other port which is not a 25x4 breakout port. If you modify the speed of a breakout port other than 25x4, it will revert to Auto.

Unified Breakout Storage Ports

Converting Fibre Channel Uplink Port to Fibre Channel Storage Port

Follow the below commands to convert Fibre Channel Uplink port to Fibre Channel Storage port using scope cabling:

Procedure

	Command or Action	Purpose
Step 1	UCS-A # scope fc-storage	Enters the Fibre Channel storage mode.
Step 2	UCS-A /fc-storage # scope fabric a	Enters cabling fabric mode for the specified fabric.
Step 3	UCS-A /fc-storage/fabric # create aggr-interface`1 36`	Creates the breakout port on the specified aggregate (main) FC storage port.
Step 4	UCS-A /fc-storage/fabric/aggr-interface* # create br-interface br-fc `1`	Creates the breakout port on the selected port.
Step 5	UCS-A /fc-storage/fabric/aggr-interface/br-fc* # commit-buffer	Commits the transaction to the server.
Step 6	UCS-A /fc-storage/fabric/aggr-interface/br-fc # up
Step 7	UCS-A /fc-storage/fabric/aggr-interface # up
Step 8	UCS-A /fc-storage/fabric # show interface fc	Displays the output.

Example

Breakout FC Interface:

Slot ID    Aggr-Port ID Port ID    Admin State Speed         Config State Operational State State Reason    Lic State            Grace Prd
---------- ------------ ---------- ----------- ------------- ------------ ----------------- --------------- -------------------- ---------
         1           36 1          Enabled     16gbps        Inconsistent Sfp Not Present   FC storage interface unsupported in FC end host mode
                                                                                                            Not Applicable       0
UCS-A /fc-storage/fabric # scope aggr-interface 1 36
UCS-A /fc-storage/fabric/aggr-interface # show br-interface br-fc

Breakout FC Interface:
    Slot ID    Aggr-Port ID Port ID    Admin State Speed         Config State Operational State State Reason Lic State            Grace Prd
    ---------- ------------ ---------- ----------- ------------- ------------ ----------------- ------------ -------------------- ---------
             1           36 1          Enabled     16gbps        Inconsistent Sfp Not Present   FC storage interface unsupported in FC end host mode
                                                                                                             Not Applicable       0
UCS-A /fc-storage/fabric/aggr-interface #

Fibre Channel Uplink Breakout Port Channels

Configuring Fibre Channel Uplink Breakout Port Channel and Member Addition

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters Fibre Channel uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric a	Enters Fibre Channel uplink fabric mode for the specified fabric.
Step 3	UCS-A /fc-uplink/fabric # create port-channel `100`	Creates a port channel on the specified Fibre Channel uplink port, and enters Fibre Channel uplink fabric port channel mode.
Step 4	UCS-A /fc-uplink/fabric/port channel* # create aggr-interface `1 36`	Creates the interface for the specified aggregate (main) Fibre Channel uplink port.
Step 5	UCS-A /fc-uplink/fabric/port channel/aggr-interface* # create br-member-port `2`	Creates the member port for the specified breakout Fibre Channel uplink port.
Step 6	UCS-A /fc-uplink/fabric/port channel/aggr-interface/br-member-port* # commit-buffer	Commits the transaction to the system configuration.
Step 7	UCS-A /fc-uplink/fabric/port channel/aggr-interface/br-member-port # up
Step 8	UCS-A /fc-uplink/fabric/port channel/aggr-interface/br-member-port # show br-member-port	Displays the output.

Example

The following is the example for creating and adding a member to a breakout port channel:

Breakout Fc Member Port:

Slot Id    Aggr-Port ID  Port Id    Membership         Admin State User Label Oper State       Speed         Oper Speed    State Reason Lic State            Grace Perio
d            Fill Pattern
---------- ------------- ---------- ------------------ ----------- ---------- ---------------- ------------- ------------- ------------ -------------------- -----------
------------ ------------
         1 36            2          Down               Enabled                Sfp Not Present  Auto          Indeterminate SFP not present Not Applicable
              0 Idle
UCS-A /fc-uplink/fabric/port-channel/aggr-interface # up
UCS-A /fc-uplink/fabric/port-channel # show aggr-interface

Aggregate-Interface:
    Slot    Port          Config State Lic State Grace Prd
    ------- ------------- ------------ --------- ---------
          1 36            Disabled     Unknown   0
UCS-A /fc-uplink/fabric/port-channel # up
UCS-A /fc-uplink/fabric # show interface

Breakout Interface:

Slot Id    Aggr-Port ID  Port Id    Admin State Oper State       Fill Pattern  State Reason    Speed         Oper Speed    Lic State            Grace Prd
---------- ------------- ---------- ----------- ---------------- ------------- --------------- ------------- ------------- -------------------- ---------
         1 34            1          Disabled    Sfp Not Present  Idle          SFP not present 16gbps        Indeterminate Not Applicable       0
         1 34            2          Disabled    Sfp Not Present  Idle          SFP not present 16gbps        Indeterminate Not Applicable       0
         1 34            3          Disabled    Sfp Not Present  Idle          SFP not present 16gbps        Indeterminate Not Applicable       0
         1 34            4          Enabled     Sfp Not Present  Idle          SFP not present 16gbps        Indeterminate Not Applicable       0
         1 35            1          Enabled     Sfp Not Present  Idle          SFP not present 32gbps        Indeterminate Not Applicable       0
         1 35            2          Enabled     Sfp Not Present  Idle          SFP not present 32gbps        Indeterminate Not Applicable       0
         1 35            3          Enabled     Sfp Not Present  Idle          SFP not present 32gbps        Indeterminate Not Applicable       0
         1 35            4          Enabled     Sfp Not Present  Idle          SFP not present 32gbps        Indeterminate Not Applicable       0
         1 36            1          Disabled    Sfp Not Present  Idle          SFP not present 16gbps        Indeterminate Not Applicable       0
         1 36            3          Enabled     Sfp Not Present  Idle          SFP not present 16gbps        Indeterminate Not Applicable       0
         1 36            4          Enabled     Sfp Not Present  Idle          SFP not present 16gbps        Indeterminate Not Applicable       0

Breakout Fc Member Port:

Port-channel Slot  AggregatePort Port  Oper State      State Reason
------------ ----- ------------- ----- --------------- ------------
100              1 36            2     Sfp Not Present SFP not present
UCS-A /fc-uplink/fabric #

Configuring Ethernet Breakout Ports on Cisco UCS Fabric Interconnects 9108 100G

Procedure

Step 1

On the Equipment tab, expand Equipment > Fabric Interconnects > Fabric_Interconnect_Name.

The Fabric Interconnect General tab appears, providing at-a-glance status, actions, physical display, properties, and firmware information for the selected fabric interconnect.

Step 2

View the available port(s) to break out.

Ensure that the port overall status is up and admin status is available. Do one of the following:

In the Work pane, click the Physical Ports tab. The Ethernet Ports and FC Ports subtabs appear.
In the Work pane, click the Physical Display tab. The Physical Display shows a graphical representation of the base fabric interconnect with a legend to help you identify port admin status.
In the Navigation pane, expand Fabric_Interconnect_Name > Fixed Module > Ethernet Ports. this action displays ports in a tree view.

Step 3

Select one or more ports that you can break out. On the Cisco UCS Fabric Interconnects 9108 100G, ports 1 to 8 support breakout. Do one of the following:

On the Physical Display, click a port or Ctrl-click to select multiple ports.
On the Ethernet Ports tab, click a port or Ctrl-click to select multiple ports.
On the Ethernet Ports tree view, click a port or Ctrl-click to select multiple ports.

Step 4

Configure the selected port(s) as breakout ports.

On the Ethernet Ports tab, right-click the selected port(s) and choose Configure 4x10G Breakout Port or Configure 4x25G Breakout Port from the pop-up menu.
On the Ethernet Ports tree view, right-click the selected port(s) and choose Configure 4x10G Breakout Port or Configure 4x25G Breakout Port from the pop-up menu. You can also select ports in the Ethernet Ports tree view and select Configure Breakout Port from the Work pane Actions Area. From the drop-down list, choose whether you want to configure the breakout port as a 4x10G port or a 4x25G port.

Step 5

Click OK.

Step 6

Configure the breakout ports according to your requirements.

Right-click one or more ports and select one of the following options. This table describes the actions that occur when you select the option. If a option is disabled, the port is already configured as such.


Configure Option	Action
Configure as Uplink Port	You confirm your action. Configuration takes place. The system displays a successful message. Click Yes.
Configure as FCoE Uplink Port	You confirm your action. Configuration takes place. The system displays a successful message. Click Yes.
Configure as FCoE Storage Port	You confirm your action. Configuration takes place. The system displays a successful message. Click Yes.
Configure as Appliance Port	You confirm your action. Configuration takes place. The system displays a successful message. Click Yes.

Note

The Configure as Server Port option is supported on Cisco UCS Fabric Interconnects 9108 100G (Cisco UCS X-Series Direct). However, configuring a server port as a breakout port is not supported.

Step 7

The confirmation dialog box displays. Click Yes.

Note

Ethernet breakout port configuration will not lead to Fabric Interconnect reboot.

Displaying VIF Port Statistics Obtained From the Adaptor

Procedure

	Command or Action	Purpose
Step 1	UCS-A /fabric-interconnect # connect nxos {a \| b}	Enters NX-OS mode for the fabric interconnect.
Step 2	UCS-A(nxos)# show interface vethernet `veth-id` counters	Displays VIF port statistics that are obtained from the adaptor.

Example

The following example shows how to display VIF port statistics that are obtained from the adaptor:


UCS-A /fabric-interconnect # connect nxos a
UCS-A(nxos)# show interface vethernet 684 counters

--------------------------------------------------------------------------------
Port                                 InOctets                      InUcastPkts
--------------------------------------------------------------------------------
Veth684                                    0                                 0

--------------------------------------------------------------------------------
Port                              InMcastPkts                      InBcastPkts
--------------------------------------------------------------------------------
Veth684                                    0                                 0

--------------------------------------------------------------------------------
Port                                OutOctets                     OutUcastPkts
--------------------------------------------------------------------------------
Veth684                                    0                                 0

--------------------------------------------------------------------------------
Port                             OutMcastPkts                     OutBcastPkts
--------------------------------------------------------------------------------
Veth684                                    0                                 0

Displaying VIF Port Statistics Obtained From the ASIC

Procedure

	Command or Action	Purpose
Step 1	UCS-A /fabric-interconnect # connect nxos {a \| b}	Enters NX-OS mode for the fabric interconnect.
Step 2	UCS-A(nxos)# show platform fwm info lif vethernet `veth-id` \| grep frame	Displays VIF-port RX and TX frame statistics obtained from the ASIC. RX statistics are for all type of frames. Tx statistics are only for known unicast frames.

Example

The following example shows how to display VIF-port RX and TX frame statistics obtained from the ASIC:


UCS-A /fabric-interconnect # connect nxos a
UCS-A(nxos)# show platform fwm info lif vethernet 684 | grep frame

vif29 pd: rx frames: 0 tx frames: 0;

UCS-A(nxos)#

Displaying VIF Ports That Correspond to NIV Ports

Procedure

	Command or Action	Purpose
Step 1	UCS-A /fabric-interconnect # connect nxos {a \| b}	Enters NX-OS mode for the fabric interconnect.
Step 2	UCS-A(nxos)# show platform fwm info lif vethernet `veth-id` \| grep niv	Displays VIF ports that correspond to NIV ports.

Example

The following example shows how to display VIF ports that correspond to NIV ports:


UCS-A /fabric-interconnect # connect nxos a
UCS-A(nxos)# show platform fwm info lif vethernet 741 | grep niv

vif20 pd: niv_port_id 0x7000001f (the 0x1F or “31” is the Source/Dest-VP index)

Verifying Status of Backplane Ports

Procedure

	Command or Action	Purpose
Step 1	UCS-A /fabric-interconnect # connect nxos {a \| b}	Enters NX-OS mode for the fabric interconnect.
Step 2	UCS-A(nxos)# show interface br	Displays the configuration of the interface, including the speed and status of the backplane ports.

Example

The following example shows how to verify the status of backplane ports for fabric interconnect A:


UCS-A /fabric-interconnect # connect nxos a
UCS-A(nxos)# show interface br


--------------------------------------------------------------------------------
Ethernet      VLAN   Type Mode   Status  Reason                   Speed     Port
Interface                                                                   Ch #
--------------------------------------------------------------------------------
Eth1/1        1       eth  access down    SFP not inserted            40G(D) --
Eth1/2        1       eth  access down    SFP not inserted            40G(D) --
Br-Eth1/3/1   1       eth  access down    Administratively down       10G(D) --
Br-Eth1/3/2   1       eth  access down    Administratively down       10G(D) --
Br-Eth1/3/3   1       eth  access down    Administratively down       10G(D) --
Br-Eth1/3/4   1       eth  access down    Administratively down       10G(D) --
Eth1/4        1       eth  access down    SFP not inserted            40G(D) --
Br-Eth1/5/1   4044    eth  trunk  down    Link not connected          10G(D) --
Br-Eth1/5/2   4044    eth  trunk  down    Link not connected          10G(D) --
Br-Eth1/5/3   4044    eth  trunk  down    Link not connected          10G(D) --
Br-Eth1/5/4   4044    eth  trunk  down    Link not connected          10G(D) --
Eth1/6        1       eth  access down    SFP not inserted            40G(D) --
Eth1/7        1       eth  access down    SFP not inserted            40G(D) --
Eth1/8        1       eth  access down    SFP not inserted            40G(D) --
Eth1/9        1       eth  access down    SFP not inserted            40G(D) --
Eth1/10       1       eth  access down    SFP not inserted            40G(D) --
Eth1/11       1       eth  fabric up      none                        40G(D) --
Eth1/12       1       eth  access down    SFP not inserted            40G(D) --
Eth1/13       1       eth  access down    SFP not inserted            40G(D) --
Eth1/14       1       eth  access down    SFP not inserted            40G(D) --
Eth1/15       1       eth  access down    SFP not inserted            40G(D) --
Eth1/16       1       eth  access down    SFP not inserted            40G(D) --
Eth1/17       1       eth  access down    SFP not inserted            40G(D) --
Eth1/18       1       eth  access down    SFP not inserted            40G(D) --
Eth1/19       1       eth  access down    SFP not inserted            40G(D) --
Eth1/20       1       eth  access down    SFP not inserted            40G(D) --
Br-Eth1/21/1  1       eth  trunk  up      none                        10G(D) --
Br-Eth1/21/2  1       eth  trunk  up      none                        10G(D) --
Br-Eth1/21/3  1       eth  trunk  down    Link not connected          10G(D) --
Br-Eth1/21/4  1       eth  trunk  up      none                        10G(D) --
Eth1/22       1       eth  access down    SFP not inserted            40G(D) --
Eth1/23       1       eth  access down    SFP not inserted            40G(D) --
Eth1/24       1       eth  access down    SFP not inserted            40G(D) --
Eth1/25       1       eth  access down    SFP not inserted            40G(D) --
Eth1/26       1       eth  access down    SFP not inserted            40G(D) --
Eth1/27       1       eth  access down    SFP not inserted            40G(D) --
Eth1/28       1       eth  access down    SFP not inserted            40G(D) --
Eth1/29       1       eth  access down    SFP not inserted            40G(D) --
Eth1/30       1       eth  access down    SFP not inserted            40G(D) --
Eth1/31       1       eth  access down    SFP not inserted            40G(D) --
Eth1/32       1       eth  access down    SFP not inserted            40G(D) --

--------------------------------------------------------------------------------
Port-channel VLAN    Type Mode   Status  Reason                    Speed   Protocol
Interface
--------------------------------------------------------------------------------
Po1285       1       eth  vntag  up      none                       a-10G(D)  none
Po1286       1       eth  vntag  up      none                       a-10G(D)  none
Po1287       1       eth  vntag  up      none                       a-10G(D)  none
Po1288       1       eth  vntag  up      none                       a-10G(D)  none
Po1289       1       eth  vntag  up      none                       a-10G(D)  none

--------------------------------------------------------------------------------
Port   VRF          Status IP Address                              Speed    MTU
--------------------------------------------------------------------------------
mgmt0  --           down   10.197.157.252                          --       1500

--------------------------------------------------------------------------------
Vethernet     VLAN   Type Mode   Status  Reason                    Speed
--------------------------------------------------------------------------------
Veth691       4047   virt trunk  down    nonParticipating         auto
Veth692       4047   virt trunk  up      none                     auto
Veth693       1      virt trunk  down    nonParticipating         auto
Veth695       1      virt trunk  up      none                     auto
Veth699       1      virt trunk  up      none                     auto

-------------------------------------------------------------------------------
Interface Secondary VLAN(Type)                    Status Reason
-------------------------------------------------------------------------------
Vlan1     --                                      down   Administratively down

--------------------------------------------------------------------------------
Ethernet       VLAN   Type Mode   Status  Reason                  Speed     Port
Interface                                                                   Ch #
--------------------------------------------------------------------------------
Eth1/1/1       1       eth  vntag  up      none                       10G(D) 1286
Eth1/1/2       1       eth  access down    Administratively down      10G(D) --
Eth1/1/3       1       eth  vntag  up      none                       10G(D) 1286
Eth1/1/4       1       eth  access down    Administratively down      10G(D) --
Eth1/1/5       1       eth  vntag  up      none                       10G(D) 1287
Eth1/1/6       1       eth  access down    Administratively down      10G(D) --
Eth1/1/7       1       eth  vntag  up      none                       10G(D) 1287
Eth1/1/8       1       eth  access down    Administratively down      10G(D) --
Eth1/1/9       1       eth  vntag  up      none                       10G(D) 1289
Eth1/1/10      1       eth  access down    Administratively down      10G(D) --
Eth1/1/11      1       eth  vntag  up      none                       10G(D) 1289
Eth1/1/12      1       eth  access down    Administratively down      10G(D) --
Eth1/1/13      1       eth  vntag  up      none                       10G(D) 1285
Eth1/1/14      1       eth  access down    Administratively down      10G(D) --
Eth1/1/15      1       eth  vntag  up      none                       10G(D) 1285
Eth1/1/16      1       eth  access down    Administratively down      10G(D) --
Eth1/1/17      1       eth  access down    Administratively down      10G(D) --
Eth1/1/18      1       eth  vntag  up      none                       10G(D) 1288
Eth1/1/19      1       eth  access down    Administratively down      10G(D) --
Eth1/1/20      1       eth  vntag  up      none                       10G(D) 1288
Eth1/1/21      1       eth  access down    Administratively down      10G(D) --
Eth1/1/22      1       eth  access down    Administratively down      10G(D) --
Eth1/1/23      1       eth  access down    Administratively down      10G(D) --
Eth1/1/24      1       eth  access down    Administratively down      10G(D) --
Eth1/1/25      1       eth  access down    Administratively down      10G(D) --
Eth1/1/26      1       eth  access down    Administratively down      10G(D) --
Eth1/1/27      1       eth  access down    Administratively down      10G(D) --
Eth1/1/28      1       eth  access down    Administratively down      10G(D) --
Eth1/1/29      1       eth  access down    Administratively down      10G(D) --
Eth1/1/30      1       eth  access down    Administratively down      10G(D) --
Eth1/1/31      1       eth  access down    Administratively down      10G(D) --
Eth1/1/32      1       eth  access down    Administratively down      10G(D) --
Eth1/1/33      4044    eth  trunk  up      none                      1000(D) --

Automatic Configuration of Fabric Interconnect Server Ports

Starting with Cisco UCS Manager release 3.1(3), you can automatically configure the fabric interconnect server ports. The server Port Auto-Discovery Policy determines how the system reacts when a new rack server, chassis, or FEX is added. By enabling this policy, Cisco UCS Manager automatically determines the type of device connected to the switch port and configures the switch port accordingly.

Note

If you do not want a Cisco UCS C-Series appliance to be UCS Managed, pre-configure the appliance ports before connecting VIC ports to the Cisco UCS Fabric Interconnects.
The Port Auto-Discovery Policy is not applicable for servers connected through direct 25G port or 4x25g breakout on Cisco UCS 6454, UCS 64108, and 6536 Fabric Interconnects.

Automatically Configuring Server Ports

Procedure

Step 1

UCS-A# scope org/

Enters the root organization mode.

Step 2

UCS-A / org# scope por

Enters organization port discovery policy mode.

Step 3

UCS-A / org / port-disc-policy# set descr

Provides a description for the port discovery policy.

Step 4

UCS-A / org / port-disc-policy# set server-auto-disc

Enables port auto-discovery.

Note

By default server-auto-disc is disabled. Port auto-discovery is triggered by enabling server-auto-disc.

Example

The following example shows how to enable automatic configuration of fabric interconnect server ports:

UCS-A# scope org/ 
UCS-A /org# scope por
UCS-A / org / port-disc-policy #  set descr
UCS-A / org / port-disc-policy #  set server-auto-disc

Configuring a Server Port

All of the port types listed are configurable on both the fixed and expansion module.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-server	Enters Ethernet server mode.
Step 2	UCS-A /eth-server # scope fabric {a \| b}	Enters Ethernet server fabric mode for the specified fabric.
Step 3	UCS-A /eth-server/fabric # create interface `slot-num` `port-num`	Creates an interface for the specified Ethernet server port.
Step 4	UCS-A /eth-server/fabric # commit-buffer	Commits the transaction to the system configuration.

Example

The following example shows how to create an interface for Ethernet server port 4 on slot 1 of fabric B and commit the transaction:

UCS-A# scope eth-server
UCS-A /eth-server # scope fabric b
UCS-A /eth-server/fabric # create interface 1 4
UCS-A /eth-server/fabric* # commit-buffer
UCS-A /eth-server/fabric #

Unconfiguring a Server Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-server	Enters Ethernet server mode.
Step 2	UCS-A /eth-server # scope fabric {a \| b}	Enters Ethernet server fabric mode for the specified fabric.
Step 3	UCS-A /eth-server/fabric # delete interface `slot-num` `port-num`	Deletes the interface for the specified Ethernet server port.
Step 4	UCS-A /eth-server/fabric # commit-buffer	Commits the transaction to the system configuration.

Example

The following example unconfigures Ethernet server port 12 on slot 1 of fabric B and commits the transaction:

UCS-A# scope eth-server
UCS-A /eth-server # scope fabric b
UCS-A /eth-server/fabric # delete interface 1 12
UCS-A /eth-server/fabric* # commit-buffer
UCS-A /eth-server/fabric #

Configuring a Server Port for Forward Error Correction

The N9K-C93180YC-FX3 in FEX mode connects to 25Gps or 100 Gps server port on the Cisco UCS 6400 series Fabric Interconnects and Cisco UCS 6500 series Fabric Interconnects. To have the link-up at 25Gps, the server port on Cisco UCS 6400 series Fabric Interconnect requires forward error correction (FEC) of CL-74. This CL-74 configuration on the server port is required only for connecting N9K-C93180YC-FX3 to Cisco UCS 6400 series Fabric Interconnects and Cisco UCS 6500 series Fabric Interconnects.

Note

The CL-74 configuration is not applicable for other server port connectivity such as I/O module or direct-attached rack server.

Table 1. FEC CL-74 Support Matrix
Port Speed	FEC CL-74
1 Gbps	Not supported
10 Gbps	Not supported
25 Gbps	Supported
40 Gbps	Not supported
100 Gbps	Supported
Auto	Based on inserted tranceiver's maximum supported speed

Procedure

Command or Action

Purpose

Step 1

UCS-A# scope eth-server

Enters Server mode.

Step 2

UCS-A /eth-server # scope fabric {a | b}

Enters Server mode for the specified fabric.

Step 3

UCS-A /eth-server/fabric/interface # scope interface slot-id port-id

Enters Server interface mode for the specified interface.

Step 4

UCS-A /eth-server/fabric/interface # set fec {auto | cl74}

Sets the forward error correction setting as auto or cl74 for the server port.

Step 5

UCS-A /eth-server/fabric/interface # set auto-neg {enabled | disabled}

Sets the auto negotiate as enabled or disabled for the server port.

Step 6

UCS-A /eth-server/fabric/interface # commit-buffer

Commits the transaction to the system configuration.

Note

Following are the mandatory configuration parameters on the server port for connecting to N9K-C93180YC-FX3:

The FEC must be auto for 100Gps server port.
The FEC must be cl74 for 25Gps server port.
The auto-negotiation must be disabled for 100Gps server port.

Example

Example 1: The following example shows how to enable forward error correction cl74 with auto-negotiation enabled, on an interface for the 25Gps server port 15 on slot 2 of fabric A, and commit the transaction:

UCS-A# scope eth-server
UCS-A /eth-server # scope fabric a 
UCS-A /eth-server/fabric # scope interface 2 15
UCS-A /eth-server/fabric # set fec cl74
UCS-A /eth-server/fabric/interface # set auto-neg enabled
UCS-A /eth-server/fabric* # commit-buffer
UCS-A /eth-server/fabric #

Example 2: The following example shows how to enable forward error correction auto with auto-negotiation disabled, on an interface for the 100 Gps server port 17 on slot 1 of fabric A, and commit the transaction:

UCS-A# scope eth-server
UCS-A /eth-server # scope fabric a 
UCS-A /eth-server/fabric # scope interface 1 17
UCS-A /eth-server/fabric # set fec auto
UCS-A /eth-server/fabric/interface # set auto-neg disabled
UCS-A /eth-server/fabric* # commit-buffer
UCS-A /eth-server/fabric #

Configuring an Uplink Ethernet Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # scope fabric a \| b}	Enters Ethernet uplink fabric mode for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # create interface `slot-num` `port-num`	Creates an interface for the specified Ethernet uplink port.
Step 4	(Optional) UCS-A /eth-uplink/fabric # set speed {10gbps \| 1gbps}	(Optional) Sets the speed for the specified Ethernet uplink port.
Step 5	UCS-A /eth-uplink/fabric # commit-buffer	Commits the transaction to the system configuration.

Example

The following example shows how to create an interface for Ethernet uplink port 3 on slot 2 of fabric B, set the speed to 10 gbps, and commit the transaction:

UCS-A# scope eth-uplink
UCS-A /eth-uplink # scope fabric b 
UCS-A /eth-uplink/fabric # create interface 2 3
UCS-A /eth-uplink/fabric # set speed 10gbps
UCS-A /eth-uplink/fabric* # commit-buffer
UCS-A /eth-uplink/fabric #

Unconfiguring an Uplink Ethernet Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # scope fabric {a \| b}	Enters Ethernet uplink fabric mode for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # delete interface `slot-num` `port-num`	Deletes the interface for the specified Ethernet uplink port.
Step 4	UCS-A /eth-uplink/fabric # commit-buffer	Commits the transaction to the system configuration.

Example

The following example unconfigures Ethernet uplink port 3 on slot 2 of fabric B and commits the transaction:

UCS-A# scope eth-uplink
UCS-A /eth-uplink # scope fabric b 
UCS-A /eth-uplink/fabric # delete interface 2 3
UCS-A /eth-uplink/fabric* # commit-buffer
UCS-A /eth-uplink/fabric #

Configuring an Uplink Ethernet Port for Forward Error Correction

You can configure forward error correction (FEC) for uplink Ethernet ports, Ethernet appliances, and FCoE uplinks for transceiver modules that operate at 25 Gbps and 100 Gbps speeds that support this feature.

Table 2. Supported Port Speed and FEC Matrix
Port Speed	FEC CL-74	FEC CL-91	RS Cons 16	RS 1eee
1 Gbps	Not supported	Not supported	-	-
10 Gbps	Not supported	Not supported	Not supported	Not supported
25 Gbps	Supported	Supported	Supported	Supported
40 Gbps	Not supported	Not supported	Not supported	Not supported
100 Gbps	Not supported	Supported	Not supported	Not supported
Auto	Automatically selects the optimal FEC mode based on the transceiver's maximum supported speed.	Automatically selects the optimal FEC mode based on the transceiver's maximum supported speed.	Automatically selects the optimal FEC mode based on the transceiver's maximum supported speed.	Automatically selects the optimal FEC mode based on the transceiver's maximum supported speed.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # scope fabric a \| b}	Enters Ethernet uplink fabric mode for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # scope interface `slot-id` `port-id`	Enters Ethernet interface mode for the specified interface.
Step 4	UCS-A /eth-uplink/fabric # set fec {auto \|cl74 \| cl91 rs-cons16 \| rs-1eee }	Sets the forward error correction setting. For the Cisco UCS 6400 and 6500 series Fabric Interconnects, forward error correction is only configurable for 25 Gbps or 100 Gbps port speed.
Step 5	UCS-A /eth-uplink/fabric # commit-buffer	Commits the transaction to the system configuration.

Q-in-Q Forwarding

QinQ is defined by IEEE 802.1ad. QinQ is also known as 802.1Q-in-802.1Q that helps to expand the VLAN space through the addition of 802.1Q tag to 802.1Q-tagged packets. This expansion is also termed as VLAN stacking or double VLAN.

In general, the QinQ packets have a standard format. In a VLAN stacking, one 802.11Q tagged packet is encapsulated in another 802.1Q tag. During transmission, packets are forwarded on the outer VLAN tag on the public network and on the inner VLAN tag for private network.

Note

The 802.1Q supports 4096 VLANs.

Configuring Q-in-Q Forwarding

You can configure Q-in-Q forwarding for Cisco UCS Fabric Interconnects 9108 100G, Cisco UCS 6536 Fabric Interconnect and Cisco UCS 6400 Series Fabric Interconnect.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # set q-in-q-forwarding enabled	Enables Q-in-Q forwarding for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # commit-buffer	Commits the transaction to the system configuration.

Example

The following example shows how to enable Q-in-Q forwarding and commit the transaction:

UCS-A# scope eth-uplink
UCS-A /eth-uplink # set q-in-q-forwarding enabled
UCS-A /eth-uplink/fabric* # commit-buffer
UCS-A /eth-uplink/fabric #

Unconfiguring Q-in-Q Forwarding

You can unconfigure Q-in-Q forwarding for Cisco UCS Fabric Interconnects 9108 100G, Cisco UCS 6536 Fabric Interconnect and Cisco UCS 6400 Series Fabric Interconnect.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # set q-in-q-forwarding disabled	Disables Q-in-Q forwarding for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # commit-buffer	Commits the transaction to the system configuration.

Example

The following example shows how to disable Q-in-Q forwarding and commit the transaction:

UCS-A# scope eth-uplink
UCS-A /eth-uplink # set q-in-q-forwarding disabled
UCS-A /eth-uplink/fabric* # commit-buffer
UCS-A /eth-uplink/fabric #

Appliance Ports

Appliance ports are only used to connect fabric interconnects to directly attached NFS storage.

Note

When you create a new appliance VLAN, its IEEE VLAN ID is not added to the LAN Cloud. Therefore, appliance ports that are configured with the new VLAN remain down, by default, due to a pinning failure. To bring up these appliance ports, you have to configure a VLAN in the LAN Cloud with the same IEEE VLAN ID.

Cisco UCS Manager supports up to four appliance ports per fabric interconnect.

Configuring an Appliance Port

Procedure

Command or Action

Purpose

Step 1

UCS-A# scope eth-storage

Enters Ethernet storage mode.

Step 2

UCS-A /eth-storage # scope fabric{a | b}

Enters Ethernet storage mode for the specified fabric.

Step 3

UCS-A /eth-storage/fabric # create interface slot-num port-num

Creates an interface for the specified appliance port.

Step 4

(Optional) UCS-A /eth-storage/fabric/interface # set portmode {access | trunk}

(Optional)

Specifies whether the port mode is access or trunk. By default, the mode is set to trunk.

Note

If traffic for the appliance port needs to traverse the uplink ports, you must also define each VLAN used by this port in the LAN cloud. For example, you need the traffic to traverse the uplink ports if the storage is also used by other servers, or if you want to ensure that traffic fails over to the secondary fabric interconnect if the storage controller for the primary fabric interconnect fails.

Step 5

(Optional) UCS-A /eth-storage/fabric/interface # set pingroupname pin-group name

(Optional)

Specifies the appliance pin target to the specified fabric and port, or fabric and port channel.

Step 6

(Optional) UCS-A /eth-storage/fabric/interface # set prio sys-class-name

(Optional)

Specifies the QoS class for the appliance port. By default, the priority is set to best-effort.

The sys-class-name argument can be one of the following class keywords:

FC—Use this priority for QoS policies that control vHBA traffic only.
Platinum—Use this priority for QoS policies that control vNIC traffic only.
Gold—Use this priority for QoS policies that control vNIC traffic only.
Silver—Use this priority for QoS policies that control vNIC traffic only.
Bronze—Use this priority for QoS policies that control vNIC traffic only.
Best Effort—Do not use this priority. It is reserved for the Basic Ethernet traffic lane. If you assign this priority to a QoS policy and configure another system class as CoS 0, Cisco UCS Manager does not default to this system class. It defaults to the priority with CoS 0 for that traffic.

Step 7

(Optional) UCS-A /eth-storage/fabric/interface # set adminspeed {10gbps | 1 gbps}

(Optional)

Specifies the admin speed for the interface. By default, the admin speed is set to 10gbps.

Step 8

UCS-A /eth-storage/fabric/interface # commit buffer

Commits the transaction to the system configuration.

Example

The following example creates an interface for an appliance port 2 on slot 3 of fabric B, sets the port mode to access, pins the appliance port to a pin group called pingroup1, sets the QoS class to fc, sets the admin speed to 10 gbps, and commits the transaction:

UCS-A# scope eth-storage
UCS-A /eth-storage # scope fabric b
UCS-A /eth-storage/fabric # create interface 3 2
UCS-A /eth-storage/fabric* # set portmode access
UCS-A /eth-storage/fabric* # set pingroupname pingroup1
UCS-A /eth-storage/fabric* # set prio fc
UCS-A /eth-storage/fabric* # set adminspeed 10gbps
UCS-A /eth-storage/fabric* # commit-buffer
UCS-A /eth-storage/fabric #

What to do next

Assign a VLAN or target MAC address for the appliance port.

Assigning a Target MAC Address to an Appliance Port or Appliance Port Channel

The following procedure assigns a target MAC address to an appliance port. To assign a target MAC address to an appliance port channel, scope to the port channel instead of the interface.

Procedure

Command or Action

Purpose

Step 1

UCS-A# scope eth-storage

Enters Ethernet storage mode.

Step 2

UCS-A /eth-storage # scope fabric{a | b}

Enters Ethernet storage mode for the specified fabric.

Step 3

UCS-A /eth-storage/fabric # scope interface slot-id port-id

Enters Ethernet interface mode for the specified interface.

Note

To assign a target MAC address to an appliance port channel, use the scope port-channel command instead of scope interface .

Step 4

UCS-A /eth-storage/fabric/interface # create eth-target eth-target name

Specifies the name for the specified MAC address target.

Step 5

UCS-A /eth-storage/fabric/interface/eth-target # set mac-address mac-address

Specifies the MAC address in nn:nn:nn:nn:nn:nn format.

Example

The following example assigns a target MAC address for an appliance device on port 3, slot 2 of fabric B and commits the transaction:

UCS-A# scope eth-storage
UCS-A /eth-storage* # scope fabric b
UCS-A /eth-storage/fabric* # scope interface 2 3
UCS-A /eth-storage/fabric/interface* # create eth-target macname
UCS-A /eth-storage/fabric/interface* # set mac-address 01:23:45:67:89:ab
UCS-A /eth-storage/fabric/interface* # commit-buffer
UCS-A /eth-storage/fabric #

The following example assigns a target MAC address for appliance devices on port channel 13 of fabric B and commits the transaction:

UCS-A# scope eth-storage
UCS-A /eth-storage* # scope fabric b
UCS-A /eth-storage/fabric* # scope port-channel 13
UCS-A /eth-storage/fabric/port-channel* # create eth-target macname
UCS-A /eth-storage/fabric/port-channel* # set mac-address 01:23:45:67:89:ab
UCS-A /eth-storage/fabric/port-channel* # commit-buffer
UCS-A /eth-storage/fabric #

Creating an Appliance Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-storage	Enters Ethernet storage mode.
Step 2	UCS-A/eth-storage# create vlan `vlan-name` `vlan-id`	Creates a named VLAN, specifies the VLAN name and VLAN ID, and enters Ethernet storage VLAN mode.
Step 3	UCS-A/eth-storage/vlan# set sharing primary	Saves the changes.
Step 4	UCS-A/eth-storage/vlan# commit buffer	Commits the transaction to the system configuration.
Step 5	UCS-A/eth-storage# create vlan `vlan-name` `vlan-id`	Creates a named VLAN, specifies the VLAN name and VLAN ID, and enters Ethernet storage VLAN mode .
Step 6	UCS-A/eth-storage/vlan# set sharing community	Associates the primary VLAN to the secondary VLAN that you are creating.
Step 7	UCS-A/eth-storage/vlan# set pubnwname `primary vlan-name`	Specifies the primary VLAN to be associated with this secondary VLAN.
Step 8	UCS-A/eth-storage/vlan# commit buffer	Commits the transaction to the system configuration.

Example

The following example creates an appliance port:

UCS-A# scope eth-storage
UCS-A/eth-storage# create vlan PRI600 600
UCS-A/eth-storage/vlan* # set sharing primary
UCS-A/eth-storage/vlan* # commit-buffer
UCS-A/eth-storage # create vlan COM602 602
UCS-A/eth-storage/vlan* # set sharing isolated
UCS-A/eth-storage/vlan* # set pubnwname PRI600 
UCS-A/eth-storage/vlan* # commit-buffer

Mapping an Appliance Port to a Community VLAN

Procedure

Command or Action

Purpose

Step 1

UCS-A# scope eth-storage

Enters Ethernet storage mode.

Step 2

UCS-A/eth-storage# scope fabric {a| b}

Enters Ethernet storage fabric interconnect mode for the specified fabric interconnect.

Step 3

UCS-A/eth-storage/fabric# create interface slot-num port-num

Creates an interface for the specified Ethernet server port.

Step 4

UCS-A/eth-storage/fabric/interface# exit

Exits from the interface.

Note

Ensure you commit the transaction after associating with the VLAN.

Step 5

UCS-A/eth-storage/fabric# exit

Exits from the fabric.

Step 6

UCS-A/eth-storage# scope vlan vlan-name

Enters the specified VLAN.

Note

Ensure community VLAN is created in the appliance cloud.

Step 7

UCS-A/eth-storage/vlan# create member-port fabric slot-num port-num

Creates the member port for the specified fabric, assigns the slot number, and port number and enters member port configuration.

Step 8

UCS-A/eth-storage/vlan/member-port# commit

Commits the transaction to the system configuration.

Example

The following example maps an appliance port to an community VLAN:

UCS-A# scope eth-storage
UCS-A/eth-storage# scope fabric a
UCS-A/eth-storage/fabric# create interface 1 22
UCS-A/eth-storage/fabric/interface*# exit
UCS-A/eth-storage/fabric*# exit
UCS-A/eth-storage*# scope vlan COM602
UCS-A/eth-storage/vlan*# create member-port a 1 22
UCS-A/eth-storage/vlan/member-port* commit

Unconfiguring an Appliance Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A # scope eth-storage	Enters Ethernet storage mode.
Step 2	UCS-A /eth-storage # scope fabric {a \| b}	Enters Ethernet storage mode for the specified fabric.
Step 3	UCS-A /eth-storage/fabric # delete eth-interface slot-num port-num	Deletes the interface for the specified appliance port.
Step 4	UCS-A /eth-storage/fabric # commit-buffer	Commits the transaction to the system configuration.

Example

The following example unconfigures appliance port 3 on slot 2 of fabric B and commits the transaction:

UCS-A# scope eth-storage
UCS-A /eth-storage # scope fabric b
UCS-A /eth-storage/fabric # delete eth-interface 2 3
UCS-A /eth-storage/fabric* # commit-buffer
UCS-A /eth-storage/fabric #

Configuring an Appliance Port for Forward Error Correction

You can configure forward error correction (FEC) for appliance ports that operate at 25 Gbps and 100 Gpbs speeds that support this feature.

Table 3. Supported Port Speed and FEC Matrix
Port Speed	FEC CL-74	FEC CL-91	RS Cons 16	RS 1eee
1 Gbps	Not supported	Not supported	-	-
10 Gbps	Not supported	Not supported	Not supported	Not supported
25 Gbps	Supported	Supported	Supported	Supported
40 Gbps	Not supported	Not supported	Not supported	Not supported
100 Gbps	Not supported	Supported	Not supported	Not supported
Auto	Automatically selects the optimal FEC mode based on the transceiver's maximum supported speed.	Automatically selects the optimal FEC mode based on the transceiver's maximum supported speed.	Automatically selects the optimal FEC mode based on the transceiver's maximum supported speed.	Automatically selects the optimal FEC mode based on the transceiver's maximum supported speed.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-storage	Enters Appliance port mode.
Step 2	UCS-A /eth-storage # scope fabric a \| b}	Enters Appliance port fabric mode for the specified fabric.
Step 3	UCS-A /eth-storage/fabric # delete eth-interface `slot-id` `port-id`	Enters Appliance interface mode for the specified interface.
Step 4	UCS-A /eth-storage/fabric # set fec {auto \|cl74 \| cl91 rs-cons16 \| rs-1eee }	Sets the forward error correction setting. For the Cisco UCS 6400 and 6500 series Fabric Interconnects, forward error correction is only configurable for 25 Gbps or 100 Gbps port speed.
Step 5	UCS-A /eth-storage/fabric # commit-buffer	Commits the transaction to the system configuration.

FCoE Uplink Ports

FCoE uplink ports are physical Ethernet interfaces between the fabric interconnects and the upstream Ethernet switch, used for carrying FCoE traffic. With this support the same physical Ethernet port can carry both Ethernet traffic and Fibre Channel traffic.

FCoE uplink ports connect to upstream Ethernet switches using the FCoE protocol for Fibre Channel traffic. This allows both the Fibre Channel traffic and Ethernet traffic to flow on the same physical Ethernet link.

Note

FCoE uplinks and unified uplinks enable the multi-hop FCoE feature, by extending the unified fabric up to the distribution layer switch.

You can configure the same Ethernet port as any of the following:

FCoE uplink port—As an FCoE uplink port for only Fibre Channel traffic.
Uplink port—As an Ethernet port for only Ethernet traffic.
Unified uplink port—As a unified uplink port to carry both Ethernet and Fibre Channel traffic.

Configuring a FCoE Uplink Port

All of the port types listed are configurable on both the fixed and expansion module including server ports.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters FC Uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric{a \| b}	Enters FC - Uplink mode for the specific fabric.
Step 3	UCS-A /fc-uplink/fabric # create fcoeinterface `slot-numberport-number`	Creates interface for the specified FCoE uplink port.
Step 4	UCS-A /fc-uplink/fabric/fabricinterface # commit-buffer	Commits the transaction to the system configuration.

Example

The following example creates an interface for FCoE uplink port 8 on slot 1 of fabric A and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # create fcoeinterface 1 8 
UCS-A /fc-uplink/fabric/fcoeinterface* # commit-buffer
UCS-A /fc-uplink/fabric/fcoeinterface #

Unconfiguring a FCoE Uplink Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters FC Uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric{a \| b}	Enters FC - Uplink mode for the specific fabric.
Step 3	UCS-A /fc-uplink/fabric # delete fcoeinterface `slot-numberport-number`	Deletes the specified interface.
Step 4	UCS-A /fc-uplink/fabric/fabricinterface # commit-buffer	Commits the transaction to the system configuration.

Example

The following example deletes the FCoE uplink interface on port 8 on slot 1 of fabric A and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # delete fcoeinterface 1 8 
UCS-A /fc-uplink/fabric/fcoeinterface* # commit-buffer
UCS-A /fc-uplink/fabric/fcoeinterface #

Viewing FCoE Uplink Ports

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters FC Uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric{a \| b}	Enters FC - Uplink mode for the specific fabric.
Step 3	UCS-A /fc-uplink/fabric # show fcoeinterface	Lists the available interfaces.

Example

The following example displays the available FCoE uplink interfaces on fabric A:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # show fcoeinterface 
FCoE Interface:

Slot Id    Port Id    Admin State Operational State Operational State Reason  Li
c State            Grace Prd
---------- ---------- ----------- ----------------- ------------------------- --
------------------ ---------
         1         26 Enabled     Indeterminate                               Li
cense Ok                    0

Fcoe Member Port:

Port-channel Slot  Port  Oper State      State Reason
------------ ----- ----- --------------- ------------
1                1    10 Sfp Not Present Unknown
1                1     3 Sfp Not Present Unknown
1                1     4 Sfp Not Present Unknown
1                1     6 Sfp Not Present Unknown
1                1     8 Sfp Not Present Unknown
2                1     7 Sfp Not Present Unknown
UCS-A /fc-uplink/fabric #

Configuring FCoE Uplink for Forward Error Correction

Cisco UCS Manager Release 4.3(4b) introduces support for FCoE uplink ports in Fibre Channel switch mode on the Cisco UCS Fabric Interconnects 9108 100G.

Cisco UCS Manager Release 4.2(3b) introduces support for FCoE uplink ports in Fibre Channel switch mode on the Cisco UCS 6536 Fabric Interconnect.

You can configure forward error correction (FEC) for FCoE uplinks that operate at 25 Gbps and 100 Gpbs speeds that support this feature.

Table 4. FEC CL-74 and FEC CL-91 Support Matrix
Port Speed	FEC CL-74	FEC CL-91
1 Gbps	Not supported	Not supported
10 Gbps	Not supported	Not supported
25 Gbps	Supported	Supported
40 Gbps	Not supported	Not supported
100 Gbps	Not supported	Supported
Auto	Based on inserted tranceiver's maximum supported speed	Based on inserted tranceiver's maximum supported speed

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters FCoE uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric a \| b}	Enters fabric mode for the specified fabric.
Step 3	UCS-A /fc-uplink/fabric # scope fcoeinterface `slot-id` `port-id`	Enters FCoE interface mode for the specified interface.
Step 4	UCS-A /fc-uplink/fabric/fcoeinterface # set fec {auto \|cl74 \| cl91}	Sets the forward error correction setting as auto, cl74, or cl91 for the FCoE uplink. For the UCS 6400 Series Fabric Interconnect, Cisco UCS 6536 Fabric Interconnect, and Cisco UCS Fabric Interconnects 9108 100G fabric interconnects, the forward error correction is only configurable for 25 Gbps or 100 Gbps port speeds.
Step 5	UCS-A /fc-uplink/fabric/fcoeinterface # commit-buffer	Commits the transaction to the system configuration.

Example

The following example shows how to enable forward error correction cl74 on an interface for FCoE uplink 35 on slot 1 of fabric A, and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a 
UCS-A /fc-uplink/fabric # scope fcoeinterface 1 35
UCS-A /fc-uplink/fabric/fcoeinterface # set fec cl74
UCS-A /fc-uplink/fabric/fcoeinterface # commit-buffer

Unified Storage Ports

Unified storage involves configuring the same physical port as both an Ethernet storage interface and an FCoE storage interface. You can configure any appliance port or FCoE storage port as a unified storage port. To configure a unified storage port, you must have the fabric interconnect in Fibre Channel switching mode.

In a unified storage port, you can enable or disable individual FCoE storage or appliance interfaces.

In an unified storage port, if you do not specify a non-default VLAN for the appliance port, the FCoE-storage-native-vlan will be assigned as the native VLAN on the unified storage port. If the appliance port has a non-default native VLAN specified as native VLAN, this will be assigned as the native VLAN for the unified storage port.
When you enable or disable the appliance interface, the corresponding physical port is enabled or disabled. So when you disable the appliance interface in unified storage, even if the FCoE storage is enabled, it goes down with the physical port.
When you enable or disable the FCoE storage interface, the corresponding VFC is enabled or disabled. So when the FCoE storage interface is disabled in a unified storage port, the appliance interface will continue to function normally.

Configuring a Unified Storage Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-storage	Enters Ethernet storage mode.
Step 2	UCS-A /eth-storage # scope fabric{a \| b}	Enters Ethernet storage mode for the specified fabric.
Step 3	UCS-A /eth-storage/fabric # create interface `slot-num` `port-num`	Creates an interface for the specified appliance port.
Step 4	UCS-A /eth-storage/fabric/interface* # commit buffer	Commits the transaction to the system configuration.
Step 5	UCS-A /eth-storage/fabric/interface* # scope fc-storage	Enters FC storage mode.
Step 6	UCS-A /fc-storage* # scope fabric{a \| b}	Enters Ethernet storage mode for the specific appliance port.
Step 7	UCS-A /fc-storage/fabric # create interface fcoe `slot-num` `port-num`	Adds FCoE storage port mode on the appliance port mode and creates a unified storage port.

Example

The following example creates an interface for an appliance port 2 on slot 3 of fabric A, adds fc storage to the same port to convert it as an unified port , and commits the transaction:

UCS-A# scope eth-storage
UCS-A /eth-storage # scope fabric a
UCS-A /eth-storage/fabric # create interface 3 2
UCS-A /eth-storage/fabric* # commit-buffer
UCS-A /eth-storage/fabric* # scope fc-storage
UCS-A /fc-storage*# scope fabric a
UCS-A /fc-storage/fabric* # create interface fcoe 3 2
UCS-A /fc-storage/fabric* # commit-buffer
UCS-A /fc-storage/fabric*

Unified Uplink Ports

When you configure an Ethernet uplink and an FCoE uplink on the same physical Ethernet port, it is called a unified uplink port. You can individually enable or disable either the FCoE or Ethernet interfaces independently.

Enabling or disabling the FCoE uplink results in the corresponding VFC being enabled or disabled.
Enabling or disabling an Ethernet uplink results in the corresponding physical port being enabled or disabled.

If you disable an Ethernet uplink, it disables the underlying physical port in a unified uplink. Therefore, even when the FCoE uplink is enabled, the FCoE uplink also goes down. But if you disable an FCoE uplink, only the VFC goes down. If the Ethernet uplink is enabled, it can still function properly in the unified uplink port.

Configuring a Unified Uplink Port

To configure a unified uplink port, you will convert an existing FCoE uplink port as a unified port.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # scope fabric {a \| b}	Enters Ethernet uplink fabric mode for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # create interface `1` `5`	Converts the FCoE uplink port as a unified port.
Step 4	UCS-A /eth-uplink/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example creates a unified uplink port on an existing FCoE port:

UCS-A# scope eth-uplink
UCS-A /eth-uplink # scope fabric b 
UCS-A /eth-uplink/fabric # create interface 1 5
UCS-A /eth-uplink/fabric/interface* # commit-buffer
UCS-A /eth-uplink/interface #

Configuring a Fibre Channel Storage or FCoE Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-storage	Enters Fibre Channel storage mode.
Step 2	UCS-A /fc-storage # scope fabric {a \| b}	Enters Fibre Channel storage mode for the specified fabric.
Step 3	UCS-A /fc-storage/fabric # create interface {fc \| fcoe} `slot-num` `port-num`	Creates an interface for the specified Fibre Channel storage port.
Step 4	UCS-A /fc-storage/fabric # commit-buffer	Commits the transaction.

Example

The following example creates an interface for Fibre Channel storage port 10 on slot 2 of fabric A and commits the transaction:

UCS-A# scope fc-storage
UCS-A /fc-storage # scope fabric a
UCS-A /fc-storage/fabric* # create interface fc 2 10
UCS-A /fc-storage/fabric # commit-buffer

What to do next

Assign a VSAN.

Unconfiguring a Fibre Channel Storage or FCoE Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-storage	Enters Fibre Channel storage mode.
Step 2	UCS-A /fc-storage # scope fabric {a \| b}	Enters Fibre Channel storage mode for the specified fabric.
Step 3	UCS-A /fc-storage/fabric # delete interface {fc \| fcoe} `slot-num` `port-num`	Deletes the interface for the specified Fibre Channel or FCoE storage port.
Step 4	UCS-A /fc-storage/fabric # commit-buffer	Commits the transaction.

Example

The following example unconfigures Fibre Channel storage port 10 on slot 2 of fabric A and commits the transaction:

UCS-A# scope fc-storage
UCS-A /fc-storage # scope fabric a
UCS-A /fc-storage/fabric* # delete interface fc 2 10
UCS-A /fc-storage/fabric # commit-buffer

Restoring a Fibre Channel Storage Port Back to an Uplink Fibre Channel Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters Fibre Channel uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric {a \| b}	Enters Fibre Channel uplink mode for the specified fabric.
Step 3	UCS-A /fc-uplink/fabric # create interface `slot-num` `port-num`	Creates an interface for the specified Fibre Channel uplink port.
Step 4	UCS-A /fc-uplink/fabric # commit-buffer	Commits the transaction.

Example

The following example creates an interface for Fibre Channel uplink port 10 on slot 2 of fabric A and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric* # create interface 2 10
UCS-A /fc-uplink/fabric # commit-buffer

Uplink Ethernet Port Channels

An uplink Ethernet port channel allows you to group several physical uplink Ethernet ports (link aggregation) to create one logical Ethernet link to provide fault-tolerance and high-speed connectivity. In Cisco UCS Manager, you create a port channel first and then add uplink Ethernet ports to the port channel. You can add up to 16 uplink Ethernet ports to a port channel.

Important

The state of a configured port changes to unconfigured in the following scenarios:

The port is deleted or removed from a port channel. The port channel can be of any type, such as, uplink or storage.
A port channel is deleted.

Note

Cisco UCS uses Link Aggregation Control Protocol (LACP), not Port Aggregation Protocol (PAgP), to group the uplink Ethernet ports into a port channel. If the ports on the upstream switch are not configured for LACP, the fabric interconnects treat all ports in an uplink Ethernet port channel as individual ports, and therefore forward packets.

Configuring an Uplink Ethernet Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # scope fabric {a \| b }	Enters Ethernet uplink fabric mode for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # create port-channel `port-num`	Creates a port channel on the specified Ethernet uplink port, and enters Ethernet uplink fabric port channel mode.
Step 4	(Optional) UCS-A /eth-uplink/fabric/port-channel # {enable \| disable}	(Optional) Enables or disables the administrative state of the port channel. The port channel is disabled by default.
Step 5	(Optional) UCS-A /eth-uplink/fabric/port-channel # set name `port-chan-name`	(Optional) Specifies the name for the port channel.
Step 6	(Optional) UCS-A /eth-uplink/fabric/port-channel # set flow-control-policy `policy-name`	(Optional) Assigns the specified flow control policy to the port channel.
Step 7	UCS-A /eth-uplink/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example creates a port channel on port 13 of fabric A, sets the name to portchan13a, enables the administrative state, assigns the flow control policy named flow-con-pol432 to the port channel, and commits the transaction:

UCS-A# scope eth-uplink
UCS-A /eth-uplink # scope fabric a
UCS-A /eth-uplink/fabric # create port-channel 13
UCS-A /eth-uplink/fabric/port-channel* # enable
UCS-A /eth-uplink/fabric/port-channel* # set name portchan13a
UCS-A /eth-uplink/fabric/port-channel* # set flow-control-policy flow-con-pol432
UCS-A /eth-uplink/fabric/port-channel* # commit-buffer
UCS-A /eth-uplink/fabric/port-channel #

Unconfiguring an Uplink Ethernet Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # scope fabric {a \| b }	Enters Ethernet uplink fabric mode for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # delete port-channel `port-num`	Deletes the port channel on the specified Ethernet uplink port.
Step 4	UCS-A /eth-uplink/fabric # commit-buffer	Commits the transaction to the system configuration.

Example

The following example unconfigures the port channel on port 13 of fabric A and commits the transaction:

UCS-A# scope eth-uplink
UCS-A /eth-uplink # scope fabric a
UCS-A /eth-uplink/fabric # delete port-channel 13
UCS-A /eth-uplink/fabric* # commit-buffer
UCS-A /eth-uplink/fabric #

Adding a Member Port to an Uplink Ethernet Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # scope fabric {a \| b }	Enters Ethernet uplink fabric mode for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # scope port-channel `port-num`	Enters Ethernet uplink fabric port channel mode for the specified port channel.
Step 4	UCS-A /eth-uplink/fabric/port-channel # create member-port `slot-num` `port-num`	Creates the specified member port from the port channel and enters Ethernet uplink fabric port channel member port mode.
Step 5	UCS-A /eth-uplink/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example adds the member port on slot 1, port 7 to the port channel on port 13 of fabric A and commits the transaction.

UCS-A# scope eth-uplink
UCS-A /eth-uplink # scope fabric a
UCS-A /eth-uplink/fabric # scope port-channel 13
UCS-A /eth-uplink/fabric/port-channel # create member-port 1 7
UCS-A /eth-uplink/fabric/port-channel* # commit-buffer
UCS-A /eth-uplink/fabric/port-channel #

Deleting a Member Port from an Uplink Ethernet Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # scope fabric {a \| b }	Enters Ethernet uplink fabric mode for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # scope port-channel `port-num`	Enters Ethernet uplink fabric port channel mode for the specified port channel.
Step 4	UCS-A /eth-uplink/fabric/port-channel # delete member-port `slot-num` `port-num`	Deletes the specified member port from the port channel.
Step 5	UCS-A /eth-uplink/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example deletes a member port from the port channel on port 13 of fabric A and commits the transaction:

UCS-A# scope eth-uplink
UCS-A /eth-uplink # scope fabric a
UCS-A /eth-uplink/fabric # scope port-channel 13
UCS-A /eth-uplink/fabric/port-channel # delete member-port 1 7
UCS-A /eth-uplink/fabric/port-channel* # commit-buffer
UCS-A /eth-uplink/fabric/port-channel #

Appliance Port Channels

An appliance port channel allows you to group several physical appliance ports to create one logical Ethernet storage link for the purpose of providing fault-tolerance and high-speed connectivity. In Cisco UCS Manager, you create a port channel first and then add appliance ports to the port channel. You can add up to eight appliance ports to a port channel.

Configuring an Appliance Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-storage	Enters Ethernet storage mode.
Step 2	UCS-A /eth-storage # scope fabric {a \| b }	Enters Ethernet storage fabric mode for the specified fabric.
Step 3	UCS-A /eth-storage/fabric # create port-channel `port-num`	Creates a port channel on the specified Ethernet storage port, and enters Ethernet storage fabric port channel mode.
Step 4	(Optional) UCS-A /eth-storage/fabric/port-channel # {enable \| disable}	(Optional) Enables or disables the administrative state of the port channel. The port channel is disabled by default.
Step 5	(Optional) UCS-A /eth-storage/fabric/port-channel # set name `port-chan-name`	(Optional) Specifies the name for the port channel.
Step 6	(Optional) UCS-A /eth-storage/fabric/port-channel # set pingroupname `pin-group name`	(Optional) Specifies the appliance pin target to the specified fabric and port, or fabric and port channel.
Step 7	(Optional) UCS-A /eth-storage/fabric/port-channel # set portmode {access \| trunk}	(Optional) Specifies whether the port mode is access or trunk. By default, the mode is set to trunk.
Step 8	(Optional) UCS-A /eth-storage/fabric/port-channel # set prio `sys-class-name`	(Optional) Specifies the QoS class for the appliance port. By default, the priority is set to best-effort. The sys-class-name argument can be one of the following class keywords: FC—Use this priority for QoS policies that control vHBA traffic only. Platinum—Use this priority for QoS policies that control vNIC traffic only. Gold—Use this priority for QoS policies that control vNIC traffic only. Silver—Use this priority for QoS policies that control vNIC traffic only. Bronze—Use this priority for QoS policies that control vNIC traffic only. Best Effort—Do not use this priority. It is reserved for the Basic Ethernet traffic lane. If you assign this priority to a QoS policy and configure another system class as CoS 0, Cisco UCS Manager does not default to this system class. It defaults to the priority with CoS 0 for that traffic.
Step 9	(Optional) UCS-A /eth-storage/fabric/port-channel # set speed {1gbps \| 2gbps \| 4gbps \| 8gbps \| auto}	(Optional) Specifies the speed for the port channel.
Step 10	UCS-A /eth-storage/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example creates a port channel on port 13 of fabric A and commits the transaction:

UCS-A# scope eth-storage
UCS-A /eth-storage # scope fabric a
UCS-A /eth-storage/fabric # create port-channel 13
UCS-A /eth-storage/fabric/port-channel* # enable
UCS-A /eth-storage/fabric/port-channel* # set name portchan13a
UCS-A /eth-storage/fabric/port-channel* # set pingroupname pingroup1
UCS-A /eth-storage/fabric/port-channel* # set portmode access
UCS-A /eth-storage/fabric/port-channel* # set prio fc
UCS-A /eth-storage/fabric/port-channel* # set speed 2gbps
UCS-A /eth-storage/fabric/port-channel* # commit-buffer
UCS-A /eth-storage/fabric/port-channel #

Unconfiguring an Appliance Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-storage	Enters Ethernet storage mode.
Step 2	UCS-A /eth-storage # scope fabric {a \| b }	Enters Ethernet storage fabric mode for the specified fabric.
Step 3	UCS-A /eth-storage/fabric # delete port-channel `port-num`	Deletes the port channel from the specified Ethernet storage port.
Step 4	UCS-A /eth-storage/fabric # commit-buffer	Commits the transaction to the system configuration.

Example

The following example unconfigures the port channel on port 13 of fabric A and commits the transaction:

UCS-A# scope eth-storage
UCS-A /eth-storage # scope fabric a
UCS-A /eth-storage/fabric # delete port-channel 13
UCS-A /eth-storage/fabric* # commit-buffer
UCS-A /eth-storage/fabric #

Enabling or Disabling an Appliance Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-storage	Enters Ethernet storage mode.
Step 2	UCS-A /eth-storage # scope fabric {a \| b }	Enters Ethernet storage mode for the specified fabric.
Step 3	UCS-A /eth-storage/fabric # scope port-channel `port-chan-name`	Enters Ethernet storage port channel mode.
Step 4	UCS-A /eth-storage/fabric/port-channel # {enable \| disable }	Enables or disables the administrative state of the port channel. The port channel is disabled by default.
Step 5	UCS-A /eth-storage/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example enables port channel 13 on fabric A and commits the transaction:

UCS-A# scope eth-storage
UCS-A /eth-storage # scope fabric a
UCS-A /eth-storage/fabric # scope port-channel 13
UCS-A /eth-storage/fabric/port-channel* # enable
UCS-A /eth-storage/fabric/port-channel* # commit-buffer
UCS-A /eth-storage/fabric/port-channel #

Adding a Member Port to an Appliance Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-storage	Enters Ethernet storage mode.
Step 2	UCS-A /eth-storage # scope fabric {a \| b }	Enters Ethernet storage fabric mode for the specified fabric.
Step 3	UCS-A /eth-storage/fabric # scope port-channel `port-num`	Enters Ethernet storage fabric port channel mode for the specified port channel.
Step 4	UCS-A /eth-storage/fabric/port-channel # create member-port `slot-num` `port-num`	Creates the specified member port from the port channel and enters Ethernet storage fabric port channel member port mode.
Step 5	UCS-A /eth-storage/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example adds the member port on slot 1, port 7 to the port channel on port 13 of fabric A and commits the transaction.

UCS-A# scope eth-storage
UCS-A /eth-storage # scope fabric a
UCS-A /eth-storage/fabric # scope port-channel 13
UCS-A /eth-storage/fabric/port-channel # create member-port 1 7
UCS-A /eth-storage/fabric/port-channel* # commit-buffer
UCS-A /eth-storage/fabric/port-channel #

Deleting a Member Port from an Appliance Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-storage	Enters Ethernet storage mode.
Step 2	UCS-A /eth-storage # scope fabric {a \| b }	Enters Ethernet storage fabric mode for the specified fabric.
Step 3	UCS-A /eth-storage/fabric # scope port-channel `port-num`	Enters Ethernet storage fabric port channel mode for the specified port channel.
Step 4	UCS-A /eth-storage/fabric/port-channel # delete member-port `slot-num` `port-num`	Deletes the specified member port from the port channel.
Step 5	UCS-A /eth-storage/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example deletes a member port from the port channel on port 13 of fabric A and commits the transaction:

UCS-A# scope eth-storage
UCS-A /eth-storage # scope fabric a
UCS-A /eth-storage/fabric # scope port-channel 13
UCS-A /eth-storage/fabric/port-channel # delete member-port 1 7
UCS-A /eth-storage/fabric/port-channel* # commit-buffer
UCS-A /eth-storage/fabric/port-channel #

Fibre Channel Port Channels

A Fibre Channel port channel allows you to group several physical Fibre Channel ports (link aggregation) to create one logical Fibre Channel link to provide fault-tolerance and high-speed connectivity. In Cisco UCS Manager, you create a port channel first and then add Fibre Channel ports to the port channel.

Note

Fibre Channel port channels are not compatible with non-Cisco technology.

You can create up to two Fibre Channel port channels in each Cisco UCS domain with Cisco UCS Fabric Interconnects 9108 100G (Cisco UCS X-Series Direct). Each Fibre Channel port channel can include a maximum of four uplink Fibre Channel ports.

For more information, see Port Breakout Functionality on respective fabric interconnects in Network Management Guide.

Ensure that the Fibre Channel port channel on the upstream NPIV switch is configured with its channel mode as active. If both the member port(s) and peer port(s) do not have the same channel mode configured, the port channel will not come up. When the channel mode is configured as active, the member ports initiate port channel protocol negotiation with the peer port(s) regardless of the channel group mode of the peer port. If the peer port, while configured in a channel group, does not support the port channel protocol, or responds with a nonnegotiable status, it defaults to the On mode behavior. The active port channel mode allows automatic recovery without explicitly enabling and disabling the port channel member ports at either end.

This example shows how to configure channel mode as active:

switch(config)# int po114
switch(config-if)# channel mode active

Configuring a Fibre Channel Port Channel

Note

If you are connecting two Fibre Channel port channels, the admin speed for both port channels must match for the link to operate. If the admin speed for one or both of the Fibre Channel port channels is set to auto, Cisco UCS adjusts the admin speed automatically.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters Fibre Channel uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric {a \| b }	Enters Fibre Channel uplink fabric mode for the specified fabric.
Step 3	UCS-A /fc-uplink/fabric # create port-channel `port-num`	Creates a port channel on the specified Fibre Channel uplink port, and enters Fibre Channel uplink fabric port channel mode.
Step 4	(Optional) UCS-A /fc-uplink/fabric/port-channel # {enable \| disable}	(Optional) Enables or disables the administrative state of the port channel. The port channel is disabled by default.
Step 5	(Optional) UCS-A /fc-uplink/fabric/port-channel # set name `port-chan-name`	(Optional) Specifies the name for the port channel.
Step 6	(Optional) UCS-A /fc-uplink/fabric/port-channel # set speed {1gbps \| 2gbps \| 4gbps \| 8gbps \| auto}	(Optional) Specifies the speed for the port channel.
Step 7	UCS-A /fc-uplink/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example creates port channel 13 on fabric A, sets the name to portchan13a, enables the administrative state, sets the speed to 2 Gbps, and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # create port-channel 13
UCS-A /fc-uplink/fabric/port-channel* # enable
UCS-A /fc-uplink/fabric/port-channel* # set name portchan13a
UCS-A /fc-uplink/fabric/port-channel* # set speed 2gbps
UCS-A /fc-uplink/fabric/port-channel* # commit-buffer
UCS-A /fc-uplink/fabric/port-channel #

Configuring a FCoE Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters FC Uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric{a \| b}	Enters FC - Uplink mode for the specific fabric.
Step 3	UCS-A /fc-uplink/fabric # create fcoe-port-channel `number`	Creates port channel for the specified FCoE uplink port.
Step 4	UCS-A /fc-uplink/fabric/fabricinterface # commit-buffer	Commits the transaction to the system configuration.

Example

The following example creates an interface for FCoE uplink port 1 on slot 4 of fabric A and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # create fcoe-port-channel 4 
UCS-A /fc-uplink/fabric/fcoe-port-channel* # commit-buffer
UCS-A /fc-uplink/fabric/fcoe-port-channel #

Adding Channel Mode Active To The Upstream NPIV Fibre Channel Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters Fibre Channel uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric {a \| b }	Enters Fibre Channel uplink fabric mode for the specified fabric.
Step 3	UCS-A /fc-uplink/fabric # create port-channel `port-num`	Creates a port channel on the specified Fibre Channel uplink port, and enters Fibre Channel uplink fabric port channel mode.
Step 4	(Optional) UCS-A /fc-uplink/fabric/port-channel # {enable \| disable}	(Optional) Enables or disables the administrative state of the port channel. The port channel is disabled by default.
Step 5	(Optional) UCS-A /fc-uplink/fabric/port-channel # set name `port-chan-name`	(Optional) Specifies the name for the port channel.
Step 6	(Optional) UCS-A /fc-uplink/fabric/port-channel # scope `port-chan-name`	(Optional) Specifies the name for the port channel.
Step 7	(Optional) UCS-A /fc-uplink/fabric/port-channel # channel mode {active}	(Optional) Configures the channel-mode active on the upstream NPIV switch.
Step 8	UCS-A /fc-uplink/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example enables channel mode to active:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # create port-channel 13
UCS-A /fc-uplink/fabric/port-channel* # enable
UCS-A /fc-uplink/fabric/port-channel* # set name portchan13a
UCS-A /fc-uplink/fabric/port-channel* # channel mode active
UCS-A /fc-uplink/fabric/port-channel* # commit-buffer
UCS-A /fc-uplink/fabric/port-channel # exit
UCS-A /fc-uplink/fabric/ # show port-channel database

portchan13a
    Administrative channel mode is active
    Operational channel mode is active

UCS-A /fc-uplink/fabric/ #

Enabling or Disabling a Fibre Channel Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters Fibre Channel uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric {a \| b }	Enters Fibre Channel uplink mode for the specified fabric.
Step 3	UCS-A /fc-uplink/fabric # scope port-channel `port-chan-name`	Enters Fibre Channel uplink port channel mode.
Step 4	UCS-A /fc-uplink/fabric/port-channel # {enable \| disable }	Enables or disables the administrative state of the port channel. The port channel is disabled by default.

Example

The following example enables port channel 13 on fabric A and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # scope port-channel 13
UCS-A /fc-uplink/fabric/port-channel* # enable
UCS-A /fc-uplink/fabric/port-channel* # commit-buffer
UCS-A /fc-uplink/fabric/port-channel #

Adding a Member Port to a Fibre Channel Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters Fibre Channel uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric {a \| b }	Enters Fibre Channel uplink fabric mode for the specified fabric.
Step 3	UCS-A /fc-uplink/fabric # scope port-channel `port-num`	Enters Fibre Channel uplink fabric port channel mode for the specified port channel.
Step 4	UCS-A /fc-uplink/fabric/port-channel # create member-port `slot-num` `port-num`	Creates the specified member port from the port channel and enters Fibre Channel uplink fabric port channel member port mode.
Step 5	UCS-A /fc-uplink/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example adds the member port on slot 1, port 7 to port channel 13 on fabric A and commits the transaction.

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # scope port-channel 13
UCS-A /fc-uplink/fabric # create member-port 1 7
UCS-A /fc-uplink/fabric/port-channel* # commit-buffer
UCS-A /fc-uplink/fabric/port-channel #

Deleting a Member Port from a Fibre Channel Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters Fibre Channel uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric {a \| b}	Enters Fibre Channel uplink fabric mode for the specified fabric.
Step 3	UCS-A /fc-uplink/fabric # scope port-channel `port-num`	Enters Fibre Channel uplink fabric port channel mode for the specified port channel.
Step 4	UCS-A /fc-uplink/fabric/port-channel # delete member-port `slot-num` `port-num`	Deletes the specified member port from the port channel.
Step 5	UCS-A /fc-uplink/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example deletes a member port from port channel 13 on fabric A and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # scope port-channel 13
UCS-A /fc-uplink/fabric # delete member-port 1 7
UCS-A /fc-uplink/fabric/port-channel* # commit-buffer
UCS-A /fc-uplink/fabric/port-channel #

FCoE Port Channels

An FCoE port channel allows you to group several physical FCoE ports to create one logical FCoE port channel. At a physical level, the FCoE port channel carries FCoE traffic over an Ethernet port channel. So an FCoE port channel with a set of members is essentially an Ethernet port channel with the same members. This Ethernet port channel is used as a physical transport for FCoE traffic.

For each FCoE port channel, Cisco UCS Manager creates a VFC internally and binds it to an Ethernet port channel. FCoE traffic received from the hosts is sent over the VFC the same way as the FCoE traffic is sent over Fibre Channel uplinks.

Configuring a FCoE Port Channel

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope fc-uplink	Enters FC Uplink mode.
Step 2	UCS-A /fc-uplink # scope fabric{a \| b}	Enters FC - Uplink mode for the specific fabric.
Step 3	UCS-A /fc-uplink/fabric # create fcoe-port-channel `number`	Creates port channel for the specified FCoE uplink port.
Step 4	UCS-A /fc-uplink/fabric/fabricinterface # commit-buffer	Commits the transaction to the system configuration.

Example

The following example creates an interface for FCoE uplink port 1 on slot 4 of fabric A and commits the transaction:

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # create fcoe-port-channel 4 
UCS-A /fc-uplink/fabric/fcoe-port-channel* # commit-buffer
UCS-A /fc-uplink/fabric/fcoe-port-channel #

Adding a Member Port to a FCoE Uplink Port Channel

Procedure

Command or Action

Purpose

Step 1

UCS-A# scope fc-uplink

Enters Fibre Channel uplink mode.

Step 2

UCS-A /fc-uplink # scope fabric {a | b }

Enters Fibre Channel uplink fabric mode for the specified fabric.

Step 3

UCS-A /fc-uplink/fabric # scope fcoe-port-channel ID

Enters FCoE uplink port channel mode for the specified port channel.

Step 4

UCS-A /fc-uplink/fabric/fcoe-port-channel # create member-port slot-num port-num

Creates the specified member port from the port channel and enters FCoE uplink fabric port channel member port mode.

Note

If the FCoE uplink port channel is a unified uplink port channel, you will get the following message:

Warning: if this is a unified port channel then member will be added to the ethernet port channel of the same id as well.

Step 5

UCS-A /fc-uplink/fabric/fcoe-port-channel # commit-buffer

Commits the transaction to the system configuration.

Example

The following example adds the member port on slot 1, port 7 to FCoE port channel 13 on fabric A and commits the transaction.

UCS-A# scope fc-uplink
UCS-A /fc-uplink # scope fabric a
UCS-A /fc-uplink/fabric # scope fcoe-port-channel 13
UCS-A /fc-uplink/fabric # create member-port 1 7
UCS-A /fc-uplink/fabric/fcoe-port-channel* # commit-buffer
UCS-A /fc-uplink/fabric/fcoe-port-channel #

Unified Uplink Port Channel

When you create an Ethernet port channel and an FCoE port channel with the same ID, it is called a unified uplink port channel. When the unified port channel is created, a physical Ethernet port channel and a VFC are created on the fabric interconnect with the specified members. The physical Ethernet port channel is used to carry both Ethernet and FCoE traffic. The VFC binds FCoE traffic to the Ethernet port channel.

The following rules will apply to the member port sets of the unified uplink port channel:

The Ethernet port channel and FCoE port channel on the same ID, must have the same set of member ports.
When you add a member port channel to the Ethernet port channel, Cisco UCS Manager adds the same port channel to FCoE port channel as well. Similarly, adding a member to the FCoE port channel adds the member port to the Ethernet port channel.
When you delete a member port from one of the port channels, Cisco UCS Manager automatically deletes the member port from the other port channel.

If you disable an Ethernet uplink port channel, it disables the underlying physical port channel in a unified uplink port channel. Therefore, even when the FCoE uplink is enabled, the FCoE uplink port channel also goes down. If you disable an FCoE uplink port channel, only the VFC goes down. If the Ethernet uplink port channel is enabled, it can still function properly in the unified uplink port channel.

Configuring a Unified Uplink Port Channel

To configure a unified uplink port channel, you will convert an existing FCoE uplink port channel as a unified port channel.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-uplink	Enters Ethernet uplink mode.
Step 2	UCS-A /eth-uplink # scope fabric {a \| b}	Enters Ethernet uplink fabric mode for the specified fabric.
Step 3	UCS-A /eth-uplink/fabric # create port-channel `ID`	Creates a port channel for the specified Ethernet uplink port.
Step 4	UCS-A /eth-uplink/fabric/port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example creates a unified uplink port channel on an existing FCoE port channel:

UCS-A# scope eth-uplink
UCS-A /eth-uplink # scope fabric b 
UCS-A /eth-uplink/fabric # create port-channel 2
UCS-A /eth-uplink/fabric/port-channel* # commit-buffer
UCS-A /eth-uplink/fabric #

Event Detection and Action

Cisco UCS Manager uses the statistics collection policy to monitor and trigger an alarm when there are faults in the network interface ports connected from the I/O Module (IOM) to the fabric interconnect.

The error statistics for the network interface ports is called NiErrStats and consists of the following errors:


NiErrStats	Description
frameTx	Collects the TX_FRM_ERROR counter values.
tooLong	Collects the RX_TOOLONG counter values.
tooShort	Collects the sum of RX_UNDERSIZE and RX_FRAGMENT counter values.
Crc	Collects the sum of RX_CRERR_NOT_STOMPED and RX_CRCERR_STOMPED counter values.
InRange	Collects the RX_INRANGEERR counter values.

Note

Only active ports collect the network interface port statistics and send the information to Cisco UCS Manager.

Policy-Based Port Error Handling

If Cisco UCS Manager detects any errors on active NI ports, and if the error-disable feature is enabled, Cisco UCS Manager automatically disables the respective FI port that is connected to the NI port that had errors. When a FI port is error disabled, it is effectively shut down and no traffic is sent or received on that port.

The error-disable function serves two purposes:

It lets you know which FI port is error-disabled and that the connected NI Port has errors.
It eliminates the possibility that this port can cause other ports, which are connected to the same Chassis/FEX, to fail. Such a failure can occur when the NI port has errors, which can ultimately cause serious network issues. The error-disable function helps prevent these situations.

Creating Threshold Definition

Procedure

	Command or Action	Purpose
Step 1	UCS-A # scope eth-server	Enters Ethernet storage mode.
Step 2	UCS-A/eth-server # scope stats-threshold-policy default	Enters statistics threshold policy mode.
Step 3	UCSA/eth-server/stats-threshold-policy # create class `class-name`	Creates the specified statistics threshold policy class and enters the organization statistics threshold policy class mode. To see a list of the available class name keywords, enter the create class ? command in organization threshold policy mode.
Step 4	UCS-A/eth-server/stats-threshold-policy/class # create property `property-name`	Creates the specified statistics threshold policy class property and enters the organization statistics threshold policy class property mode. To see a list of the available property name keywords, enter the create property ? command in organization threshold policy class mode.
Step 5	UCS-A/eth-server/stats-threshold-policy/class/property # set normal-value `value`	Specifies the normal value for the class property. The `value` format can vary depending on the class property being configured. To see the required format, enter the set normal-value ? command in organization statistics threshold policy class property mode.
Step 6	UCS-A/eth-server/stats-threshold-policy/class/property # create threshold-value {`above-normal` \| `below-normal`} {`cleared` \| `condition` \| `critical` \| `info` \| `major` \| `minor` \| `warning`}	Creates the specified threshold value for the class property and enters the organization statistics threshold policy class property threshold value mode.
Step 7	UCS-A/eth-server/stats-threshold-policy/class/property/threshold-value # set {deescalating \| escalating} `value`	Specifies the deescalating and escalating class property threshold value. The `value` format can vary depending on the class property threshold value being configured. To see the required format, enter the set deescalating ? or set escalating ? command in the organization statistics threshold policy class property threshold value mode.
Step 8	UCS-A/eth-server/stats-threshold-policy/class/property/threshold-value # commit-buffer	Commits the transaction to the system configuration.

Example

The following example shows how to create a threshold definition:

 
UCS-A # scope eth-server
UCS-A /eth-server # scope stats-threshold-policy default
UCS-A /eth-server/stats-threshold-policy # create class ni-ether-error-stats
UCS-A /eth-server/stats-threshold-policy/class* # create property crc-delta
UCS-A /eth-server/stats-threshold-policy/class/property* # set normal-value 0
UCS-A /eth-server/stats-threshold-policy/class/property* # create threshold-value above-normal major
UCS-A /eth-server/stats-threshold-policy/class/property/threshold-value* # set escalating 5
UCS-A /eth-server/stats-threshold-policy/class/property/threshold-value* # set deescalating 3
UCS-A /eth-server/stats-threshold-policy/class/property/threshold-value* # commit-buffer

Configuring Error Disable on a Fabric Interconnect Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A # scope eth-server	Enters Ethernet storage mode.
Step 2	UCS-A/eth-server # scope stats-threshold-policy default	Enters statistics threshold policy mode.
Step 3	UCSA/eth-server/stats-threshold-policy # scope class `class-name`	Enters the organization statistics threshold policy class mode for the specified statistics threshold policy class.
Step 4	UCS-A/eth-server/stats-threshold-policy/class # scope property `property-name`	Enters the organization statistics threshold policy class property mode for the specified statistics threshold policy class property.
Step 5	UCS-A/eth-server/stats-threshold-policy/class/property # set error-disable-fi-port {yes \| no}	Specifies the error disable state for the class property. Use the no option to disable error disable for the class property.
Step 6	UCS-A/eth-server/stats-threshold-policy/class/property* # commit-buffer	Commits the transaction to the system configuration.

Example

The following example shows how to enable error disable on an FI port:

 
UCS-A # scope eth-server
UCS-A /eth-server # scope stats-threshold-policy default
UCS-A /eth-server/stats-threshold-policy # scope class ni-ether-error-stats
UCS-A /eth-server/stats-threshold-policy/class # scope property crc-delta
UCS-A /eth-server/stats-threshold-policy/class/property # set error-disable-fi-port yes
UCS-A /eth-server/stats-threshold-policy/class/property* # commit-buffer

Configuring Auto Recovery on a Fabric Interconnect Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A # scope eth-server	Enters Ethernet storage mode.
Step 2	UCS-A/eth-server # scope stats-threshold-policy default	Enters statistics threshold policy mode.
Step 3	UCSA/eth-server/stats-threshold-policy # scope class `class-name`	Enters the organization statistics threshold policy class mode for the specified statistics threshold policy class.
Step 4	UCS-A/eth-server/stats-threshold-policy/class # scope property `property-name`	Enters the organization statistics threshold policy class property mode for the specified statistics threshold policy class property.
Step 5	UCS-A/eth-server/stats-threshold-policy/class/property # set auto-recovery {enabled \| disabled}	Specifies the auto recovery state for the class property. Use the disabled option to disable auto recovery for the class property.
Step 6	UCS-A/eth-server/stats-threshold-policy/class/property* # set auto-recovery-time `time`	Specifies the time in minutes after which the port is automatically re-enabled. The auto recovery time can range from 0 minutes to 4294967295 minutes.
Step 7	UCS-A/eth-server/stats-threshold-policy/class/property* # commit-buffer	Commits the transaction to the system configuration.

Example

The following example shows how to configure auto recovery on an FI port:

 
UCS-A # scope eth-server
UCS-A /eth-server # scope stats-threshold-policy default
UCS-A /eth-server/stats-threshold-policy # scope class ni-ether-error-stats
UCS-A /eth-server/stats-threshold-policy/class # scope property crc-delta
UCS-A /eth-server/stats-threshold-policy/class/property # set auto-recovery enabled
UCS-A /eth-server/stats-threshold-policy/class/property* # set auto-recovery-time 5
UCS-A /eth-server/stats-threshold-policy/class/property* # commit-buffer

Viewing the Network Interface Port Error Counters

Procedure

	Command or Action	Purpose
Step 1	UCS-A # scope chassis `chassis-num`	Enters chassis mode for the specified chassis.
Step 2	UCS-A/chassis # scope iom {a \| b}	Enters chassis IOM mode for the specified IOM.
Step 3	UCS-A/chassis/iom # scope port-group fabric	Enters the network interface port.
Step 4	UCS-A/chassis/iom/port-group # scope fabric-if `fabric-if number`	Enters the specified network interface port number.
Step 5	UCS-A/chassis/iom/port-group/fabric-if # show stats	Displays the error counters for the network interface port.

Example

The following example shows how to display the statistics for the network interface ports:

UCS-A # scope chassis 1
UCS-A/chassis # scope iom a
UCS-A/chassis/iom # scope port-group fabric
UCS-A/chassis/iom/port-group # scope faric-if 1
UCS-A/chassis/iom/port-group/fabric-if # show stats
NI Ether Error Stats:
Time Collected: 2014-08-20T15:37:24:688
Monitored Object: sys/chassis-1/slot-1/fabric/port-1/ni-err-stats
Suspect: Yes
Crc (errors): 5000
Frame Tx (errors): 0
Too Long (errors): 0
Too Short (errors): 0
In Range (errors): 0
Thresholded: 0

Adapter Port Channels

An adapter port channel groups into one logical link all the physical links going from a Cisco UCS Virtual Interface Card (VIC) into an I/O.

Adapter port channels are created and managed internally by Cisco UCS Manager when it detects that the correct hardware is present. Adapter port channels cannot be configured manually. Adapter port channels are viewable using the Cisco UCS Manager GUI or the Cisco UCS Manager CLI.

Viewing Adapter Port Channels

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope chassis `chassis-num`	Enters chassis mode for the specified chassis.
Step 2	UCS-A /chassis # scope iom {a b}	Enters chassis IOM mode for the specified IOM.
Step 3	UCS-A /chassis/iom # scope port group	Enters port group mode for the specified port group.
Step 4	UCS-A /chassis/iom/port group # show host-port-channel [detail \| expand]	Displays the adapter port channels on the specified chassis.

Example

This following example shows how to display information on host port channels within a port group mode:

UCS-A # scope chassis 1
UCS-A /chassis # scope iom a
UCS-A /chassis/iom # scope port group
UCS-A /chassis/iom/port group # show host-port-channel

Host Port channel:

  Port Channel Id Fabric ID Oper State       State Reason
    --------------- --------- ---------------- ------------
               1289 B         Up
               1290 B         Up
               1306 B         Up
               1307 B         Up
               1309 B         Up
               1315 B         Up  

UCS-A /chassis/iom/port group #

Fabric Port Channels

Fabric port channels allow you to group several of the physical links from an IOM and IFM (IOM for Cisco UCS X-Series Servers) to a fabric interconnect into one logical link for redundancy and bandwidth sharing. As long as one link in the fabric port channel remains active, the fabric port channel continues to operate.

If the correct hardware is connected, fabric port channels are created by Cisco UCS Manager in the following ways:

During chassis discovery according to the settings configured in the chassis discovery policy.
After chassis discovery according to the settings configured in the chassis connectivity policy for a specific chassis.

For each IOM and IFM (IOM for Cisco UCS X-Series Servers) there is a single fabric port channel. Each uplink connecting an IOM and IFM (IOM for Cisco UCS X-Series Servers) to a fabric interconnect can be configured as a discrete link or included in the port channel, but an uplink cannot belong to more than one fabric port channel. For example, if a chassis with two IOMs is discovered and the chassis discovery policy is configured to create fabric port channels, Cisco UCS Manager creates two separate fabric port channels: one for the uplinks connecting IOM-1 and another for the uplinks connecting IOM-2. No other chassis can join these fabric port channels. Similarly, uplinks belonging to the fabric port channel for IOM-1 cannot join the fabric port channel for IOM-2.

Load Balancing Over Ports

Load balancing traffic among ports between IOMs and fabric interconnects uses the following criteria for hashing.

For Ethernet traffic:

Layer 2 source and destination address

Layer 3 source and destination address

Layer 4 source and destination ports
For FCoE traffic:

Layer 2 source and destination address

Source and destination IDs (SID and DID) and Originator Exchange ID (OXID)

In this example, a 2200 Series IOM module is verified by connecting iom X (where X is the chassis number).

show platform software fwmctrl nifport
(....)
 Hash Parameters:
   l2_da: 1 l2_sa: 1 l2_vlan: 0
   l3_da: 1 l3_sa: 1
   l4_da: 1 l4_sa: 1
   FCoE l2_da: 1 l2_sa: 1 l2_vlan: 0
   FCoE l3_did: 1 l3_sid: 1 l3_oxid: 1

Cabling Considerations for Fabric Port Channels

When you configure the links between the Cisco UCS 2200 Series FEX and a Cisco UCS 6200 series fabric interconnect in fabric port channel mode, the available virtual interface namespace (VIF) on the adapter varies depending on where the FEX uplinks are connected to the fabric interconnect ports.

Inside the 6248 fabric interconnect there are six sets of eight contiguous ports, with each set of ports managed by a single chip. When all uplinks from an FEX are connected to a set of ports managed by a single chip, Cisco UCS Manager maximizes the number of VIFs used in service profiles deployed on the blades in the chassis. If uplink connections from an IOM are distributed across ports managed by separate chips, the VIF count is decreased.

Figure 1. Port Groups for Fabric Port Channels

Caution

Adding a second link to a fabric-port-channel port group is disruptive and will automatically increase the available amount of VIF namespace from 63 to 118. Adding further links is not disruptive and the VIF namespace stays at 118.

Caution

Linking a chassis to two fabric-port-channel port groups does not affect the VIF namespace unless it is manually acknowledged. The VIF namespace is then automatically set to the smaller size fabric port-channel port group usage (either 63 or 118 VIFs) of the two groups.

For high availability cluster-mode applications, we strongly recommend symmetric cabling configurations. If the cabling is asymmetric, the maximum number of VIFs available is the smaller of the two cabling configurations.

For more information on the maximum number of VIFs for your Cisco UCS environment, see the Configuration Limits document for your hardware and software configuration.

Configuring a Fabric Port Channel

Procedure

Step 1	To include all links from the IOM to the fabric interconnect in a fabric port channel during chassis discovery, set the link grouping preference in the chassis discovery policy to port channel.
Step 2	To include links from individual chassis in a fabric port channel during chassis discovery, set the link grouping preference in the chassis connectivity policy to port channel.
Step 3	After chassis discovery, enable or disable additional fabric port channel member ports.

What to do next

To add or remove chassis links from a fabric port channel after making a change to the chassis discovery policy or the chassis connectivity policy, reacknowledge the chassis. Chassis reacknowledgement is not required to enable or disable chassis member ports from a fabric port channel

Viewing Fabric Port Channels

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-server	Enters Ethernet server mode.
Step 2	UCS-A /eth-server # scope fabric {a \| b}	Enters Ethernet server fabric mode for the specified fabric.
Step 3	UCS-A /eth-server/fabric # show fabric-port-channel [detail \| expand]	Displays fabric port channels on the specified fabric interconnect.

Example

The following example displays information about configured fabric port channels on fabric interconnect A:

UCS-A# scope eth-server
UCS-A /eth-server # scope fabric a
UCS-A /eth-server/fabric # show fabric-port-channel
Fabric Port Channel:
    Port Channel Id Chassis Id Admin State Oper State       State Reason
    --------------- ---------- ----------- ---------------- ------------
               1025 1          Enabled     Failed           No operational members
               1026 2          Enabled     Up

UCS-A /eth-server/fabric #

Enabling or Disabling a Fabric Port Channel Member Port

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope eth-server	Enters Ethernet server mode.
Step 2	UCS-A /eth-server # scope fabric {a \| b}	Enters Ethernet server fabric mode for the specified fabric.
Step 3	UCS-A /eth-server/fabric # scope fabric-port-channel `port-chan-id`	Enters Ethernet server fabric, fabric port channel mode for the specified fabric.
Step 4	UCS-A /eth-server/fabric/fabric-port-channel # scope member-port `slot-id` `port-id`	Enters Ethernet server fabric, fabric port channel mode for the specified member port.
Step 5	UCS-A /eth-server/fabric/fabric-port-channel # {enable \| disable}	Enables or disables the specified member port.
Step 6	UCS-A /eth-server/fabric/fabric-port-channel # commit-buffer	Commits the transaction to the system configuration.

Example

The following example disables fabric channel member port 1 31 on fabric port channel 1025 and commits the transaction:

UCS-A# scope eth-server
UCS-A /eth-server # scope fabric a
UCS-A /eth-server/fabric # scope fabric-port-channel 1025
UCS-A /eth-server/fabric/fabric-port-channel # scope member-port 1 31
UCS-A /eth-server/fabric/fabric-port-channel/member-port # disable
UCS-A /eth-server/fabric/fabric-port-channel/member-port* # commit-buffer
UCS-A /eth-server/fabric/fabric-port-channel/member-port #

Bias-Free Language

Results

Chapter: LAN Ports and Port Channels

LAN Ports and Port Channels

Port Functionality on Cisco UCS 6664 Fabric Interconnect

Front Panel Port Configuration and Types

Unified Ports on the Cisco UCS 6500 Series Fabric Interconnects

Configuring Ethernet Breakout Ports on UCS 6536 Fabric Interconnects

Procedure

Converting Ethernet Ports to Fibre Channel Breakout Port

Procedure

Example

Converting Ethernet Breakout Port to Fibre Channel Breakout Port

Procedure

Example

Converting Ethernet Breakout Port to Fibre Channel Breakout Port Using Fibre Channel Uplink

Procedure

Example

Deleting Fibre Channel Breakout Ports

Procedure

What to do next

Deleting Fibre Channel Breakout Ports Using Fibre Channel Uplink

Procedure

What to do next

Configuring Breakout Appliance Ports

Procedure

Example:

Example:

Modifying Speed for Breakout Port of Type 25x4Gbps

Procedure

Modifying FEC Value for Breakout Port of Type 25 x 4Gbps

Procedure

Converting Fibre Channel Uplink Port to Fibre Channel Storage Port

Procedure

Example

Configuring Fibre Channel Uplink Breakout Port Channel and Member Addition

Procedure

Example

Configuring Ethernet Breakout Ports on Cisco UCS Fabric Interconnects 9108 100G

Procedure

Displaying VIF Port Statistics Obtained From the Adaptor

Procedure

Example

Displaying VIF Port Statistics Obtained From the ASIC

Procedure

Example

Displaying VIF Ports That Correspond to NIV Ports

Procedure

Example

Verifying Status of Backplane Ports

Procedure

Example

Automatic Configuration of Fabric Interconnect Server Ports

Automatically Configuring Server Ports

Procedure

Example

Configuring a Server Port

Procedure

Example

Unconfiguring a Server Port

Procedure

Example

Configuring a Server Port for Forward Error Correction

Procedure

Example

Configuring an Uplink Ethernet Port

Procedure

Example

Unconfiguring an Uplink Ethernet Port

Procedure

Example

Configuring an Uplink Ethernet Port for Forward Error Correction

Procedure

Q-in-Q Forwarding

Configuring Q-in-Q Forwarding

Procedure

Example

Unconfiguring Q-in-Q Forwarding

Procedure