Cisco UCS C-Series Integrated Management Controller GUI Configuration Guide - Cisco UCS M7 and Later Rack Servers, Release 4.3 - Managing Network Adapters [Cisco Integrated Management Controller]

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 15238 Virtual Interface Card
Cisco UCS VIC 15428 Virtual Interface Card
Cisco UCS VIC 1497 Virtual Interface Card
Cisco UCS VIC 1495 Virtual Interface Card
Cisco UCS VIC 1477 Virtual Interface Card
Cisco UCS VIC 1467 Virtual Interface Card
Cisco UCS VIC 1457 Virtual Interface Card
Cisco UCS VIC 1455 Virtual Interface Card
Cisco UCS VIC 1387 Virtual Interface Card
Cisco UCS VIC 1227T Virtual Interface Card
Cisco UCS VIC 1225 Virtual Interface Card
Cisco UCS P81E 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 15238 Virtual Interface Card

The Cisco UCS VIC 15238 is a dual-port quad small-form-factor pluggable (QSFP/QSFP28/QSFP56) mLOM card designed for designed for the M6 and M7 generation of Cisco UCS C-series Rack servers. The card supports 40/100/200-Gbps Ethernet or FCoE. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as either NICs or HBAs.

Cisco UCS VIC 15428 Virtual Interface Card

The Cisco VIC 15428 is a quad-port Small Form-Factor Pluggable (SFP+/SFP28/SFP56) mLOM card designed for the M6 and M7 generation of Cisco UCS C-Series Rack servers. The card supports 10/25/50-Gbps Ethernet or FCoE. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as either NICs or HBAs.

Cisco UCS VIC 1497 Virtual Interface Card

The Cisco VIC 1497 is a dual-port Small Form-Factor (QSFP28) mLOM card designed for the M5 generation of Cisco UCS C-Series Rack Servers. The card supports 40/100-Gbps Ethernet and FCoE. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs and HBAs.

Cisco UCS VIC 1495 Virtual Interface Card

The Cisco UCS VIC 1495 is a dual-port Small Form-Factor (QSFP28) PCIe card designed for the M5 generation of Cisco UCS C-Series Rack Servers. The card supports 40/100-Gbps Ethernet and FCoE. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs and HBAs.

Cisco UCS VIC 1477 Virtual Interface Card

The Cisco VIC 1477 is a dual-port Quad Small Form-Factor (QSFP28) mLOM card designed for the M6 generation of Cisco UCS C-Series Rack Servers. The card supports 40/100-Gbps Ethernet or FCoE. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs or HBAs.

Cisco UCS VIC 1467 Virtual Interface Card

The Cisco UCS VIC 1467 is a quad-port Small Form-Factor Pluggable (SFP28) mLOM card designed for the M6 generation of Cisco UCS C-Series Rack Servers. The card supports 10/25-Gbps Ethernet or FCoE. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as either NICs or HBA.

Cisco UCS VIC 1457 Virtual Interface Card

The Cisco UCS VIC 1457 is a quad-port Small Form-Factor Pluggable (SFP28) mLOM card designed for M5 generation of Cisco UCS C-Series rack servers. The card supports 10/25-Gbps Ethernet or FCoE. It incorporates Cisco’s next-generation CNA technology and offers a comprehensive feature set, providing investment protection for future feature software releases. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs and HBAs.

Cisco UCS VIC 1455 Virtual Interface Card

The Cisco UCS VIC 1455 is a quad-port Small Form-Factor Pluggable (SFP28) half-height PCIe card designed for M5 generation of Cisco UCS C-Series rack servers. The card supports 10/25-Gbps Ethernet or FCoE. It incorporates Cisco’s next-generation CNA technology and offers a comprehensive feature set, providing investment protection for future feature software releases. The card can present PCIe standards-compliant interfaces to the host, and these can be dynamically configured as NICs and HBAs.

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.

Cisco UCS VIC 1385 Virtual Interface Card

The Cisco UCS VIC 1385 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.

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.

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.

Cisco UCS P81E Virtual Interface Card

The Cisco UCS P81E Virtual Interface Card is optimized for virtualized environments, for organizations that seek increased mobility in their physical environments, and for data centers that want reduced costs through NIC, HBA, cabling, and switch reduction and reduced management overhead. This Fibre Channel over Ethernet (FCoE) PCIe card offers the following benefits:

Allows up to 16 virtual Fibre Channel and 16 virtual Ethernet adapters to be provisioned in virtualized or nonvirtualized environments using just-in-time provisioning, providing tremendous system flexibility and allowing consolidation of multiple physical adapters.
Delivers uncompromising virtualization support, including hardware-based implementation of Cisco VN-Link technology and pass-through switching.
Improves system security and manageability by providing visibility and portability of network polices and security all the way to the virtual machine.

The virtual interface card makes Cisco VN-Link connections to the parent fabric interconnects, which allows virtual links to connect virtual NICs in virtual machines to virtual interfaces in the interconnect. In a Cisco Unified Computing System environment, virtual links then can be managed, network profiles applied, and interfaces dynamically reprovisioned as virtual machines move between servers in the system.

Viewing Cisco UCS Network Adapter Properties

Before you begin

You must log in as a user with admin privileges to perform this task.
The server must be powered on, or the properties will not display.

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the General tab.

Step 3

In the Properties area, review the following information:

Table 1. Properties Area

Name

Description

PCI Slot

The PCI slot in which the adapter is installed.

Vendor

The vendor for the adapter.

Product Name

The product name for the adapter.

Product ID

The product ID for the adapter.

Serial Number

The serial number for the adapter.

Version ID

The version ID for the adapter.

Hardware Revision

The hardware revision for the adapter.

Cisco IMC Management Enabled

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

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.

ISCSI Boot Capable

Whether iSCSI boot is supported on the adapter.

CDN Capable

Whether CDN is supported on the adapter.

usNIC Capable

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

Port Channel Capable field

Indicates whether Port Channel is supported on the adapter.

Note

This option is available only on some of the adapters and servers.

Running Version

The firmware version that is currently active.

Backup Version

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

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

Bootloader Version

The bootloader version associated with the adapter card.

Status

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

Note

The status is reset each time the adapter is rebooted.

In the Settings area, review the following information:

Table 2. Settings Area

Name

Description

Description field

A user-defined description for the adapter.

You can enter between 1 and 63 characters.

