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.
In the Templates panel, you can select vNICs from the list of all templates installed on the system.
You can filter the list by Type, Usage Status, and Org to view availability and usage data.
To edit a specific vNIC template, type vNIC Template in the search bar to find the vNIC template you want to edit.
Note | Global vNICs can be used in local service profiles created in Cisco UCS Manager. |
Default vNIC behavior policy allows you to configure how vNICs are created for a service profile. You can choose to create vNICS manually, or you can create them automatically.
You can configure the default vNIC behavior policy to define how vNICs are created. This can be one of the following:
None—Cisco UCS Central does not create default vNICs for a service profile. All vNICs must be explicitly created.
HW Inherit—If a service profile requires vNICs and none have been explicitly defined, Cisco UCS Central creates the required vNICs based on the adapter installed in the server associated with the service profile.
Note | If you do not specify a default behavior policy for vNICs, HW Inherit is used by default. |
If you do not specify a default behavior policy for vNICs, HWInherit is used by default.