Users Guide

Retry Service

You can redeploy a service for which deployment is not successful due to some issues.

NOTE: Standard users can only redeploy a failed service that they have deployed.

1. In the left pane, click Services.

The Services page is displayed.

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

The Service Details page is displayed.

3. In the right pane, under Service Actions, click Retry.

Click Yes when a confirmation message appears.

View 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, 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.