Enable FIP Mode toggle button

Allows you to enable or disable FCoE Initialization Protocol (FIP). FIP mode ensures that the adapter is compatible with current FCoE standards.

Note

We recommend that you use this option only when explicitly directed to do so by a technical support representative.

Enable LLDP toggle button

Note

For LLDP change to be effective, it is required that you reboot the server.

If enabled, then Link Layer Discovery Protocol (LLDP) enables all the Data Center Bridging Capability Exchange protocol (DCBX) functionality, which includes FCoE, priority based flow control.

By default, LLDP option is enabled.

Note

We recommend that you do not disable LLDP option, as it disables all the DCBX functionality.

Enable VNTAG Mode toggle button

If VNTAG mode is enabled:

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

Port Channel toggle button

This option is enabled by default.

When Port channel is enabled, two vNICs and two vHBAs are available for use on the adapter card.

When disabled, four vNICs and four vHBAs are available for use on the adapter card.

Note

This option is available only on some of the adapters and servers.

Physical NIC Mode toggle button

This option is disabled by default.

When Physical NIC Mode is enabled, up-link ports of the VIC are set to pass-through mode. This allows the host to transmit packets without any modification. VIC ASIC does not rewrite the VLAN tag of the packets based on the VLAN and CoS settings for the vNIC.

Note

This option is available for Cisco UCS VIC 14xx series and 15xxx series adapters.
For the VIC configuration changes to be effective, you must reboot the host.
This option cannot be enabled on an adapter that has:
- Port Channel mode enabled
- VNTAG mode enabled
- LLDP enabled
- FIP mode enabled
- Cisco IMC Management Enabled value set to Yes
- Multiple user created vNICs

When Physical NIC Mode is enabled, the following message is displayed in a pop-up window:

After physical nic-mode mode switch, vNIC configurations will be lost and new default vNICs will be created.

Click OK.

Note

Beginning with the release 4.3(6), when Physical NIC mode is enabled, you cannot create default vLANs using Cisco IMC user interfaces.

Transmit Enhanced Mode toggle button

Allows you to enable enhance TCP performance on the transmit side for 1500 byte packets.

Step 4

Select the DCE Interfaces tab.

Step 5

You can review the following information:

Table 3. DCE Interfaces

Name

Description

Port column

The uplink port ID.

MAC Address column

The MAC address of the uplink port.

Link Status column

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

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

Note

A Serdes reset causes the Link State field to change from Link-Up to Link-down. If the Oper Link Training setting is valid, Link-Partners determine a Link-up or Link-down after the reset.
You might require to refresh the Web UI several times to view Link State field change.

Admin Link Training column

Indicates if admin link training is enabled on the port.

Select any of the below options for Admin Link Training:

Auto
Off
On

Admin Link Training is set to Auto, by default.

Note

This option is available only on some of the adapters and servers.

Encap column

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

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

Operating Speed column

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

1 Gbps
10 Gbps
25 Gbps
40 Gbps
50 Gbps
100 Gbps
4 x 10 Gbps
Auto

Admin Speed column

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

1 Gbps
10 Gbps
40 Gbps
4 x 10 Gbps
Auto

Note

This option is available only on some of the adapters and servers.

Admin FEC Mode column

Admin Forward Error Correction (FEC) apply only to Cisco UCS VIC 14xx adapters at speed 25/100G and Cisco UCS VIC 15xxx adapters at speeds 25G/50G.

Following Admin Forward Error Correction (FEC) mode options are available for configuration:

cl108 (RS-IEEE, clause 108)
cl91-cons16 (RS-FEC, clause 91, consortium version 1.6)
cl91 (RS-FEC, clause 91, consortium version 1.5)
cl74 (FC-FEC, clause 74), 25G only
Off

Admin FEC Mode is set to cl91, by default.

Note

This option is available only on some of the adapters and servers.
Any changes in the Admin FEC Mode settings leads to the reset of the port, even when the value for Operating FEC mode remains the same.

Oper Link Training column

Oper Link Training values are fetched from the values set in the Admin Link Training drop-down list.

Beginning from 4.2(2a), the below different settings apply only to Cisco UCS VIC 15xxx adapters and Copper cables at speeds 10G/25G/50G only.

If Admin Link Training is set to Auto, Adapter firmware sets Oper Link Training value (AutoNeg) as on or off, depending upon the transceivers.
- AutoNeg disabled with 25G copper
- AutoNeg enabled with 50G copper
If Admin Link Training is set to on, Adapter firmware sets Oper Link Training value as on.
- AutoNeg enabled with 25G copper
- AutoNeg enabled with 50G copper
If Admin Link Training is off, Adapter firmware sets Oper Link Training as off.
- AutoNeg disabled with 25G copper
- AutoNeg disabled with 50G copper

Note

For all non-passive copper cables, Oper Link Training (AN) mode is set to Off, irrespective of the Admin Link Training mode.
Any changes in the Admin Link Training settings leads to the reset of the Series for that port, even if the Oper Link Training value remains the same.

Operating FEC Mode

column

The value of Operating FEC Mode is the same as Admin FEC mode with these exceptions:

The value is Off when the speed is 10 Gbps or 40 Gbps. This is because FEC is not supported.
The value is Off for QSFP-100G-LR4-S transceiver.
The value is Off for QSFP-40/100-SRBD transceiver.

Note

This option is available only on some of the adapters and servers.

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.

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, 1457, 1455, and 1467 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 in VNTAG mode.

Note

If VNTAG 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 and Modifying vHBA Properties

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the vHBA Interfaces tab.

Step 3

From the list of the vHBA, click the one for which you wish to view or modify the properties.

Step 4

In the General Settings tab, review or modify the following properties:

Table 4. Settings

Name

Description

Name field

The name of the virtual HBA.

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

Initiator WWNN toggle button and field

The WWNN associated with the vHBA.

To let the system generate the WWNN, disable Initiator WWNN. To specify a WWNN, enable Initiator WWNN and enter the WWNN in the corresponding field.

Initiator WWPN toggle button and field

The WWPN associated with the vHBA.

To let the system generate the WWPN, disable Initiator WWPN. To specify a WWPN, enable Initiator WWPN and enter the WWPN in the corresponding field.

PCI Order field

The order in which this vHBA will be used.

Enter an integer between 0 and 17.

MAC Address toggle button and field

The MAC address associated with the vHBA.

