The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Configuring Dynamic vNIC Connection Policies
Note | In an SR-IOV topology, such as a Hyper-V or KVM cluster, a Virtual Function (VF) takes the place of the dynamic vNIC. The VF is essentially a restricted version of the dynamic vNIC, in which all system communication and configuration of the VF is performed through the associated physical function (PF). |
The dynamic vNIC connection policy determines how the connectivity between VMs and dynamic vNICs is configured. This policy is required for Cisco UCS domains that include servers with VIC adapters on which you have installed VMs and configured dynamic vNICs.
Each dynamic vNIC connection policy includes an Ethernet adapter policy and designates the number of vNICs that can be configured for any server associated with a service profile that includes the policy.
For Hyper-V, use the predefined Ethernet adapter policy named Windows.
Note | If you migrate a server that is configured with dynamic vNICs, the dynamic interface used by the vNICs fails and notifies you of that failure. When the server comes back up, assigns new dynamic vNICs to the server. If you are monitoring traffic on the dynamic vNIC, you must reconfigure the monitoring source. |
Step 1 | In the Navigation pane, click LAN. | ||||||||||
Step 2 | Expand . | ||||||||||
Step 3 | Expand the node
for the organization that contains the policy that you want to change.
If the system does not include multitenancy, expand the root node. | ||||||||||
Step 4 | Expand the Dynamic vNIC Connection Policies node and click the policy that you want to change. | ||||||||||
Step 5 | In the Work pane, click the General tab. | ||||||||||
Step 6 | Change one or
more of the following fields:
You cannot change the other properties of the policy, such as the Name field. | ||||||||||
Step 7 | Click Save Changes. | ||||||||||
Step 8 | If a confirmation dialog box displays, click Yes. |
You can delete a dynamic vNIC connection policy.
You can view dynamic vNIC properties in a VM.
The VM must be operational.
Step 1 | In the Navigation pane, click VM. |
Step 2 | On the VM tab, expand . |
Step 3 | Expand Virtual Machines. |
Step 4 | Expand the virtual machine that contains the dynamic vNIC. |
Step 5 | Choose the dynamic vNIC. |
Step 6 | In the
Work pane, click the
General tab.
In the Properties area, the vNIC properties appear. |
The predefined SRIOV Ethernet adapter policy supports up to 32 CPU threads. If the server has more than 32 CPU threads, you must follow this procedure to create and specify a custom adapter policy that supports a number of interrupts equal to the number of CPU threads.
For more information about creating an adapter policy, see "Configuring Ethernet Adapter Policies" in the Cisco UCS Manager GUI Configuration Guide.
Tip | If the fields in an area do not display, click the Expand icon to the right of the heading. |
Determine the number of CPU threads used by your server. You can find this information by navigating to Equipment > Chassis > Servers and viewing the Threads heading for your server in the Servers table.
Step 1 | If you opened the Create Ethernet Adapter Policy directly from another menu, skip to Step 6. | ||||||||||||||||||||||||||||||||
Step 2 | In the Navigation pane, click Servers. | ||||||||||||||||||||||||||||||||
Step 3 | Expand . | ||||||||||||||||||||||||||||||||
Step 4 | Expand the
node for the organization where you want to create the policy.
If the system does not include multitenancy, expand the root node. | ||||||||||||||||||||||||||||||||
Step 5 | Right-click Adapter Policies and choose Create Ethernet Adapter Policy. | ||||||||||||||||||||||||||||||||
Step 6 | Enter a name and
description for the policy in the following fields:
| ||||||||||||||||||||||||||||||||
Step 7 | In the
Resources area, configure the following values as
shown:
| ||||||||||||||||||||||||||||||||
Step 8 | In the
Options area, configure the following values as
shown:
| ||||||||||||||||||||||||||||||||
Step 9 | Click OK. | ||||||||||||||||||||||||||||||||
Step 10 | If a confirmation dialog box displays, click Yes. |