Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide for C22 M3, C24 M3, C220 M3 and C240 M3 Servers, Release 3.0

Overview of the Cisco UCS C-Series Network Adapters

Note

The procedures in this chapter are available only when a Cisco UCS C-Series network adapter is installed in the chassis.

A Cisco UCS C-Series network adapter can be installed to provide options for I/O consolidation and virtualization support. The following adapters are available:

Cisco UCS VIC 1225 Virtual Interface Card
Cisco UCS VIC 1227T Virtual Interface Card
Cisco UCS VIC 1385 Virtual Interface Card
Cisco UCS VIC 1387 Virtual Interface Card

Note

You must have same generation VIC cards on a server. For example, you cannot have a combination of 3rd generation and 4th generation VIC cards on a single server.

The interactive UCS Hardware and Software Interoperability Utility lets you view the supported components and configurations for a selected server model and software release. The utility is available at the following URL: http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

Cisco UCS VIC 1225 Virtual Interface Card

The Cisco UCS VIC 1225 Virtual Interface Card is a high-performance, converged network adapter that provides acceleration for the various new operational modes introduced by server virtualization. It brings superior flexibility, performance, and bandwidth to the new generation of Cisco UCS C-Series Rack-Mount Servers.

The Cisco UCS VIC 1225 implements the Cisco Virtual Machine Fabric Extender (VM-FEX), which unifies virtual and physical networking into a single infrastructure. It provides virtual-machine visibility from the physical network and a consistent network operations model for physical and virtual servers. In virtualized environments, this highly configurable and self-virtualized adapter provides integrated, modular LAN interfaces on Cisco UCS C-Series Rack-Mount Servers. Additional features and capabilities include:

Supports up to 256 PCIe virtual devices, either virtual network interface cards (vNICs) or virtual host bus adapters (vHBAs), with high I/O operations per second (IOPS), support for lossless Ethernet, and 20 Gbps to servers.
PCIe Gen2 x16 helps assure optimal bandwidth to the host for network-intensive applications with a redundant path to the fabric interconnect.
Half-height design reserves full-height slots in servers for Cisco certified third-party adapters.
Centrally managed by Cisco UCS Manager with support for Microsoft Windows, Red Hat Enterprise Linux, SUSE Linux, VMware vSphere, and Citrix XenServer.

Cisco UCS VIC 1385 Virtual Interface Card

The Cisco UCS VIC 1385 Virtual Interface Cardis a dual-port Enhanced Quad Small Form-Factor Pluggable (QSFP) 40 Gigabit Ethernet and Fibre Channel over Ethernet (FCoE)-capable half-height PCI Express (PCIe) card designed exclusively for Cisco UCS C-Series Rack Servers. It incorporates Cisco’s next-generation converged network adapter (CNA) technology, with a comprehensive feature set, providing investment protection for future feature software releases. The card enables a policy-based, stateless, agile server infrastructure that can present over 256 PCIe standards-compliant interfaces to the host that can be dynamically configured as either network interface cards (NICs) or host bus adapters (HBAs). In addition, the Cisco UCS VIC 1385 card supports Cisco Data Center Virtual Machine Fabric Extender (VM-FEX) technology, which extends the Cisco UCS fabric interconnect ports to virtual machines, simplifying server virtualization deployment.

The personality of the card is determined dynamically at boot time using the service profile associated with the server. The number, type (NIC or HBA), identity (MAC address and World Wide Name [WWN]), failover policy, bandwidth, and quality-of-service (QoS) policies of the PCIe interfaces are all determined using the service profile. The capability to define, create, and use interfaces on demand provides a stateless and agile server infrastructure. Additional features and capabilities include:

Each PCIe interface created on the VIC is associated with an interface on the Cisco UCS fabric interconnect, providing complete network separation for each virtual cable between a PCIe device on the VIC and the interface on the fabric interconnect
The Cisco UCS VIC 1385 Virtual Interface Card provides high network performance and low latency for the most demanding applications such as SMB-Direct, VMQ, DPDK, and Cisco NetFlow

Cisco UCS VIC 1227T Virtual Interface Card

The Cisco UCS VIC 1227T Virtual Interface Card is a dual-port 10GBASE-T (RJ-45) 10-Gbps Ethernet and Fibre Channel over Ethernet (FCoE)–capable PCI Express (PCIe) modular LAN-on-motherboard (mLOM) adapter designed exclusively for Cisco UCS C-Series Rack Servers. New to Cisco rack servers, the mLOM slot can be used to install a Cisco VIC without consuming a PCIe slot, which provides greater I/O expandability. It incorporates next-generation converged network adapter (CNA) technology from Cisco, providing Fibre Channel connectivity over low-cost twisted pair cabling with a bit error rate (BER) of 10 to 15 up to 30 meters and investment protection for future feature releases. The mLOM card enables a policy-based, stateless, agile server infrastructure that can present up to 256 PCIe standards-compliant interfaces to the host that can be dynamically configured as either network interface cards (NICs) or host bus adapters (HBAs). In addition, the Cisco UCS VIC 1227T Virtual Interface Card supports Cisco Data Center Virtual Machine Fabric Extender (VM-FEX) technology, which extends the Cisco UCS fabric interconnect ports to virtual machines, simplifying server virtualization deployment. Additional features and capabilities include:

Stateless and agile design - The personality of the card is determined dynamically at boot time using the service profile associated with the server. The number, type (NIC or HBA), identity (MAC address and World Wide Name [WWN]), failover policy, bandwidth, and quality-of-service (QoS) policies of the PCIe interfaces are all determined using the service profile. The capability to define, create, and use interfaces on demand provides a stateless and agile server infrastructure.
Each PCIe interface created on the VIC is associated with an interface on the Cisco UCS fabric interconnect, providing complete network separation for each virtual cable between a PCIe device on the VIC and the interface on the fabric interconnect.
Cisco SingleConnect technology provides an exceptionally easy, intelligent, and efficient way to connect and manage computing in the data center. Cisco SingleConnect technology dramatically simplifies the way that data centers connect to rack and blade servers, physical servers, virtual machines, LANs, SANs, and management networks.

Cisco UCS VIC 1387 Virtual Interface Card

The Cisco UCS VIC 1387 Virtual Interface Card is a dual-port Enhanced Quad Small Form-Factor Pluggable (QSFP) 40 Gigabit Ethernet and Fibre Channel over Ethernet (FCoE)-capable half-height PCI Express (PCIe) card designed exclusively for Cisco UCS C-Series Rack Servers. It incorporates Cisco’s next-generation converged network adapter (CNA) technology, with a comprehensive feature set, providing investment protection for future feature software releases. The card enables a policy-based, stateless, agile server infrastructure that can present over 256 PCIe standards-compliant interfaces to the host that can be dynamically configured as either network interface cards (NICs) or host bus adapters (HBAs). In addition, the Cisco UCS VIC 1387 card supports Cisco Data Center Virtual Machine Fabric Extender (VM-FEX) technology, which extends the Cisco UCS fabric interconnect ports to virtual machines, simplifying server virtualization deployment.

The personality of the card is determined dynamically at boot time using the service profile associated with the server. The number, type (NIC or HBA), identity (MAC address and World Wide Name [WWN]), failover policy, bandwidth, and quality-of-service (QoS) policies of the PCIe interfaces are all determined using the service profile. The capability to define, create, and use interfaces on demand provides a stateless and agile server infrastructure. Additional features and capabilities include:

Each PCIe interface created on the VIC is associated with an interface on the Cisco UCS fabric interconnect, providing complete network separation for each virtual cable between a PCIe device on the VIC and the interface on the fabric interconnect
The Cisco UCS VIC 1387 Virtual Interface Card provides high network performance and low latency for the most demanding applications such as SMB-Direct, VMQ, DPDK, and Cisco NetFlow

Viewing Network Adapter Properties

Before you begin

The server must be powered on, or the properties will not display.

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Network Adapters tab.

Step 4

In the Network Adapters area, review the following information:


Name	Description
Slot column	The slot in which the adapter is installed.
Product Name column	The product name for the adapter.
Number of Interfaces column	The number of interfaces for the adapter.
External Ethernet Interfaces	ID—The ID for the external ethernet interface. MAC Address—The MAC address for the external ethernet interface.

Step 5

In the Adapter Card area, review the following information:


Name	Description
Slot column	The slot in which the network adapter resides.
Product Name column	The product name of the network adapter.
Number of Interfaces column	The number of interfaces for the network adapter.
External Ethernet Interfaces column
ID column	The ID number of the external ethernet interface.
MAC Address column	The MAC address of the external ethernet interface.

Viewing VIC Adapter Properties

Before you begin

The server must be powered on, or the properties will not display.
A supported Virtual Interface Card (VIC) must be installed in the chassis and the server must be powered on.

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, click an adapter in the table to display its properties.

The resources of the selected adapter appear in the tabbed menu below the Adapter Cards area.

Step 5

In the Adapter Cards area, review the following information for the installed adapters:


Name	Description
PCI Slot column	The PCI slot in which the adapter is installed.
Product Name column	The product name for the adapter.
Serial Number column	The serial number for the adapter.
Product ID column	The product ID for the adapter.
Vendor column	The vendor for the adapter.
Cisco IMC Management Enabled column	Whether the adapter is able to manage Cisco IMC. This functionality depends on the type of adapter installed and how it is configured. For details, see the hardware installation guide for the type of server you are using.

