- Service Profiles that Override Server Identity
- Service Profiles that Inherit Server Identity
- Service Profile Templates
- Creating a Service Profile with the Expert Wizard
- Creating a Service Profile that Inherits Server Identity
- Creating a Hardware Based Service Profile for a Server
- Creating a Service Profile Template
- Page 1: Identifying the Service Profile Template
- Page 2: Specifying the Template Storage Options
- Page 3: Specifying the Template Networking Options
- Page 4: Setting the vNIC/vHBA Placement
- Page 5: Specifying the Template Server Boot Order Options
- Page 6: Specifying the Template Server Assignment Options
- Page 7: Specifying Template Policy Options
- Creating One or More Service Profiles from a Service Profile Template
- Creating a Template Based Service Profile for a Server
- Creating a Service Profile Template from a Service Profile
- Changing the UUID in a Service Profile Template
- Associating a Service Profile Template with a Server Pool
- Disassociating a Service Profile Template from its Server Pool
- Cloning a Service Profile
- Associating a Service Profile with a Server or Server Pool
- Disassociating a Service Profile from a Server or Server Pool
- Changing the UUID in a Service Profile
- Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile Template
- Modifying the Boot Order in a Service Profile
- Creating a vNIC for a Service Profile
- Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template
- Deleting a vNIC from a Service Profile
- Creating a vHBA for a Service Profile
- Changing the WWPN for a vHBA
- Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template
- Clearing Persistent Binding for a vHBA
- Deleting a vHBA from a Service Profile
- Binding a Service Profile to a Service Profile Template
- Unbinding a Service Profile from a Service Profile Template
- Deleting a Service Profile
Configuring Service Profiles
This chapter includes the following sections:
- Service Profiles that Override Server Identity
- Service Profiles that Inherit Server Identity
- Service Profile Templates
- Creating a Service Profile with the Expert Wizard
- Creating a Service Profile that Inherits Server Identity
- Creating a Hardware Based Service Profile for a Server
- Creating a Service Profile Template
- Creating One or More Service Profiles from a Service Profile Template
- Creating a Template Based Service Profile for a Server
- Creating a Service Profile Template from a Service Profile
- Changing the UUID in a Service Profile Template
- Associating a Service Profile Template with a Server Pool
- Disassociating a Service Profile Template from its Server Pool
- Cloning a Service Profile
- Associating a Service Profile with a Server or Server Pool
- Disassociating a Service Profile from a Server or Server Pool
- Changing the UUID in a Service Profile
- Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile Template
- Modifying the Boot Order in a Service Profile
- Creating a vNIC for a Service Profile
- Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template
- Deleting a vNIC from a Service Profile
- Creating a vHBA for a Service Profile
- Changing the WWPN for a vHBA
- Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template
- Clearing Persistent Binding for a vHBA
- Deleting a vHBA from a Service Profile
- Binding a Service Profile to a Service Profile Template
- Unbinding a Service Profile from a Service Profile Template
- Deleting a Service Profile
Service Profiles that Override Server Identity
This type of service profile provides the maximum amount of flexibility and control. This profile allows you to override the identity values that are on the server at the time of association and use the resource pools and policies set up in Cisco UCS Manager to automate some administration tasks.
You can disassociate this service profile from one server and then associate it with another server. This re-association can be done either manually or through an automated server pool policy. The burned-in settings, such as UUID and MAC address, on the new server are overwritten with the configuration in the service profile. As a result, the change in server is transparent to your network. You do not need to reconfigure any component or application on your network to begin using the new server.
This profile allows you to take advantage of and manage system resources through resource pools and policies, such as the following:
Service Profiles that Inherit Server Identity
This hardware-based service profile is the simplest to use and create. This profile uses the default values in the server and mimics the management of a rack-mounted server. It is tied to a specific server and cannot be moved to another server.
You do not need to create pools or configuration policies to use this service profile.
This service profile inherits and applies the identity and configuration information that is present at the time of association, such as the following:
-
MAC addresses for the two NICs
-
For a converged network adapter or a virtual interface card, the WWN addresses for the two HBAs
-
BIOS versions
-
Server UUID
The server identity and configuration information inherited through this service profile may not be the values burned into the server hardware at manufacture if those values were changed before this profile is associated with the server.
Service Profile Templates
With a service profile template, you can quickly create several service profiles with the same basic parameters, such as the number of vNICs and vHBAs, and with identity information drawn from the same pools.
Tip |
If you need only one service profile with similar values to an existing service profile, you can clone a service profile in the Cisco UCS Manager GUI. |
For example, if you need several service profiles with similar values to configure servers to host database software, you can create a service profile template, either manually or from an existing service profile. You then use the template to create the service profiles.
Cisco UCS supports the following types of service profile templates:
- Initial template
-
Service profiles created from an initial template inherit all the properties of the template. However, after you create the profile, it is no longer connected to the template. If you need to make changes to one or more profiles created from this template, you must change each profile individually.
- Updating template
-
Service profiles created from an updating template inherit all the properties of the template and remain connected to the template. Any changes to the template automatically update the service profiles created from the template.
Creating Service Profiles
Creating a Service Profile with the Expert Wizard
- Page 1: Identifying the Service Profile
- Page 2: Configuring the Storage Options
- Page 3: Configuring the Networking Options
- Page 4: Setting the vNIC/vHBA Placement
- Page 5: Setting the Server Boot Order
- Page 6: Specifying the Server Assignment
- Page 7: Adding Operational Policies
Page 1: Identifying the Service Profile
This procedure directly follows the steps in Creating a Service Profile with the Expert Wizard. It describes how to set the identity of a service proflie on the Identify Service Profile page of the Create Service Profile (expert) wizard.
Step 1 |
In the Name field, enter a unique name that you can use to identify the service profile. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters, and you cannot change this name after the object has been saved. This name must be unique within the organization or sub-organization in which you are creating the service profile. |
Step 2 | From the UUID Assignment drop-down list, do one of the following: |
Step 3 | (Optional) If you selected the XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX option, do the following: |
Step 4 |
(Optional)If you want to create a new UUID Suffix pool, click Create UUID Suffix Pool and complete the fields in the Create UUID Suffix Pool wizard. For more information, see Creating a UUID Suffix Pool. |
Step 5 |
(Optional) In the text box, enter a description of this service profile. The description can contain up to 256 characters. |
Step 6 | Click Next. |
What to Do Next
Complete the steps in Page 2: Configuring the Storage Options.
Page 2: Configuring the Storage Options
This procedure directly follows Page 1: Identifying the Service Profile. It describes how to configure the storage options for a service profile on the Storage page of the Create Service Profile (expert) wizard.
What to Do Next
Page 3: Configuring the Networking Options
This procedure directly follows Page 2: Configuring the Storage Options. It describes how to configure the networking options, including LAN connectivity, on the Networking page of the Create Service Profile (expert) wizard.
Step 1 |
(Optional)If you plan to assign this service profile to a server with an adapter that supports dynamic vNICs, choose one of the following options from the Dynamic vNIC Connection drop-down list:
|
||||||||||
Step 2 |
(Optional) If want to create a new dynamic vNIC connection policy that can only be used by this service profile, click Create a Specific Dynamic vNIC Connection Policy and do the following:
|
||||||||||
Step 3 |
(Optional) To create a dynamic vNIC connection policy that will be available to all service profiles, do the following:
|
||||||||||
Step 4 |
In the How would you like to configure LAN connectivity? field, click one of the following options:
|
||||||||||
Step 5 |
(Optional) If you chose the simple LAN connectivity option, do the following:
|
||||||||||
Step 6 |
If you chose the expert LAN connectivity option, do the following:
|
||||||||||
Step 7 | Click Next. |
What to Do Next
Complete Page 4: Setting the vNIC/vHBA Placement.
Page 4: Setting the vNIC/vHBA Placement
This procedure directly follows Page 3: Configuring the Networking Options. It describes how to set the vNIC and vHBA placement options on the vNIC/vHBA Placement page of the Create Service Profile (expert) wizard.
Step 1 |
From the Select Placement drop-down list, choose one of the following:
|
||||||||
Step 2 |
(Optional) If you chose Let System Perform Placement, do the following:
|
||||||||
Step 3 |
(Optional)If you chose Specify Manually, do the following:
|
||||||||
Step 4 |
If you clicked Create Placement Policy, do the following in the Create Placement Policy dialog box:
|
||||||||
Step 5 | Click Next. |
What to Do Next
Page 5: Setting the Server Boot Order
This procedure directly follows Page 4: Setting the vNIC/vHBA Placement. It describes how to set the server boot order options on the Server Boot Order page of the Create Service Profile (expert) wizard.
Tip |
We recommend that the boot order in a boot policy include either a local disk or a SAN LUN, but not both, to avoid the possibility of the server booting from the wrong storage type. If you configure a local disk and a SAN LUN for the boot order storage type and the operating system or logical volume manager (LVM) is configured incorrectly, the server may boot from the local disk rather than the SAN LUN. For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local disk. |
Step 1 |
From the Boot Policy drop-down list, choose one of the following:
|
||||||||
Step 2 |
If you chose to create a boot policy that all service profiles and templates can use, do the following:
|
||||||||
Step 3 |
(Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the Reboot on Boot Order Change check box. In Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, then deleting or adding the device does not directly affect the boot order and the server does not reboot. |
||||||||
Step 4 |
(Optional)To ensure that Cisco UCS Manager uses any vNICs or vHBAs in the order shown in the Boot Order table, check the Enforce vNIC/vHBA Name check box. If you do not check this check box, Cisco UCS Manager uses the priority specified in the vNIC or vHBA. |
||||||||
Step 5 |
To add a local disk, virtual CD-ROM, or virtual floppy to the boot order, do the following:
|
||||||||
Step 6 | To add a LAN boot to the boot order, do the following: | ||||||||
Step 7 |
To add a SAN boot to the boot order, do the following:
|
||||||||
Step 8 | If you created a new boot policy accessible to all service profiles and template, select that policy from the Boot Policy drop-down list. | ||||||||
Step 9 | Click Next. |
What to Do Next
Page 6: Specifying the Server Assignment
This procedure directly follows Page 5: Setting the Server Boot Order. It describes how to specify the way a server is assigned and which firmware packages are associated with the service profile on the Server Assignment page of the Create Service Profile (expert) wizard.
Step 1 |
From the Server Assignment drop-down list, choose one of the following:
|
||||||||||
Step 2 | If you chose Pre-provision a slot, do the following: | ||||||||||
Step 3 | If you chose Select existing Server, do the following: | ||||||||||
Step 4 |
In the Power State field, click one of the following radio buttons to set the power state that will be applied to the server when it is associated with this service profile:
By default, the server is powered up. |
||||||||||
Step 5 |
(Optional) In the Firmware Management area, do the following to use policies to update the firmware on the server associated with the service profile:
|
||||||||||
Step 6 | Click Next. |
What to Do Next
Complete Page 7: Adding Operational Policies.
Page 7: Adding Operational Policies
This procedure directly follows Page 6: Specifying the Server Assignment. It describes how to add operational policies to the service profile on the Operational Policies page of the Create Service Profile (expert) wizard. These policies are optional.
Step 1 |
To provide external access to the CIMC on the server, click the down arrows to expand the External IPMI Management Configuration bar and add an IPMI profile and a serial over LAN policy. If you do not want to provide external access, continue with Step 4. |
Step 2 |
To add an IPMI profile to the service profile, do one of the following:
|
Step 3 |
To add a Serial over LAN policy to the service profile, do one of the following:
For more information about how to create a serial over LAN policy, see Creating a Serial over LAN Policy. |
Step 4 |
To monitor thresholds and collect statistics for the associated server, click the down arrows to expand the Monitoring Configuration bar and do one of the following:
For more information about how to create a threshold policy, see Creating a Server and Server Component Threshold Policy. |
Step 5 |
To override the default BIOS settings and configure them through the service profile, click the down arrows to expand the BIOS Configuration bar and do one of the following:
For more information about how to create a BIOS policy, see Creating a BIOS Policy. |
Step 6 |
To associate a scrub policy with the service profile, click the down arrows to expand the Scrub Policy bar and do one of the following:
For more information about how to create a scrub policy, see Creating a Scrub Policy. |
Step 7 | Click Finish. |
Creating a Service Profile that Inherits Server Identity
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 service profile. If the system does not include multi-tenancy, expand the root node. |
||||||||||||||||||||||||
Step 4 | Right-click the organization and select Create Service Profile. | ||||||||||||||||||||||||
Step 5 |
In the Naming area of the Create Service Profile dialog box, complete the following fields:
|
||||||||||||||||||||||||
Step 6 |
In the vNICs area of the Create Service Profile dialog box, complete the following fields:
|
||||||||||||||||||||||||
Step 7 |
In the vHBAs area of the Create Service Profile dialog box, complete the following fields:
|
||||||||||||||||||||||||
Step 8 |
In the Boot Order area of the Create Service Profile dialog box, complete the following fields:
|
||||||||||||||||||||||||
Step 9 | (Optional) In the Select column of the Server Association (optional) area, click the radio button for a server to associate this service profile with that server. | ||||||||||||||||||||||||
Step 10 | Click OK. |
Creating a Hardware Based Service Profile for a Server
You cannot move a hardware based service profile to another server.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server for which you want to create a hardware based service profile. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Create Service Profile. |
Step 6 |
In the Create Service Profile for Server dialog box, do the following:
Cisco UCS Manager inherits and automatically applies the identity and configuration information in the server, creates the service profile, and associates it with the server. |
Working with Service Profile Templates
Creating a Service Profile Template
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 service profile template. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Right-click the organization and select Create Service Profile Template. |
Step 5 |
In the Create Service Profile Template wizard, complete the following: |
- Page 1: Identifying the Service Profile Template
- Page 2: Specifying the Template Storage Options
- Page 3: Specifying the Template Networking Options
- Page 4: Setting the vNIC/vHBA Placement
- Page 5: Specifying the Template Server Boot Order Options
- Page 6: Specifying the Template Server Assignment Options
- Page 7: Specifying Template Policy Options
Page 1: Identifying the Service Profile Template
This procedure directly follows the steps in Creating a Service Profile Template. It describes how to set the identity of a service profile template on the Identify Service Profile Template page of the Create Service Profile Template wizard.
Step 1 |
In the Name field, enter a unique name that you can use to identify this service profile template. This name can be between 2 and 32 alphanumeric characters. You cannot use spaces or any special characters, and you cannot change this name after the object has been saved. This name must be unique within the organization or sub-organization in which you are creating the service profile. |
||||||||
Step 2 |
In the Type field, click one of the following radio buttons: |
||||||||
Step 3 |
From the UUID Assignment drop-down list, choose one of the following:
|
||||||||
Step 4 |
(Optional) In the text box, enter a description of this service profile template. The description can contain up to 256 characters. |
||||||||
Step 5 | Click Next. |
What to Do Next
Complete the steps in Page 2: Specifying the Template Storage Options.
Page 2: Specifying the Template Storage Options
This procedure directly follows Page 1: Identifying the Service Profile Template. It describes how to configure the storage options for a service profile template on the Storage page of the Create Service Profile Template wizard.
Step 1 |
From the Local Storage drop-down list, choose one of the following:
|
||||||||
Step 2 |
(Optional) If you chose Create a Specific Storage Policy, do the following:
|
||||||||
Step 3 |
(Optional) To create a local disk configuration policy that will be available to all service profiles and templates, do the following:
|
||||||||
Step 4 |
In the How would you like to configure SAN storage? field, click one of the following options:
|
||||||||
Step 5 |
(Optional) If you chose the simple SAN storage option, do the following:
|
||||||||
Step 6 |
(Optional) If you chose the expert SAN storage option, do the following:
|
||||||||
Step 7 | Click Next. |
What to Do Next
Complete Page 3: Specifying the Template Networking Options.
Page 3: Specifying the Template Networking Options
This procedure directly follows Page 2: Specifying the Template Storage Options. It describes how to configure the networking options, including LAN connectivity, on the Networking page of the Create Service Profile Template wizard.
Step 1 |
(Optional)If you plan to assign service profiles created from this template to a server with an adapter that supports dynamic vNICs, choose one of the following options from the Dynamic vNIC Connection drop-down list:
|
||||||||
Step 2 |
(Optional) If want to create a new dynamic vNIC connection policy that can only be used by service profiles created from this template, click Create a Specific Dynamic vNIC Connection Policy and do the following:
|
||||||||
Step 3 |
(Optional) To create a dynamic vNIC connection policy that will be available to all service profiles and templates, do the following:
|
||||||||
Step 4 |
In the How would you like to configure LAN connectivity? field, click one of the following options:
|
||||||||
Step 5 |
(Optional) If you chose the simple LAN connectivity option, do the following:
|
||||||||
Step 6 |
If you chose the expert LAN connectivity option, do the following:
|
||||||||
Step 7 | Click Next. |
What to Do Next
Complete Page 4: Setting the vNIC/vHBA Placement.
Page 4: Setting the vNIC/vHBA Placement
This procedure directly follows Page 3: Specifying the Template Networking Options. It describes how to set the vNIC and vHBA placement options on the vNIC/vHBA Placement page of the Create Service Profile Template wizard.
Step 1 |
From the Select Placement drop-down list, choose one of the following:
|
||||||||
Step 2 |
(Optional) If you chose Let System Perform Placement, do the following:
|
||||||||
Step 3 |
(Optional)If you chose Specify Manually, do the following:
|
||||||||
Step 4 |
If you clicked Create Placement Policy, do the following in the Create Placement Policy dialog box:
|
||||||||
Step 5 | Click Next. |
What to Do Next
Complete Page 5: Specifying the Template Server Boot Order Options
Page 5: Specifying the Template Server Boot Order Options
This procedure directly follows Page 4: Setting the vNIC/vHBA Placement. It describes how to set the server boot order options on the Server Boot Order page of the Create Service Profile Template wizard.
Tip |
We recommend that the boot order in a boot policy include either a local disk or a SAN LUN, but not both, to avoid the possibility of the server booting from the wrong storage type. If you configure a local disk and a SAN LUN for the boot order storage type and the operating system or logical volume manager (LVM) is configured incorrectly, the server may boot from the local disk rather than the SAN LUN. For example, on a server with Red Hat Linux installed, where the LVM is configured with default LV names and the boot order is configured with a SAN LUN and a local disk, Linux reports that there are two LVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local disk. |
Step 1 |
From the Boot Policy drop-down list, choose one of the following:
|
||||||||
Step 2 |
If you chose to create a boot policy that all service profiles and templates can use, do the following:
|
||||||||
Step 3 |
(Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the Reboot on Boot Order Change check box. In Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, then deleting or adding the device does not directly affect the boot order and the server does not reboot. |
||||||||
Step 4 |
(Optional)To ensure that Cisco UCS Manager uses any vNICs or vHBAs in the order shown in the Boot Order table, check the Enforce vNIC/vHBA Name check box. If you do not check this check box, Cisco UCS Manager uses the priority specified in the vNIC or vHBA. |
||||||||
Step 5 |
To add a local disk, virtual CD-ROM, or virtual floppy to the boot order, do the following:
|
||||||||
Step 6 | To add a LAN boot to the boot order, do the following: | ||||||||
Step 7 |
To add a SAN boot to the boot order, do the following:
|
||||||||
Step 8 | If you created a new boot policy accessible to all service profiles and template, select that policy from the Boot Policy drop-down list. | ||||||||
Step 9 | Click Next. |
What to Do Next
Complete Page 6: Specifying the Template Server Assignment Options.
Page 6: Specifying the Template Server Assignment Options
This procedure directly follows Page 5: Specifying the Template Server Boot Order Options. It describes how to specify the way a server is assigned to a service profile created from this template on the Server Assignment page of the Create Service Profile Template wizard.
Step 1 |
From the Server Assignment drop-down list, choose one of the following:
|
||||||
Step 2 |
In the Power State field, click one of the following radio buttons to set the power state that will be applied to the server when it is associated with a service profile created from this template:
By default, the server is powered up. |
||||||
Step 3 |
(Optional) In the Firmware Management area, do the following to use policies to update the firmware on the server associated with a service profile created from this template:
|
||||||
Step 4 | Click Next. |
What to Do Next
Page 7: Specifying Template Policy Options
This procedure directly follows Page 6: Specifying the Template Server Assignment Options. It describes how to add operational policies to the service profile template on the Operational Policies page of the Create Service Profile Template wizard. These policies are optional.
Step 1 |
To provide external access to the CIMC on the server, click the down arrows to expand the External IPMI Management Configuration bar and add an IPMI profile and a serial over LAN policy. If you do not want to provide external access, continue with Step 4. |
Step 2 |
To add an IPMI profile to service profiles created from this template, do one of the following:
For more information about how to create an IPMI profile, see Creating an IPMI Access Profile. |
Step 3 |
To add a Serial over LAN policy to service profiles created from this template, do one of the following:
For more information about how to create a serial over LAN policy, see Creating a Serial over LAN Policy. |
Step 4 |
To monitor thresholds and collect statistics for the associated server, click the down arrows to expand the Monitoring Configuration bar and do one of the following:
For more information about how to create a threshold policy, see Creating a Server and Server Component Threshold Policy. |
Step 5 |
To override the default BIOS settings and configure them through the service profile, click the down arrows to expand the BIOS Configuration bar and do one of the following:
For more information about how to create a BIOS policy, see Creating a BIOS Policy. |
Step 6 |
To associate a scrub policy with the service profile, click the down arrows to expand the Scrub Policy bar and do one of the following:
For more information about how to create a scrub policy, see Creating a Scrub Policy. |
Step 7 | Click Finish. |
Creating One or More Service Profiles from a Service Profile Template
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 contains the service profile template that you want to use as the basis for your service profiles. If the system does not include multi-tenancy, expand the root node. |
||||||
Step 4 | Right-click the service profile template from which you want to create the profiles and select Create Service Profiles From Template. | ||||||
Step 5 |
In the Create Service Profiles From Template dialog box, complete the following fields:
|
||||||
Step 6 | Click OK. |
Creating a Template Based Service Profile for a Server
A qualified service template with the desired values must exist in Cisco UCS Manager.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server for which you want to create a hardware based service profile. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Create Service Profile. |
Step 6 |
In the Create Service Profile for Server dialog box, do the following:
|
Creating a Service Profile Template from a 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 contains the service profile that you want to use as the basis for your template. If the system does not include multi-tenancy, expand the root node. |
||||||||
Step 4 | Right-click the service profile from which you want to create the template and select Create a Service Profile Template. | ||||||||
Step 5 |
In the Create Template From Service Profile dialog box, complete the following fields:
|
||||||||
Step 6 | Click OK. |
Changing the UUID in a Service Profile Template
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 contains the service profile template for which you want to change the UUID. If the system does not include multi-tenancy, expand the root node. |
||||||||
Step 4 | Choose the service profile template whose UUID assignment you want to change. | ||||||||
Step 5 | In the Work pane, click the General tab. | ||||||||
Step 6 | In the Actions area, click Change UUID. | ||||||||
Step 7 |
From the UUID Assignment drop-down list, choose one of the following:
|
||||||||
Step 8 | Click OK. |
Associating a Service Profile Template with a Server Pool
Follow this procedure if you did not associate the service profile template with a server pool when you created it, or to change the server pool with which a service profile created from this template is associated.
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 contains the service profile that you want to associate with a server pool. If the system does not include multi-tenancy, expand the root node. |
Step 4 |
Right-click the service profile template you want to associate with a server pool and select Associate with Server Pool. The Associate with Server Pool dialog box opens. |
Step 5 |
From the Server Pool section of the Pool Assignment drop-down list, select a server pool. If you select Assign Later, the service profile template is not associated with a server pool. |
Step 6 | Select one of the following radio buttons to determine the power state applied to a server which is associated with a service profile profile created from this template: |
Step 7 | From the Select Qualification drop-down list, select the server pool policy qualifications you want to apply to a server that is associated with a service profile created from this template. |
Step 8 | Click OK. |
Disassociating a Service Profile Template from its Server Pool
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 contains the service profile that you want to disassociate from its server pool. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Right-click the service profile template you want to disassociate from its server pool and select Disassociate Template. |
Step 5 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Managing Service Profiles
Cloning a 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 where you want to create the service profile. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Right-click the service profile you want to clone and select Create a Clone. |
Step 5 |
In the Create Clone From Service Profile dialog box:
|
Step 6 | Navigate to the service profile you just created and make sure that all options are correct. |
Associating a Service Profile with a Server or Server Pool
Follow this procedure if you did not associate the service profile with a server or server pool when you created it, or to change the server or server pool with which a service profile is associated.
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 contains the service profile that you want to associate with a new server or server pool. If the system does not include multi-tenancy, expand the root node. |
||||||||
Step 4 | Right-click the service profile you want to associate with a server and select Change Service Profile Association. | ||||||||
Step 5 |
In the Associate Service Profile dialog box, select one of the following options:
|
||||||||
Step 6 | If you chose Custom Server, do the following: | ||||||||
Step 7 | Click OK. |
Disassociating a Service Profile from a Server or Server Pool
When you disassociate a service profile, Cisco UCS Manager attempts to shutdown the operating system on the server. If the operating system does not shutdown within a reasonable length of time, Cisco UCS Manager forces the server to shutdown.
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 contains the service profile that you want to disassociate from a server or server pool. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Right-click the service profile you want to disassociate from a server and select Disassociate Service Profile. |
Step 5 | In the Disassociate Service Profile dialog box, click Yes to confirm that you want to disassociate the service profile. |
Step 6 | (Optional) Monitor the status and FSM for the server to confirm that the disassociation completed. |
Changing the UUID in a 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 contains the service profile for which you want to change the UUID. If the system does not include multi-tenancy, expand the root node. |
||||||||||
Step 4 | Choose the service profile that requires the UUID for the associated server to be changed. | ||||||||||
Step 5 | In the Work pane, click the General tab. | ||||||||||
Step 6 | In the Actions area, click Change UUID. | ||||||||||
Step 7 |
From the UUID Assignment drop-down list, do one of the following:
|
||||||||||
Step 8 | (Optional) If you selected the XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX option, do the following: | ||||||||||
Step 9 | Click OK. |
Resetting the UUID Assigned to a Service Profile from a Pool in a Service Profile Template
If you change the UUID suffix pool assigned to an updating service profile template, Cisco UCS Manager does not change the UUID assigned to a service profile created with that template. If you want Cisco UCS Manager to assign a UUID from the newly assigned pool to the service profile, and therefore to the associated server, you must reset the UUID. You can only reset the UUID assigned to a service profile and its associated server under the following circumstances:
-
The service profile was created from an updating service profile template and includes a UUID assigned from a UUID suffix pool.
-
The UUID suffix pool name is specified in the service profile. For example, the pool name is not empty.
-
The UUID value is not 0, and is therefore not derived from the server hardware.
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 contains the service profile for which you want to reset the UUID. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Choose the service profile that requires the UUID for the associated server to be reset to a different UUID suffix pool. |
Step 5 | In the Work pane, click the General tab. |
Step 6 |
In the Actions area, click Reset UUID. If this action is not visible, then the UUID configuration in the service profile does not meet the requirements for resetting a UUID. |
Step 7 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Step 8 | Click OK |
Modifying the Boot Order in a 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 for which you want to change the boot order. If the system does not include multi-tenancy, expand the root node. |
||||||||
Step 4 | Click the service profile for which you want to change the boot order. | ||||||||
Step 5 | In the Work pane, click the Boot Order tab. | ||||||||
Step 6 | Click Modify Boot Policy to change the existing boot policy. | ||||||||
Step 7 |
In the Modify Boot Policy dialog box, choose one of the following from the Boot Policy drop-down list:
|
||||||||
Step 8 |
If you chose to create a boot policy, in the Create Boot Policy dialog box, enter a unique name and description for 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. |
||||||||
Step 9 |
(Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the Reboot on Boot Order Change check box. In Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot policy, and if CD-ROM or Floppy is the last device in the boot order, then deleting or adding the device does not directly affect the boot order and the server does not reboot. |
||||||||
Step 10 |
(Optional)To ensure that Cisco UCS Manager uses any vNICs or vHBAs in the order shown in the Boot Order table, check the Enforce vNIC/vHBA Name check box. If you do not check this check box, Cisco UCS Manager uses the priority specified in the vNIC or vHBA. |
||||||||
Step 11 |
To add a local disk, virtual CD-ROM, or virtual floppy to the boot order, do the following:
|
||||||||
Step 12 | To add a LAN boot to the boot order, do the following: | ||||||||
Step 13 |
To add a SAN boot to the boot order, do the following:
|
||||||||
Step 14 | Click OK. |
Creating a vNIC for a 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 contains the service profile for which you want to create a vNIC. |
Step 4 | Expand the service profile for which you want to create a vNIC. |
Step 5 | Right-click the vNICs node and choose Create vNICs. |
Step 6 |
In the Create vNICs dialog box, do the following:
|
Resetting the MAC Address Assigned to a vNIC from a Pool in a Service Profile Template
If you change the MAC pool assigned to an updating service profile template, Cisco UCS Manager does not change the MAC address assigned to a service profile created with that template. If you want Cisco UCS Manager to assign a MAC address from the newly assigned pool to the service profile, and therefore to the associated server, you must reset the MAC address. You can only reset the MAC address assigned to a service profile and its associated server under the following circumstances:
-
The service profile was created from an updating service profile template and includes a MAC address assigned from a MAC pool.
-
The MAC pool name is specified in the service profile. For example, the pool name is not empty.
-
The MAC address value is not 0, and is therefore not derived from the server hardware.
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 contains the service profile for which you want to reset the MAC address. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Expand . |
Step 5 | Click the vNIC for which you want to reset the MAC address. |
Step 6 | In the Work pane, click the General tab. |
Step 7 | In the Actions area, click Reset MAC Address. |
Step 8 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Step 9 | Click OK. |
Deleting a vNIC from a 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 contains the service profile from which you want to delete a vNIC. |
Step 4 | Expand the service profile from which you want to delete a vNIC. |
Step 5 | Expand the vNICs node. |
Step 6 | Right-click the vNIC you want to delete and choose Delete. |
Step 7 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Creating a vHBA for a 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 contains the service profile for which you want to create a vHBA. |
Step 4 | Expand the service profile for which you want to create a vHBA. |
Step 5 | Right-click the vHBAs node and choose Create vHBAs. |
Step 6 |
In the Create vHBAs dialog box, do the following:
|
Changing the WWPN for a vHBA
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 contains the service profile for which you want to change the WWPN. |
Step 4 | Expand . |
Step 5 | Click the vHBA for which you want to change the WWPN. |
Step 6 | In the Work pane, click the General tab. |
Step 7 | In the Actions area, click Change World Wide Name. |
Step 8 |
In the Change World Wide Port Name dialog box, do the following:
|
Resetting the WWPN Assigned to a vHBA from a Pool in a Service Profile Template
If you change the WWPN pool assigned to an updating service profile template, Cisco UCS Manager does not change the WWPN assigned to a service profile created with that template. If you want Cisco UCS Manager to assign a WWPN from the newly assigned pool to the service profile, and therefore to the associated server, you must reset the WWPN. You can only reset the WWPN assigned to a service profile and its associated server under the following circumstances:
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 contains the service profile for which you want to reset the WWPN. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Expand . |
Step 5 | Click the vHBA for which you want to reset the WWPN. |
Step 6 | In the Work pane, click the General tab. |
Step 7 | In the Actions area, click Reset WWPN. |
Step 8 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Step 9 | Click OK. |
Clearing Persistent Binding for a vHBA
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 contains the service profile for which you want to modify the vHBA. |
Step 4 | Expand . |
Step 5 | Click the vHBA for which you want to clear the persistent binding. |
Step 6 | In the Work pane, click the General tab. |
Step 7 | In the Actions area, click Clear Persistent Binding. |
Step 8 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Deleting a vHBA from a 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 contains the service profile from which you want to delete a vHBA. |
Step 4 | Expand the service profile from which you want to delete a vHBA. |
Step 5 | Expand the vHBAs node. |
Step 6 | Right-click the vHBA you want to delete and choose Delete. |
Step 7 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Binding a Service Profile to a Service Profile Template
You can bind a service profile to a service profile template. When you bind the service profile to a template, Cisco UCS Manager configures the service profile with the values defined in the service profile template. If the existing service profile configuration does not match the template, Cisco UCS Manager reconfigures the service profile. You can only change the configuration of a bound service profile through the associated template.
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 you want to bind. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Click the service profile you want to bind. |
Step 5 | In the Work pane, click the General tab. |
Step 6 | In the Actions area, click Bind to a Template. |
Step 7 | In the Bind to a Service Profile Template dialog box, do the following: |
Unbinding a Service Profile from a Service Profile Template
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 you want to unbind. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Click the service profile you want to unbind. |
Step 5 | In the Work pane, click the General tab. |
Step 6 | In the Actions area, click Unbind from the Template. |
Step 7 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Deleting a Service Profile
Step 1 | In the Navigation pane, click the Servers tab. |
Step 2 | In the Servers tab, expand . |
Step 3 | Right-click the service profile you want to delete and select Delete. |
Step 4 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Step 5 | Click OK. |