- Notes, cautions, and warnings
- Overview
- Getting started with ASM 8.2
- Initial Setup
- Dashboard
- Services
- Deploy Service
- Add existing service
- Viewing Service Details
- Editing service information
- Deleting service
- Exporting service details
- Retry Service
- View All Settings
- Migrating servers (service mobility)
- Migrating servers
- Upgrade Components
- Adding components to an existing service deployments
- Deleting resources from service
- 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
- Adding New Interface
- Server (OS Installation only) Component Setting
- Importing from existing template
- Uploading Server Configuration Profile
- Cluster
- Cluster component settings
- Virtual Machine
- Application
- VMware vSAN
- Sample templates
- Template — deploy Citrix XenDesktop for 500 users
- Template – deploy operating system to hard drive
- Template — deploy virtual machines to cluster
- 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 SQL Server 2012
- Template-deploy Hyper-V Cluster with iSCSI Storage To SCVMM
- Template-deploy VMware Cluster with FC Storage
- Template-deploy VMware Cluster with FCoE Storage
- Template-deploy VMware Cluster with iSCSI Storage
- Template-deploy VMware Cluster with iSCSI Storage Using Software Initiator
- Template-deploy VMware VSAN with Virtual Distributed Switch
- Application component settings
- Component combinations in templates
- Additional template information
- Manage templates
- Resources
- Resource health status
- Resource operational state
- Port View
- Resource firmware compliance status
- Updating firmware
- Removing resources
- 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
- Updating resource inventory
- Viewing resource details
- Understanding server pools
- Settings
- Add-On Modules
- Backup and restore
- Credentials management
- Getting Started
- Application logs
- Networks
- Repositories
- Jobs
- Users
- Virtual appliance management
- Virtual identity pools
- Troubleshooting
Velkommen
Dell-websteder
Dell-websteder
Velkommen hos Dell
Min konto
- Afgiv ordrer hurtigt og nemt
- Se ordrer og spor status for din forsendelse
- Opret og få adgang til en liste med dine produkter
- Administrer dine Dell EMC-websteder, -produkter og -kontaktpersoner på produktniveau ved hjælp af Company Administration (Virksomhedsadministration).
Active System Manager Release 8.2 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
Angiv vurderinger (1-5 stjerner).
Angiv vurderinger (1-5 stjerner).
Angiv vurderinger (1-5 stjerner).
Angiv, om artiklen var nyttig eller ej.
Kommentarer må ikke indeholde følgende specialtegn: <>()\