Step 6

In the tabbed menu below the Adapter Cards area, click the General tab.

Step 7

In the Adapter Card Properties area, review the following information for the adapter:

Name

Description

PCI Slot field

The PCI slot in which the adapter is installed.

Note

For the C220 M4 and C240 M4 servers, PCI slot could also display as MLOM.

Vendor field

The vendor for the adapter.

Product Name field

The product name for the adapter.

Product ID field

The product ID for the adapter.

Serial Number field

The serial number for the adapter.

Version ID field

The version ID for the adapter.

Hardware Revision field

The hardware revision for the adapter.

Cisco IMC Management Enabled field

If this field displays yes, then the adapter is functioning in Cisco Card Mode and passing Cisco IMC management traffic through to the server Cisco IMC.

Configuration Pending field

If this field displays yes, the adapter configuration has changed in Cisco IMC but these changes have not been communicated to the host operating system.

To activate the changes, an administrator must reboot the adapter.

Description field

The user-defined description for the adapter, if any.

FIP Mode field

Whether FCoE Initialization Protocol (FIP) mode is enabled. FIP mode ensures that the adapter is compatible with current FCoE standards.

LLDP field

Whether the LLDP option is enabled for this VIC card.

Note

This option is available only on some UCS C-Series servers.

VNTAG Mode field

Whether virtual network tag (VNTAG) is enabled.

If VNTAG mode is enabled:

vNICs and vHBAs can be assigned to a specific channel
vNICs and vHBAs can be associated with a port profile
vNICs can fail over to another vNIC if there are communication problems

ISCSI Boot Capable field

Whether iSCSI boot is supported on the adapter.

usNIC Capable field

Whether the adapter and the firmware running on the adapter support the usNIC.

Step 8

In the External Ethernet Interfaces area, review the following information for the adapter:

Name

Description

ID column

The uplink port ID.

MAC Address column

The MAC address of the uplink port.

Link State column

The current operational state of the uplink port. This can be one of the following:

Fault
Link Up
Link Down
SFP ID Error
SFP Not Installed
SFP Security Check Failed
Unsupported SFP

Encap column

The mode in which adapter operates. This can be one of the following:

CE—Classical Ethernet mode.
NIV—Network Interface Virtualization mode.

Admin Speed column

The data transfer rate for the port. This can be one of the following:

Auto
1 Gpbs
10 Gpbs
40 Gpbs

Note

This option is only available for some adapter cards.

Operating Speed column

The operating rate for the port. This can be one of the following:

Auto
1 Gpbs
10 Gpbs
40 Gpbs

Note

This option is only available for some adapter cards.

Training Link column

Indicates if link training is enabled on the port.

Connector Present column

Indicated whether or not the connector is present. This can be one of the following:

Yes—Connector is present.
No—Connector not present.

Note

This option is only available for some adapter cards.

Connector Supported column

Indicates whether or not the connector is supported by Cisco. This can be one of the following:

Yes—The connector is supported by Cisco.
No—The connector is not supported by Cisco.

If the connector is not supported then the link will not be up.

Note

This option is only available for some adapter cards.

Connector Type column

The type of the connector.

Note

This option is only available for some adapter cards.

Connector Vendor column

The vendor for the connector.

Note

This option is only available for some adapter cards.

Connector Part Number column

The part number of the connector.

Note

This option is only available for some adapter cards.

Connector Part Revision column

The part revision number of the connector.

Note

This option is only available for some adapter cards.

Step 9

In the Firmware area, review the following information for the adapter:

Name

Description

Running Version field

The firmware version that is currently active.

Backup Version field

The alternate firmware version installed on the adapter, if any. The backup version is not currently running. To activate it, administrators can click Activate Firmware in the Actions area.

Note

When you install new firmware on the adapter, any existing backup version is deleted and the new firmware becomes the backup version. You must manually activate the new firmware if you want the adapter to run the new version.

Startup Version field

The firmware version that will become active the next time the adapter is rebooted.

Bootloader Version field

The bootloader version associated with the adapter card.

Status field

The status of the last firmware activation that was performed on this adapter.

Note

The status is reset each time the adapter is rebooted.

What to do next

To view the properties of virtual NICs and virtual HBAs, see the following sections:

Viewing vNIC Properties
Viewing vHBA Properties

Viewing Storage Adapter Properties

Before you begin

The server must be powered on.

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click Storage Adapters tab and review the following information:


Name	Description
Controller field	The type of controller.
PCI Slot field	The PCI slot in which the adapter is installed.
Product Name field	The product name for the adapter.
Serial Number field	The serial number for the adapter.
Firmware Package Build field	The installed firmware package for the adapter.
Product ID field	The product ID for the adapter.
Battery Status field	The vendor for the adapter.
Cache Memory Size field	The size of the cache memory, in megabytes.
Health field	The health of the adapter. This can be one of the following: Good Moderate Fault Severe Fault N/A
Details link	Click the Details link to view the Storage tab.

Guidelines for Managing vHBAs

When managing vHBAs, consider the following guidelines and restrictions:

The Cisco UCS Virtual Interface Cards provide two vHBAs and two vNICs by default. You can create up to 14 additional vHBAs or vNICs on these adapter cards.

The Cisco UCS 1455 and 1457 Virtual Interface Cards, in non-port channel mode, provide four vHBAs and four vNICs by default. You can create up to 10 additional vHBAs or vNICs on these adapter cards.

Note

If Network Interface Virtualization (NIV) mode is enabled for the adapter, you must assign a channel number to a vHBA when you create it.

When using the Cisco UCS Virtual Interface Cards in an FCoE application, you must associate the vHBA with the FCoE VLAN. Follow the instructions in the Modifying vHBA Properties section to assign the VLAN.
After making configuration changes, you must reboot the host for settings to take effect.

Viewing vHBA Properties

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vHBAs tab.

Step 6

In the Host Fibre Channel Interfaces area, select a vHBA from the table.

Step 7

Click Properties to open the vHBA Properties dialog box.

Step 8

In the General area, review the information in the following fields:

Name

Description

Name field

The name of the virtual HBA.

This name cannot be changed after the vHBA has been created.

Target WWNN field

The WWNN associated with the vHBA.

To let the system generate the WWNN, select AUTO. To specify a WWNN, click the second radio button and enter the WWNN in the corresponding field.

Target WWPN field

The WWPN associated with the vHBA.

To let the system generate the WWPN, select AUTO. To specify a WWPN, click the second radio button and enter the WWPN in the corresponding field.

FC SAN Boot check box

If checked, the vHBA can be used to perform a SAN boot.

Enable Persistent LUN Binding check box

If checked, any LUN ID associations are retained in memory until they are manually cleared.

Uplink Port field

The uplink port associated with the vHBA.

Note

This value cannot be changed for the system-defined vHBAs fc0 and fc1.

MAC Address field

The MAC address associated with the vHBA.

To let the system generate the MAC address, select AUTO. To specify an address, click the second radio button and enter the MAC address in the corresponding field.

Default VLAN field

If there is no default VLAN for this vHBA, click NONE. Otherwise, click the second radio button and enter a VLAN ID between 1 and 4094 in the field.

Class of Service drop-down list

The CoS for the vHBA.

Select an integer between 0 and 6, with 0 being lowest priority and 6 being the highest priority.

Note

This option cannot be used in VNTAG mode.

Rate Limit field

The data rate limit for traffic on this vHBA, in Mbps.

If you want this vHBA to have an unlimited data rate, select OFF. Otherwise, click the second radio button and enter an integer between 1 and 10,000.

Note

This option cannot be used in VNTAG mode.

PCIe Device Order field

The order in which this vHBA will be used.

To let the system set the order, select ANY. To specify an order, select the second radio button and enter an integer between 0 and 17.

EDTOV field

The error detect timeout value (EDTOV), which is the number of milliseconds to wait before the system assumes that an error has occurred.

Enter an integer between 1,000 and 100,000. The default is 2,000 milliseconds.

RATOV field

The resource allocation timeout value (RATOV), which is the number of milliseconds to wait before the system assumes that a resource cannot be properly allocated.

Enter an integer between 5,000 and 100,000. The default is 10,000 milliseconds.

Max Data Field Size field

The maximum size of the Fibre Channel frame payload bytes that the vHBA supports.

Enter an integer between 256 and 2112.

Channel Number field

The channel number that will be assigned to this vHBA.

Enter an integer between 1 and 1,000.

Note

VNTAG mode is required for this option.

Port Profile drop-down list

The port profile that should be associated with the vHBA, if any.

This field displays the port profiles defined on the switch to which this server is connected.

Note

VNTAG mode is required for this option.

Step 9

In the Error Recovery area, review the information in the following fields:


