Feedback
Contents
Configuring Storage-Related Policies
This chapter includes the following sections:
- vHBA Template
- Creating a vHBA Template
- Deleting a vHBA Template
- Binding a vHBA to a vHBA Template
- Unbinding a vHBA from a vHBA Template
- Ethernet and Fibre Channel Adapter Policies
- Creating a Fibre Channel Adapter Policy
- Deleting a Fibre Channel Adapter Policy
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 need to include this policy in a service profile for it to take effect.
Creating a vHBA Template
Before You BeginProcedureThis policy requires that one or more of the following resources already exist in the system:
What to Do Next
Include the vHBA template in a service profile.
Binding a vHBA to a vHBA Template
ProcedureYou 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 the Servers tab. Step 2 On the Servers tab, 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.
Unbinding a vHBA from a vHBA Template
Procedure
Step 1 In the Navigation pane, click the Servers tab. Step 2 On the Servers tab, 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 Cisco UCS Manager displays a confirmation dialog box, click Yes.
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
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.
NoteFor 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:
Max LUNs Per Target—SANsurfer has a maximum of 256 LUNs and does not display more than that number. Cisco UCS Manager supports a higher maximum number of LUNs.
Link Down Timeout—In SANsurfer, you configure the timeout threshold for link down in seconds. In Cisco UCS Manager, you configure this value in milliseconds. Therefore, a value of 5500 ms in Cisco UCS Manager displays as 5s in SANsurfer.
Max Data Field Size—SANsurfer has allowed values of 512, 1024, and 2048. Cisco UCS Manager allows you to set values of any size. Therefore, a value of 900 in Cisco UCS Manager displays as 512 in SANsurfer.
Creating a Fibre Channel Adapter Policy
Procedure
Step 1 In the Navigation pane, click the SAN tab. Step 2 On the SAN tab, expand . Step 3 Expand the node for the organization where you want to create the policy. If the system does not include multi-tenancy, expand the root node.
Step 4 Right-click Fibre Channel Policies and choose Create Fibre Channel Adapter Policy. Step 5 Enter a name and description for the policy in the following fields:
Name Description Name field
The name of the policy.
This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters, and you cannot change this name after the object has been saved.
Description field
A description of the policy. We recommend including information about where and when the policy should be used.
Step 6 (Optional) In the Queues area, adjust the following values for the transmit, receive, and SCSI IO queues:
Name Description Count field
The number of SCSI IO queue resources the system should allocate.
Enter an integer between 1 and 8.
Note You can only have one transmit queue and one receive queue.
Ring size field
The number of descriptors in each queue.
For transmit and receive queues, enter an integer between 64 and 128. For completion queues, enter an integer between 64 and 512.
Step 7 (Optional) In the FLogi/PLogi area, adjust the following values:
Name Description Flogi Area
Retries field
The number of times that the system tries to log in to the fabric after the first failure.
Enter an integer between 0 and 255. To specify that the system continue to try indefinitely, enter -1 in this field.
Timeout field
The number of milliseconds that the system waits before it tries to log in again.
Enter an integer between 1000 and 255000.
Plogi Area
Retries field
The number of times that the system tries to log into a port after the first failure.
Enter an integer between 0 and 255.
Timeout field
The number of milliseconds that the system waits before it tries to log in again.
Enter an integer between 1000 and 255000.
Step 8 (Optional) In the Error Handling area, adjust the following values:
Name Description Error Detect Timeout field
The number of milliseconds to wait before the system assumes that there has been an error.
Enter an integer between 1,000 and 100,000. The default is 2,000.
Port Down Timeout field
The number of milliseconds a remote Fibre Channel port should be offline before informing the SCSI upper layer that the port is unavailable.
Enter an integer between 0 and 240,000. The default is 10,000.
Port Down IO Retry field
The number of times an IO request to a port is returned because the port is busy before the system decides the port is unavailable.
Enter an integer between 0 and 255. The default is 8.
Link Down Timeout field
The number of milliseconds the uplink port should be offline before it informs the system that the uplink port is down and fabric connectivity has been lost.
Enter an integer between 0 and 240,000. The default is 30,000.
Resource Allocation Timeout field
The number of milliseconds to wait before the system assumes that a resource cannot be properly allocated.
Enter an integer between 5,000 and 100,000. The default is 10,000.
FCP Error Recovery field
Whether the system uses FCP Sequence Level Error Recovery protocol (FC-TAPE). This can be:
Step 9 (Optional) In the FC Port Behavior area, adjust the following values:
Name Description IO Throttle Count field
The number of IO operations that can be pending in the vHBA at one time.
Enter an integer between 256 and 4,096. The default is 512.
Max LUNs Per Target field
The maximum number of LUNs that the driver supports. This is usually an operating system platform limitation.
Enter an integer between 1 and 1,024. The default is 256.
Max Data Field Size field
The maximum size of the Fibre Channel frame payload bytes that the vHBA supports.
Enter an integer between 256 and 2,112. The default is 2,112.
Step 10 Click OK.
