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.
This chapter includes the following sections:
Configuring Boot Policies
The boot policy determines the following:
Configuration of the boot device
Location from which the server boots
Order in which boot devices are invoked
For example, you can choose to have associated servers boot from a local device, such as a local disk or CD-ROM (VMedia), or you can select a SAN boot or a LAN (PXE) boot.
You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect. If you do not include a boot policy in a service profile, the server uses the default settings in the BIOS to determine the boot order.
Changes to a boot policy may be propagated to all servers created with an updating service profile template that includes that boot policy. Reassociation of the service profile with the server to rewrite the boot order information in the BIOS is auto-triggered.
When you create a boot policy, you can add one or more of the following to the boot policy and specify their boot order:
Boot type |
Description |
---|---|
SAN boot |
Boots from an operating system image on the SAN. You can specify a primary and a secondary SAN boot. If the primary boot fails, the server attempts to boot from the secondary. We recommend that you use a SAN boot, because it offers the most service profile mobility within the system. If you boot from the SAN, when you move a service profile from one server to another, the new server boots from the exact same operating system image. Therefore, the new server appears to be the exact same server to the network. |
LAN boot |
Boots from a centralized provisioning server. It is frequently used to install operating systems on a server from that server. |
Local disk boot |
If the server has a local drive, boots from that drive. |
Virtual media boot |
Mimics the insertion of a physical CD-ROM disk (read-only) or floppy disk (read-write) into a server. It is typically used to manually install operating systems on a server. |
Note |
You can also create a local boot policy that is restricted to a service profile or service profile template. However, we recommend that you create a global boot policy that can be included in multiple service profiles or service profile templates.
Include the boot policy in a service profile and/or template.
Configuring Chassis Discovery Policies
This discovery policy determines how the system reacts when you add a new chassis. If you create a chassis discovery policy, the system does the following:
Configuring IPMI Profiles
This policy allows you to determine whether IPMI commands can be sent directly to the server, using the IP address. For example, you can send commands to retrieve sensor data from the BMC. This policy defines the IPMI access, including a username and password that can be authenticated locally on the server, and whether the access is read-only or read-write.
You must include this policy in a service profile and that service profile must be associated with a server for it to take effect.
An IPMI profile requires that one or more of the following resources already exist in the system:
Username with appropriate permissions that can be authenticated by the operating system of the server
Password for the username
Permissions associated with the username
Include the IPMI profile in a service profile and/or template.
Configuring Local Disk Configuration Policies
This policy configures any optional SAS local drives that have been installed on a server through the onboard RAID controller of the local drive. This policy enables you to set a local disk mode for all servers that are associated with a service profile that includes the local disk configuration policy. The local disk modes include the following:
Any Configuration—For a server configuration that carries forward the local disk configuration without any changes.
No Local Storage—For a diskless workstation or a SAN only configuration. If you select this option, you cannot associate any service profile which uses this policy with a server that has a local disk.
No RAID—For a server configuration that removes the RAID and leaves the disk MBR and payload unaltered.
RAID Mirrored—For a 2-disk RAID 1 server configuration.
RAID Stripes—For a 2-disk RAID 0 server configuration.
You must include this policy in a service profile, and that service profile must be associated with a server for it to take effect.
This procedure describes how to change a local disk configuration policy from an associated service profile. You can also change a local disk configuration policy from the Policies node of the Servers tab.
Step 1 | In the Navigation pane, click the Servers tab. | ||||||||
Step 2 | On the Servers tab, expand . | ||||||||
Step 3 |
Expand the organization that includes the service service profile with the local disk configuration policy you want to change. If the system does not include multi-tenancy, expand the root node. |
||||||||
Step 4 | Click the service profile that contains the local disk configuration policy you want to change. | ||||||||
Step 5 | In the Work pane, click the Policies tab. | ||||||||
Step 6 | In the Actions area, click Change Local Disk Configuration Policy. | ||||||||
Step 7 |
In the Change Local Disk Configuration Policy dialog box, choose one of the following options from the Select the Local Disk Configuration Policy drop-down list.
|
||||||||
Step 8 | Click OK. | ||||||||
Step 9 | (Optional) Expand the Local Disk Configuration Policy area to confirm that the change has been made. |
Step 1 | In the Navigation pane, click the Servers tab. |
Step 2 | On the Servers tab, expand . |
Step 3 | Expand the Local Disk Config Policies node. |
Step 4 | Right-click the policy you want to delete and select Delete. |
Step 5 | If Cisco UCS Manager displays a confirmation dialog box, click Yes. |
Configuring Scrub Policies
This policy determines what happens to local data on a server during the discovery process and when the server is disassociated from a service profile. This policy can ensure that the data on local drives is erased at those times.
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 where you want to create the policy. If the system does not include multi-tenancy, expand the root node. |
||||||||||
Step 4 | Right-click Scrub Policies and select Create Scrub Policy. | ||||||||||
Step 5 |
In the Create Scrub Policy wizard, complete the following fields:
|
||||||||||
Step 6 | Click OK. |
Step 1 | In the Navigation pane, click the Servers tab. |
Step 2 | On the Servers tab, expand . |
Step 3 | Expand the Scrub Policies node. |
Step 4 | Right-click the policy you want to delete and select Delete. |
Step 5 | If Cisco UCS Manager displays a confirmation dialog box, click Yes. |
Configuring Serial over LAN Policies
This policy sets the configuration for the serial over LAN connection for all servers associated with service profiles that use the policy. By default, the serial over LAN connection is disabled.
If you implement a serial over LAN policy, we recommend that you also create an IPMI profile.
You must include this policy in a service profile and that service profile must be associated with a server for it to take effect.
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 where you want to create the policy. If the system does not include multi-tenancy, expand the root node. |
||||||||||
Step 4 | Right-click Serial over LAN Policies and select Create Serial over LAN Policy. | ||||||||||
Step 5 |
In the Create Serial over LAN Policy wizard, complete the following fields:
|
||||||||||
Step 6 | Click OK. |
Step 1 | In the Navigation pane, click the Servers tab. |
Step 2 | On the Servers tab, expand . |
Step 3 | Expand the Serial over LAN Policies node. |
Step 4 | Right-click the policy you want to delete and select Delete. |
Step 5 | If Cisco UCS Manager displays a confirmation dialog box, click Yes. |
Configuring Server Autoconfiguration Policies
This policy determines whether one or more of the following is automatically applied to a new server:
This policy requires that one or more of the following resources already exist in the system:
Server pool policy qualifications
Service profile template
Organizations, if a system implements multi-tenancy
Step 1 | In the Navigation pane, click the Equipment tab. | ||||||||||||
Step 2 | Click the Equipment node. | ||||||||||||
Step 3 | In the Work pane, click the Policies tab. | ||||||||||||
Step 4 | Click the Autoconfig Policies subtab. | ||||||||||||
Step 5 |
On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. |
||||||||||||
Step 6 |
In the Create Autoconfiguration Policy dialog box, complete the following fields:
|
||||||||||||
Step 7 | Click OK. |
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | Click the Equipment node. |
Step 3 | In the Work pane, click the Policies tab. |
Step 4 | Click the Autoconfig Policies subtab. |
Step 5 | Right-click the autoconfiguration policy that you want to delete and choose Delete. |
Step 6 | If Cisco UCS Manager displays a confirmation dialog box, click Yes. |
Configuring Server Discovery Policies
This discovery policy determines how the system reacts when you add a new server. If you create a server discovery policy, you can control whether the system conducts a deep discovery when a server is added to a chassis, or whether a user must first acknowledge the new server. By default, the system conducts a full discovery.
With this policy, an inventory of the server is conducted, then server pool policy qualifications are run to determine whether the new server qualifies for one or more server pools.
If you plan to associate this policy with a server pool, create server pool policy qualifications.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | Click the Equipment node. |
Step 3 | In the Work pane, click the Policies tab. |
Step 4 | Click the Server Discovery Policies subtab. |
Step 5 | Click the + icon on the table icon bar to open the Create Server Discovery Policy dialog box. |
Step 6 | In the Description field, enter a description for the discovery policy. |
Step 7 |
In the Action field, select one of the following options: |
Step 8 | (Optional) To associate this policy with a server pool, select server pool policy qualifications from the Qualification drop-down list. |
Step 9 | (Optional) To include a scrub policy, select a policy from the Scrub Policy drop-down list. |
Step 10 | Click OK. |
Include the server discovery policy in a service profile and/or template.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | Click the Equipment node. |
Step 3 | In the Work pane, click the Policies tab. |
Step 4 | Click the Server Discovery Policies subtab. |
Step 5 | Right-click the server discover policy that you want to delete and choose Delete. |
Step 6 | If Cisco UCS Manager displays a confirmation dialog box, click Yes. |
Configuring Server Inheritance Policies
This policy is invoked during the server discovery process to create a service profile for the server. All service profiles created from this policy use the values burned into the blade at manufacture. The policy performs the following:
Analyzes the inventory of the server
If configured, assigns the server to the selected organization
Creates a service profile for the server with the identity burned into the server at manufacture
You cannot migrate a service profile created with this policy to another server.
Step 1 | In the Navigation pane, click the Equipment tab. | ||||||||||
Step 2 | Click the Equipment node. | ||||||||||
Step 3 | In the Work pane, click the Policies tab. | ||||||||||
Step 4 | Click the Server Inheritance Policies subtab. | ||||||||||
Step 5 |
On the icon bar to the right of the table, click +. If the + icon is disabled, click an entry in the table to enable it. |
||||||||||
Step 6 |
In the Create Server Inheritance Policy dialog box, complete the following fields:
|
||||||||||
Step 7 | Click OK. |
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | Click the Equipment node. |
Step 3 | In the Work pane, click the Policies tab. |
Step 4 | Click the Server Inheritance Policies subtab. |
Step 5 | Right-click the server inheritance policy that you want to delete and choose Delete. |
Step 6 | If Cisco UCS Manager displays a confirmation dialog box, click Yes. |
Configuring Server Pool Policies
This policy is invoked during the server discovery process. It determines what happens if server pool policy qualifications match a server to the target pool specified in the policy.
If a server qualifies for more than one pool and those pools have server pool policies, the server is added to all those pools.
This policy requires that one or more of the following resources already exist in the system:
A minimum of one server pool
Server pool policy qualifications, if you choose to have servers automatically added to pools
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 where you want to create the policy. If the system does not include multi-tenancy, expand the root node. |
||||||||||
Step 4 | Right-click Server Pool Policies and select Create Server Pool Policy. | ||||||||||
Step 5 |
In the Create Server Pool Policy dialog box, complete the following fields:
|
||||||||||
Step 6 | Click OK. |
Step 1 | In the Navigation pane, click the Servers tab. |
Step 2 | On the Servers tab, expand . |
Step 3 | Expand the Server Pool Policies node. |
Step 4 | Right-click the policy you want to delete and select Delete. |
Step 5 | If Cisco UCS Manager displays a confirmation dialog box, click Yes. |
Configuring Server Pool Policy Qualifications
This policy qualifies servers based on the inventory of a server conducted during the discovery process. The qualifications are individual rules that you configure in the policy to determine whether a server meets the selection criteria. For example, you can create a rule that specifies the minimum memory capacity for servers in a data center pool.
Qualifications are used in other policies to place servers, not just by the server pool policies. For example, if a server meets the criteria in a qualification policy, it can be added to one or more server pools or have a service profile automatically associated with it.
Depending upon the implementation, you may include server pool policy qualifications in the following policies:
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 where you want to create the policy. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Right-click the Server Pool Policy Qualifications node and select Create Server Pool Policy Qualification. |
Step 5 | In the Create Server Pool Policy Qualification dialog box, enter a unique name and description for the policy. |
Step 6 |
(Optional) To use this policy to qualify servers according to their adapter configuration:
|
Step 7 |
(Optional) To use this policy to qualify servers according to their physical location:
|
Step 8 |
(Optional) To use this policy to qualify servers according to their memory configuration:
|
Step 9 |
(Optional) To use this policy to qualify servers according to their CPU/Cores configuration:
|
Step 10 |
(Optional) To use this policy to qualify servers according to their storage configuration and capacity:
|
Step 11 | Verify the qualifications in the table and correct if necessary. |
Step 12 | Click OK. |
Step 1 | In the Navigation pane, click the Servers tab. |
Step 2 | On the Servers tab, expand . |
Step 3 | Expand the Server Pool Policy Qualifications node. |
Step 4 | Right-click the policy qualifications you want to delete and select Delete. |
Step 5 | If Cisco UCS Manager displays a confirmation dialog box, click Yes. |
Use this procedure to modify Server Pool Policy Qualifications by deleting one or more sets of qualifications.
Step 1 | In the Navigation pane, click the Servers tab. |
Step 2 | On the Servers tab, expand . |
Step 3 | Expand the Server Pool Policy Qualifications node. |
Step 4 | Choose the policy you want to modify. |
Step 5 | In the Work pane, choose the Qualifications tab. |
Step 6 | To delete a set of qualifications: |
Step 7 | Click Save Changes. |