Name	Description
Enable FCP Error Recovery check box	If checked, the system uses FCP Sequence Level Error Recovery protocol (FC-TAPE).
Link Down Timeout field	The number of milliseconds the uplink port should be offline before it informs the system that the uplink port is down and fabric connectivity has been lost. Enter an integer between 0 and 240,000.
Port Down I/O Retries field	The number of times an I/O request to a port is returned because the port is busy before the system decides the port is unavailable. Enter an integer between 0 and 255.
I/O Timeout Retry field	The time period till which the system waits for timeout before retrying. When a disk does not respond for I/O within the defined timeout period, the driver aborts the pending command, and resends the same I/O after the timer expires. Enter an integer between 1 and 59.
Port Down Timeout field	The number of milliseconds a remote Fibre Channel port should be offline before informing the SCSI upper layer that the port is unavailable. Enter an integer between 0 and 240,000.

Step 10

In the Fibre Channel Interrupt area, review the information in the following fields:


Name	Description
Interrupt Mode drop-down list	The preferred driver interrupt mode. This can be one of the following: MSIx—Message Signaled Interrupts (MSI) with the optional extension. This is the recommended option. MSI—MSI only. INTx—PCI INTx interrupts.

Step 11

In the Fibre Channel Port area, review the information in the following fields:


Name	Description
I/O Throttle Count field	The number of I/O operations that can be pending in the vHBA at one time. Enter an integer between 1 and 1,024.
LUNs per Target field	The maximum number of LUNs that the driver will export. This is usually an operating system platform limitation. Enter an integer between 1 and 1,024. The recommended value is 1024.
LUN Queue Depth field	The number of commands that the HBA can send or receive in a single chunk per LUN. This parameter adjusts the initial queue depth for all LUNs on the adapter. Default value is 20 for physical miniports and 250 for virtual miniports.

Step 12

In the Fibre Channel Port FLOGI area, review the information in the following fields:


Name	Description
FLOGI Retries field	The number of times that the system tries to log in to the fabric after the first failure. To specify an unlimited number of retries, select the INFINITE radio button. Otherwise select the second radio button and enter an integer into the corresponding field.
FLOGI Timeout field	The number of milliseconds that the system waits before it tries to log in again. Enter an integer between 1,000 and 255,000.

Step 13

In the Fibre Channel Port PLOGI area, review the information in the following fields:


Name	Description
PLOGI Retries field	The number of times that the system tries to log in to a port after the first failure. Enter an integer between 0 and 255.
PLOGI Timeout field	The number of milliseconds that the system waits before it tries to log in again. Enter an integer between 1,000 and 255,000.

Step 14

In the SCSI I/O area, review the information in the following fields:


Name	Description
CDB Transmit Queue Count field	The number of SCSI I/O queue resources the system should allocate. Enter an integer between 1 and 8.
CDB Transmit Queue Ring Size field	The number of descriptors in each SCSI I/O queue. Enter an integer between 64 and 512.

Step 15

In the Receive/Transmit Queues area, review the information in the following fields:


Name	Description
FC Work Queue Ring Size field	The number of descriptors in each transmit queue. Enter an integer between 64 and 128.
FC Receive Queue Ring Size field	The number of descriptors in each receive queue. Enter an integer between 64 and 128.

Modifying vHBA Properties

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vHBAs tab.

Step 6

In the Host Fibre Channel Interfaces area, select a vHBA from the table.

Step 7

Click Properties to open the vHBA Properties dialog box.

Step 8

In the General area, update the following fields:

Name

Description

Name field

The name of the virtual HBA.

This name cannot be changed after the vHBA has been created.

Target WWNN field

The WWNN associated with the vHBA.

To let the system generate the WWNN, select AUTO. To specify a WWNN, click the second radio button and enter the WWNN in the corresponding field.

Target WWPN field

The WWPN associated with the vHBA.

To let the system generate the WWPN, select AUTO. To specify a WWPN, click the second radio button and enter the WWPN in the corresponding field.

FC SAN Boot check box

If checked, the vHBA can be used to perform a SAN boot.

Enable Persistent LUN Binding check box

If checked, any LUN ID associations are retained in memory until they are manually cleared.

Uplink Port field

The uplink port associated with the vHBA.

Note

This value cannot be changed for the system-defined vHBAs fc0 and fc1.

MAC Address field

The MAC address associated with the vHBA.

To let the system generate the MAC address, select AUTO. To specify an address, click the second radio button and enter the MAC address in the corresponding field.

Default VLAN field

If there is no default VLAN for this vHBA, click NONE. Otherwise, click the second radio button and enter a VLAN ID between 1 and 4094 in the field.

Class of Service drop-down list

The CoS for the vHBA.

Select an integer between 0 and 6, with 0 being lowest priority and 6 being the highest priority.

Note

This option cannot be used in VNTAG mode.

Rate Limit field

The data rate limit for traffic on this vHBA, in Mbps.

If you want this vHBA to have an unlimited data rate, select OFF. Otherwise, click the second radio button and enter an integer between 1 and 10,000.

Note

This option cannot be used in VNTAG mode.

PCIe Device Order field

The order in which this vHBA will be used.

To let the system set the order, select ANY. To specify an order, select the second radio button and enter an integer between 0 and 17.

EDTOV field

The error detect timeout value (EDTOV), which is the number of milliseconds to wait before the system assumes that an error has occurred.

Enter an integer between 1,000 and 100,000. The default is 2,000 milliseconds.

RATOV field

The resource allocation timeout value (RATOV), which is the number of milliseconds to wait before the system assumes that a resource cannot be properly allocated.

Enter an integer between 5,000 and 100,000. The default is 10,000 milliseconds.

Max Data Field Size field

The maximum size of the Fibre Channel frame payload bytes that the vHBA supports.

Enter an integer between 256 and 2112.

Channel Number field

The channel number that will be assigned to this vHBA.

Enter an integer between 1 and 1,000.

Note

VNTAG mode is required for this option.

Port Profile drop-down list

The port profile that should be associated with the vHBA, if any.

This field displays the port profiles defined on the switch to which this server is connected.

Note

VNTAG mode is required for this option.

Step 9

In the Error Recovery area, update the following fields:


Name	Description
Enable FCP Error Recovery check box	If checked, the system uses FCP Sequence Level Error Recovery protocol (FC-TAPE).
Link Down Timeout field	The number of milliseconds the uplink port should be offline before it informs the system that the uplink port is down and fabric connectivity has been lost. Enter an integer between 0 and 240,000.
Port Down I/O Retries field	The number of times an I/O request to a port is returned because the port is busy before the system decides the port is unavailable. Enter an integer between 0 and 255.
I/O Timeout Retry field	The time period till which the system waits for timeout before retrying. When a disk does not respond for I/O within the defined timeout period, the driver aborts the pending command, and resends the same I/O after the timer expires. Enter an integer between 1 and 59.
Port Down Timeout field	The number of milliseconds a remote Fibre Channel port should be offline before informing the SCSI upper layer that the port is unavailable. Enter an integer between 0 and 240,000.

Step 10

In the Fibre Channel Interrupt area, update the following fields:


Name	Description
Interrupt Mode drop-down list	The preferred driver interrupt mode. This can be one of the following: MSIx—Message Signaled Interrupts (MSI) with the optional extension. This is the recommended option. MSI—MSI only. INTx—PCI INTx interrupts.

Step 11

In the Fibre Channel Port area, update the following fields:


Name	Description
I/O Throttle Count field	The number of I/O operations that can be pending in the vHBA at one time. Enter an integer between 1 and 1,024.
LUNs per Target field	The maximum number of LUNs that the driver will export. This is usually an operating system platform limitation. Enter an integer between 1 and 1,024. The recommended value is 1024.
LUN Queue Depth field	The number of commands that the HBA can send or receive in a single chunk per LUN. This parameter adjusts the initial queue depth for all LUNs on the adapter. Default value is 20 for physical miniports and 250 for virtual miniports.

Step 12

In the Fibre Channel Port FLOGI area, update the following fields:


Name	Description
FLOGI Retries field	The number of times that the system tries to log in to the fabric after the first failure. To specify an unlimited number of retries, select the INFINITE radio button. Otherwise select the second radio button and enter an integer into the corresponding field.
FLOGI Timeout field	The number of milliseconds that the system waits before it tries to log in again. Enter an integer between 1,000 and 255,000.

Step 13

In the Fibre Channel Port PLOGI area, update the following fields:


Name	Description
PLOGI Retries field	The number of times that the system tries to log in to a port after the first failure. Enter an integer between 0 and 255.
PLOGI Timeout field	The number of milliseconds that the system waits before it tries to log in again. Enter an integer between 1,000 and 255,000.

Step 14

In the SCSI I/O area, update the following fields:


Name	Description
CDB Transmit Queue Count field	The number of SCSI I/O queue resources the system should allocate. Enter an integer between 1 and 8.
CDB Transmit Queue Ring Size field	The number of descriptors in each SCSI I/O queue. Enter an integer between 64 and 512.

Step 15

In the Receive/Transmit Queues area, update the following fields:


Name	Description
FC Work Queue Ring Size field	The number of descriptors in each transmit queue. Enter an integer between 64 and 128.
FC Receive Queue Ring Size field	The number of descriptors in each receive queue. Enter an integer between 64 and 128.

Step 16

Click Save Changes.

Creating a vHBA

The adapter provides two permanent vHBAs. If NIV mode is enabled, you can create up to 16 additional vHBAs.

Procedure