To let the system generate the MAC address, disable MAC Address. To specify a MAC address, enable MAC Address and enter the MAC address in the corresponding field.

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.

Uplink Port drop-down list

The uplink port associated with the vHBA.

Note

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

Class of Service field

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.

Default VLAN toggle button and field

If there is no default VLAN for this vHBA, disable Default VLAN. Otherwise, enable Default VLAN and enter a VLAN ID between 1 and 4094 in the field.

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.

vHBA Type drop-down list

Note

This option is available only with Cisco UCS 14xx series VIC adapters and Cisco UCS 15428 VIC adapters.

The vHBA type used in this policy. vHBAs supporting FC and FC-NVMe can now be created on the same adapter. The vHBA type used in this policy can be one of the following:

fc-initiator—Legacy SCSI FC vHBA initiator

fc-target—vHBA that supports SCSI FC target functionality

Note

This option is available as a Tech Preview.

fc-nvme-initiator—vHBA that is an FC NVME initiator, which discovers FC NVME targets and connects to them.
fc-nvme-target—vHBA that acts as an FC NVME target and provides connectivity to the NVME storage.

PCI Link field

It is read-only field.

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.

Rate Limit toggle button and field

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

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

Note

This option cannot be used in VNTAG mode.

Step 5

In the Advanced Settings tab, review or modify the following properties:

Table 5. Error Recovery Area
Name	Description
FCP Error Recovery toggle button	If enabled, 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 Retry Count 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.
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.
IO 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.
FLOGI Retries toggle button and 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, enable FLOGI Retries. Otherwise disable FLOGI Retries 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.
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.

Table 6. Fiber Channel Port
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 1024.
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 4096.
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. Enter an integer between 1 and 254.
CDB Transmit Queue Count field	The number of SCSI I/O queue resources the system should allocate. For any other VIC adapter, enter an integer between 1 and 245.
CDB Transmit Queue Ring Size field	The number of descriptors in each SCSI I/O queue. Enter an integer between 64 and 512.
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 2048.

Step 6

In the Boot Table tab, review or modify the following properties:

Table 7. Boot Table
Name	Description
FC SAN Boot toggle button	If enabled, the vHBA can be used to perform a SAN boot.
Add Boot Entry button	Adds a new entry to the boot table.
Delete Boot Entry button	Allows you to delete the selected boot table row entry.
ID column	The default value for this field is 0.
Target WWPN column and 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 column and field	The LUN ID that corresponds to the location of the boot image. Enter an ID between 0 and 255.
Edit icon	Allows you to edit the Target WWPN and LUN ID of the selected boot table row.

Step 7

In the Persistent Bindings tab, review or modify the following properties:

Table 8. Persistent Binding
Name	Description
Persistent LUN Bindings toggle button	Allows you to enable Persistent LUN Bindings.
Reset button	Allows you to reset to factory settings.
Save button	Saves the configuration after changing Persistent LUN Bindings settings.
Rebuild Persistent Bindings button	Clears all unused bindings and resets the ones that are in use.
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.

Creating a vHBA

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.

Cisco UCS 1455, 1457, and 1467 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.

Before you begin

Ensure that Enable VNTAG Mode is on.

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

From the Actions drop-down list, select VIC > Create Virtual HBA Interface.

Add vHBA dialog box is displayed.

Step 3

Under Select Cisco VIC Adapter, update the following properties and click Next.

Table 9. Select Cisco VIC Adapter

Name

Description

Slot drop-down list

Allows you to select the VIC slot.

Note

If there is one slot available, then this option is grayed out.

Next button

Click Next to proceed.

Step 4

Under General Settings, update the following properties and click Next.

Table 10. General Settings

Name

Description

Name field

Allows you to enter a user defined name.

PCIe Order field

This is the order in which the vHBA is used. Enter an integer between 0 and 4.

Uplink Port drop-down list

The uplink port associated with this vHBA. All traffic for this vHBA goes through this uplink port. Select 0 or 1.

Channel Number field

Select the channel number which is assigned to this vHBA. Enter an integer between 0 and 1000.

Advance Options toggle button

Enable this to update advance properites.

Note

All the other properties are visible only when Advance Options is enabled.

Initiator WWNN toggle button and field

The WWNN associated with the vHBA.

To let the system generate the WWNN, disable Initiator WWNN. To specify a WWNN, enable Initiator WWNN and enter the WWNN in the corresponding field.

Initiator WWPN toggle button and field

The WWPN associated with the vHBA.

To let the system generate the WWPN, disable Initiator WWPN. To specify a WWPN, enable Initiator WWPN and enter the WWPN in the corresponding field.

FC SAN Boot toggle button

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

Persistent LUN Binding toggle button

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

MAC Address toggle button and field

The MAC address associated with the vHBA.

To let the system generate the MAC address, disable MAC Address. To specify a MAC address, enable MAC Address and enter the MAC address in the corresponding field.

Default VLAN toggle button and field

If there is no default VLAN for this vHBA, disable Default VLAN. Otherwise, enable Default VLAN and enter a VLAN ID between 1 and 4094 in the field.

Rate Limit toggle button and field

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

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

Note

This option cannot be used in VNTAG mode.

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.

vHBA Type drop-down list

Note

This option is available only with Cisco UCS 14xx series VIC adapters and Cisco UCS 15428 VIC adapters.

The vHBA type used in this policy. vHBAs supporting FC and FC-NVMe can now be created on the same adapter. The vHBA type used in this policy can be one of the following:

fc-initiator—Legacy SCSI FC vHBA initiator
fc-target—vHBA that supports SCSI FC target functionality
fc-nvme-initiator—vHBA that is an FC NVME initiator, which discovers FC NVME targets and connects to them.
fc-nvme-target—vHBA that acts as an FC NVME target and provides connectivity to the NVME storage.

Class of Service field

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.

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.

PCI Link field

It is read-only field.

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 5

Under Error Recovery, update the following properties and click Next.

Table 11. Error Recovery
Name	Description
FCP Error Recovery toggle button	If enabled, 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 Retry Count 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.
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.
IO 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.

Step 6

Under Fibre Channel Port, update the following properties and click Next.

Table 12. Fibre Channel Port
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 1024.
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 4096.
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. Enter an integer between 1 and 254.
FLOGI Retries toggle button and 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, enable FLOGI Retries. Otherwise disable FLOGI Retries 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.
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 7

