Users Guide

Table Of Contents

• 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 congure a server pool that has servers with same model, RAID, and networking devices, including the

specic slot to which network resources are connected.

Related links

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 dierent hardware can be selected.

You may encounter some issues during conguration of the new servers. In such scenarios, you can address the issues preventing

the proper conguration of the target server, and retry the deployment.

To migrate a server’s conguration to a dierent 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.

NOTE: When you boot from SAN, you always get a migrate option on Service Details page. Migrate is not available

for any other type of deployment so in that case, you do not get Migrate Server option Service Details page.

Upgrading components

If an upgrade to ASM has added new required elds to components within the template from which the service was deployed, the

Upgrade Components button is displayed. While this action is not mandatory, certain service or resource functions are not available

until this upgrade has been completed.

Click on the Upgrade Components button to launch the Update Service Component window. Fields in this window vary depending

on which components contain newly required settings. Complete all the displayed elds. Click Save.

Adding components to an existing service deployment

After a successful service deployment, you can add one or more application, storage, server, cluster, and virtual machine

components to an existing service.

NOTE: Standard users are allowed only to add components to a service for which they have permission.

NOTE: You can add components even if they are currently not in the template. For example, if you have storage, server

and cluster, you can still add VM.

NOTE: You can add components to a service for which deployment is successful or to a failed service deployment.

To add components to a service:

1. On the home page, click Services.

The Services page is displayed.

2. Select a service and click View Details in the right pane.