Step 1	In the Navigation pane, click the Server tab.
Step 2	On the Server tab, click Inventory.
Step 3	In the Inventory pane, click the Cisco VIC Adapters tab.
Step 4	In the Adapter Cards area, select the adapter card. If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.
Step 5	In the tabbed menu below the Adapter Cards area, click the vHBAs tab.
Step 6	In the Host Fibre Channel Interfaces area, choose one of these actions: To create a vHBA using default configuration settings, click Add. To create a vHBA using the same configuration settings as an existing vHBA, select that vHBA and click Clone. The Add vHBA dialog box appears.
Step 7	In the Add vHBA dialog box, enter a name for the vHBA in the Name entry box.
Step 8	Click Add vHBA.

What to do next

Reboot the server to create the vHBA.
If configuration changes are required, configure the new vHBA as described in Modifying vHBA Properties.

Deleting a vHBA

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vHBAs tab.

Step 6

In the Host Fibre Channel Interfaces area, select a vHBA from the table.

Note

You cannot delete either of the two default vHBAs, fc0 or fc1.

Step 7

Click Delete and click OK to confirm.

vHBA Boot Table

In the vHBA boot table, you can specify up to four LUNs from which the server can boot.

Creating a Boot Table Entry

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vHBAs tab.

Step 6

In the Host Fibre Channel Interfaces area, select a vHBA from the table.

Step 7

Click Boot Table to open the Boot Table dialog box for the selected vHBA.

Step 8

In the Boot Table dialog box, click Add to open the Add Boot Entry dialog box.

Step 9

In the Add Boot Entry dialog box, update the following fields:


Name	Description
Target WWPN field	The World Wide Port Name (WWPN) that corresponds to the location of the boot image. Enter the WWPN in the format `hh:hh:hh:hh:hh:hh:hh:hh`.
LUN ID field	The LUN ID that corresponds to the location of the boot image. Enter an ID between 0 and 255.
Add Boot Entry button	Adds the specified location to the boot table.
Reset Values button	Clears the values currently entered in the fields.
Cancel button	Closes the dialog box without saving any changes made while the dialog box was open.

Step 10

Click Add Boot Entry.

Deleting a Boot Table Entry

Procedure

Step 1	In the Navigation pane, click the Server tab.
Step 2	On the Server tab, click Inventory.
Step 3	In the Inventory pane, click the Cisco VIC Adapters tab.
Step 4	In the Adapter Cards area, select the adapter card. If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.
Step 5	In the tabbed menu below the Adapter Cards area, click the vHBAs tab.
Step 6	In the Host Fibre Channel Interfaces area, select a vHBA from the table.
Step 7	Click Boot Table to open the Boot Table dialog box for the selected vHBA.
Step 8	In the Boot Table dialog box, click the entry to be deleted.
Step 9	Click Delete and click OK to confirm.

vHBA Persistent Binding

Persistent binding ensures that the system-assigned mapping of Fibre Channel targets is maintained after a reboot.

Viewing Persistent Bindings

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vHBAs tab.

Step 6

In the Host Fibre Channel Interfaces area, select a vHBA from the table.

Step 7

Click Persistent Bindings to open the Persistent Bindings dialog box for the selected vHBA.

Step 8

In the Persistent Bindings dialog box for the selected vHBA, review the following information:


Name	Description
Index column	The unique identifier for the binding.
Target WWPN column	The target World Wide Port Name with which the binding is associated.
Host WWPN column	The host World Wide Port Name with which the binding is associated.
Bus ID column	The bus ID with which the binding is associated.
Target ID column	The target ID on the host system with which the binding is associated.
Rebuild Persistent Bindings button	Clears all unused bindings and resets the ones that are in use.
Close button	Closes the dialog box and saves your changes.

Step 9

Click Close.

Rebuilding Persistent Bindings

Procedure

Step 1	In the Navigation pane, click the Server tab.
Step 2	On the Server tab, click Inventory.
Step 3	In the Inventory pane, click the Cisco VIC Adapters tab.
Step 4	In the Adapter Cards area, select the adapter card. If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.
Step 5	In the tabbed menu below the Adapter Cards area, click the vHBAs tab.
Step 6	In the Host Fibre Channel Interfaces area, select a vHBA from the table.
Step 7	Click Persistent Bindings to open the Persistent Bindings dialog box for the selected vHBA.
Step 8	In the Persistent Bindings dialog box for the selected vHBA, click Rebuild Persistent Bindings.
Step 9	Click Close.

Guidelines for Managing vNICs

When managing vNICs, consider the following guidelines and restrictions:

The Cisco UCS Virtual Interface Cards provide two vHBAs and two vNICs by default. You can create up to 14 additional vHBAs or vNICs on these adapter cards.

The Cisco UCS 1455 and 1457 Virtual Interface Cards, in non-port channel mode, provide four vHBAs and four vNICs by default. You can create up to 10 additional vHBAs or vNICs on these adapter cards.

Note

If Network Interface Virtualization (NIV) mode is enabled for the adapter, you must assign a channel number to a vNIC when you create it.

After making configuration changes, you must reboot the host for settings to take effect.

Cisco C-series servers use Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) for packet transfers. RoCE defines the mechanism of performing RDMA over ethernet, based on the similar mechanism of RDMA over Infiniband. However, RoCE, with its performance oriented characteristics, delivers a superior performance compared to traditional network socket implementation because of the lower latency, lower CPU utilization and higher utilization of network bandwidth. RoCE meets the requirement of moving large amount of data across networks very efficiently.

The RoCE firmware requires the following configuration parameters provided by Cisco UCS Manager for better vNIC performance:

Queue Pairs
Memory Regions
Resource Groups

Guidelines and Limitations for SMB Direct with RoCE

Microsoft SMB Direct with RoCE is supported:
- On Windows 2012 R2.
- On Windows 2016.
Cisco UCS C-Series server does not support more than 4 RoCE-enabled vNICs per adapter.
Cisco UCS C-Series server does not support RoCE with NVGRE, VXLAN, VMQ, or usNIC.
Maximum number of queue pairs per adapter is 8192.
Maximum number of memory regions per adapter is 524288.
RoCE configuration is supported between Cisco adapters. Interoperability between Cisco adapters and third party adapters is not supported.

Important

It is required to configure the no-drop QOS policy settings at the switches in the RDMA traffic path.

Viewing vNIC Properties

Procedure

Step 1

In the Navigation pane, click the Networking menu.

Step 2

In the Adapter Card pane, click the vNICs tab.

Step 3

In the vNICs pane, click eth0 or eth1.

Step 4

In the Ethernet Interfaces pane's vNIC Properties area, review the information in the following fields:

Name

Description

Name field

The name for the virtual NIC.

This name cannot be changed after the vNIC has been created.

CDN field

The Consistent Device Name (CDN) that you can assign to the ethernet vNICs on the VIC cards. Assigning a specific CDN to a device helps in identifying it on the host OS.

Note

This feature works only when the CDN Support for VIC token is enabled in the BIOS.

MTU field

The maximum transmission unit, or packet size, that this vNIC accepts.

Enter an integer between 1500 and 9000.

Uplink Port drop-down list

The uplink port associated with this vNIC. All traffic for this vNIC goes through this uplink port.

MAC Address field

The MAC address associated with the vNIC.

To let the adapter select an available MAC address from its internal pool, select Auto. To specify an address, click the second radio button and enter the MAC address in the corresponding field.

Class of Service drop-down list

The class of service to associate with traffic from this vNIC.

Select an integer between 0 and 6, with 0 being lowest priority and 6 being the highest priority.

Note

This option cannot be used in VNTAG mode.

Trust Host CoS check box

Check this box if you want the vNIC to use the class of service provided by the host operating system.

PCI Order field

The order in which this vNIC will be used.

To specify an order, enter an integer within the displayed range.

Default VLAN field

If there is no default VLAN for this vNIC, click NONE. Otherwise, click the second radio button and enter a VLAN ID between 1 and 4094 in the field.

Note

This option cannot be used in VNTAG mode.

VLAN Mode drop-down list

If you want to use VLAN trunking, select TRUNK. Otherwise, select ACCESS.

Note

This option cannot be used in VNTAG mode.

Rate Limit field

If you want this vNIC to have an unlimited data rate, select OFF. Otherwise, click the second radio button and enter a rate limit in the associated field.

Enter an integer between 1 and 10,000 Mbps.

For VIC 13xx controllers, you can enter an integer between 1 and 40,000 Mbps.

For VIC 1455 and 1457 controllers:

If the adapter is connected to 25 Gbps link on a Switch, then you can enter an integer between 1 to 25,000 Mbps for the Rate Limit field.
If the adapter is connected to 10 Gbps link on a Switch, then you can enter an integer between 1 to 10,000 Mbps for the Rate Limit field.

For VIC 1495 and 1497 controllers:

If the adapter is connected to 40 Gbps link on a switch, then you can enter an integer between 1 to 40,000 Mbps for the Rate Limit field.
If the adapter is connected to 100 Gbps link on a switch, then you can enter an integer between 1 to 100,000 Mbps for the Rate Limit field.

Note

This option cannot be used in VNTAG mode.

Enable PXE Boot check box

Check this box if the vNIC can be used to perform a PXE boot.

Channel Number field

Select the channel number that will be assigned to this vNIC.

Note

VNTAG mode is required for this option.

PCI Link field

The link through which vNICs can be connected. These are the following values:

