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.
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.
About vHBA Templates
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.
This policy requires that one or more of the following resources already exist in the system:
Named VSAN
WWNN pool or WWPN pool
SAN pin group
Statistics threshold policy
Step 1 |
In the Navigation pane, click SAN. |
||||||||||||||||||||||||
Step 2 |
Expand . |
||||||||||||||||||||||||
Step 3 |
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 4 |
Right-click the vHBA Templates node and choose Create vHBA Template. |
||||||||||||||||||||||||
Step 5 |
In the Create vHBA Template dialog box, complete the following fields:
|
||||||||||||||||||||||||
Step 6 |
Click OK. |
Include the vHBA template in a service profile.
You can bind a vHBA associated with a service profile to a vHBA template. When you bind the vHBA to a vHBA template, Cisco UCS Manager configures the vHBA with the values defined in the vHBA template. If the existing vHBA configuration does not match the vHBA template, Cisco UCS Manager reconfigures the vHBA. You can only change the configuration of a bound vHBA through the associated vHBA template. You cannot bind a vHBA to a vHBA template if the service profile that includes the vHBA is already bound to a service profile template.
Important |
If the vHBA is reconfigured when you bind it to a template, Cisco UCS Manager reboots the server associated with the service profile. |
Step 1 |
In the Navigation pane, click Servers. |
Step 2 |
Expand . |
Step 3 |
Expand the node for the organization that includes the service profile with the vHBA you want to bind. If the system does not include multi-tenancy, expand the root node. |
Step 4 |
Expand . |
Step 5 |
Click the vHBA you want to bind to a template. |
Step 6 |
In the Work pane, click the General tab. |
Step 7 |
In the Actions area, click Bind to a Template. |
Step 8 |
In the Bind to a vHBA Template dialog box, do the following:
|
Step 9 |
In the warning dialog box, click Yes to acknowledge that Cisco UCS Manager may need to reboot the server if the binding causes the vHBA to be reconfigured. |
Step 1 |
In the Navigation pane, click Servers. |
Step 2 |
Expand . |
Step 3 |
Expand the node for the organization that includes the service profile with the vHBA you want to unbind. If the system does not include multi-tenancy, expand the root node. |
Step 4 |
Expand . |
Step 5 |
Click the vHBA you want to unbind from a template. |
Step 6 |
In the Work pane, click the General tab. |
Step 7 |
In the Actions area, click Unbind from a Template. |
Step 8 |
If a confirmation dialog box displays, click Yes. |
Step 1 |
In the Navigation pane, click SAN. |
Step 2 |
Expand . |
Step 3 |
Expand the vHBA Templates node. |
Step 4 |
Right-click the vHBA template that you want to delete and choose Delete. |
Step 5 |
If a confirmation dialog box displays, click Yes. |
Fibre Channel Adapter Policies
These policies govern the host-side behavior of the adapter, including how the adapter handles traffic. For example, you can use these policies to change default settings for the following:
Queues
Interrupt handling
Performance enhancement
RSS hash
Failover in a cluster configuration with two fabric interconnects
Note |
For Fibre Channel adapter policies, the values displayed by Cisco UCS Manager may not match those displayed by applications such as QLogic SANsurfer. For example, the following values may result in an apparent mismatch between SANsurfer and Cisco UCS Manager:
|
By default, Cisco UCS provides a set of Ethernet adapter policies and Fibre Channel adapter policies. These policies include the recommended settings for each supported server operating system. Operating systems are sensitive to the settings in these policies. Storage vendors typically require non-default adapter settings. You can find the details of these required settings on the support list provided by those vendors.
Important |
We recommend that you use the values in these policies for the applicable operating system. Do not modify any of the values in the default policies unless directed to do so by Cisco Technical Support. However, if you are creating an Ethernet adapter policy for an OS (instead of using the default adapter policy), you must use the following formulas to calculate values that work for that OS. |
Drivers on Linux operating systems use differing formulas to calculate the Interrupt Count, depending on the eNIC driver version. The UCS 3.2 release increased the number of Tx and Rx queues for the eNIC driver from 8 to 256 each.
Use one of the following strategies, according to your driver version.
For Linux drivers before the UCS 3.2 firmware release, use the following formula to calculate the Interrupt Count.
For example, if Transmit Queues = 1 and Receive Queues = 8 then:
On drivers for UCS firmware release 3.2 and higher, the Linux eNIC drivers use the following formula to calculate the Interrupt Count.
Interrupt Count = (#Tx or Rx Queues) + 2
Tip |
If the fields in an area do not display, click the Expand icon to the right of the heading. |
Step 1 |
In the Navigation pane, click Servers. |
||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 |
Expand . |
||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 |
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 4 |
Right-click Adapter Policies and choose Create Fibre Channel Adapter Policy. |
||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 |
Enter a name and description for the policy in the following fields:
|
||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 |
(Optional) In the Resources area, adjust the following values:
|
||||||||||||||||||||||||||||||||||||||||||||||||||
Step 7 |
(Optional) In the Options area, adjust the following values:
|
||||||||||||||||||||||||||||||||||||||||||||||||||
Step 8 |
Click OK. |
||||||||||||||||||||||||||||||||||||||||||||||||||
Step 9 |
If a confirmation dialog box displays, click Yes. |
Step 1 |
In the Navigation pane, click SAN. |
Step 2 |
Expand . |
Step 3 |
Expand the Fibre Channel Policies node. |
Step 4 |
Right-click the policy you want to delete and choose Delete. |
Step 5 |
If a confirmation dialog box displays, click Yes. |
About the 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—Cisco UCS Manager 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, Cisco UCS Manager 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. |
Step 1 |
In the Navigation pane, click SAN. |
Step 2 |
Expand . |
Step 3 |
Expand the root node. You can configure only the default vHBA behavior policy in the root organization. You cannot configure the default vHBA behavior policy in a sub-organization. |
Step 4 |
Click Default vHBA Behavior. |
Step 5 |
On the General Tab, in the Properties area, click one of the following radio buttons in the Action field:
|
Step 6 |
Click Save Changes. |
SAN Connectivity Policies
Connectivity policies determine the connections and the network communication resources between the server and the LAN or SAN on the network. These policies use pools to assign MAC addresses, WWNs, and WWPNs to servers and to identify the vNICs and vHBAs that the servers use to communicate with the network.
Note |
We do not recommend that you use static IDs in connectivity policies, because these policies are included in service profiles and service profile templates and can be used to configure multiple servers. |
Connectivity policies enable users without network or storage privileges to create and modify service profiles and service profile templates with network and storage connections. However, users must have the appropriate network and storage privileges to create connectivity policies.
Connectivity policies require the same privileges as other network and storage configurations. For example, you must have at least one of the following privileges to create connectivity policies:
admin—Can create LAN and SAN connectivity policies
ls-server—Can create LAN and SAN connectivity policies
ls-network—Can create LAN connectivity policies
ls-storage—Can create SAN connectivity policies
After the connectivity policies have been created, a user with ls-compute privileges can include them in a service profile or service profile template. However, a user with only ls-compute privileges cannot create connectivity policies.
You can configure the LAN and SAN connectivity for a service profile through either of the following methods:
LAN and SAN connectivity policies that are referenced in the service profile
Local vNICs and vHBAs that are created in the service profile
Local vNICs and a SAN connectivity policy
Local vHBAs and a LAN connectivity policy
Cisco UCS maintains mutual exclusivity between connectivity policies and local vNIC and vHBA configuration in the service profile. You cannot have a combination of connectivity policies and locally created vNICs or vHBAs. When you include a LAN connectivity policy in a service profile, all existing vNIC configuration is erased, and when you include a SAN connectivity policy, all existing vHBA configuration in that service profile is erased.
Step 1 |
In the Navigation pane, click SAN. |
Step 2 |
Expand . |
Step 3 |
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 4 |
Right-click SAN Connectivity Policies and choose Create SAN Connectivity Policy. |
Step 5 |
In the Create SAN Connectivity Policy dialog box, enter a name and optional description. |
Step 6 |
From the WWNN Assignment drop-down list in the World Wide Node Name area, choose one of the following:
|
Step 7 |
In the vHBAs table, click Add. |
Step 8 |
In the Create vHBAs dialog box, enter the name and optional description. |
Step 9 |
Choose the Fabric ID, Select VSAN, Pin Group, Persistent Binding, and Max Data Field Size. You can also create a VSAN or SAN pin group from this area. |
Step 10 |
In the Operational Parameters area, choose the Stats Threshold Policy. |
Step 11 |
In the Adapter Performance Profile area, choose the Adapter Policy and QoS Policy. You can also create a fibre channel adapter policy or QoS policy from this area. |
Step 12 |
After you have created all the vHBAs you need for the policy, click OK. |
Include the policy in a service profile or service profile template.
Step 1 |
In the Navigation pane, click SAN. |
Step 2 |
On the SAN tab, expand . |
Step 3 |
Choose the policy for which you want to create a vHBA. |
Step 4 |
In the Work pane, click the General tab. |
Step 5 |
In the table icon bar, click the + button. |
Step 6 |
In the Create vHBAs dialog box, enter the name and optional description. |
Step 7 |
Choose the Fabric ID, Select VSAN, Pin Group, Persistent Binding, and Max Data Field Size. You can also create a VSAN or SAN pin group from this area. |
Step 8 |
In the Operational Parameters area, choose the Stats Threshold Policy. |
Step 9 |
In the Adapter Performance Profile area, choose the Adapter Policy and QoS Policy. You can also create a fibre channel adapter policy or QoS policy from this area. |
Step 10 |
Click Save Changes. |
Step 1 |
In the Navigation pane, click SAN. |
Step 2 |
Expand . |
Step 3 |
Choose the policy from which you want to delete the vHBA. |
Step 4 |
In the Work pane, click the General tab. |
Step 5 |
In the vHBAs table, do the following:
|
Step 6 |
If a confirmation dialog box displays, click Yes. |
Step 1 |
In the Navigation pane, click SAN. |
||||||||||||
Step 2 |
Expand . |
||||||||||||
Step 3 |
Choose the policy for which you want to create an initiator group. |
||||||||||||
Step 4 |
In the Work pane, click the vHBA Initiator Groups tab. |
||||||||||||
Step 5 |
In the table icon bar, click the + button. |
||||||||||||
Step 6 |
In the Create vHBA Initiator Group dialog box, complete the following fields:
|
||||||||||||
Step 7 |
Click OK. |
Step 1 |
In the Navigation pane, click SAN. |
Step 2 |
Expand . |
Step 3 |
Choose the policy from which you want to delete the initiator group |
Step 4 |
In the Work pane, click the vHBA Initiator Groups tab. |
Step 5 |
In the table, do the following:
|
Step 6 |
If a confirmation dialog box displays, click Yes. |
If you delete a SAN connectivity policy that is included in a service profile, it also deletes all vHBAs from that service profile and disrupts SAN data traffic for the server associated with the service profile.
Step 1 |
In the Navigation pane, click SAN. |
Step 2 |
Expand . |
Step 3 |
Expand the SAN Connectivity Policies node. |
Step 4 |
Right-click the policy that you want to delete and choose Delete. |
Step 5 |
If a confirmation dialog box displays, click Yes. |