Feedback
Contents
- Configuring Server-Related Policies
- Server Autoconfiguration Policy
- Configuring a Server Autoconfiguration Policy
- Deleting a Server Autoconfiguration Policy
- Boot Policy
- Configuring a Boot Policy
- Configuring a LAN Boot for a Boot Policy
- Configuring a Storage Boot for a Boot Policy
- Configuring a Virtual Media Boot for a Boot Policy
- Deleting a Boot Policy
- Chassis Discovery Policy
- Configuring a Chassis Discovery Policy
- IPMI Access Profile
- Configuring an IPMI Access Profile
- Deleting an IPMI Access Profile
- Adding an Endpoint User to an IPMI Access Profile
- Deleting an Endpoint User from an IPMI Access Profile
- Local Disk Configuration Policy
- Configuring a Local Disk Configuration Policy
- Deleting a Local Disk Configuration Policy
- Scrub Policy
- Configuring a Scrub Policy
- Deleting a Scrub Policy
- Server Discovery Policy
- Configuring a Server Discovery Policy
- Deleting a Server Discovery Policy
- Server Pool Policy
- Configuring a Server Pool Policy
- Deleting a Server Pool Policy
- Server Pool Policy Qualifications
- Creating a Server Pool Policy Qualification
- Deleting a Server Pool Policy Qualification
- Configuring an Adapter Qualification
- Deleting an Adapter Qualification
- Configuring a Chassis Qualification
- Deleting a Chassis Qualification
- Configuring a Memory Qualification
- Deleting a Memory Qualification
- Configuring a Processor Qualification
- Deleting a Processor Qualification
- Configuring a Storage Qualification
- Deleting a Storage Qualification
- Server Inheritance Policy
- Configuring a Server Inheritance Policy
- Deleting a Server Inheritance Policy
- Serial over LAN Policy
- Configuring a SOL Policy
- Deleting a SOL Policy
Configuring Server-Related Policies
This chapter includes the following sections:
- Local Disk Configuration Policy
- Configuring a Local Disk Configuration Policy
- Deleting a Local Disk Configuration Policy
- Scrub Policy
- Configuring a Scrub Policy
- Deleting a Scrub Policy
- Server Autoconfiguration Policy
- Configuring a Server Autoconfiguration Policy
- Deleting a Server Autoconfiguration Policy
- Boot Policy
- Configuring a Boot Policy
- Deleting a Boot Policy
- Chassis Discovery Policy
- Configuring a Chassis Discovery Policy
- IPMI Access Profile
- Configuring an IPMI Access Profile
- Deleting an IPMI Access Profile
- Adding an Endpoint User to an IPMI Access Profile
- Deleting an Endpoint User from an IPMI Access Profile
- Server Discovery Policy
- Configuring a Server Discovery Policy
- Deleting a Server Discovery Policy
- Server Pool Policy
- Configuring a Server Pool Policy
- Deleting a Server Pool Policy
- Server Pool Policy Qualifications
- Creating a Server Pool Policy Qualification
- Deleting a Server Pool Policy Qualification
- Configuring an Adapter Qualification
- Deleting an Adapter Qualification
- Configuring a Chassis Qualification
- Deleting a Chassis Qualification
- Configuring a Memory Qualification
- Deleting a Memory Qualification
- Configuring a Processor Qualification
- Deleting a Processor Qualification
- Configuring a Storage Qualification
- Deleting a Storage Qualification
- Server Inheritance Policy
- Configuring a Server Inheritance Policy
- Deleting a Server Inheritance Policy
- Serial over LAN Policy
- Configuring a SOL Policy
- Deleting a SOL Policy
Server Autoconfiguration Policy Configuration
Server Autoconfiguration Policy
Configuring a Server Autoconfiguration Policy
ProcedureThe following example creates a server autoconfiguration policy named AutoConfigFinance, provides a description for the policy, specifies finance as the destination organization, ServPoolQual22 as the server pool policy qualification, and ServTemp2 as the service profile template, and commits the transaction:
UCS-A# scope org / UCS-A /org* # create server-autoconfig-policy AutoConfigFinance UCS-A /org/server-autoconfig-policy* # set descr "Server Autoconfiguration Policy for Finance" UCS-A /org/server-autoconfig-policy* # set destination org finance UCS-A /org/server-autoconfig-policy* # set qualifier ServPoolQual22 UCS-A /org/server-autoconfig-policy* # set template ServTemp2 UCS-A /org/server-autoconfig-policy* # commit-buffer UCS-A /org/server-autoconfig-policy #Deleting a Server Autoconfiguration Policy
Procedure
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 server-autoconfig-policy policy-name Deletes the specified server autoconfiguration policy.
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.
Boot Policy Configuration
Boot Policy
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.
Important: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.
Guidelines
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
Configuring a Boot Policy
Procedure
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 # create boot-policy policy-name [purpose {operational | utility}] Creates a boot policy with the specified policy name, and enters organization boot policy mode.
When you create the boot policy, specify the operational option. This ensures that the server boots from the operating system installed on the server. The utility options is reserved and should only be used if instructed to do so by a Cisco representative.
Step 3 UCS-A /org/boot-policy # set descr description (Optional) Provides a description for the boot policy.
Note If your description includes spaces, special characters, or punctuation, you must begin and end your description with quotation marks. The quotation marks do not appear in the description field of any show command output.
Step 4 UCS-A /org/boot-policy # set reboot-on-update {no | yes} Specifies whether the servers using this boot policy are automatically rebooted after you make changes to the boot order.
Step 5 UCS-A /org/boot-policy # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example creates a boot policy named boot-policy-LAN, provides a description for the boot policy, specifies that servers using this policy will not be automatically rebooted when the boot order is changed, and commits the transaction:
UCS-A# scope org / UCS-A /org* # create boot-policy boot-policy-LAN purpose operational UCS-A /org/boot-policy* # set descr "Boot policy that boots from the LAN." UCS-A /org/boot-policy* # set reboot-on-update no UCS-A /org/boot-policy* # commit-buffer UCS-A /org/boot-policy #
Configure one or more of the following boot options for the boot policy and set their boot order:
LAN Boot—Boots from a centralized provisioning server. It is frequently used to install operating systems on a server from that server.
If you choose the LAN Boot option, continue to "Configuring a LAN Boot for a Boot Policy."
Storage 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.
Cisco recommends 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 will boot from the exact same operating system image. Therefore, the new server will appear to be the exact same server to the network.
If you choose the Storage Boot option, continue to "Configuring a Storage Boot for a Boot Policy."
Virtual Media Boot—Mimics the insertion of a physical CD into a server. It is typically used to manually install operating systems on a server.
If you choose the Virtual Media boot option, continue to "Configuring a Virtual Media Boot for a Boot Policy."
Include the boot policy in a service profile and/or template.
- Configuring a LAN Boot for a Boot Policy
- Configuring a Storage Boot for a Boot Policy
- Configuring a Virtual Media Boot for a Boot Policy
Configuring a LAN Boot for a Boot Policy
Procedure
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 # scope boot-policy policy-name Enters organization boot policy mode for the specified boot policy.
Step 3 UCS-A /org/boot-policy # create lan Creates a LAN boot for the boot policy and enters organization boot policy LAN mode.
Step 4 UCS-A /org/boot-policy/lan # set order {1 | 2 | 3 | 4} Specifies the boot order for the LAN boot.
Step 5 UCS-A /org/boot-policy/lan # create path {primary | secondary} Creates a primary or secondary LAN boot path and enters organization boot policy LAN path mode.
Step 6 UCS-A /org/boot-policy/lan/path # set vnic vnic-name Specifies the vNIC to use for the LAN path to the boot image.
Step 7 UCS-A /org/boot-policy/lan/path # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example creates a boot policy named boot-policy-LAN, creates a LAN boot for the policy, sets the boot order to 2, creates primary and secondary paths using the vNICs named vNIC1 and vNIC2 , and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope boot-policy boot-policy-LAN UCS-A /org/boot-policy* # create lan UCS-A /org/boot-policy/lan* # set order 2 UCS-A /org/boot-policy/lan* # create path primary UCS-A /org/boot-policy/lan/path* # set vnic vNIC1 UCS-A /org/boot-policy/lan/path* # exit UCS-A /org/boot-policy/lan* # create path secondary UCS-A /org/boot-policy/lan/path* # set vnic vNIC2 UCS-A /org/boot-policy/lan/path* # commit-buffer UCS-A /org/boot-policy/lan/path #
Include the boot policy in a service profile and/or template.
Configuring a Storage Boot for a Boot Policy
Procedure
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 # scope boot-policy policy-name Enters organization boot policy mode for the specified boot policy.
Step 3 UCS-A /org/boot-policy # create storage Creates a storage boot for the boot policy and enters organization boot policy storage mode.
Step 4 UCS-A /org/boot-policy/storage # set order {1 | 2 | 3 | 4} Sets the boot order for the storage boot.
Step 5 UCS-A /org/boot-policy/storage # create {local | san-image {primary | secondary} Creates a local or SAN image storage location, and if the san-image option is specified, enters organization boot policy storage SAN image mode.
Step 6 UCS-A /org/boot-policy/storage/san-image # set vhba vhba-name Specifies the vHBA to be used for the storage boot.
Step 7 UCS-A /org/boot-policy/storage/san-image # create path {primary | secondary} Creates a primary or secondary storage boot path and enters organization boot policy LAN path mode.
Step 8 UCS-A /org/boot-policy/storage/san-image/path # set {lun lun-id | wwn wwn-num} Specifies the LUN or WWN to be used for the storage path to the boot image.
Step 9 UCS-A /org/boot-policy/storage/san-image/path # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example creates a boot policy named boot-policy-storage, creates a storage boot for the policy, sets the boot order to 1, creates a primary SAN image, uses a vHBA named vHBA2, creates primary path using LUN 967295200, and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope boot-policy boot-policy-storage UCS-A /org/boot-policy* # create storage UCS-A /org/boot-policy/storage* # set order 1 UCS-A /org/boot-policy/storage* # create san-image primary UCS-A /org/boot-policy/storage* # set vhba vHBA2 UCS-A /org/boot-policy/storage/san-image* # create path primary UCS-A /org/boot-policy/storage/san-image/path* # set lun 967295200 UCS-A /org/boot-policy/storage/san-image/path* # commit-buffer UCS-A /org/boot-policy/storage/san-image/path #
Include the boot policy in a service profile and/or template.
Configuring a Virtual Media Boot for a Boot Policy
Procedure
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 # scope boot-policy policy-name Enters organization boot policy mode for the specified boot policy.
Step 3 UCS-A /org/boot-policy # create virtual-media {read-only | read-write} Creates a virtual media boot for the boot policy, specifies whether the virtual media is has read-only or read-write privileges, and enters organization boot policy virtual media mode.
Step 4 UCS-A /org/boot-policy/virtual-media # set order {1 | 2 | 3 | 4} Sets the boot order for the virtual-media boot.
Step 5 UCS-A /org/boot-policy/virtual-media # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example
UCS-A# scope org / UCS-A /org* # scope boot-policy boot-policy-vm UCS-A /org/boot-policy* # create virtual-media read-only UCS-A /org/boot-policy/virtual-media* # set order 3 UCS-A /org/boot-policy/virtual-media* # commit-buffer
Include the boot policy in a service profile and/or template.
Deleting a Boot Policy
Procedure
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 boot-policy policy-name Deletes the specified boot policy.
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.
Chassis Discover Configuration
Chassis Discovery Policy
Configuring a Chassis Discovery Policy
Procedure
Command or Action Purpose Step 1 UCS-A# scope org / Enters the root organization mode.
Note The chassis discovery policy can only be accessed from the root organization.
Step 2 UCS-A /org # scope chassis-disc-policy Enters organization chassis discovery policy mode.
Step 3 UCS-A /org/chassis-disc-policy # set action {1-link | 2-link | 4-link} Specifies the number of links to the fabric interconnect that the chassis must have before it can be discovered.
Step 4 UCS-A /org/chassis-disc-policy # set descr description (Optional) Provides a description for the chassis discovery policy.
Note If your description includes spaces, special characters, or punctuation, you must begin and end your description with quotation marks. The quotation marks will not appear in the description field of any show command output.
Step 5 UCS-A /org/chassis-disc-policy # set qualifier qualifier (Optional) Uses the specified server pool policy qualifications to associates this policy with a server pool.
Step 6 UCS-A /org/chassis-disc-policy # commit-buffer Commits the transaction to the system configuration.
The following example scopes to the default chassis discovery policy, sets it to discover chassis with four links to a fabric interconnect, provides a description for the policy, and specifies the server pool policy qualifications that will be used to qualify the chassis, and commits the transaction:
UCS-A# scope org / UCS-A /org # scope chassis-disc-policy UCS-A /org/chassis-disc-policy* # set action 4-link UCS-A /org/chassis-disc-policy* # set descr "This is an example chassis discovery policy." UCS-A /org/chassis-disc-policy* # set qualifier ExampleQual UCS-A /org/chassis-disc-policy* # commit-buffer UCS-A /org/chassis-disc-policy #IPMI Access Profile Configuration
IPMI Access Profile
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.
Configuring an IPMI Access Profile
Before You BeginProcedure
Username with appropriate permissions that can be authenticated by the operating system of the server
Password for the username
Permissions associated with the username
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 # create ipmi-access-profile profile-name Creates the specified IPMI access profile and enters organization IPMI access profile mode.
Step 3 UCS-A /org/ipmi-access-profile # create epuser epuser-name Creates the specified endpoint user and enters organization IPMI access profile endpoint user mode.
Note More than one endpoint user can be created within an IPMI access profile, with each endpoint user having its own password and privileges.
Step 4 UCS-A /org/ipmi-access-profile/epuser # set password Sets the password for the endpoint user.
After entering the set password command, you are prompted to enter and confirm the password. For security purposes, the password that you type does not appear in the CLI.
Step 5 UCS-A /org/ipmi-access-profile/epuser # set privilege {admin | readonly} Specifies whether the endpoint user has administrative or read-only privileges.
Step 6 UCS-A /org/ipmi-access-profile/epuser # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example creates an IPMI access profile named ReadOnly, creates an endpoint user named bob, sets the password and the privileges for bob, and commits the transaction:
UCS-A# scope org / UCS-A /org* # create ipmi-access-profile ReadOnly UCS-A /org/ipmi-access-profile* # create epuser bob UCS-A /org/ipmi-access-profile/epuser* # set password Enter a password: Confirm the password: UCS-A /org/ipmi-access-profile/epuser* # set privilege readonly UCS-A /org/ipmi-access-profile/epuser* # commit-buffer UCS-A /org/ipmi-access-profile/epuser #
Include the IPMI profile in a service profile and/or template.
Deleting an IPMI Access Profile
Procedure
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 ipmi-access-profile profile-name Deletes the specified IPMI access profile.
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.
Adding an Endpoint User to an IPMI Access Profile
Procedure
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 # scope ipmi-access-profile profile-name Enters organization IPMI access profile mode for the specified IPMI access profile.
Step 3 UCS-A /org/ipmi-access-profile # create epuser epuser-name Creates the specified endpoint user and enters organization IPMI access profile endpoint user mode.
Note More than one endpoint user can be created within an IPMI access profile, with each endpoint user having its own password and privileges.
Step 4 UCS-A /org/ipmi-access-profile/epuser # set password Sets the password for the endpoint user.
After entering the set password command, you are prompted to enter and confirm the password. For security purposes, the password that you type does not appear in the CLI.
Step 5 UCS-A /org/ipmi-access-profile/epuser # set privilege {admin | readonly} Specifies whether the endpoint user has administrative or read-only privileges.
Step 6 UCS-A /org/ipmi-access-profile/epuser # commit-buffer Commits the transaction to the system configuration.
The following example adds an endpoint user named alice to the IPMI access profile named ReadOnly and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope ipmi-access-profile ReadOnly UCS-A /org/ipmi-access-profile* # create epuser alice UCS-A /org/ipmi-access-profile/epuser* # set password Enter a password: Confirm the password: UCS-A /org/ipmi-access-profile/epuser* # set privilege readonly UCS-A /org/ipmi-access-profile/epuser* # commit-buffer UCS-A /org/ipmi-access-profile/epuser #Deleting an Endpoint User from an IPMI Access Profile
Procedure
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 # scope ipmi-access-profile profile-name Enters organization IPMI access profile mode for the specified IPMI access profile.
Step 3 UCS-A /org/ipmi-access-profile # delete epuser epuser-name Deletes the specified endpoint user from the IPMI access profile.
Step 4 UCS-A /org/ipmi-access-profile # commit-buffer Commits the transaction to the system configuration.
The following example deletes the endpoint user named alice from the IPMI access profile named ReadOnly and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope ipmi-access-profile ReadOnly UCS-A /org/ipmi-access-profile* # delete epuser alice UCS-A /org/ipmi-access-profile* # commit-buffer UCS-A /org/ipmi-access-profile #Local Disk Configuration Policy Configuration
Local Disk Configuration Policy
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.
Configuring a Local Disk Configuration Policy
Procedure
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 # create local-disk-config-policy policy-name Creates a local disk configuration policy and enters local disk configuration policy mode.
Step 3 UCS-A /org/local-disk-config-policy # set descr description (Optional) Provides a description for the local disk configuration policy.
Step 4 UCS-A /org/local-disk-config-policy # set mode {any-configuration | no-local-storage | no-raid | raid-mirrored | raid-striped} Specifies the mode for the local disk configuration policy.
Step 5 UCS-A /org/local-disk-config-policy # commit-buffer Commits the transaction to the system configuration.
Deleting a Local Disk Configuration Policy
Procedure
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 local-disk-config-policy policy-name Deletes the specified local disk configuration policy.
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.
Scrub Policy Configuration
Scrub Policy
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.
Configuring a Scrub Policy
Procedure
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 # create scrub-policy policy-name Creates a scrub policy with the specified policy name, and enters organization scrub policy mode.
Step 3 UCS-A /org/scrub-policy # set descr description (Optional) Provides a description for the scrub policy.
Note If your description includes spaces, special characters, or punctuation, you must begin and end your description with quotation marks. The quotation marks will not appear in the description field of any show command output.
Step 4 UCS-A /org/scrub-policy # set disk-scrub {no | yes} Disables or enables disk scrubbing on servers using this scrub policy.
Step 5 UCS-A /org/scrub-policy # commit-buffer Commits the transaction to the system configuration.
The following example creates a scrub policy named ScrubPolicy2, enables disk scrubbing on servers using the scrub policy, and commits the transaction:
UCS-A# scope org / UCS-A /org* # create scrub-policy ScrubPolicy2 UCS-A /org/scrub-policy* # set descr "Scrub policy set to yes." UCS-A /org/scrub-policy* # set disk-scrub yes UCS-A /org/scrub-policy* # commit-buffer UCS-A /org/scrub-policy #Deleting a Scrub Policy
Procedure
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 scrub-policy policy-name Deletes the specified scrub policy.
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.
Server Discovery Configuration
Server Discovery Policy
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.
Configuring a Server Discovery Policy
Before You BeginProcedureIf you plan to associate this policy with a server pool, create server pool policy qualifications.
Command or Action Purpose Step 1 UCS-A# scope org / Enters the root organization mode.
Note Chassis discovery policies can only be accessed from the root organization.
Step 2 UCS-A /org # create server-disc-policy policy-name Creates a server discovery policy with the specified policy name, and enters org server discovery policy mode.
Step 3 UCS-A /org/server-disc-policy # set action {diag | immediate | user-acknowledged} Specifies when the system will attempt to discover new servers.
Step 4 UCS-A /org/chassis-disc-policy # set descr description (Optional) Provides a description for the server discovery policy.
Note If your description includes spaces, special characters, or punctuation, you must begin and end your description with quotation marks. The quotation marks will not appear in the description field of any show command output.
Step 5 UCS-A /org/server-disc-policy # set qualifier qualifier (Optional) Uses the specified server pool policy qualifications to associates this policy with a server pool.
Step 6 UCS-A /org/server-disc-policy # set scrub-policy Specifies the scrub policy to be used by this policy. The scrub policy defines whether the disk drive on a server should be scrubbed clean upon discovery.
Step 7 UCS-A /org/server-disc-policy # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example creates a server discovery policy named ServDiscPolExample, sets it to immediately discover new servers, provides a description for the policy, specifies the server pool policy qualifications and scrub policy, and commits the transaction:
UCS-A# scope org / UCS-A /org* # create server-disc-policy ServDiscPolExample UCS-A /org/server-disc-policy* # set action immediate UCS-A /org/server-disc-policy* # set descr "This is an example server discovery policy." UCS-A /org/server-disc-policy* # set qualifier ExampleQual UCS-A /org/server-disc-policy* # set scrub-policy NoScrub UCS-A /org/server-disc-policy # commit-buffer
Include the server discovery policy in a service profile and/or template.
Deleting a Server Discovery Policy
Procedure
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 server-disc-policy policy-name Deletes the specified server discovery policy.
Step 3 UCS-A /org/server-disc-policy # commit-buffer Commits the transaction to the system configuration.
Server Pool Policy Configuration
Server Pool Policy
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.
Configuring a Server Pool Policy
Procedure
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 # create pooling-policy policy-name Creates a server pool policy with the specified name, and enters organization pooling policy mode.
Step 3 UCS-A /org/pooling-policy # set descr description (Optional) Provides a description for the server pool policy.
Note If your description includes spaces, special characters, or punctuation, you must begin and end your description with quotation marks. The quotation marks will not appear in the description field of any show command output.
Step 4 UCS-A /org/pooling-policy # set pool pool-distinguished-name Specifies the server pool to use with the server pool policy. You must specify the full distinguished name for the pool.
Step 5 UCS-A /org/pooling-policy # set qualifier qualifier-name Specifies the server pool qualifier to use with the server pool policy.
Step 6 UCS-A /org/pooling-policy # commit-buffer Commits the transaction to the system configuration.
The following example creates a server pool policy named PoolPolicy4 and commits the transaction:
UCS-A# scope org / UCS-A /org* # create pooling-policy ServerPoolPolicy4 UCS-A /org/pooling-policy* # set pool org-root/compute-pool-pool3 UCS-A /org/pooling-policy* # set qualifier ServPoolQual8 UCS-A /org/pooling-policy* # commit-buffer UCS-A /org/pooling-policy #Deleting a Server Pool Policy
Procedure
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 pooling-policy policy-name Deletes the specified server pool policy.
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.
Server Pool Policy Qualification Configuration
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:
Creating a Server Pool Policy Qualification
Procedure
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 # create server-qual server-qual-name Creates a server pool qualification with the specified name, and enters organization server qualification mode.
Step 3 UCS-A /org/server-qual # commit-buffer Commits the transaction to the system configuration.
What to Do NextThe following example creates a server pool qualification named ServPoolQual22 and commits the transaction:
UCS-A# scope org / UCS-A /org* # create server-qual ServPoolQual22 UCS-A /org/server-qual* # commit-buffer UCS-A /org/server-qual #
Configure one or more of the following server component qualifications:
Deleting a Server Pool Policy Qualification
Procedure
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 server-qual server-qual-name Deletes the specified server pool qualification.
Step 3 UCS-A /org/server-qual # commit-buffer Commits the transaction to the system configuration.
Configuring an Adapter Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # create adapter Creates an adapter qualification and enters organization server qualification adapter mode.
Step 4 UCS-A /org/server-qual/adapter # create cap-qual adapter-type Creates an adapter capacity qualification for the specified adapter type and enters organization server qualification adapter capacity qualification mode. The adapter-type argument can be any of the following values:
fcoe—Fibre Channel over Ethernet
non-virtualized-eth-if—Non-virtualized Ethernet interface
non-virtualized-fc-if—Non-virtualized Fibre Channel interface
path-encap-consolidated—Path encapsulation consolidated
path-encap-virtual—Path encapsulation virtual
protected-eth-if—Protected Ethernet interface
protected-fc-if—Protected Fibre Channel interface
protected-fcoe—Protected Fibre Channel over Ethernet
virtualized-eth-if—Virtualized Ethernet interface
virtualized-fc-if—Virtualized Fibre Channel interface
virtualized-scsi-if—Virtualized SCSI interface
Step 5 UCS-A /org/server-qual/adapter/cap-qual # set maximum {max-cap | unspecified} Specifies the maximum capacity for the selected adapter type.
Step 6 UCS-A /org/server-qual/adapter/cap-qual # commit-buffer Commits the transaction to the system configuration.
The following example configures an adapter qualification for a non-virtualized Ethernet interface and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope server-qual ServPoolQual22 UCS-A /org/server-qual* # create adapter UCS-A /org/server-qual/adapter* # create cap-qual non-virtualized-eth-if UCS-A /org/server-qual/adapter/cap-qual* # set maximum 2500000000 UCS-A /org/server-qual/adapter/cap-qual* # commit-buffer UCS-A /org/server-qual/adapter/cap-qual #Deleting an Adapter Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # delete adapter Deletes the adapter qualification from the server pool policy qualification.
Step 4 UCS-A /org/server-qual # commit-buffer Commits the transaction to the system configuration.
The following example deletes the adapter qualification from the server pool policy qualification named ServPoolQual22 and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope server-qual ServPoolQual22 UCS-A /org/server-qual* # delete adapter UCS-A /org/server-qual* # commit-buffer UCS-A /org/server-qual #Configuring a Chassis Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # create chassis min-chassis-num max-chassis-num Creates a chassis qualification for the specified chassis range and enters organization server qualification chassis mode.
Step 4 UCS-A /org/server-qual/chassis # create slot min-slot-num max-slot-num Creates a chassis slot qualification for the specified slot range and enters organization server qualification chassis slot mode.
Step 5 UCS-A /org/server-qual/chassis/slot # commit-buffer Commits the transaction to the system configuration.
The following example configures a chassis qualification for slots 1 to 4 on chassis 1 and 2, and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope server-qual ServPoolQual22 UCS-A /org/server-qual* # create chassis 1 2 UCS-A /org/server-qual/chassis* # create slot 1 4 UCS-A /org/server-qual/chassis/slot* # commit-buffer UCS-A /org/server-qual/chassis/slot #Deleting a Chassis Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # delete chassis min-chassis-num max-chassis-num Deletes the chassis qualification for the specified chassis range.
Step 4 UCS-A /org/server-qual # commit-buffer Commits the transaction to the system configuration.
Configuring a Memory Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # create memory Creates a memory qualification and enters organization server qualification memory mode.
Step 4 UCS-A /org/server-qual/memory # set clock {clock-num | unspec} Specifies the memory clock speed.
Step 5 UCS-A /org/server-qual/memory # set maxcap {max-cap-num | unspec} Specifies the maximum capacity of the memory array.
Step 6 UCS-A /org/server-qual/memory # set mincap {min-cap-num | unspec} Specifies the minimum capacity of the memory array.
Step 7 UCS-A /org/server-qual/memory # set speed {speed-num | unspec} Specifies the memory data rate.
Step 8 UCS-A /org/server-qual/memory # set units {unit-num | unspec} Specifies the number of memory units (DRAM chips mounted to the PCB).
Step 9 UCS-A /org/server-qual/memory # set width {width-num | unspec} Specifies the bit width of the data bus.
Step 10 UCS-A /org/server-qual/memory # commit-buffer Commits the transaction to the system configuration.
The following example configures a memory qualification and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope server-qual ServPoolQual22 UCS-A /org/server-qual* # create memory UCS-A /org/server-qual/memory* # set clock 1067 UCS-A /org/server-qual/memory* # set maxcap 4096 UCS-A /org/server-qual/memory* # set mincap 2048 UCS-A /org/server-qual/memory* # set speed unspec UCS-A /org/server-qual/memory* # set units 16 UCS-A /org/server-qual/memory* # set width 64 UCS-A /org/server-qual/memory* # commit-buffer UCS-A /org/server-qual/memory #Deleting a Memory Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # delete memory Deletes the memory qualification.
Step 4 UCS-A /org/server-qual # commit-buffer Commits the transaction to the system configuration.
Configuring a Processor Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # create processor Creates a processor qualification and enters organization server qualification processor mode.
Step 4 UCS-A /org/server-qual/processor # set arch {any | dual-core-opteron | intel-p4-c | opteron | pentium-4 | turion-64 | xeon | xeon-mp} Specifies the processor architecture type.
Step 5 UCS-A /org/server-qual/processor # set maxcores {max-core-num | unspecified} Specifies the maximum number of processor cores.
Step 6 UCS-A /org/server-qual/processor # set mincores {min-core-num | unspecified} Specifies the minimum number of processor cores.
Step 7 UCS-A /org/server-qual/processor # set maxprocs {max-proc-num | unspecified} Specifies the maximum number of processors.
Step 8 UCS-A /org/server-qual/processor # set minprocs {min-proc-num | unspecified} Specifies the minimum number of processors.
Step 9 UCS-A /org/server-qual/processor # set maxthreads {max-thread-num | unspecified} Specifies the maximum number of threads.
Step 10 UCS-A /org/server-qual/processor # set minthreads {min-thread-num | unspecified} Specifies the minimum number of threads.
Step 11 UCS-A /org/server-qual/processor # set stepping {step-num | unspecified} Specifies the processor stepping number.
Step 12 UCS-A /org/server-qual/processor # commit-buffer Commits the transaction to the system configuration.
The following example configures a processor qualification and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope server-qual ServPoolQual22 UCS-A /org/server-qual* # create processor UCS-A /org/server-qual/processor* # set arch xeon UCS-A /org/server-qual/processor* # set maxcores 8 UCS-A /org/server-qual/processor* # set mincores 4 UCS-A /org/server-qual/processor* # set maxprocs 2 UCS-A /org/server-qual/processor* # set minprocs 1 UCS-A /org/server-qual/processor* # set maxthreads 16 UCS-A /org/server-qual/processor* # set minthreads 8 UCS-A /org/server-qual/processor* # set stepping 5 UCS-A /org/server-qual/processor* # commit-buffer UCS-A /org/server-qual/processor #Deleting a Processor Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # delete processor Deletes the processor qualification.
Step 4 UCS-A /org/server-qual # commit-buffer Commits the transaction to the system configuration.
Configuring a Storage Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # create storage Creates a storage qualification and enters organization server qualification storage mode.
Step 4 UCS-A /org/server-qual/storage # set blocksize {block-size-num | unspecified} Specifies the storage block size.
Step 5 UCS-A /org/server-qual/storage # set maxcap {max-cap-num | unspecified} Specifies the maximum capacity of the storage array.
Step 6 UCS-A /org/server-qual/storage # set mincap {min-cap-num | unspecified} Specifies the minimum capacity of the storage array.
Step 7 UCS-A /org/server-qual/storage # set numberofblocks {block-num | unspecified} Specifies the number of blocks.
Step 8 UCS-A /org/server-qual/storage # set perdiskcap {disk-cap-num | unspecified} Specifies the per-disk capacity.
Step 9 UCS-A /org/server-qual/storage # set units {unit-num | unspecified} Specifies the number of storage units.
Step 10 UCS-A /org/server-qual/storage # commit-buffer Commits the transaction to the system configuration.
The following example configures a storage qualification and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope server-qual ServPoolQual22 UCS-A /org/server-qual* # create storage UCS-A /org/server-qual/storage* # set blocksize 512 UCS-A /org/server-qual/storage* # set maxcap 420000 UCS-A /org/server-qual/storage* # set mincap 140000 UCS-A /org/server-qual/storage* # set numberofblocks 287277984 UCS-A /org/server-qual/storage* # set perdiskcap 140000 UCS-A /org/server-qual/storage* # set units 1 UCS-A /org/server-qual/storage* # commit-buffer UCS-A /org/server-qual/storage #Deleting a Storage Qualification
Procedure
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 # scope server-qual server-qual-name Enters organization server qualification mode for the specified server pool policy qualification.
Step 3 UCS-A /org/server-qual # delete storage Deletes the storage qualification.
Step 4 UCS-A /org/server-qual/ # commit-buffer Commits the transaction to the system configuration.
Server Inheritance Policy Configuration
Server Inheritance Policy
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.
Configuring a Server Inheritance Policy
Procedure
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 # create server-inherit-policy policy-name Creates a server inheritance policy with the specified policy name, and enters organization server inheritance policy mode.
Step 3 UCS-A /org/server-inherit-policy # set descr description (Optional) Provides a description for the policy.
Note If your description includes spaces, special characters, or punctuation, you must begin and end your description with quotation marks. The quotation marks will not appear in the description field of any show command output.
Step 4 UCS-A /org/server-inherit-policy # set destination org org-name (Optional) Specifies the organization for which the server is to be used.
Step 5 UCS-A /org/server-inherit-policy # set qualifier server-qual-name (Optional) Specifies server pool policy qualification to use for qualifying the server.
Step 6 UCS-A /org/server-inherit-policy # commit-buffer Commits the transaction to the system configuration.
The following example creates a server inheritance policy named InheritEngineering, provides a description for the policy, specifies engineering as the destination organization and ServPoolQual22 as the server pool policy qualification, and commits the transaction:
UCS-A# scope org / UCS-A /org* # create server-inherit-policy InheritEngineering UCS-A /org/server-inherit-policy* # set descr "Server Inheritance Policy for Engineering" UCS-A /org/server-inherit-policy* # set destination org engineering UCS-A /org/server-inherit-policy* # set qualifier ServPoolQual22 UCS-A /org/server-inherit-policy* # commit-buffer UCS-A /org/server-inherit-policy #Deleting a Server Inheritance Policy
Procedure
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 server-inherit-policy policy-name Deletes the specified server inheritance policy.
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.
SOL Policy Configuration
Serial over LAN Policy
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.
Configuring a SOL Policy
Procedure
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 # create sol-policy policy-name Creates a serial over LAN (SOL) policy and enters organization SOL policy mode.
Step 3 UCS-A /org/sol-policy # set descr description (Optional) Provides a description for the policy.
Note If your description includes spaces, special characters, or punctuation, you must begin and end your description with quotation marks. The quotation marks will not appear in the description field of any show command output.
Step 4 UCS-A /org/sol-policy # set speed {115200 | 19200 | 38400 | 57600 | 9600} Specifies the serial baud rate.
Step 5 UCS-A /org/sol-policy # {disable | enable} Disables or enables the SOL policy. By default, the SOL policy is disabled; you must enable it before it can be applied.
Step 6 UCS-A /org/sol-policy # commit-buffer Commits the transaction to the system configuration.
The following example creates a SOL policy named Sol9600, provides a description for the policy, sets the speed to 9,600 baud, enables the policy, and commits the transaction:
UCS-A# scope org / UCS-A /org* # create sol-policy Sol9600 UCS-A /org/sol-policy* # set descr "Sets SOL policy to 9600 baud." UCS-A /org/sol-policy* # set speed 9600 UCS-A /org/sol-policy* # enable UCS-A /org/sol-policy* # commit-buffer UCS-A /org/sol-policy #Deleting a SOL Policy
Procedure
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 sol-policy policy-name Deletes the specified SOL policy.
Step 3 UCS-A /org # commit-buffer Commits the transaction to the system configuration.