0 - The first cross-edged link where the vNIC is placed.
1 - The second cross-edged link where the vNIC is placed.

Note

This option is available only on some Cisco UCS C-Series servers.

Port Profile drop-down list

Select the port profile that should be associated with the vNIC.

This field displays the port profiles defined on the switch to which this server is connected.

Note

VNTAG mode is required for this option.

Enable Uplink Failover check box

Check this box if traffic on this vNIC should fail over to the secondary interface if there are communication problems.

Note

VNTAG mode is required for this option.

Enable VMQ check box

Check this box to enable Virtual Machine Queue (VMQ).

Note

Ensure that VMQ is not enabled when SR-IOV or netflow option is enabled on the adapter.

This option is available only on some Cisco UCS C-Series servers.

Enable aRFS check box

Check this box to enable Accelerated Receive Flow steering (aRFS).

This option is available only on some Cisco UCS C-Series servers.

Enable NVGRE check box

Check this box to enable Network Virtualization using Generic Routing Encapsulation.

This option is available only on some Cisco UCS C-Series servers.
This option is available only on C-Series servers with Cisco VIC 1385 cards.

Enable VXLAN check box

Check this box to enable Virtual Extensible LAN.

This option is available only on some Cisco UCS C-Series servers.
This option is available only on C-Series servers with Cisco VIC 1385 and VIC 14xx cards.

Advanced Filter check box

Check this box to enable advanced filter options in vNICs.

Failback Timeout field

After a vNIC has started using its secondary interface, this setting controls how long the primary interface must be available before the system resumes using the primary interface for the vNIC.

Enter a number of seconds between 0 and 600.

Note

VNTAG mode is required for this option.

Step 5

In the Ethernet Interrupt area, review the information in the following fields:


Name	Description
Interrupt Count field	The number of interrupt resources to allocate. In general, this value should be equal to the number of completion queue resources. Enter an integer between 1 and 514.
Coalescing Time field	The time to wait between interrupts or the idle period that must be encountered before an interrupt is sent. Enter an integer between 1 and 65535. To turn off interrupt coalescing, enter 0 (zero) in this field.
Coalescing Type drop-down list	This can be one of the following: MIN—The system waits for the time specified in the Coalescing Time field before sending another interrupt event. IDLE—The system does not send an interrupt until there is a period of no activity lasting as least as long as the time specified in the Coalescing Time field.
Interrupt Mode drop-down list	The preferred driver interrupt mode. This can be one of the following: MSI-X—Message Signaled Interrupts (MSI) with the optional extension. This is the recommended option. MSI—MSI only. INTx—PCI INTx interrupts.

Step 6

In the Ethernet Receive Queue area, review the information in the following fields:


Name	Description
Receive Queue Count field	The number of receive queue resources to allocate. Enter an integer between 1 and 256.
Receive Queue Ring Size field	The number of descriptors in each receive queue. Enter an integer between 64 and 4096.

Step 7

In the Ethernet Transmit Queue area, review the information in the following fields:


Name	Description
Transmit Queue Count field	The number of transmit queue resources to allocate. Enter an integer between 1 and 256.
Transmit Queue Ring Size field	The number of descriptors in each transmit queue. Enter an integer between 64 and 4096.

Step 8

In the Completion Queue area, review the information in the following fields:


Name	Description
Completion Queue Count field	The number of completion queue resources to allocate. In general, the number of completion queue resources you should allocate is equal to the number of transmit queue resources plus the number of receive queue resources. Enter an integer between 1 and 512.
Completion Queue Ring Size field	The number of descriptors in each completion queue. This value cannot be changed.

Step 9

In the TCP Offload area, review the information in the following fields:

Name

Description

Enable TCP Segmentation Offload check box

If checked, the CPU sends large TCP packets to the hardware to be segmented. This option may reduce CPU overhead and increase throughput rate.

If cleared, the CPU segments large packets.

Note

This option is also known as Large Send Offload (LSO).

Enable TCP Rx Offload Checksum Validation check box

If checked, the CPU sends all packet checksums to the hardware for validation. This option may reduce CPU overhead.

If cleared, the CPU validates all packet checksums.

Enable TCP Tx Offload Checksum Generation check box

If checked, the CPU sends all packets to the hardware so that the checksum can be calculated. This option may reduce CPU overhead.

If cleared, the CPU calculates all packet checksums.

Enable Large Receive check box

If checked, the hardware reassembles all segmented packets before sending them to the CPU. This option may reduce CPU utilization and increase inbound throughput.

If cleared, the CPU processes all large packets.

Step 10

In the Receive Side Scaling area, review the information in the following fields:


Name	Description
Enable TCP Receive Side Scaling check box	Receive Side Scaling (RSS) distributes network receive processing across multiple CPUs in multiprocessor systems. If checked, network receive processing is shared across processors whenever possible. If cleared, network receive processing is always handled by a single processor even if additional processors are available.
Enable IPv4 RSS check box	If checked, RSS is enabled on IPv4 networks.
Enable TCP-IPv4 RSS check box	If checked, RSS is enabled for TCP transmissions across IPv4 networks.
Enable IPv6 RSS check box	If checked, RSS is enabled on IPv6 networks.
Enable TCP-IPv6 RSS check box	If checked, RSS is enabled for TCP transmissions across IPv6 networks.
Enable IPv6 Extension RSS check box	If checked, RSS is enabled for IPv6 extensions.
Enable TCP-IPv6 Extension RSS check box	If checked, RSS is enabled for TCP transmissions across IPv6 networks.

Modifying vNIC Properties

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vNICs tab.

Step 6

In the Host Ethernet Interfaces area, select a vNIC from the table.

Step 7

Click Properties to open the vNIC Properties dialog box.

Step 8

In the General area, update the following fields:

Name

Description

Name field

The name for the virtual NIC.

This name cannot be changed after the vNIC has been created.

CDN field

The Consistent Device Name (CDN) that you can assign to the ethernet vNICs on the VIC cards. Assigning a specific CDN to a device helps in identifying it on the host OS.

Note

This feature works only when the CDN Support for VIC token is enabled in the BIOS.

MTU field

The maximum transmission unit, or packet size, that this vNIC accepts.

Enter an integer between 1500 and 9000.

Uplink Port drop-down list

The uplink port associated with this vNIC. All traffic for this vNIC goes through this uplink port.

MAC Address field

The MAC address associated with the vNIC.

To let the adapter select an available MAC address from its internal pool, select Auto. To specify an address, click the second radio button and enter the MAC address in the corresponding field.

Class of Service drop-down list

The class of service to associate with traffic from this vNIC.

Select an integer between 0 and 6, with 0 being lowest priority and 6 being the highest priority.

Note

This option cannot be used in VNTAG mode.

Trust Host CoS check box

Check this box if you want the vNIC to use the class of service provided by the host operating system.

PCI Link field

The link through which vNICs can be connected. These are the following values:

0 - The first cross-edged link where the vNIC is placed.
1 - The second cross-edged link where the vNIC is placed.

Note

This option is available only on some Cisco UCS C-Series servers.
This option is available only on C-Series servers with Cisco VIC 1385 cards.

PCI Order field

The order in which this vNIC will be used.

To let the system set the order, select Any. To specify an order, select the second radio button and enter an integer between 0 and 17.

Default VLAN field

If there is no default VLAN for this vNIC, click NONE. Otherwise, click the second radio button and enter a VLAN ID between 1 and 4094 in the field.

Note

This option cannot be used in VNTAG mode.

VLAN Mode drop-down list

If you want to use VLAN trunking, select TRUNK. Otherwise, select ACCESS. When the VLAN is set to ACCESS mode, any frame received from the specified default VLAN (1-4094) that is received from the switch with a TAG removes that TAG when it is sent to the host OS through the vNIC.

Note

This option cannot be used in VNTAG mode.

Rate Limit field

If you want this vNIC to have an unlimited data rate, select OFF. Otherwise, click the second radio button and enter a rate limit in the associated field.

Enter an integer between 1 and 10,000 Mbps or 40,000 Mbps depending on the adapter card you choose.

Note

This option cannot be used in VNTAG mode.

Enable PXE Boot check box

Check this box if the vNIC can be used to perform a PXE boot.

Channel Number field

Select the channel number that will be assigned to this vNIC.

Note

VNTAG mode is required for this option.

Port Profile drop-down list

Select the port profile that should be associated with the vNIC.

This field displays the port profiles defined on the switch to which this server is connected.

Note

VNTAG mode is required for this option.

Enable Uplink Failover check box

Check this box if traffic on this vNIC should fail over to the secondary interface if there are communication problems.

Note

VNTAG mode is required for this option.

Enable VMQ check box

Check this box to enable Virtual Machine Queue (VMQ).

Note

Ensure that VMQ is not enabled when SR-IOV or netflow option is enabled on the adapter.

Enable aRFS check box

Check this box to enable Accelerated Receive Flow steering (aRFS).

This option is available only on some Cisco UCS C-Series servers.

Enable NVGRE check box

Check this box to enable Network Virtualization using Generic Routing Encapsulation.

This option is available only on some Cisco UCS C-Series servers.
This option is available only on C-Series servers with Cisco VIC 1385 cards.

Enable VXLAN check box

Check this box to enable Virtual Extensible LAN.

