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 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 Virtual Ethernet Interface Cards area, select a vNIC from the table. |
Step 7 |
Click Properties to open the vNIC Properties dialog box. |
Step 8 |
In the General area, review the information in the following fields:
Name |
Description |
Name field |
A user-defined name for the virtual NIC. Once you create the vNIC, this name cannot be changed. |
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. |
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 let the system set the order, select Any. To specify an order, select the second radio button and enter an integer between 0 and 99. |
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 in the field. The ID can be an integer between 1 and 4094. |
VLAN Mode drop-down list |
If you want to use VLAN trunking, select TRUNK. Otherwise, select ACCESS. |
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. You can enter an integer between 1 and 10,000 Mbps. |
Enable PXE Boot check box |
Check this box if the vNIC can be used to perform a PXE boot. |
|
Step 9 |
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 a value 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:
|
|
Step 10 |
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 11 |
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 12 |
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 13 |
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 14 |
In the Receive Side Scaling area, review the information in the following fields:
Name |
Description |
Enable TCP Receive Side Scaling check box |
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. |
|