Under I/O Receive & Transmit, update the following properties and click Next.

Table 13. **I/O Receive & Transmit Queues**
Name	Description
CDB Transmit Queue Count field	The number of SCSI I/O queue resources the system should allocate. For any other VIC adapter, enter an integer between 1 and 245.
CDB Transmit Queue Ring Size field	The number of descriptors in each SCSI I/O queue. Enter an integer between 64 and 512.
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 2048.

Step 8

Under Summary, review the information and click Save.

What to do next

Reboot the server to create the vHBA.

Cloning a vHBA

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the vHBA Interfaces tab.

Step 3

Select the vHBA Interface which you wish to clone and click Clone vHBA button.

Clone vHBA dialog box is displayed.

Step 4

Update the following properties in the Clone vHBA dialog box.

Table 14. Clone vHBA

Name

Description

Name field

Allows you to enter a user defined name.

Uplink Port drop-down list

The uplink port associated with this vHBA. All traffic for this vHBA goes through this uplink port. Select 0 or 1.

vHBA Type drop-down list

Note

This option is available only with Cisco UCS 14xx series VIC adapters and Cisco UCS 15428 VIC adapters.

The vHBA type used in this policy. vHBAs supporting FC and FC-NVMe can now be created on the same adapter. The vHBA type used in this policy can be one of the following:

fc-initiator—Legacy SCSI FC vHBA initiator
fc-target—vHBA that supports SCSI FC target functionality
fc-nvme-initiator—vHBA that is an FC NVME initiator, which discovers FC NVME targets and connects to them.
fc-nvme-target—vHBA that acts as an FC NVME target and provides connectivity to the NVME storage.

PCIe Order field

This is the order in which the vHBA is used. Enter an integer between 0 and 4.

Channel Number field

Select the channel number which is assigned to this vHBA. Enter an integer between 0 and 1000.

Step 5

Click Clone vHBA to save the changes.

Deleting a vHBA

Default vHBAs cannot be deleted. You can delete any other vHBAs created using VNTAG mode.

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the vHBA Interfaces tab.

Step 3

Select the vHBA Interfaces which you wish to delete and click Delete vHBAs button.

Note

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

Step 4

Click OK to confirm.

What to do next

Reboot the server to delete the vHBA.

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

From the Apps drop-down list, select Networking.

Step 2

Select the vHBA Interfaces tab.

Step 3

From the list of the vHBA, click the one for which you wish to view or modify the boot table.

Step 4

Select the Boot Table tab.

Step 5

Click the Add Boot Entry button.

This adds a new entry in the boot entry table.

Step 6

In the Add Boot Entry table, click the edit icon to update the following properties:


Name	Description
Target WWPN column and 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 column and field	The LUN ID that corresponds to the location of the boot image. Enter an ID between 0 and 255.

Step 7

Click Save.

Deleting a Boot Table Entry

Procedure

Step 1	From the Apps drop-down list, select Networking.
Step 2	Select the vHBA Interfaces tab.
Step 3	From the list of the vHBA, click the one for which you wish to view or modify the boot table.
Step 4	Select the Boot Table tab.
Step 5	From the boot entry table, select the entry which you wish to delete.
Step 6	Click Delete Boot Entry 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 and Enabling Persistent Bindings

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the vHBA Interfaces tab.

Step 3

From the list of the vHBA, click the one for which you wish to view or modify the boot table.

Step 4

Select the Persistent Binding tab.

Step 5

In the Persistent Bindings area, review or modify the following properties:

Table 15. Persistent Binding
Name	Description
Persistent LUN Bindings toggle button	Allows you to enable Persistent LUN Bindings.
Reset button	Allows you to reset to factory settings.
Save button	Saves the configuration after changing Persistent LUN Bindings settings.
Rebuild Persistent Bindings button	Clears all unused bindings and resets the ones that are in use.
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.

Rebuilding Persistent Bindings

Procedure

Step 1	From the Apps drop-down list, select Networking.
Step 2	Select the vHBA Interfaces tab.
Step 3	From the list of the vHBA, click the one for which you wish to view or modify the boot table.
Step 4	Select the Persistent Binding tab.
Step 5	Click the Rebuild Persistent Bindings button.
Step 6	Click Yes to confirm.

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.

Additional vHBAs can be created using VNTAG mode.

The Cisco UCS 1455, 1457, and 1467 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 VNTAG 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.

Viewing and Modifying vNIC Properties

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the vNIC Interfaces tab.

Step 3

From the list of the vNIC, click the one for which you wish to view or modify the properties.

Step 4

In the General Settings tab, review or modify the following properties:

Table 16. Settings Area

Name

Description

Name field

The name of the virtual NIC.

You cannot change the name of default vNIC.

MTU field

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

Enter an integer between 1500 and 9000.

VLAN Mode drop-down list

The mode for the associated VLAN. This can be one of the following:

TRUNK
ACCESS

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

In TRUNK mode:

In addition to the Cisco VIC adapter policy configuration, you can configure sub-interface on bare metal RHEL Linux host with a specific vlan for the packets to be correctly VLAN tagged.

You can also do this by creating Vswitch on ESXi Hypervisor and adding it to VM. Please work with the Host OS vendor accordingly.

PCI Order field

The order in which this vNIC will be used.

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

MAC Address toggle button

Allows you to enable automatic the MAC address for the vNIC.

MAC Address field

Allows you to enter MAC address manually.

Uplink Port drop-down list

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

Class of Service field

The Class of Service assigned to the vNIC.

Trust Host CoS toggle button

Allows you to enable class of service provided by the host operating system.

Default VLAN toggle button

Allows you to enable the number of the default VLAN associated with the vNIC.

Note

Beginning with the release 4.3(6), if Physical NIC mode is enabled, then this option is disabled.

Number of Default VLAN field

Enter the number of default VLAN.

Rate Limit toggle button

Allows you to enable or disable unlimited data rate. If you want vNIC to have an unlimited data rate, select OFF. Otherwise, enable the toggle button and enter a rate limit in the associated Rate Limit field.

Rate Limit field

Enter a rate limit value between 1 and 50000.

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.

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.

Channel Number field

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

Enter an interger between 1 and 1000.

Note

VNTAG mode is required for this option.

Port Profile field

The port profile associated with the vNIC, if any.

Note

VNTAG mode is required for this option. :

