User's Manual
Table Of Contents
- Contents
- About This Guide
- Chapter 1
- Active System Manager Overview
- Chapter 2
- Getting Started
- Chapter 3
- Account Management
- Chapter 4
- User Profile Management
- Managing Security Functions
- Managing Groups
- Defining Permissions
- Modifying Permissions
- Managing Authentication Repositories
- Chapter 5
- Inventory Management
- Understanding Resource Modeling
- Building a Standard Active System Manager Inventory
- Configuring Discovery Setup
- Running Discovery
- Using Resource Types
- Using Resource Instances
- Building Resource Instances
- Modifying Core Properties for Resource Instances
- Modifying Resource Instance Resource Availability Dates
- Modifying Resource Instance Interfaces
- Displaying the Resource Availability Calendar View
- Deleting Resource Instances
- Setting Inventory Parameter Values
- Resolving Resource Dependencies
- Using Resource Interface Types
- Linking Resources
- Importing Inventory
- Importing Connectivity
- Exporting Connectivity
- Managing Resource Pools
- Managing Maintenance Windows
- Managing Virtual Resources
- Chapter 6
- Firmware Management
- Creating Active System Manager Software Repositories
- Updating Dell Chassis Firmware from the Operations Center
- Updating Dell Server Firmware
- Updating Dell Blade/Rack Servers Firmware from the Operation Center
- Updating Dell Blade/Rack Servers Firmware from an Active Session
- Updating Dell Blade/Rack Servers Firmware Using the Attach Server Profile Virtual Operation
- Updating Dell Blade/Rack Servers Firmware through an Orchestration
- Updating Dell Blade/Rack Servers Firmware Using the Attach Server Profile Custom Operation
- Minimum Firmware Versions for Active System Manager Components
- Chapter 7
- Server Template and Profiles
- Creating a Server Template
- Editing a Server Template
- Adding or Editing BIOS Information on a Server Template
- Adding or Editing RAID Information on a Server Template
- Adding or Editing Firmware Settings on a Server Template
- Adding or Editing Networks Settings on a Server Template
- Naming Conventions when using Orchestrations
- Server Profiles
- Chapter 8
- Using Inventory
- Chapter 9
- Repository Management
- Chapter 10
- Network Management
- Chapter 11
- Template Management
- Template Types
- Working with Templates
- Creating New Templates
- Saving Templates
- Changing Template Ownership and Permissions
- Opening Templates
- Closing Templates
- Deleting Templates
- Managing Template History Details
- Filtering Templates
- Validating Templates
- Importing Templates
- Exporting Templates
- Attaching a Template Image
- Scheduling Templates
- Archiving Templates using the Templates View
- Restoring Archived Templates
- Updating Templates using the Template Editor
- Viewing and Modifying Template Properties
- Adding Resource Types
- Setting Resource Type Properties for Scheduling
- Deleting Resource Types
- Adding Resource Types Based on Manufacturer Only
- Adding Resource Instances
- Modifying Resource Properties
- Deleting Resource Instances
- Defining Provisioning Policies
- Supporting Layer 2 Switching
- Using Annotations
- Updating Templates using the Link Editor
- Associating an Orchestration Workflow with Templates
- Chapter 12
- Session Management
- Introducing the Sessions Perspective
- Working with Running Sessions
- Scheduling a Session Using Templates
- Creating an Instant Session
- Opening Sessions
- Opening the Session Editor
- Using the Sessions Calendar
- Viewing Session Properties
- Editing Default Session Properties
- Assigning and Changing Session Ownership
- Canceling Sessions
- Deleting Sessions
- Purging Sessions
- Rescheduling Sessions
- Managing Session Links
- Handling Link Preemption
- Managing Session Resources
- Associating Scripts to Sessions
- Archiving Sessions
- Supporting Layer 2 Switching
- Saving Sessions
- Configuring Session Notifications and Reminders
- Starting and Stopping ASAP Rescheduling
- Managing Virtual Resources
- Chapter 13
- Orchestration Management
- Chapter 14
- Working with Test and Script Execution
- Chapter 15
- Reports
- Chapter 16
- Settings
- Chapter 17
- Dashboard
11-4 Active System Manager User Guide, Release 7.1
Linking Editor
The first step in the workflow consists of connecting raw blades and L2 matrix switch in the linking editor.
Creating a Physical Template
The next step consists of dragging and dropping the managed devices in the Template editor to provision
Hypervisors. You are also required to drag some VLAN components in the Template editor and assign some
VLAN ID range to it or auto schedule it. Then, connect managed devices to VLAN component.
Note The managed devices to be used in the Physical template should not be shared. This is because the
device being provisioned with a Hypervisor in a session, should not be used in another session.
For more information, see the “Creating New Templates” section on page 11-6.
Creating Orchestration for Provisioning
In the next step, create a Setup type orchestration, to be mapped to the Physical template. The steps to create
orchestration are as follows:
• Create clusters on the vCenter.
• Create a Hypervisor on the blades.
• Register Hypervisors with the vCenter.
• Add hosts to the cluster created.
• Run discovery to populate the Active System Manager inventory (vCenter discovery) with cluster
entities.
Scheduling Template to Create a Session
The next step consists of scheduling Template to create a session.
Note The session scheduled from the Physical template is of permanent type.
If the session scheduled from a Physical template is being used by the system to realize a Logical
template (in present/future), and if the user cancels the physical session, then the system throws an
error message.
Provisioning
To provision Hypervisors and clusters, the Resource Adapters are required. To achieve this, a series of
Setup orchestration steps are configured. In the session provisioning parameter, the RA adds cluster or
independent Hypervisor’s assettag [cluster=cluster1,cluster2 hypervisor=hypervisor1,hypervisor2].
Logical Template
The Logical template is used to provision virtual machines (VMs) on Hypervisor or cluster from sessions
created from the physical template. It is also used to provision the VLAN component from VLAN range
given in the Physical template.
Note The difference between the Logical and Normal template is that, the Logical template is realized
upon a Physical template based session.