vHBA
Management
vHBA Template
This template is a policy that defines how a vHBA on a server connects to the SAN. It is also referred to as a vHBA SAN connectivity template.
You must include this policy in a service profile for it to take effect.
- Configuring a vHBA Template
- Deleting a vHBA Template
- Default vHBA Behavior Policy
- Configuring a Default vHBA Behavior Policy
Configuring a vHBA Template
The following example configures a vHBA template and commits the transaction:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org* # create vhba template VhbaTempFoo UCSC(policy-mgr) /org/vhba-templ* # set descr "This is a vHBA template example." UCSC(policy-mgr) /org/vhba-templ* # set fabric a UCSC(policy-mgr) /org/vhba-templ* # set fc-if accounting UCSC(policy-mgr) /org/vhba-templ* # set max-field-size 2112 UCSC(policy-mgr) /org/vhba-templ* # set pin-group FcPinGroup12 UCSC(policy-mgr) /org/vhba-templ* # set qos-policy policy34foo UCSC(policy-mgr) /org/vhba-templ* # set stats-policy ServStatsPolicy UCSC(policy-mgr) /org/vhba-templ* # set type updating-template UCSC(policy-mgr) /org/vhba-templ* # set wwpn-pool SanPool7 UCSC(policy-mgr) /org/vhba-templ* # commit-buffer UCSC(policy-mgr) /org/vhba-templ #
Deleting a vHBA Template
The following example deletes the vHBA template named VhbaTempFoo and commits the transaction:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # delete vhba template VhbaTempFoo UCSC(policy-mgr) /org* # commit-buffer UCSC(policy-mgr) /org #
Default vHBA Behavior Policy
Default vHBA behavior policy allow you to configure how vHBAs are created for a service profile. You can choose to create vHBAs manually, or you can allow them to be created automatically.
You can configure the default vHBA behavior policy to define how vHBAs are created. This can be one of the following:
-
None— does not create default vHBAs for a service profile. All vHBAs must be explicitly created.
-
HW Inherit—If a service profile requires vHBAs and none have been explicitly defined, creates the required vHBAs based on the adapter installed in the server associated with the service profile.
![]() Note | If you do not specify a default behavior policy for vHBAs, none is used by default. |
Configuring a Default vHBA Behavior Policy
This example shows how to set the default vHBA behavior policy to hw-inherit.
UCSC# connect policy-mgr UCSC(policy-mgr) # scope org / UCSC(policy-mgr)/org # scope vhba-beh-policy UCSC(policy-mgr)/org/vhba-beh-policy # set action hw-inherit UCSC(policy-mgr)/org/vhba-beh-policy* # commit-buffer UCSC(policy-mgr)/org/vhba-beh-policy #
vNIC/vHBA Placement Policies
vNIC/vHBA placement policies are used to determine the following:
-
How the virtual network interface connections (vCons) are mapped to the physical adapters on a server.
-
What types of vNICs or vHBAs can be assigned to each vCon.
Each vNIC/vHBA placement policy contains four vCons that are virtual representations of the physical adapters. When a vNIC/vHBA placement policy is assigned to a service profile, and the service profile is associated with a server, the vCons in the vNIC/vHBA placement policy are assigned to the physical adapters and the vNICs and vHBAs are assigned to those vCons.
For blade or rack servers that contain one adapter, Cisco UCS assigns all vCons to that adapter. For servers that contain four adapters, Cisco UCS assigns vCon1 to Adapter1, vCon2 to Adapter2, vCon3 to Adapter3, and vCon4 to Adapter4.
For blade or rack servers that contain two or three adapters, Cisco UCS assigns the vCons based on the type of server and the selected virtual slot mapping scheme, which can be Round Robin or Linear Ordered. For details about the available mapping schemes, see vCon to Adapter Placements.
![]() Note | You can specify the PCI order for the vHBA; however, the desired order works within a class of devices, such as vNICs or vHBAs and not across them. Within an adapter, vNICs are always placed ahead of the vHBAs. |
-
all—All configured vNICs and vHBAs can be assigned to the vCon, whether they are explicitly assigned to it, unassigned, or dynamic. This is the default.
-
assigned-only—vNICs and vHBAs must be explicitly assigned to the vCon. You can assign them explicitly through the service profile or the properties of the vNIC or vHBA.
-
exclude-dynamic—Dynamic vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for all static vNICs and vHBAs, whether they are unassigned or explicitly assigned to it.
-
exclude-unassigned—Unassigned vNICs and vHBAs cannot be assigned to the vCon. The vCon can be used for dynamic vNICs and vHBAs and for static vNICs and vHBAs that are explicitly assigned to it.
-
exclude-usnic—Cisco usNICs cannot be assigned to the vCon. The vCon can be used for all other configured vNICs and vHBAs, whether they are explicitly assigned to it, unassigned, or dynamic.
Note
An SRIOV usNIC that is explicitly assigned to a vCon set to exclude-usnic will remain assigned to that vCon.
If you do not include a vNIC/vHBA placement policy in the service profile, defaults to the Round Robin vCon mapping scheme and the All vNIC/vHBA selection preference, distributing the vNICs and vHBAs between the adapters based on the capabilities and relative capacities of each adapter.
Configuring a vNIC/vHBA Placement Policy
The following example creates a vNIC/vHBA placement policy named Adapter1All, sets the vCon mapping scheme to Linear Ordered, specifies that only assigned vNICs and vHBAs can be placed on adapter 1, and commits the transaction:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # create vcon-policy Adapter1 UCSC(policy-mgr) /org/vcon-policy* # set descr "This profile places all vNICs and vHBAs on adapter 1." UCSC(policy-mgr) /org/vcon-policy* # set mapping-scheme linear-ordered UCSC(policy-mgr) /org/vcon-policy* # set vcon 1 selection assigned-only UCSC(policy-mgr) /org/vcon-policy* # commit-buffer UCSC(policy-mgr) /org/vcon-policy* # UCSC(policy-mgr) /org #
Deleting a vNIC/vHBA Placement Policy
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . |
Step 3 | UCSC(policy-mgr) /org # delete vcon-policy policy-name |
Deletes the specified vNIC/vHBA placement profile. |
Step 4 | UCSC(policy-mgr) /org # commit-buffer |
Commits the transaction. |
The following example deletes the vNIC/vHBA placement profile named Adapter1All and commits the transaction:
UCSC# connect policy-mgr UCSC(policy-mgr)scope org / UCSC(policy-mgr) /org # delete vcon-policy Adapter1All UCSC(policy-mgr) /org* # commit-buffer UCSC(policy-mgr) /org #