Enable Uplink Failover toggle button

Allows you to enable or disable whether the traffic on this vNIC should fail over to the secondary interface if there are communication problems.

Failback Timeout field

After a vNIC has started using the 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 an integer between 0 and 600.

Table 17. Resources Area
Name	Description
Receive Queue Count field	The number of receive queue resources to allocate. Enter an integer between 1 and 256.
Transmit Queue Count field	The number of transmit 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.
Receive Queue Ring Size field	The number of descriptors in each receive queue. Enter an integer between 64 and 16384. VIC 14xx Series adapters support a 4K (4096) maximum Ring Size VIC15xxx Series adapters support up to 16K Ring Size.
Transmit Queue Ring Size field	The number of descriptors in each transmit queue. Enter an integer between 64 and 16384. VIC 14xx Series adapters support a 4K (4096) maximum Ring Size VIC15xxx Series adapters support up to 16K Ring Size.
Completion Queue Ring Size field	The number of descriptors in each completion queue. This value cannot be changed.
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 1024.
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.
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.

Step 5

In the Features tab, review or modify the following properties:

Table 18. Offload Feature Area

Name

Description

TCP Segmentation Offload toggle button

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 NVGRE toggle button

Allows you to enable or disable Network Virtualization using Generic Routing Encapsulation.

Geneve Offload toggle button

Cisco IMC supports Generic Network Virtualization Encapsulation (Geneve) Offload feature with Cisco VIC 14xx series and VIC 15xxx adapters in ESX 7.0 (NSX-T 3.0) and ESX 6.7U3(NSX-T 2.5) OS.

Geneve is a tunnel encapsulation functionality for network traffic . Check this box if you want to enable Geneve Offload encapsulation in Cisco VIC 14xx series adapters.

Disable Geneve Offload, in order to prevent non-encapsulated UDP packets whose destination port numbers match with the Geneve destination port from being treated as tunneled packets.

If you enable Geneve Offload feature, then Cisco recommends the following settings:

Transmit Queue Count—1
Transmit Queue Ring Size—4096
Receive Queue Count—8
Receive Queue Ring Size—4096
Completion Queue Count—9
Interrupt Count—11

Note

You cannot enable the following when Geneve Offload is enabled in a setup with Cisco VIC 14xx series:

RDMA on the same vNIC
usNIC on the same vNIC
Non-Port Channel Mode on Cisco VIC 145x adapters
aRFS
Advanced Filters
NetQueue
Physical NIC Mode

Note

Cisco UCS C220 M7 and C240 M7 servers do not support Cisco VIC 14xx series.

Note

You cannot enable the following when Geneve Offload is enabled in a setup with Cisco VIC 15xxx:

aRFS
RoCEv2

Outer IPV6 is not supported with GENEVE Offload feature.

Downgrade Limitation—If Geneve Offload is enabled, you cannot downgrade to any release earlier than 4.2(2a).

TCP Large Receive toggle button

If enabled, 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.

aRFS toggle button

Allows yout to enable or disable Accelerated Receive Flow steering (aRFS).

Advanced Filter toggle button

Enable this feature for advanced filter options in vNICs.

TCP Tx Offload Checksum Generation toggle button

If enabled, 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 PTP toggle button

Check this box to enable Precision Time Protocol (PTP).

Precision Time Protocol (PTP) precisely synchronizes the server clock with other devices and peripherals on Linux operating systems.

Clocks managed by PTP follow a client-worker hierarchy, with workers sychronized to a master client. The hierarchy is updated by the best master clock (BMC) algorithm, which runs on every clock. One PTP interface per adapter must be enabled to sychronize it to the grand master clock.

Note

This option is supported only with Linux operating system.
This option is available only for Cisco UCS VIC 15xxx series adapters.

This option is available only on some Cisco UCS C-Series servers.
For the PTP enabling to be effective, it is required that you reboot the server.

Receive Side Scaling toggle button

Receive Side Scaling (RSS) distributes network receive processing across multiple CPUs in multiprocessor systems.

If enabled, 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.

TCP Rx Offload Checksum Validation toggle button

If enabled, 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.

VXLAN toggle button

Allows you to enable Virtual Extensible LAN.

QinQ Offload toggle button

Cisco IMC provides VIC QinQ Tunneling support for Cisco UCS M7 servers with Cisco UCS VIC 14xx series and 15xxx series VIC adapters.

Check this box to enable the QinQ Offload option on the specified vNIC.

Note

VIC QinQ Tunneling is not supported on 13xx adapters.

You cannot enable the following when QinQ Offload is enabled in a setup with Cisco VIC 14xx:

usNIC on the same vNIC
Geneve offload on the same vNIC
VMMQ on the same vNIC
RDMA v2 on the same vNIC
SR-IOV on the same vNIC
iSCSI boot on the same vNIC
PXE boot on the same vNIC

You cannot enable the following when QinQ Offload is enabled in a setup with Cisco VIC 15xxx:

usNIC on the same vNIC
VMMQ on the same vNIC
RDMA v2 on the same vNIC
SR-IOV on the same vNIC
iSCSI boot on the same vNIC
PXE boot on the same vNIC

QinQ VLAN field

Enter a QinQ VLAN ID between 2 and 4094 in the field.

Table 19. VMQ Properties
Name	Description
Enable VMQ toggle button	Allows you to enable Virtual Machine Queue (VMQ).
Enable Multi Queue toggle button	Allows you to enable the Multi Queue option on vNICs. When enabled multi queue vNICs will be available to the host. By default this is disabled. Multi queue is supported only on C-Series servers with 14xx and VIC 15xxx adapters. VMQ must be in enabled state to enable this option. When you enable this option on one of the vNICs, configuring only VMQ (without choosing multi-queue) on other vNICs is not supported. When this option is enabled usNIC configuration will be disabled
No. of Sub vNICs field	Number of sub vNICs available to the host when the multi queue option is enabled. Enter an integer between 1 and 64.
Receive Queue Count field	The number of receive queue resources to allocate. Enter an integer between 1 and 1000.
Transmit Queue Count field	The number of transmit queue resources to allocate. Enter an integer between 1 and 1000.
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 2000.

Table 20. RoCE Properties

Name

Description

RDMA Mode 1/2 toggle button

Check the check box to change the RoCE Properties.

Note

If Enable Multi Queue is enabled, ensure that RDMA Mode 2 is also enabled.