This option is available only on some Cisco UCS C-Series servers.
This option is available only on C-Series servers with Cisco VIC 1385 cards.

Failback Timeout field

After a vNIC has started using its secondary interface, this setting controls how long the primary interface must be available before the system resumes using the primary interface for the vNIC.

Enter a number of seconds between 0 and 600.

Note

VNTAG mode is required for this option.

Step 9

In the Ethernet Interrupt area, update the following fields:


Name	Description
Interrupt Count field	The number of interrupt resources to allocate. In general, this value should be equal to the number of completion queue resources. Enter an integer between 1 and 514.
Coalescing Time field	The time to wait between interrupts or the idle period that must be encountered before an interrupt is sent. Enter an integer between 1 and 65535. To turn off interrupt coalescing, enter 0 (zero) in this field.
Coalescing Type drop-down list	This can be one of the following: MIN—The system waits for the time specified in the Coalescing Time field before sending another interrupt event. IDLE—The system does not send an interrupt until there is a period of no activity lasting as least as long as the time specified in the Coalescing Time field.
Interrupt Mode drop-down list	The preferred driver interrupt mode. This can be one of the following: MSI-X—Message Signaled Interrupts (MSI) with the optional extension. This is the recommended option. MSI—MSI only. INTx—PCI INTx interrupts.

Step 10

In the Ethernet Receive Queue area, update the following fields:


Name	Description
Receive Queue Count field	The number of receive queue resources to allocate. Enter an integer between 1 and 256.
Receive Queue Ring Size field	The number of descriptors in each receive queue. Enter an integer between 64 and 4096.

Step 11

In the Ethernet Transmit Queue area, update the following fields:


Name	Description
Transmit Queue Count field	The number of transmit queue resources to allocate. Enter an integer between 1 and 256.
Transmit Queue Ring Size field	The number of descriptors in each transmit queue. Enter an integer between 64 and 4096.

Step 12

In the Completion Queue area, update the following fields:


Name	Description
Completion Queue Count field	The number of completion queue resources to allocate. In general, the number of completion queue resources you should allocate is equal to the number of transmit queue resources plus the number of receive queue resources. Enter an integer between 1 and 512.
Completion Queue Ring Size field	The number of descriptors in each completion queue. This value cannot be changed.

Step 13

In the RoCE Properties area, update the following fields:


Name	Description
RoCE checkbox	Check the check box to change the RoCE Properties.
Queue Pairs (1 - 8192) field	The number of queue pairs per adapter. Enter an integer between 1 and 8192. We recommend that this number be an integer power of 2. The recommended value for queue pairs per vNIC is 2048. This allows four vNICs to be created per adapter. Windows driver reserves two queue pairs for internal use, so a valid range of values would be 4 to 8192 queue pairs per vNIC.
Memory Regions (1 - 524288) field	The number of memory regions per adapter. Enter an integer between 1 and 524288. We recommend that this number be an integer power of 2. The recommended value is 131072. The number of memory regions supported should be enough to meet application requirements as the regions are primarily used to send operation channel semantics.
Resource Groups (1 - 128) field	The number of resource groups per adapter. Enter an integer between 1 and 128. We recommend that this number be an integer power of 2 greater than or equal to the number of CPU cores on the system for optimum performance. Recommended value is 32. The resource group defines the total number of hardware resources such as WQ, RQ, CQ, and interrupts required to support the RDMA functionality, and is based on the total number of processor cores available with the host. The host chooses to dedicate a particular resource group to a core to maximize performance and get a better non-uniform memory access.

Step 14

In the TCP Offload area, update the following fields:

Name

Description

Enable TCP Segmentation Offload check box

If checked, the CPU sends large TCP packets to the hardware to be segmented. This option may reduce CPU overhead and increase throughput rate.

If cleared, the CPU segments large packets.

Note

This option is also known as Large Send Offload (LSO).

Enable TCP Rx Offload Checksum Validation check box

If checked, the CPU sends all packet checksums to the hardware for validation. This option may reduce CPU overhead.

If cleared, the CPU validates all packet checksums.

Enable TCP Tx Offload Checksum Generation check box

If checked, the CPU sends all packets to the hardware so that the checksum can be calculated. This option may reduce CPU overhead.

If cleared, the CPU calculates all packet checksums.

Enable Large Receive check box

If checked, the hardware reassembles all segmented packets before sending them to the CPU. This option may reduce CPU utilization and increase inbound throughput.

If cleared, the CPU processes all large packets.

Step 15

In the Receive Side Scaling area, update the following fields:


Name	Description
Enable TCP Receive Side Scaling check box	Receive Side Scaling (RSS) distributes network receive processing across multiple CPUs in multiprocessor systems. If checked, network receive processing is shared across processors whenever possible. If cleared, network receive processing is always handled by a single processor even if additional processors are available.
Enable IPv4 RSS check box	If checked, RSS is enabled on IPv4 networks.
Enable TCP-IPv4 RSS check box	If checked, RSS is enabled for TCP transmissions across IPv4 networks.
Enable IPv6 RSS check box	If checked, RSS is enabled on IPv6 networks.
Enable TCP-IPv6 RSS check box	If checked, RSS is enabled for TCP transmissions across IPv6 networks.
Enable IPv6 Extension RSS check box	If checked, RSS is enabled for IPv6 extensions.
Enable TCP-IPv6 Extension RSS check box	If checked, RSS is enabled for TCP transmissions across IPv6 networks.

Step 16

Click Save Changes.

Creating a vNIC

The adapter provides two permanent vNICs. You can create up to 16 additional vNICs.

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vNICs tab.

Step 6

In the Host Ethernet Interfaces area, choose one of these actions:

To create a vNIC using default configuration settings, click Add.
To create a vNIC using the same configuration settings as an existing vNIC, select that vNIC and click Clone.

The Add vNIC dialog box appears.

Step 7

In the Add vNIC dialog box, enter a name for the vNIC in the Name entry box.

Step 8

(Optional) In the Add vNIC dialog box, enter a channel number for the vNIC in the Channel Number entry box.

Note

If NIV is enabled on the adapter, you must assign a channel number for the vNIC when you create it.

Step 9

Click Add vNIC.

What to do next

If configuration changes are required, configure the new vNIC as described in Modifying vNIC Properties.

Deleting a vNIC

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vNICs tab.

Step 6

In the Host Ethernet Interfaces area, select a vNIC from the table.

Note

You cannot delete either of the two default vNICs, eth0 or eth1.

Step 7

Click Delete and click OK to confirm.

Overview of Cisco usNIC

The Cisco user-space NIC (Cisco usNIC) feature improves the performance of software applications that run on the Cisco UCS servers in your data center by bypassing the kernel when sending and receiving networking packets. The applications interact directly with a Cisco UCS VIC second generation or later generation adapter, such as the , which improves the networking performance of your high-performance computing cluster. To benefit from Cisco usNIC, your applications must use the Message Passing Interface (MPI) instead of sockets or other communication APIs.

Cisco usNIC offers the following benefits for your MPI applications:

Provides a low-latency and high-throughput communication transport.
Employs the standard and application-independent Ethernet protocol.
Takes advantage of lowlatency forwarding, Unified Fabric, and integrated management support in the following Cisco data center platforms:
- Cisco UCS server
- Cisco UCS VIC second generation or later generation adapter
- 10 or 40GbE networks

Standard Ethernet applications use user-space socket libraries, which invoke the networking stack in the Linux kernel. The networking stack then uses the Cisco eNIC driver to communicate with the Cisco VIC hardware. The following figure shows the contrast between a regular software application and an MPI application that uses Cisco usNIC.

Figure 1. Kernel-Based Network Communication versus Cisco usNIC-Based Communication

Configuring Cisco usNIC Using the Cisco IMC GUI

Note

Even though several properties are listed for Cisco usNIC in the usNIC properties dialog box, you must configure only the following properties because the other properties are not currently being used.

cq-count
rq-count
tq-count
usnic-count

Before you begin

You must log in to the Cisco IMC GUI with administrator privileges to perform this task. Click Play on this video to watch how to configure Cisco usNIC in CIMC.

Procedure

Step 1

Log into the Cisco IMC GUI.

For more information about how to log into Cisco IMC, see Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide.

Step 2

In the Navigation pane, click the Server tab.

Step 3

On the Server tab, click Inventory.

Step 4

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 5

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 6

In the tabbed menu below the Adapter Cards area, click the vNICs tab.

Step 7

In the Host Ethernet Interfaces area, select a vNIC from the table.

Note

For each vNIC that you want to configure as a usNIC, select the vNIC entry from the table and specify its properties as explained in steps 9 through step 18.

Step 8

Click usNIC to open the usNIC Properties dialog box.

Step 9

In the usNICs property, specify the number of Cisco usNICs that you want to create.

Each MPI process that is running on the server requires a dedicated usNIC. You might need to create up to 64 usNICs to sustain 64 MPI processes running simultaneously. We recommend that you create at least as many usNICs, per usNIC-enabled vNIC, as the number of physical cores on your server. For example, if you have 8 physical cores on your server, create 8 usNICs.

Step 10

In the Properties area, update the following fields:


