Assign one or more target devices so the appliance automatically deploys templates on them. Target devices can be specified by using their Service Tag, IDs, or importing a CSV file.
Prerequisites
To perform any tasks on OpenManage Enterprise, you must have necessary role-based user privileges and scope-based operational access to the devices. See
Role and scope-based access.
To auto deploy a template with custom telemetry configuration, ensure that the server has a valid iDRAC DataCenter license and the iDRAC firmware is 4.40 and above.
Steps
Click
Configuration > Auto Deploy > Create
The Auto Deploy Template wizard is displayed.
On the
Template Information screen, select the deployment template type (Server or Chassis).
From the
Select Template drop-down menu, select an appropriate template. If the selected template has identity attributes which are not associated with any virtual identity pool, the following message is displayed:
The selected template has identity attributes, but it has not been associated with a virtual identity pool. Deploying this template will not change virtual network addresses on the target devices.
Click Next.
The
Target Information screen is displayed.
On the
Target Information
screen, target devices can be selected in one of the following methods:
Enter Manually : Enter the Service Tag or node IDs to identify the target devices. The identifiers can be entered in any order, however, identifiers must be comma-separated. Click Validate to verify the accuracy of the values. It is mandatory to validate the identifiers.
Import CSV: Click
Import CSV to browse the folders and select the respective .csv file with the target device details. A summary of the number of successfully imported and invalid entries is displayed. For a more detailed view of the import result, click
View details. The entries in the CSV file must have the following format: The identifiers must be listed in the first column, one per row, starting from the second row. For a template CSV file, click
Download sample CSV file.
Click
Next.
On the
Target Group Information screen, specify a subgroup under the
Static group if available. For more information about grouping of devices, see
Organize devices into groups. The target devices would be placed under the specified target group on their discovery.
Click
Next.
If the target device is a server, on the
Boot to Network ISO screen :
Select the
Boot to Network ISO check box.
Select
CIFS or
NFS.
Enter the
ISO Path of location where the ISO image file is stored. Use tool tips to enter the correct syntax.
Enter
Share IP Address,
Workgroup,
Username, and
password.
Select the
Time to Attach ISO dropdown menu options to set the number of hours the network ISO file will remain mapped to the target device(s). By default, this value is set as four hours.
Click
Next.
On the
Virtual Identities screen, click
Reserve identities.
The assigned virtual identities of the NIC cards of the selected target device are displayed. To view all the assigned identities of the identity pool of the selected target device, click
View all NIC details.
In the
Target Attributes section, the non-virtual identity attributes specific to each of the selected target devices, such as the location attributes and IP address, can be changed before deploying the deployment template. When the template is deployed, these changed target attributes are implemented on only the specific devices. To change the device-specific, non-virtual identity attributes:
Select a target device from the list displaying the previously-selected target devices.
Expand the attribute categories and then select or clear the attributes that must be included or excluded during template deployment on the target device.
Click
Next.
Click
Finish.
An alert message
Deploying a template can cause data loss and can cause a restart of the device. Are you sure you want to deploy the template?
is displayed.
Click
Yes.
A new Auto Deploy target is created and listed on the
Auto Deploy screen.
NOTE: For templates with custom telemetry configuration, ensure that the device has a valid iDRAC DataCenter license. Otherwise, the job fails, and the task execution history shows the following:
#Attributes Failed to apply
CustomComponents - required license is missin or expired.
Data is not available for the Topic
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: <>()\