Queue Pairs 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.

Memory Regions 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.

Resource Groups field

The number of resource groups per adapter. Enter an integer between 1 and 256. 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.

Class of Service drop-down list

This field is read-only and is set to 5.

Note

This option is available only on some of the adapters.

Table 21. SR-IOV Properties

Name

Description

Enable SR-IOV toggle button

Allows you to enable or disable SR-IOV feature.

No. of VFs field

Enter an integer between 1 and 64.

Note

Other SR-IOV properties are enabled only when you enter an integer between 1 and 64.

Receive Queue Count Per VF field

The number of receive queue resources to allocate.

Enter an integer between 1 and 8.

Transmit Queue Count Per VF field

The number of descriptors in each transmit queue.

Enter an integer between 1 and 8.

Completion Queue Count Per VF 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 16.

Interrupt Count Per VF 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 16.

Step 6

In the iSCSI Boot Properties tab, review or modify the following properties:

Table 22. PXE Boot/iSCSI Boot
Name	Description
PXE Boot toggle button	If enabled, the PXE boot device is visible to BIOS in a boot order configuration.
iSCSI Boot toggle button	If enabled, the iSCSI boot device is visible to BIOS in a boot order configuration.

Table 23. iSCSI Settings

Name

Description

DHCP Network toggle button

Whether DHCP Network is enabled for the vNIC.

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

DHCP iSCSI toggle button

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.

Table 24. Initiator Area

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.

Initiator Priority drop-down list

Allows you to select one of the following:

Primary
Secondary

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.

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.

Table 25. Primary Target
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.

Table 26. Secondary Target
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 7

In the usNIC Properties tab, review or modify the following properties:

Table 27. usNIC Properties

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.

Receive Queue Count field

The number of receive queue resources to allocate.

Enter an integer between 1 and 256.

Transmit Queue Count field

The number of transmit 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.

Large Receive toggle button

If enabled, 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 Segment Offload toggle button

If enabled, 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).

TCP Tx Checksum toggle button

If enabled, 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 toggle button

If enabled, 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.

What to do next

Reboot the server to create the vHBA.

Creating a vNIC

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, 1457, and 1467 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

Beginning with the release 4.3(6), you cannot create a vNIC if Physical NIC Mode is enabled.

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

From the Actions drop-down list, select VIC > Create Virtual NIC Interface.

Add vNIC dialog box is displayed.

Step 3

Under Select Cisco VIC Adapter, update the following properties and click Next.

Table 28. Select Cisco VIC Adapter
Name	Description
Slot drop-down list
Next button	Click Next to continue.

Step 4

Under General Settings, update the following properties and click Next.

Table 29. General Settings

Name

Description

Name field

The name of the virtual NIC.

PCI Order field

The order in which this vNIC will be used.

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

Uplink Port drop-down list

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

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.

Channel field

The channel associated with the vNIC, if any.

Note

VNTAG mode is required for this option. :

Advance Options toggle button

Allows yout to enable or disable advance properties.

MAC Address toggle button

Allows you to enable automatic the MAC address for the vNIC.

MAC Address field

Allows you to enter MAC address manually.

NVGRE toggle button

Allows you to enable or disable Network Virtualization using Generic Routing Encapsulation.

VXLAN toggle button

Allows you to enable Virtual Extensible LAN.

PTP toggle button

Check this box to enable Precision Time Protocol (PTP).

Precision Time Protocol (PTP) precisely synchronizes the server clock with other devices and peripherals on Linux operating systems.

Clocks managed by PTP follow a client-worker hierarchy, with workers sychronized to a master client. The hierarchy is updated by the best master clock (BMC) algorithm, which runs on every clock. One PTP interface per adapter must be enabled to sychronize it to the grand master clock.

Note

This option is supported only with Linux operating system.
This option is available only for Cisco UCS VIC 15xxx series adapters.

This option is available only on some Cisco UCS C-Series servers.
For the PTP enabling to be effective, it is required that you reboot the server.

aRFS toggle button

Allows yout to enable or disable Accelerated Receive Flow steering (aRFS).

Geneve Offload toggle button

Cisco IMC supports Generic Network Virtualization Encapsulation (Geneve) Offload feature with Cisco VIC 14xx series and VIC 15xxx adapters in ESX 7.0 (NSX-T 3.0) and ESX 6.7U3(NSX-T 2.5) OS.

Geneve is a tunnel encapsulation functionality for network traffic . Check this box if you want to enable Geneve Offload encapsulation in Cisco VIC 14xx series adapters.

Disable Geneve Offload, in order to prevent non-encapsulated UDP packets whose destination port numbers match with the Geneve destination port from being treated as tunneled packets.

If you enable Geneve Offload feature, then Cisco recommends the following settings:

Transmit Queue Count—1
Transmit Queue Ring Size—4096
Receive Queue Count—8
Receive Queue Ring Size—4096
Completion Queue Count—9
Interrupt Count—11

Note

You cannot enable the following when Geneve Offload is enabled in a setup with Cisco VIC 14xx series:

RDMA on the same vNIC
usNIC on the same vNIC
Non-Port Channel Mode on Cisco VIC 145x adapters
aRFS
Advanced Filters
NetQueue
Physical NIC Mode

Note

Cisco UCS C220 M7 and C240 M7 servers do not support Cisco VIC 14xx series.

Note

You cannot enable the following when Geneve Offload is enabled in a setup with Cisco VIC 15xxx:

aRFS
RoCEv2

Outer IPV6 is not supported with GENEVE Offload feature.

Downgrade Limitation—If Geneve Offload is enabled, you cannot downgrade to any release earlier than 4.2(2a).

Advanced Filter toggle button

Enable this feature for advanced filter options in vNICs.

PXE Boot toggle button

Whether PXE boot is enabled for this vNIC.

Uplink Failover toggle button

Whether traffic on this vNIC will fail over to a secondary interface if the primary interface fails.

Note

VNTAG mode is required for this option. :

QinQ Offload toggle button

Cisco IMC provides VIC QinQ Tunneling support for Cisco UCS M7 servers with Cisco UCS VIC 14xx series and 15xxx series VIC adapters.

Check this box to enable the QinQ Offload option on the specified vNIC.

Note

VIC QinQ Tunneling is not supported on 13xx adapters.

