Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

Dell EMC OpenManage Essentials Version 2.5 User's Guide

Deploying a device deployment template—Bare-metal deployment

The Deploy Template task allows you to deploy a configuration template that includes a set of configuration attributes to specific devices. Deploying a device configuration template on the devices ensures that the devices are uniformly configured. Bare-metal servers and chassis are devices that only have basic iDRAC communication configured are not yet provisioned for operations.

Before you begin deploying a device deployment template, ensure that:
  • NOTE: Dell EMC recommends that you deploy the configuration templates that are captured from a server with BOSS-S1 AHCI controller as-is without editing the attributes.
  • CAUTION: Deploying a configuration template on a device may result in potentially destructive changes to the device configuration including performance, connectivity, and ability to boot the device.

To deploy the configuration template on bare-metal devices:

  1. Click Deployment. The Deployment Portal is displayed.
  2. Perform one of the following:
    • In the Common Tasks pane, click Deploy Template.
    • In the Compute Pools pane, right-click the compute pool that has the target devices, and then click Deploy.
    The Deploy Template Wizard wizard is displayed.
  3. On the Name and Deploy Options page:
    1. Enter an appropriate name for the task.
    2. Under Deploy Target, select Bare Metal.
    3. Under Select Deploy Options, select Deploy Template.
      • NOTE: If you want to deploy a configuration template and then boot the device to a network ISO image, you can select both Deploy Template and Boot to Network ISO. Separate tasks are created for each operation.
    4. Click Next.
  4. On the Select Template page:
    1. Based on the target device type, click Server Template or Chassis Template.
    2. Select the configuration template you want to deploy.
      • NOTE: Only configuration templates that you have either created or cloned are available for selection.
    3. Click Next.
  5. On the Select Virtual I/O Pool page, click Next.
  6. On the Select Devices page, select the target devices from the Repurpose and Bare Metal Devices tree, and click Next.
    • NOTE: Only devices added to the repurpose and bare-metal group that are not assigned to a compute pool are available for selection.
  7. On the Edit Attributes page:
    • NOTE: OpenManage Essentials does not include any passwords from the source when the configuration template is created. If you want to set the passwords for the target devices, all password attributes must be edited in the configuration template before deployment. If you want to change the password, ensure to run the deployment task as a different user. If you are changing the password of the device through the deployment, ensure that you run the deployment task with a different user account.
    1. Click the Template Attributes tab.
    2. Click the attribute group name to view the list of attributes in a group.
    3. If you do not want to deploy a particular attribute in the template and want to retain the current attribute value on the target device, clear the check box in the Deploy column.
    4. Edit or select the values in the Value column based on your preference. The total number of attributes in the template and the number of attributes that you edit are displayed in the Grouped by bar.
    5. Click Save.
    6. Click the Device Specific Attributes tab to edit the attributes that are unique for the target device.
      • NOTE: The Device Specific Attributes tab may or may not display attributes based on the template selected for deployment.
    7. Click the attribute group name to view the list of attributes in a group.
    8. To assign a new Static IPv4 Address for the deployment, enter the Static IPv4 Address in the Value column of IPv4Static 1 IPv4 Address attribute.
      • NOTE: Deploying the template with the changed Static IPv4 Address initiates a new discovery task for the device. For more information on the task details, see Task Status. The new Static IPv4 Address is added to the discovery range under Manage > Discovery and Inventory > Discovery Ranges > All Ranges .
      • NOTE: If Static IPv4 Address is used in the deployment of a chassis template, then all the components in the chassis are rediscovered after the deployment task is completed.
      • NOTE: If Static IPv4 Address is provided and the DHCP attribute is enabled, then the DHCP settings take precedence over the provided Static IPv4 address. Similarly, If Static IPv4 Address is provided and the DHCP attribute is disabled, then the Static IPv4 Address is used for the template deployment.
    9. If you do not want to deploy a particular attribute in the template and want to retain the current attribute value on the target device, clear the check box in the Deploy column.
    10. Edit or select the values in the Value column based on your preference.
    11. Click Save.
    12. (For IOA VLAN configuration deployment only) Click the IOA VLAN Attributes tab to view the IOA VLAN attributes for the selected template.
    13. Click Next.
  8. On the Set Schedule page:
    1. Select either Run now, or click the calendar icon and select the date and time you want to run the task.
    2. Under Execution Credentials:
      • For server configuration deployment — type the credentials that have Administrator privileges on the iDRAC of the target servers.

      • For chassis configuration deployment — type the credentials that have Administrator privileges on the CMC of the target chassis.

    3. (Only for IOA VLAN configuration deployment) Under IOA Credentials, type the credentials that have Administrator privileges on the IOA.
    4. Click Next.
  9. On the Preview page:
    1. Optional: Click Preview to verify if the attributes of the device configuration template will be deployed successfully on the target devices.
    2. Click Next.
  10. On the Summary page, review the information that you have provided, and then click Finish. The Deploy Template warning is displayed.
  11. If you want to continue the deployment, click Yes.

The Deploy Template task is created and run based on the schedule you have selected. You can double-click the task in Task Execution History to view the task execution details.

The Deploy Template task fails if:
  • The file share setting is not enabled for servers with unsupported firmware versions installed.
  • The streaming functionality is disabled on target servers and if the file share setting is not enabled on OpenManage Essentials.
  • NOTE: In OpenManage Essentials 2.5, the device configuration deployment by using the streaming functionality is taking longer than deploying by using the file share setting. The following table lists the time taken for the device configuration deployment tasks to complete in an environment with 1–100 devices by using the file share and streaming functionality:
    Table 1. Time taken by the device configuration deployment task. Table listing the time taken for deploying the device configuration by using the file share and streaming functionality.
    Number of device(s) Time required for configuration deployment by using the file share and iDRAC 2.41.40.40 when... Time required for configuration deployment by using the streaming functionality and iDRAC 2.52.52.52 when...
    Devices are turned off Devices are turned on Devices are turned off Devices are turned on
    1 2 minutes 30 seconds 1 minute 50 seconds 5 minutes 40 seconds 2 minutes 10 seconds
    50 2 hours 1 hour 30 minutes 3 hours 2 hours
    100 5 hours 20 minutes 3 hours 40 minutes 7 hours 4 hours 30 minutes

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\