- Preface
-
- Configuring the Fabric Interconnects
- Configuring Ports and Port Channels
- Configuring Communication Services
- Configuring Authentication
- Configuring Organizations
- Configuring Role-Based Access Control
- Configuring DNS Servers
- Configuring System-Related Policies
- Managing Licenses
- Managing Virtual Interfaces
- Registering Cisco UCS Domains with Cisco UCS Central
- Index
Contents
- Configuring Storage-Related Policies
- Configuring vHBA Templates
- vHBA Template
- Configuring a vHBA Template
- Deleting a vHBA Template
- Configuring Fibre Channel Adapter Policies
- Ethernet and Fibre Channel Adapter Policies
- Configuring a Fibre Channel Adapter Policy
- Deleting a Fibre Channel Adapter Policy
- Configuring the Default vHBA Behavior Policy
- Default vHBA Behavior Policy
- Configuring a Default vHBA Behavior Policy
- Configuring SAN Connectivity Policies
- LAN and SAN Connectivity Policies
- Privileges Required for LAN and SAN Connectivity Policies
- Interactions between Service Profiles and Connectivity Policies
- Creating a SAN Connectivity Policy
- Creating a vHBA for a SAN Connectivity Policy
- Deleting a vHBA from a SAN Connectivity Policy
- Creating an Initiator Group for a SAN Connectivity Policy
- Deleting an Initiator Group from a SAN Connectivity Policy
- Deleting a SAN Connectivity Policy
Configuring Storage-Related Policies
This chapter includes the following sections:
- Configuring vHBA Templates
- Configuring Fibre Channel Adapter Policies
- Configuring the Default vHBA Behavior Policy
- Configuring SAN Connectivity Policies
Configuring vHBA Templates
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
The following example configures a vHBA template and commits the transaction:
UCS-A# scope org / UCS-A /org* # create vhba template VhbaTempFoo UCS-A /org/vhba-templ* # set descr "This is a vHBA template example." UCS-A /org/vhba-templ* # set fabric a UCS-A /org/vhba-templ* # set fc-if accounting UCS-A /org/vhba-templ* # set max-field-size 2112 UCS-A /org/vhba-templ* # set pin-group FcPinGroup12 UCS-A /org/vhba-templ* # set qos-policy policy34foo UCS-A /org/vhba-templ* # set stats-policy ServStatsPolicy UCS-A /org/vhba-templ* # set type updating-template UCS-A /org/vhba-templ* # set wwpn-pool SanPool7 UCS-A /org/vhba-templ* # commit-buffer UCS-A /org/vhba-templ #
Deleting a vHBA Template
The following example deletes the vHBA template named VhbaTempFoo and commits the transaction:
UCS-A# scope org / UCS-A /org # delete vhba template VhbaTempFoo UCS-A /org* # commit-buffer UCS-A /org #
Configuring Fibre Channel Adapter Policies
Ethernet and 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 an cluster configuration with two fabric interconnects
Operating System Specific Adapter Policies
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.
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 a Windows OS (instead of using the default Windows adapter policy), you must use the following formulas to calculate values that work with Windows:
- Completion Queues = Transmit Queues + Receive Queues
- Interrupt Count = (Completion Queues + 2) rounded up to nearest power of 2
For example, if Transmit Queues = 1 and Receive Queues = 8 then:
- Completion Queues = 1 + 8 = 9
- Interrupt Count = (9 + 2) rounded up to the nearest power of 2 = 16
Configuring a Fibre Channel Adapter Policy
The following example configures a Fibre Channel adapter policy and commits the transaction:
UCS-A# scope org / UCS-A /org* # create fc-policy FcPolicy42 UCS-A /org/fc-policy* # set descr "This is a Fibre Channel adapter policy example." UCS-A /org/fc-policy* # set error-recovery error-detect-timeout 2500 UCS-A /org/fc-policy* # set port max-luns 4 UCS-A /org/fc-policy* # set port-f-logi retries 250 UCS-A /org/fc-policy* # set port-p-logi timeout 5000 UCS-A /org/fc-policy* # set recv-queue count 1 UCS-A /org/fc-policy* # set scsi-io ring-size 256 UCS-A /org/fc-policy* # set trans-queue ring-size 256 UCS-A /org/fc-policy* # commit-buffer UCS-A /org/fc-policy #
Deleting a Fibre Channel Adapter Policy
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | UCS-A# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . |
| Step 2 | UCS-A /org # delete fc-policy policy-name |
Deletes the specified Fibre Channel adapter policy. |
| Step 3 | UCS-A /org # commit-buffer |
Commits the transaction to the system configuration. |
The following example deletes the Fibre Channel adapter policy named FcPolicy42 and commits the transaction:
UCS-A# scope org / UCS-A /org # delete fc-policy FcPolicy42 UCS-A /org* # commit-buffer UCS-A /org #
Configuring the Default vHBA Behavior Policy
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. |
Configuring a Default vHBA Behavior Policy
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | UCS-A# scope org / |
Enters the root organization mode. |
| Step 2 | UCS-A/org # scope vhba-beh-policy | Enters default vHBA behavior policy mode. |
| Step 3 | UCS-A/org/vhba-beh-policy # set action {hw-inherit [template_name name] | none} | Specifies the default vHBA behavior policy. This can be one of the following:
|
| Step 4 | UCS-A/org/vhba-beh-policy # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to set the default vHBA behavior policy to hw-inherit.
UCS-A # scope org / UCS-A/org # scope vhba-beh-policy UCS-A/org/vhba-beh-policy # set action hw-inherit UCS-A/org/vhba-beh-policy* # commit-buffer UCS-A/org/vhba-beh-policy #
Configuring SAN Connectivity Policies
LAN and 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. |
Privileges Required for LAN and SAN Connectivity Policies
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.
Privileges Required 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:
Privileges Required to Add Connectivity Policies to Service Profiles
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.
Interactions between Service Profiles and 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.
Creating a SAN Connectivity Policy
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | UCS-A# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
| Step 2 | UCS-A /org # create san-connectivity-policy policy-name |
Creates the specified SAN connectivity policy, and enters organization network control policy mode. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. |
| Step 3 | UCS-A /org/lan-connectivity-policy # set descr policy-name | (Optional)
Adds a description to the policy. We recommend that you include information about where and how the policy should be used. Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than), < (less than), or ' (single quote). |
| Step 4 | UCS-A /org/service-profile # set identity {dynamic-uuid {uuid | derived} | dynamic-wwnn {wwnn | derived} | uuid-pool pool-name | wwnn-pool pool-name} |
Specifies how the server acquires a UUID or WWNN. You can do one of the following:
|
| Step 5 | UCS-A /org/lan-connectivity-policy # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to create a SAN connectivity policy named SanConnect242 and commit the transaction:
UCS-A# scope org / UCS-A /org* # create san-connectivity-policy SanConnect242 UCS-A /org/san-connectivity-policy* # set descr "SAN connectivity policy" UCS-A /org/san-connectivity-policy* # set identity wwnn-pool SanPool7 UCS-A /org/san-connectivity-policy* # commit-buffer UCS-A /org/san-connectivity-policy #
Add one or more vHBAs and/or initiator groups to this SAN connectivity policy.
Creating a vHBA for a SAN Connectivity Policy
If you are continuing from Creating a SAN Connectivity Policy, begin this procedure at Step 3.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | UCS-A# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
| Step 2 | UCS-A /org # scope san-connectivity-policy policy-name |
Enters SAN connectivity policy mode for the specified SAN connectivity policy. |
| Step 3 | UCS-A /org/san-connectivity-policy # create vhba vhba-name [fabric {a | b}] [fc-if fc-if-name] |
Creates a vHBA for the specified SAN connectivity policy and enters vHBA mode. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. |
| Step 4 | UCS-A /org/san-connectivity-policy/vhba # set adapter-policy policy-name |
Specifies the adapter policy to use for the vHBA. |
| Step 5 | UCS-A /org/san-connectivity-policy/vhba # set identity {dynamic-wwpn {wwpn | derived} | wwpn-pool wwn-pool-name} |
Specifies the WWPN for the vHBA. You can set the storage identity using one of the following options:
|
| Step 6 | UCS-A /org/san-connectivity-policy/vhba # set max-field-size size-num |
Specifies the maximum size of the Fibre Channel frame payload (in bytes) that the vHBA supports. Enter an integer between 256 and 2112. The default is 2048. |
| Step 7 | UCS-A /org/san-connectivity-policy/vhba # set order {order-num | unspecified} |
Specifies the PCI scan order for the vHBA. |
| Step 8 | UCS-A /org/san-connectivity-policy/vhba # set pers-bind {disabled | enabled} |
Disables or enables persistent binding to Fibre Channel targets. |
| Step 9 | UCS-A /org/san-connectivity-policy/vhba # set pin-group group-name |
Specifies the SAN pin group to use for the vHBA. |
| Step 10 | UCS-A /org/san-connectivity-policy/vhba # set qos-policy policy-name |
Specifies the QoS policy to use for the vHBA. |
| Step 11 | UCS-A /org/san-connectivity-policy/vhba # set stats-policy policy-name |
Specifies the statistics threshold policy to use for the vHBA. |
| Step 12 | UCS-A /org/san-connectivity-policy/vhba # set template-name policy-name |
Specifies the vHBA template to use for the vHBA. If you choose to use a vHBA template for the vHBA, you must still complete all of the configuration not included in the vHBA template, including Steps 4, 7, and 8. |
| Step 13 | UCS-A /org/san-connectivity-policy/vhba # set vcon {1 | 2 | 3 | 4 | any} |
Assigns the vHBA to one or all virtual network interface connections. |
| Step 14 | UCS-A /org/san-connectivity-policy/vhba # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to configure a vHBA for a SAN connectivity policy named SanConnect242 and commit the transaction:
UCS-A# scope org / UCS-A /org* # scope san-connectivity-policy SanConnect242 UCS-A /org/san-connectivity-policy* # create vhba vhba3 fabric a UCS-A /org/san-connectivity-policy/vhba* # set adapter-policy AdaptPol2 UCS-A /org/san-connectivity-policy/vhba* # set identity wwpn-pool SanPool7 UCS-A /org/san-connectivity-policy/vhba* # set max-field-size 2112 UCS-A /org/san-connectivity-policy/vhba* # set order 0 UCS-A /org/san-connectivity-policy/vhba* # set pers-bind enabled UCS-A /org/san-connectivity-policy/vhba* # set pin-group FcPinGroup12 UCS-A /org/san-connectivity-policy/vhba* # set qos-policy QosPol5 UCS-A /org/san-connectivity-policy/vhba* # set stats-policy StatsPol2 UCS-A /org/san-connectivity-policy/vhba* # set template-name SanConnPol3 UCS-A /org/san-connectivity-policy/vhba* # set vcon any UCS-A /org/san-connectivity-policy/vhba* # commit-buffer UCS-A /org/san-connectivity-policy/vhba #
If desired, add another vHBA or an initiator group to the SAN connectivity policy. If not, include the policy in a service profile or service profile template.
Deleting a vHBA from a SAN Connectivity Policy
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | UCS-A# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
| Step 2 | UCS-A /org # scope san-connectivity-policy policy-name |
Enters SAN connectivity policy mode for the specified SAN connectivity policy. |
| Step 3 | UCS-A /org/san-connectivity-policy # delete vHBA vhba-name |
Deletes the specified vHBA from the SAN connectivity policy. |
| Step 4 | UCS-A /org/san-connectivity-policy # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to delete a vHBA named vHBA3 from a SAN connectivity policy named SanConnect242 and commit the transaction:
UCS-A# scope org / UCS-A /org # scope san-connectivity-policy SanConnect242 UCS-A /org/san-connectivity-policy # delete vHBA vHBA3 UCS-A /org/san-connectivity-policy* # commit-buffer UCS-A /org/san-connectivity-policy #
Creating an Initiator Group for a SAN Connectivity Policy
If you are continuing from Creating a SAN Connectivity Policy, begin this procedure at Step 3.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 | UCS-A# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. | ||
| Step 2 | UCS-A /org # scope san-connectivity-policy policy-name |
Enters SAN connectivity policy mode for the specified SAN connectivity policy. | ||
| Step 3 | UCS-A /org/san-connectivity-policy # create initiator-group group-name fc | Creates the specified initiator group for Fibre Channel zoning and enters initiator group mode. This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved. | ||
| Step 4 | UCS-A /org/san-connectivity-policy/initiator-group # create initiator vhba-name | Creates the specified vHBA initiator in the initiator group. If desired, repeat this step to add a second vHBA initiator to the group. | ||
| Step 5 | UCS-A /org/san-connectivity-policy/initiator-group # set storage-connection-policy policy-name | Associates the specified storage connection policy with the SAN connectivity policy.
| ||
| Step 6 | UCS-A /org/san-connectivity-policy/initiator-group/storage-connection-def # create storage-target wwpn | Creates a storage target endpoint with the specified WWPN, and enters storage target mode. | ||
| Step 7 | UCS-A /org/san-connectivity-policy/initiator-group/storage-connection-def/storage-target # set target-path {a | b} | Specifies which fabric interconnect is used for communications with the target endpoint. | ||
| Step 8 | UCS-A /org/san-connectivity-policy/initiator-group/storage-connection-def/storage-target # set target-vsan vsan |
Specifies which VSAN is used for communications with the target endpoint. | ||
| Step 9 | UCS-A /org/san-connectivity-policy/initiator-group # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to configure an initiator group named initGroupZone1 with two initiators for a a SAN connectivity policy named SanConnect242, configure a local storage connection policy definition named scPolicyZone1, and commit the transaction:
UCS-A# scope org / UCS-A /org* # scope san-connectivity-policy SanConnect242 UCS-A /org/san-connectivity-policy # create initiator-group initGroupZone1 fc UCS-A /org/san-connectivity-policy/initiator-group* # set zoning-type sist UCS-A /org/san-connectivity-policy/initiator-group* # create initiator vhba1 UCS-A /org/san-connectivity-policy/initiator-group* # create initiator vhba2 UCS-A /org/san-connectivity-policy/initiator-group* # create storage-connection-def scPolicyZone1 UCS-A /org/san-connectivity-policy/initiator-group/storage-connection-def* # create storage-target 20:10:20:30:40:50:60:70 UCS-A /org/san-connectivity-policy/initiator-group/storage-connection-def/storage-target* # set target-path a UCS-A /org/san-connectivity-policy/initiator-group/storage-connection-def/storage-target* # set target-vsan default UCS-A /org/san-connectivity-policy/initiator-group* # commit-buffer UCS-A /org/san-connectivity-policy/initiator-group #
If desired, add another initiator group or a vHBA to the SAN connectivity policy. If not, include the policy in a service profile or service profile template.
Deleting an Initiator Group from a SAN Connectivity Policy
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | UCS-A# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
| Step 2 | UCS-A /org # scope san-connectivity-policy policy-name |
Enters SAN connectivity policy mode for the specified SAN connectivity policy. |
| Step 3 | UCS-A /org/san-connectivity-policy # delete initiator-group group-name |
Deletes the specified initiator group from the SAN connectivity policy. |
| Step 4 | UCS-A /org/san-connectivity-policy # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to delete an initiator group named initGroup3 from a SAN connectivity policy named SanConnect242 and commit the transaction:
UCS-A# scope org / UCS-A /org # scope san-connectivity-policy SanConnect242 UCS-A /org/san-connectivity-policy # delete initiator-group initGroup3 UCS-A /org/san-connectivity-policy* # commit-buffer UCS-A /org/san-connectivity-policy #
Deleting a SAN Connectivity Policy
If you delete a SAN connectivity policy that is included in a service profile, you will delete all vHBAs from that service profile and disrupt SAN data traffic for the server associated with the service profile.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | UCS-A# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
| Step 2 | UCS-A /org # delete san-connectivity-policy policy-name |
Deletes the specified SAN connectivity policy. |
| Step 3 | UCS-A /org # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to delete a SAN connectivity policy named SanConnect52 from the root organization and commit the transaction:
UCS-A# scope org / UCS-A /org # delete san-connectivity-policy SanConnect52 UCS-A /org* # commit-buffer UCS-A /org #