Field Name	Description
Transmit Queue Count	The number of transmit queue resources to allocate. Cisco recommends setting this value to 6.
Receive Queue Count	The number of receive queue resources to allocate. Cisco recommends setting this value to 6.
Completion Queue Count	The number of completion queue resources to allocate. Cisco recommends setting this value to 6.

Step 11

Click Apply.

Step 12

In the Navigation pane, click the Server tab.

Step 13

On the Server tab, click BIOS.

Step 14

In the Actions area, click Configure BIOS.

Step 15

In the Configure BIOS Parameters dialog box, click the Advanced tab.

Step 16

In the Processor Configuration area, set the following properties to Enabled:

Intel(R) VT-d
Intel(R) VT-d ATS support
Intel(R) VT-d Coherency Support

Step 17

Click Save Changes.

The changes take effect upon the next server reboot.

Viewing usNIC Properties

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vNICs tab.

Step 6

In the Host Ethernet Interface area, select the usNIC that is assigned to vNIC, to open the usNIC properties dialog box.

Step 7

In the usNIC area, review or update the information in the following fields:

Name

Description

Name

The name for the vNIC that is the parent of the usNIC.

Note

This field is read-only.

usNIC field

The number of usNICs assigned to the specific vNIC.

Enter an integer between 0 and 225.

To assign additional usNICs to a specified vNIC, enter value higher than the existing value.

To delete usNICs from a specified vNIC, enter value smaller than the existing value.

To delete all the usNICs assigned to a vNIC, enter zero.

Step 8

In the Properties area, review or update the information in the following fields:

Name

Description

Transmit Queue Count field

The number of transmit queue resources to allocate.

Enter an integer between 1 and 256.

Receive Queue Count field

The number of receive queue resources to allocate.

Enter an integer between 1 and 256.

Completion Queue Count field

The number of completion queue resources to allocate. In general, the number of completion queue resources you should allocate is equal to the number of transmit queue resources plus the number of receive queue resources.

Enter an integer between 1 and 512.

Transmit Queue Ring Size field

The number of descriptors in each transmit queue.

Enter an integer between 64 and 4096.

Receive Queue Ring Size field

The number of descriptors in each receive queue.

Enter an integer between 64 and 4096.

Interrupt Count field

The number of interrupt resources to allocate. In general, this value should be equal to the number of completion queue resources.

Enter an integer between 1 and 514.

Interrupt Coalescing Type drop-down list

This can be one of the following:

MIN—The system waits for the time specified in the Coalescing Time field before sending another interrupt event.
IDLE—The system does not send an interrupt until there is a period of no activity lasting as least as long as the time specified in the Coalescing Time field.

Interrupt Coalescing Timer Time field

The time to wait between interrupts or the idle period that must be encountered before an interrupt is sent.

Enter an integer between 1 and 65535. To turn off interrupt coalescing, enter 0 (zero) in this field.

Class of Service field

The class of service to associate with traffic from this usNIC.

Select an integer between 0 and 6, with 0 being lowest priority and 6 being the highest priority.

Note

This option cannot be used in VNTAG mode.

TCP Segment Offload check box

If checked, the CPU sends large TCP packets to the hardware to be segmented. This option may reduce CPU overhead and increase throughput rate.

If cleared, the CPU segments large packets.

Note

This option is also known as Large Send Offload (LSO).

Large Receive check box

If checked, the hardware reassembles all segmented packets before sending them to the CPU. This option may reduce CPU utilization and increase inbound throughput.

If cleared, the CPU processes all large packets.

TCP Tx Checksum check box

If checked, the CPU sends all packets to the hardware so that the checksum can be calculated. This option may reduce CPU overhead.

If cleared, the CPU calculates all packet checksums.

TCP Rx Checksum check box

If checked, the CPU sends all packet checksums to the hardware for validation. This option may reduce CPU overhead.

If cleared, the CPU validates all packet checksums.


Name	Description
Apply button	Applies changes to all the usNICs associated with the vNIC device.
Reset values button	Restores the values for the usNIC to the settings that were in effect when this dialog box was first opened.
Cancel button	Closes the dialog box without making any changes.

Configuring iSCSI Boot Capability for vNICs

When the rack-servers are configured in a standalone mode, and when the VIC adapters are directly attached to the Nexus 5000 family of switches, you can configure these VIC adapters to boot the servers remotely from iSCSI storage targets. You can configure Ethernet vNICs to enable a rack server to load the host OS image from remote iSCSI target devices.

To configure the iSCSI boot capability on a vNIC:

You must log in with admin privileges to perform this task.
To configure a vNIC to boot a server remotely from an iSCSI storage target, you must enable the PXE boot option on the vNIC.

Note

You can configure a maximum of 2 iSCSI vNICs for each host.

Configuring iSCSI Boot Capability on a vNIC

You can configure a maximum of 2 iSCSI vNICs for each host.

Before you begin

To configure a vNIC to boot a server remotely from an iSCSI storage target, you must enable the PXE boot option on the vNIC.
You must log in with admin privileges to perform this task.

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the vNICs tab.

Step 6

In the Host Ethernet Interfaces area, select a vNIC from the table, and click iSCSI Boot.

Step 7

In the General Area, update the following fields:

Name

Description

Name field

The name of the vNIC.

DHCP Network check box

Whether DHCP Network is enabled for the vNIC.

If enabled, the initiator network configuration is obtained from the DHCP server.

DHCP iSCSI check box

Whether DHCP iSCSI is enabled for the vNIC. If enabled and the DHCP ID is set, the initiator IQN and target information are obtained from the DHCP server.

Note

If DHCP iSCSI is enabled without a DHCP ID, only the target information is obtained.

DHCP ID field

The vendor identifier string used by the adapter to obtain the initiator IQN and target information from the DHCP server.

Enter a string up to 64 characters.

DHCP Timeout field

The number of seconds to wait before the initiator assumes that the DHCP server is unavailable.

Enter an integer between 60 and 300 (default: 60 seconds)

Link Timeout field

The number of seconds to wait before the initiator assumes that the link is unavailable.

Enter an integer between 0 and 255 (default: 15 seconds)

LUN Busy Retry Count field

The number of times to retry the connection in case of a failure during iSCSI LUN discovery.

Enter an integer between 0 and 255. The default is 15.

IP Version field

The IP version to use during iSCSI boot.

Step 8

In the Initiator Area, update the following fields:

Name

Description

Name field

A regular expression that defines the name of the iSCSI initiator.

You can enter any alphanumeric string as well as the following special characters:

. (period)
: (colon)
- (dash)

Note

The name is in the IQN format.

IP Address field

The IP address of the iSCSI initiator.

Subnet Mask field

The subnet mask for the iSCSI initiator.

Gateway field

The default gateway.

Primary DNS field

The primary DNS server address.

Secondary DNS field

The secondary DNS server address.

TCP Timeout field

The number of seconds to wait before the initiator assumes that TCP is unavailable.

Enter an integer between 0 and 255 (default: 15 seconds)

CHAP Name field

The Challenge-Handshake Authentication Protocol (CHAP) name of the initiator.

CHAP Secret field

The Challenge-Handshake Authentication Protocol (CHAP) shared secret of the initiator.

Step 9

In the Primary Target Area, update the following fields:


Name	Description
Name field	The name of the primary target in the IQN format.
IP Address field	The IP address of the target.
TCP Port field	The TCP port associated with the target.
Boot LUN field	The Boot LUN associated with the target.
CHAP Name field	The Challenge-Handshake Authentication Protocol (CHAP) name of the initiator.
CHAP Secret field	The Challenge-Handshake Authentication Protocol (CHAP) shared secret of the initiator.

Step 10

In the Secondary Target Area, update the following fields:


Name	Description
Name field	The name of the secondary target in the IQN format.
IP Address field	The IP address of the target.
TCP Port field	The TCP port associated with the target.
Boot LUN field	The Boot LUN associated with the target.
CHAP Name field	The Challenge-Handshake Authentication Protocol (CHAP) name of the initiator.
CHAP Secret field	The Challenge-Handshake Authentication Protocol (CHAP) shared secret of the initiator.


Name	Description
Configure ISCSI button	Configures iSCSI boot on the selected vNIC.
Unconfigure ISCSI button	Removes the configuration from the selected vNIC.
Reset Values button	Restores the values for the vNIC to the settings that were in effect when this dialog box was first opened.
Cancel button	Closes the dialog box without making any changes.

Step 11

Click Configure ISCSI.

Removing iSCSI Boot Configuration from a vNIC

Before you begin

You must log in with admin privileges to perform this task.

Procedure

Step 1	In the Navigation pane, click the Server tab.
Step 2	On the Server tab, click Inventory.
Step 3	In the Inventory pane, click the Cisco VIC Adapters tab.
Step 4	In the Adapter Cards area, select the adapter card. If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.
Step 5	In the tabbed menu below the Adapter Cards area, click the vNICs tab.
Step 6	In the Host Ethernet Interfaces area, select a vNIC from the table, and click iSCSI Boot.
Step 7	In the dialog box that appears, click Unconfigure ISCSI.

Configuring Virtual Machine Queues on a vNIC

Before you begin

You must log in to the Cisco IMC GUI with administrator privileges to perform this task.

Procedure

