Users Guide
Viewing all settings
The View All Settings page displays all the component settings used to configure the resources in the deployment of the service.
• For more details about the Application properties, see Application Settings.
• For more details about the Virtual Machine properties, see Virtual Machine Settings.
• For more details about the Cluster properties, see Cluster Settings.
• For more details about the Server properties, see Server Settings.
• For more details about the Storage properties, see Storage Settings.
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, 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 pre-requisites
• 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 to 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 links
Migrating servers
Migrating servers
NOTE: Standard users can migrate the servers that are part of the server pool for with they have permission.
You can migrate only one server at a time. However, after a successful migration, extra servers can be migrated. During migration,
ASM tries to identify an exact match for the hardware. If it is not available in the server pool, a different hardware can be selected.
You may encounter some issues during configuration of the new servers. In such scenarios, you can address the issues preventing
the proper configuration of the target server, and retry the deployment.
To migrate a server’s configuration to a different server pool:
1. On the Service Details page, perform one of the following actions:
• In the topology view, click a server component, and click Migrate in the box that is displayed
• In the topology view, click a server component, and click Migrate in the right page.
2. In the Migrate Server(s) dialog box, in the State column, select the server, and then in the New Server Pool column, select
the designated server pool to migrate.
26