You cannot enable the following when QinQ Offload is enabled in a setup with Cisco VIC 14xx:

usNIC on the same vNIC
Geneve offload on the same vNIC
VMMQ on the same vNIC
RDMA v2 on the same vNIC
SR-IOV on the same vNIC
iSCSI boot on the same vNIC
PXE boot on the same vNIC

You cannot enable the following when QinQ Offload is enabled in a setup with Cisco VIC 15xxx:

usNIC on the same vNIC
VMMQ on the same vNIC
RDMA v2 on the same vNIC
SR-IOV on the same vNIC
iSCSI boot on the same vNIC
PXE boot on the same vNIC

QinQ VLAN field

Enter a QinQ VLAN ID between 2 and 4094 in the field.

Default VLAN toggle button

Allows you to enable the number of the default VLAN associated with the vNIC.

Number of Default VLAN field

Enter the number of default VLAN.

Rate Limit toggle button

Allows you to enable or disable unlimited data rate. If you want vNIC to have an unlimited data rate, select OFF. Otherwise, enable the toggle button and enter a rate limit in the associated Rate Limit field.

Rate Limit field

Enter a rate limit value between 1 and 50000.

MTU field

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

Enter an integer between 1500 and 9000.

Class of Service field

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.

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.

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.

Port Profile field

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.

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.

Next button

Click Next to continue.

Step 5

Under Ethernet Interrupt, update the following properties and click Next.

Table 30. Ethernet Interrupt
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 1024.
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.
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.
Next button	Click Next to continue.

Step 6

Under TCP Offload, update the following properties and click Next.

Table 31. TCP Offload

Name

Description

TCP Large Receive toggle button

If enabled, 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 Segmentation Offload toggle button

If enabled, 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).

TCP Rx Offload Checksum Validation toggle button

If enabled, 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.

TCP Tx Offload Checksum Generation toggle button

If enabled, 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.

Next button

Click Next to continue.

Step 7

Under VMQ Settings, update the following properties and click Next.

Table 32. VMQ Settings
Name	Description
VMQ toggle button	Allows you to enable or disable Virtual Machine Queue (VMQ).
Multi Queue toggle button	Allows you to enable the Multi Queue option on vNICs. When enabled multi queue vNICs will be available to the host. By default this is disabled. Multi queue is supported only on C-Series servers with 14xx and VIC 15xxx adapters. VMQ must be in enabled state to enable this option. When you enable this option on one of the vNICs, configuring only VMQ (without choosing multi-queue) on other vNICs is not supported. When this option is enabled usNIC configuration will be disabled
Trust Host CoS toggle button	Enable this option if you want the vNIC to use the class of service provided by the host operating system.
No. of Sub vNICs field	Number of sub vNICs available to the host when the multi queue option is enabled.
Receive Queue Count field	The number of receive queue resources to allocate. Enter an integer between 1 and 1000.
Transmit Queue Count field	The number of transmit queue resources to allocate. Enter an integer between 1 and 1000.
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 2000.
Next button	Click Next to continue.

Step 8

Under RoCE Properties, update the following properties and click Next.

Table 33. RoCE Properties

Name

Description

RoCEv2 toggle button

Check the check box to change the RoCE Properties.

Note

If Enable Multi Queue is enabled, ensure that RDMA Mode 2 is also enabled.

Queue Pairs 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.

Memory Regions 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.

Resource Groups field

The number of resource groups per adapter. Enter an integer between 1 and 256. 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.

Class of Service drop-down list

This field is read-only and is set to 5.

Note

This option is available only on some of the adapters.

Next button

Click Next to continue.

Step 9

Under Queue Settings, update the following properties and click Next.

Table 34. Queue Settings
Name	Description
Receive Queue Count field	The number of receive queue resources to allocate. Enter an integer between 1 and 256.
Transmit Queue Count field	The number of transmit 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.
Receive Queue Ring Size field	The number of descriptors in each receive queue. Enter an integer between 64 and 16384. VIC 14xx Series adapters support a 4K (4096) maximum Ring Size VIC15xxx Series adapters support up to 16K Ring Size.
Transmit Queue Ring Size field	The number of descriptors in each transmit queue. Enter an integer between 64 and 16384. VIC 14xx Series adapters support a 4K (4096) maximum Ring Size VIC15xxx Series adapters support up to 16K Ring Size.
Completion Queue Ring Size field	The number of descriptors in each completion queue. This value cannot be changed.
Next button	Click Next to continue.

Step 10

Under SR-IOV Properties, update the following properties and click Next.

Table 35. SR-IOV Properties

Name

Description

No. of VFs field

Enter an integer between 1 and 64.

Note

Other SR-IOV properties are enabled only when you enter an integer between 1 and 64.

Receive Queue Count Per VF field

The number of receive queue resources to allocate.

Enter an integer between 1 and 8.

Transmit Queue Count Per VF field

The number of descriptors in each transmit queue.

Enter an integer between 1 and 8.

Completion Queue Count Per VF 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 16.

Interrupt Count Per VF 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 16.

Next button

Click Next to continue.

Step 11

Under Summary, review the information and click Next.

Cloning a vNIC

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the vNIC Interfaces tab.

Step 3

Select the vNIC Interface which you wish to clone and click Clone vNIC button.

Clone vNIC dialog box is displayed.

Step 4

Update the following properties in the Clone vNIC dialog box.

Table 36. Clone vNIC
Name	Description
Name field	Allows you to enter a user defined name.
Uplink Port drop-down list	The uplink port associated with this vNIC. All traffic for this vNIC goes through this uplink port. Select 0 or 1.
PCIe Order field	This is the order in which the vNIC is used. Enter an integer between 0 and 4.
VLAN Mode drop-down list	The mode for the associated VLAN. This can be one of the following: TRUNK ACCESS If you want to use VLAN trunking, select TRUNK. Otherwise, select ACCESS.
Default VLAN toggle button and field	If there is no default VLAN for this vNIC, disable Default VLAN. Otherwise, enable Default VLAN and enter a VLAN ID between 1 and 4094 in the field.
Channel Number field	Select the channel number which is assigned to this vNIC. Enter an integer between 0 and 1000.
Clone vNIC button	Allows you to clone a vNIC.

Step 5

Click Clone vNIC to save the changes.

Deleting a vNIC

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the vNIC Interfaces tab.

Step 3

Select the vNIC Interfaces which you wish to delete and click Delete vNIC button.

