- Notes, cautions, and warnings
- Overview
- Getting started with ASM 8.1.1
- Initial Setup
- Dashboard
- Services
- Templates
- Manage templates
- Viewing template details
- Creating template
- Editing template information
- Building template overview
- Building and publishing template
- Importing template
- Export Template
- Upload External Template
- Editing template
- Viewing template details
- Deleting template
- Cloning template
- Deploying service
- Deploy Multiple Instances of Service
- Add Attachments
- Decommissioning services provisioned by ASM
- Component types
- Storage
- Storage settings
- Server
- Server settings
- Server (OS Installation only) Component Setting
- Configuring interface on rack servers
- Configuring Interface on Blade or FX Servers
- Importing Configuration from Reference Server
- Importing from existing template
- Uploading Server Configuration Profile
- Cluster
- Cluster component settings
- Virtual Machine
- Virtual Machine settings
- Application
- Application component settings
- Component combinations in templates
- Sample templates
- Template – deploy Citrix XenDesktop for 500 users
- Template – deploy operating system to hard drive
- Template – deploy physical server and virtual machine
- Template – deploying with Compellent iSCSI
- Template – deploy virtual machines to cluster
- Template – install ESXi to SD card with Fibre Channel storage
- Template – install ESXi to SD card with iSCSI storage
- Template – deploy Hyper-V host with iSCSI storage
- Template – deploy Hyper-V cluster with iSCSI storage
- Template – deploy Hyper-V cluster with Fibre Channel storage to SCVMM
- Template – deploy VMware cluster with NetApp storage
- Template – boot from Fibre Channel SAN
- Template – boot from iSCSI SAN
- Template – deploy virtual machine template clone on Hyper-V cluster
- Template – deploy virtual machine template clone on VMware cluster
- Template – deploy SQL Server 2012
- Additional template information
- Manage templates
- Resources
- Understanding
All Resources tab
- Resource health status
- Resource operational state
- Resource firmware compliance status
- Updating firmware
- Viewing firmware 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
- Removing resources
- Updating resource inventory
- Viewing resource details
- Understanding server pools
- Understanding
All Resources tab
- Settings
- Backup and restore
- Credentials management
- Getting Started
- Application logs
- Networks
- Repositories
- Jobs
- Users
- Virtual appliance management
- Virtual identity pools
- Troubleshooting
- LC operation times out while deploying server profile to a server
- Hyper-V host deployments using network storage only support certain configurations
- iSCSI storage network only support static IP addressing
- Unable to deploy a service for Compellent component with same server object and volume names
- Unable to deploy a service using the template with two EqualLogic CHAP components
- Unable to log in to ASM using active directory using “”
- Chain booting issue occurs while booting microkernel in a multi-hop DHCP environment
Active System Manager Release 8.1.1 User’s Guide
Migrating servers (service mobility)
In ASM, service mobility refers to the capability to migrate server’s BIOS, NICs, storage connectivity, and assigned identity information to another server in a designated server pool, in order to perform planned maintenance or service activities or to respond to a hardware fault or failure issue.
Currently, migration is supported only for boot form SAN server, and it is supported only for bare metal OS installs of Linux or Windows. It is not supported for ESXi. Therefore, the migration will not affect the virtual machines.
It is recommended only to migrate between identically configured hardware. Different operating systems may not boot correctly on hardware that is different.
Migration prerequisites
-
ASM does not install operating systems on the boot from SAN volume. Therefore, you must install operating system on the servers prior to migration.
-
Make sure that the free servers are available in the server pool for migration, and it is compatible.
-
During the migration, the operating systems will not be booted. Therefore, it is recommended to shut down the server before migrating the boot from SAN image.
-
It is recommended configure a server pool that has servers with same model, RAID, and networking devices, including the specific slot to which network resources are connected.
Related tasks
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: <>()\