ISIM Server does not start on the new primary or backup node

ISIM Server does not start on the new primary or backup node, which was made by applying a snapshot of the primary node.

Problem

After you apply the snapshot of the primary node on the backup node, ISIM Server on the new primary node does not start.

Symptom

When you log on to the new primary or backup node, the Server Control widget displays the status of ISIM Server as Stopped.

Diagnosing the problem

1. Set up a primary node and make sure that its activation is completed.
2. Set up another node as a backup of the primary node. The backup node must be in a different subnet than the primary node.
3. After we create the snapshot of the primary node on the backup node, apply the snapshot on the new primary or backup node.
4. Restart the new primary node.
5. Observe that ISIM Server is not running on the new primary node.

6. From the Server Control widget on the Appliance Dashboard, click Start to start ISIM Server on the new primary node.

The ISIM Server does not start.

Resolving the problem

Make sure that the backup node is in the same subnet as the primary node. For subnet information, see Set up the initial IBM Security Identity Manager virtual appliance.

Parent topic: Troubleshooting virtual appliance problems