Note

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

Step 4

Click OK to confirm.

Configuring iSCSI Boot Capability for vNICs

To configure the iSCSI boot capability on a vNIC:

You must log in as an admin to perform this procedure.
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

Before you begin

You must log in as an admin to perform this procedure.

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the vNIC Interfaces tab.

Step 3

Select the vNIC Interface which you wish to modify the properties and click the Name column.

vNIC Properties dialog box is displayed.

Step 4

Select the iSCSI Boot Properties tab.

You can view or modify the following properties:

Table 37. PXE Boot/iSCSI Boot
Name	Description
PXE Boot toggle button	If enabled, the PXE boot device is visible to BIOS in a boot order configuration.
iSCSI Boot toggle button	If enabled, the iSCSI boot device is visible to BIOS in a boot order configuration.

Table 38. iSCSI Settings

Name

Description

DHCP Network toggle button

Whether DHCP Network is enabled for the vNIC.

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

DHCP iSCSI toggle button

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.

Table 39. Initiator Area

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.

Initiator Priority drop-down list

Allows you to select one of the following:

Primary
Secondary

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.

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.

Table 40. Primary Target
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.

Table 41. Secondary Target
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 5

Click Save.

Removing iSCSI Boot Configuration from a vNIC

Before you begin

You must log in as an admin to perform this procedure.

Procedure

Step 1	From the Apps drop-down list, select Networking.
Step 2	Select the vNIC Interfaces tab.
Step 3	Select the vNIC Interface which you wish to modify the properties and click the Name column. vNIC Properties dialog box is displayed.
Step 4	Select the iSCSI Boot Properties tab.
Step 5	Click the iSCSI Boot toggle button to disable iSCSI boot.

What to do next

Reboot the server to remove the iSCSI Boot Configuration.

Viewing and Configuring Cisco usNIC on a vNIC

Before you begin

You must log in as an admin to perform his procedure.

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

Select the vNIC Interfaces tab.

Step 3

Select the vNIC Interface which you wish to modify the properties and click the Name column.

vNIC Properties dialog box is displayed.

Step 4

Select the usNIC Properties tab.

Step 5

In the usNIC Properties area, review and update the following fields.

Table 42. usNIC Properties

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.

Receive Queue Count field

The number of receive queue resources to allocate.

Enter an integer between 1 and 256.

Transmit Queue Count field

The number of transmit 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.

Large Receive toggle button

If enabled, 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 Segment Offload toggle button

If enabled, 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).

TCP Tx Checksum toggle button

If enabled, 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 toggle button

If enabled, 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.

Step 6

Click Save Changes.

The changes take effect upon the next server reboot.

Exporting the Adapter Configuration

Before you begin

Obtain the remote server IP address.

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

From the Actions drop-down list, select VIC > Export vNIC.

Export vNIC dialog box is displayed.

Step 3

In the Export vNIC dialog box, update the following properties:

Table 43. Export vNIC

Name

Description

Server IP/Hostname field

The IP address or hostname of the server to which you wish to export the file.

Upload Protocol button

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

TFTP
FTP
SFTP
SCP
HTTP

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.

Path and Filename field

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

Username field

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.

Step 4

Click Export Configuration.

Importing the Adapter Configuration

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

From the Actions drop-down list, select VIC > Import vNIC.

Import vNIC dialog box is displayed.

Step 3

In the Import vNIC dialog box, update the following properties:

Table 44. Import vNIC

Name

Description

Server IP/Hostname field

The IP address or hostname of the server on which the configuration file resides.

Upload Protocol button

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

TFTP
FTP
SFTP
SCP
HTTP

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.

Path and Filename field

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

Username field

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.

Step 4

Click Import Configuration.

What to do next

Reboot the server to apply the imported configuration.

Restoring Adapter Defaults

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

From the Actions drop-down list, select VIC > Reset To Defaults.

Reset To Defaults dialog box is displayed.

Step 3

Click Yes to confirm.

Resetting the Adapter

Procedure

Step 1

From the Apps drop-down list, select Networking.

Step 2

From the Actions drop-down list, select VIC > Reset.

Reset dialog box is displayed.

Step 3

Click OK to confirm.

Cisco UCS C-Series Integrated Management Controller GUI Configuration Guide - Cisco UCS M7 and Later Rack Servers, Release 4.3

Bias-Free Language

Results

Chapter: Managing Network Adapters

Managing Network Adapters

Overview of the Cisco UCS C-Series Network Adapters

Cisco UCS VIC 15238 Virtual Interface Card

Cisco UCS VIC 15428 Virtual Interface Card

Cisco UCS VIC 1497 Virtual Interface Card

Cisco UCS VIC 1495 Virtual Interface Card

Cisco UCS VIC 1477 Virtual Interface Card

Cisco UCS VIC 1467 Virtual Interface Card

Cisco UCS VIC 1457 Virtual Interface Card

Cisco UCS VIC 1455 Virtual Interface Card

Cisco UCS VIC 1387 Virtual Interface Card

Cisco UCS VIC 1385 Virtual Interface Card

Cisco UCS VIC 1227T Virtual Interface Card

Cisco UCS VIC 1225 Virtual Interface Card

Cisco UCS P81E Virtual Interface Card

Viewing Cisco UCS Network Adapter Properties

Before you begin

Procedure

Guidelines for Managing vHBAs

Viewing and Modifying vHBA Properties

Procedure

Creating a vHBA

Before you begin

Procedure

What to do next

Cloning a vHBA

Procedure

Deleting a vHBA

Procedure

What to do next

vHBA Boot Table

Creating a Boot Table Entry

Procedure

Deleting a Boot Table Entry

Procedure

vHBA Persistent Binding

Viewing and Enabling Persistent Bindings

Procedure

Rebuilding Persistent Bindings

Procedure

Guidelines for Managing vNICs

Viewing and Modifying vNIC Properties

Procedure

What to do next

Creating a vNIC

Procedure

Cloning a vNIC

Procedure

Deleting a vNIC

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

What to do next

Viewing and Configuring Cisco usNIC on a vNIC

Before you begin

Procedure

Exporting the Adapter Configuration

Before you begin

Procedure

Importing the Adapter Configuration

Procedure

What to do next

Restoring Adapter Defaults

Procedure

Resetting the Adapter

Procedure

Was this Document Helpful?

Contact Cisco