Users Guide
Table Of Contents
- Active System Manager Release 8.3.1 User’s Guide
- Overview
- Getting started with ASM 8.3.1
- Initial Setup
- Dashboard
- Services
- Deploying service
- Add existing service
- Viewing service details
- Editing service information
- Deleting service
- Exporting service details
- Retrying service
- Viewing all settings
- Migrating servers (service mobility)
- Migrating servers
- Upgrading components
- Adding components to an existing service deployment
- Deleting resources from service
- Templates
- Managing templates
- Viewing template details
- Creating template
- Editing template information
- Building template overview
- Building and publishing template
- Importing template
- Exporting template
- Uploading external template
- Editing template
- Viewing template details
- Deleting template
- Cloning template
- Deploying service
- Deploying multiple instances of service
- Adding Attachments
- Decommissioning services provisioned by ASM
- Component types
- Component combinations in templates
- Additional template information
- Managing templates
- Resources
- Resource health status
- Resource operational state
- Port View
- Resource firmware compliance status
- Updating firmware
- Removing resources
- Viewing firmware and software compliance report
- Discovery overview
- Configuring resources or chassis
- Removing discovered resources
- Configuring default firmware repository
- Running firmware compliance
- Configuring global chassis settings
- Configuring unique chassis settings
- Configuring unique server settings
- Configuring unique I/O module settings
- I/O module configuration
- Completing the chassis configuration
- Adding or editing Chassis Management Controller (CMC) user
- Adding or editing Integrated Dell Remote Access Controller (iDRAC) user
- Updating resource inventory
- Viewing resource details
- Understanding server pools
- Settings
- Troubleshooting

NOTE: Initially, a newly created or a cloned template appears in a Draft state on the Template page and remains in the
same state until published.
The following component types can be congured in a template:
• Storage
• Server
• Cluster
• Virtual Machine
• Application
NOTE: While building a template, it is recommended to rst provision the physical resources, then congure virtual
resources and lastly congure application settings to be deployed on the resources.
On this page, you can:
• Build and Publish a template
• Delete a Template
• Import a Template
• Deploy a Service
NOTE: The Deploy Service functionality is applicable only on published templates.
Related links
Building and publishing template
Building and publishing template
After creating a template using the Create Template dialog box, to start building a customized template using the Template Builder
page, perform the following steps:
1. To add a component type to your template, click the respective component icon on top of the Template Builder.
The corresponding <component type> component dialog box is displayed.
2. From the Select a Component drop-down list, select the component that you want to add.
3. In the # of Instances box, enter the number of component instances that you want to include in a template.
4. Under Associated Resources, perform one of the following actions:
• When you are adding a new component to a template, if you want to associate the component with all the existing
components, click Associate All resources.
The new component automatically associated with the existing components.
• When you are adding a new component to a template, if you want to associate the component only with the selected
components, click Associate Selected Resources, and then select the components to associate as needed.
Based on the component type, specic settings and properties appear automatically that are required and can be edited. For
more information about the specic component type settings, see Component Types.
5. Click Add to add the component to the Template Builder.
6. Repeat the steps 1 through 5 to add multiple components.
7. After you complete adding components to your template, click Publish Template. Publishing a template indicates that a
template is ready for deployment.
If a template is not published, it cannot be deployed and remains in the Draft state until published.
8. After publishing a template, you can use the template to deploy a service in the Services page.
35