Configuring Global Service Profiles

This chapter contains the following sections:

Global Service Profiles

Global service profiles centralize the logical configuration deployed across the data center. This centralization enables the maintenance of all service profiles in the registered Cisco UCS domains from one central location, Cisco UCS Central. When you use a global service profile, you can do the following across all Cisco UCS domains that are registered with the same Cisco UCS Central:

  • Select a compute element for the service profile from any of the Cisco UCS domains.

  • Migrate the service profile from one domain to another.

  • Select servers from the available global server pools from any of the Cisco UCS domains.

  • Associate global resources such as ID pools and policies.

For more information about global service profiles, including guidelines for implementing them, see the Cisco UCS Central configuration guides.

Global Service Profile Templates

Global service profile templates enable you to 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. Service profile templates in Cisco UCS Central are similar to the service profile templates in Cisco UCS Manager.

Creating a Global Service Profile

Before You Begin

At a minimum, the following pools and policies that are required for service profiles must exist in the Cisco UCS Central account:

  • UUID pool

  • Storage policy

  • PXE Network policy

  • Blade Boot policy


Note

You cannot create a host firmware package in Cisco UCS Director. If you want to incorporate this policy in a service profile, import it from the Cisco UCS Central account.

The other policies that you can include in a global service profile are optional. However, we recommend that you review the Add Service Profile dialog box. Ensure that you have created all of the policies that you want to include in the global service profile before you begin.

    Step 1   On the menu bar, choose Physical > Compute.
    Step 2   In the left pane, expand Multi-Domain Managers.
    Step 3   In the left pane, expand UCS Central Accounts and then click the Cisco UCS Central account.
    Step 4   Click the Global Service Profiles tab.
    Step 5   Click Add.
    Step 6   In the Add Service Profile dialog box, enter a name and description for the service profile.
    Step 7   From the following drop-down lists, choose the pools and policies that you want to include in this service profile:

    • Organization—Required. Choose the organization to which the global service profile belongs.

      Note    If the organization does not appear on the drop-down list, you can use the + button to add an addition organization to the drop-down.

    • UUID Assignment—Required. Include this policy to specify the UUID for the server.

    • Storage Policy—Required. Include this policy to specify the SAN connectivity for the server.

    • PXE Network Policy—Required. Include this policy if you must have the server connected to the LAN.

    • PXE Boot Policy—Optional. Include this policy if you want to have the server perform a PXE boot. The secondary boot in this policy must be from a local disk or a SAN boot. If you do not include this policy, the server uses the blade boot policy to determine the boot order.

    • Blade Boot Policy—Required. Include this policy to determine the server boot.

    • BIOS Policy—Optional. Include this policy if you want to change any of the default settings for the BIOS on the server.

    • IPMI Access Profile—Optional. Include this policy if you want to be able to access the server through IPMI.

    • SOL Configuration Profile—Optional. Include this policy if you want to be able to access the server through Serial over LAN.

    • Threshold Policy—Optional. Include this policy to specify the thresholds for the server.

    • Scrub Policy—Optional. Include this policy if you want to specify what happens to the local data and BIOS settings on a server during discovery and disassociation.

    • Host Firmware Policy—Optional. Include this policy if you want to use a host firmware package to upgrade the server firmware.

    • Maintenance Policy—Optional. Include this policy if you want to specify what happens when change that requires a server reboot is made to this service profile.

    • Power Control Policy—Optional. Include this policy if the service profile is associated with a blade server and you want to specify the initial power allocation for the server.

    Step 8   Server Power State drop-down list—Required. Choose one of the following to set the power state that is applied to the server when it is associated with this service profile:
    • Down—If you want the server to be powered down before the profile is associated with the server.
    • Up—If you want the server to be powered up before the profile is associated with the server.
    Step 9   Click Submit.

    Creating a Global Service Profile Template

    Before You Begin

    At a minimum, the following pools and policies that are required for service profile templates must exist in the Cisco UCS Central account:

    • UUID pool

    • Storage policy

    • Network policy

    • Boot policy


    Note

    You cannot create a host firmware package in Cisco UCS Director. If you want to incorporate this policy in a service profile template, import it from the Cisco UCS Central account.

    The other policies that you can include in a service profile template are optional. However, we recommend that you review the Create Service Profile Template dialog box. Ensure that you have created all of the policies that you want to include in the template before you begin.

      Step 1   On the menu bar, choose Physical > Compute.
      Step 2   In the left pane, expand Multi-Domain Managers.
      Step 3   In the left pane, expand UCS Central Accounts and then click the Cisco UCS Central account.
      Step 4   Click the Global Service Profile Templates tab.
      Step 5   Click Add.
      Step 6   In the Create Service Profile Template dialog box, enter a name and description for the service profile template.
      Step 7   From the Organization drop-down list, choose the organization to which the global service profile template belongs.
      Step 8   From the TemplateType drop-down list, choose one of the following:
      • Initial Template—Any service profiles created from this template are not updated if the template changes.
      • Updating Template—Any service profiles created from this template are updated if the template changes.
      Step 9   From the following drop-down lists, choose the pools and policies that you want to include in this service profile:

      • UUID Assignment—Required. Include this policy to specify the UUID for the server.

      • Storage Policy—Required. Include this policy to specify the SAN connectivity for the server.

      • PXE Network Policy—Optional. Include this policy if you must have the server connected to the LAN.

      • PXE Boot Policy—Optional. Include this policy if you want to have the server to perform a PXE boot. The secondary boot in this policy must be from a local disk or a SAN boot. If you do not include this policy, the server uses the blade boot policy to determine the boot order.

      • Blade Boot Policy—Optional. Include this policy to determine the server boot order.

      • BIOS Policy—Optional. Include this policy if you want to change any of the default settings for the BIOS on the server.

      • IPMI Access Profile—Optional. Include this policy if you want to be able to access the server through IPMI.

      • SOL Configuration Profile—Optional. Include this policy if you want to be able to access the server through Serial over LAN.

      • Management IP Address Policy—Optional. Include this policy to specify the management IP address for the server.

      • Threshold Policy—Optional. Include this policy to specify the thresholds for the server.

      • Scrub Policy—Optional. Include this policy if you want to specify what happens to the local data and BIOS settings on a server during discovery and disassociation.

      • Host Firmware Policy—Optional. Include this policy if you want to use a host firmware package to upgrade the server firmware.

      • Maintenance Policy—Optional. Include this policy if you want to specify what happens when change that requires a server reboot is made to this service profile.

      • Power Control Policy—Optional. Include this policy if the service profile is associated with a blade server and you want to specify the initial power allocation for the server.

      Step 10   From the Server Power State drop-down list, choose one of the following to set the power state that is applied to the server when it is associated with this service profile:
      • Down—If you want the server to be powered down before the profile is associated with the server.
      • Up—If you want the server to be powered up before the profile is associated with the server.
      Step 11   Click Submit.