Step 1	In the Navigation pane, click the Networking menu.
Step 2	In the Adapter Card pane, click the vNICs tab.
Step 3	In the Ethernet Interfaces pane's vNIC Properties area, check the Enable VMQ checkbox.
Step 4	In the Ethernet Transmit Queue area, enter an integer in the Transmit Queue Count field. This number should be greater than 1.
Step 5	In the Ethernet Receive Queue area, enter an integer in the Receive Queue Count field. This number should be equal to the number of transmit queues.
Step 6	In the Ethernet Interrupt area, enter an integer in the Interrupt Count field. This should be equal to the number of logical processors, or completion queues.

What to do next

Reboot the server.
Create a logical switch on the NIC.

Exporting the Adapter Configuration

The adapter configuration can be exported as an XML file to a remote server which can be one of the following:

TFTP
FTP
SFTP
SCP
HTTP

Before you begin

Obtain the remote server IP address.

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the General tab.

Step 6

In the Actions area of the General tab, click Export Configuration.

The Export Adapter Configuration dialog box opens.

Step 7

In the Export Adapter Configuration dialog box, update the following fields:

Name

Description

Export to drop-down list

The remote server type. This can be one of the following:

TFTP Server
FTP Server
SFTP Server
SCP Server
HTTP Server

Note

If you chose SCP or SFTP as the remote server type while performing this action, a pop-up window is displayed with the message Server (RSA) key fingerprint is <server_finger_print _ID> Do you wish to continue?. Click Yes or No depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

Server IP/Hostname field

The IPv4 or IPv6 address, or hostname of the server to which the adapter configuration file will be exported. Depending on the setting in the Export to drop-down list, the name of the field may vary.

Path and Filename field

The path and filename Cisco IMC should use when exporting the file to the remote server.

Username

The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP or HTTP.

Password

The password for the remote server username. This field does not apply if the protocol is TFTP or HTTP.

Step 8

Click Export Configuration.

Importing the Adapter Configuration

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the General tab.

Step 6

In the Actions area of the General tab, click Import Configuration.

The Import Adapter Configuration dialog box opens.

Step 7

In the Import Adapter Configuration dialog box, update the following fields:

Name

Description

Import from drop-down list

The remote server type. This can be one of the following:

TFTP Server
FTP Server
SFTP Server
SCP Server
HTTP Server

Note

If you chose SCP or SFTP as the remote server type while performing this action, a pop-up window is displayed with the message Server (RSA) key fingerprint is <server_finger_print _ID> Do you wish to continue?. Click Yes or No depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

Server IP/Hostname field

The IPv4 or IPv6 address, or hostname of the server on which the adapter configuration file resides. Depending on the setting in the Import from drop-down list, the name of the field may vary.

Path and Filename field

The path and filename of the configuration file on the remote server.

Username

The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP or HTTP.

Password

The password for the remote server username. This field does not apply if the protocol is TFTP or HTTP.

Step 8

Click Import Configuration.

The adapter downloads the configuration file from the specified path on the TFTP server at the specified IP address. The configuration will be installed during the next server reboot.

What to do next

Reboot the server to apply the imported configuration.

Restoring Adapter Defaults

Procedure

Step 1	In the Navigation pane, click the Server tab.
Step 2	On the Server tab, click Inventory.
Step 3	In the Inventory pane, click the Cisco VIC Adapters tab.
Step 4	In the Adapter Cards area, select the adapter card. If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.
Step 5	In the tabbed menu below the Adapter Cards area, click the General tab.
Step 6	In the Actions area of the General tab, click Reset To Defaults and click OK to confirm.

Adapter Firmware

A Cisco UCS C-Series network adapter contains the following firmware components:

Adapter firmware —The main operating firmware, consisting of an active and a backup image, can be installed from the Cisco IMC GUI or CLI interface or from the Host Upgrade Utility (HUU). You can upload a firmware image from either a local file system or a TFTP server.
Bootloader firmware—The bootloader firmware cannot be installed from the Cisco IMC. You can install this firmware using the Host Upgrade Utility.

Installing Adapter Firmware From a Local File

Before you begin

Store the adapter firmware file in the file system of the managing computer.

Procedure

Step 1	In the Navigation pane, click the Server tab.
Step 2	On the Server tab, click Inventory.
Step 3	In the Inventory pane, click the Cisco VIC Adapters tab.
Step 4	In the Adapter Cards area, select the adapter card. If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.
Step 5	In the tabbed menu below the Adapter Cards area, click the General tab.
Step 6	In the Actions area of the General tab, click Install Firmware to open the Install Adapter Firmware dialog box.
Step 7	In the Install Adapter Firmware dialog box, select Install from local file, then click Next.
Step 8	Click Browse... and locate the adapter firmware file.
Step 9	Click Install Firmware.

What to do next

To activate the new firmware, see Activating Adapter Firmware.

Installing Adapter Firmware From a Remote Server

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the General tab.

Step 6

In the Actions area of the General tab, click Install Firmware to open the Install Adapter Firmware dialog box.

Step 7

In the Install Adapter Firmware dialog box, select Install from Remote Server, then click Next.

Step 8

In the Install Adapter Firmware dialog box, update the following fields:

Name

Description

Install from drop-down list

The remote server type. This can be one of the following:

TFTP Server
FTP Server
SFTP Server
SCP Server
HTTP Server

Note

If you chose SCP or SFTP as the remote server type while performing this action, a pop-up window is displayed with the message Server (RSA) key fingerprint is <server_finger_print _ID> Do you wish to continue?. Click Yes or No depending on the authenticity of the server fingerprint.

The fingerprint is based on the host's public key and helps you to identify or verify the host you are connecting to.

Server IP/Hostname field

The IP address or hostname of the server on which the adapter configuration file resides. Depending on the setting in the Install from drop-down list, the name of the field may vary.

Path and Filename field

The path and filename of the configuration file on the remote server.

Username

The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP or HTTP.

Password

The password for the remote server username. This field does not apply if the protocol is TFTP or HTTP.

Back button

Click this button if you want to specify a local path for the firmware package.

Install Firmware button

Click this button to install the selected firmware package in the adapter's backup memory slot.

Close button

Click this button to close the wizard without making any changes to the firmware versions stored on the server.

Step 9

Click Install Firmware.

What to do next

To activate the new firmware, see Activating Adapter Firmware.

Activating Adapter Firmware

Procedure

Step 1	In the Navigation pane, click the Server tab.
Step 2	On the Server tab, click Inventory.
Step 3	In the Inventory pane, click the Cisco VIC Adapters tab.
Step 4	In the Adapter Cards area, select the adapter card. If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.
Step 5	In the tabbed menu below the Adapter Cards area, click the General tab.
Step 6	In the Actions area of the General tab, click Activate Firmware to open the Activate Adapter Firmware dialog box.
Step 7	In the Activate Adapter Firmware dialog box, select the image to run the next time the firmware starts up.
Step 8	Click Activate Adapter Firmware.

Resetting the Adapter

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click Inventory.

Step 3

In the Inventory pane, click the Cisco VIC Adapters tab.

Step 4

In the Adapter Cards area, select the adapter card.

If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area.

Step 5

In the tabbed menu below the Adapter Cards area, click the General tab.

Step 6

In the Actions area of the General tab, click Reset and click Yes to confirm.

Note

Resetting the adapter also resets the host.

Bias-Free Language

Results

Chapter: Managing Network Adapters

Managing Network Adapters

Overview of the Cisco UCS C-Series Network Adapters

Cisco UCS VIC 1225 Virtual Interface Card

Cisco UCS VIC 1385 Virtual Interface Card

Cisco UCS VIC 1227T Virtual Interface Card

Cisco UCS VIC 1387 Virtual Interface Card

Viewing Network Adapter Properties

Before you begin

Procedure

Viewing VIC Adapter Properties

Before you begin

Procedure

What to do next

Viewing Storage Adapter Properties

Before you begin

Procedure

Guidelines for Managing vHBAs

Viewing vHBA Properties

Procedure

Modifying vHBA Properties

Procedure

Creating a vHBA

Procedure

What to do next

Deleting a vHBA

Procedure

vHBA Boot Table

Creating a Boot Table Entry

Procedure

Deleting a Boot Table Entry

Procedure

vHBA Persistent Binding

Viewing Persistent Bindings

Procedure

Rebuilding Persistent Bindings

Procedure

Guidelines for Managing vNICs

Guidelines and Limitations for SMB Direct with RoCE

Viewing vNIC Properties

Procedure

Modifying vNIC Properties

Procedure

Creating a vNIC

Procedure

What to do next

Deleting a vNIC

Procedure

Overview of Cisco usNIC

Configuring Cisco usNIC Using the Cisco IMC GUI

Before you begin

Procedure

Viewing usNIC Properties

Procedure

Configuring iSCSI Boot Capability for vNICs

Configuring iSCSI Boot Capability on a vNIC

Before you begin

Procedure

Removing iSCSI Boot Configuration from a vNIC

Before you begin

Procedure

Configuring Virtual Machine Queues on a vNIC

Before you begin

Procedure

What to do next

Exporting the Adapter Configuration

Before you begin

Procedure

Importing the Adapter Configuration

Procedure

What to do next

Restoring Adapter Defaults

Procedure

Adapter Firmware

Installing Adapter Firmware From a Local File

Before you begin

Procedure