4.2 When Migration to 3.2 Access Manager Terminates Abruptly

The 3.2 migration may terminate due to any reason such as network issue. In such cases, re-run the migration after cleaning up partly installed components as in the following procedure:

To workaround this issue, perform the following steps to cleanup before re-running the install_and_migrate script:

  1. Ensure that the 3.1 SP4 machine remains as master replica

    1. In the 3.1 SP4 machine, run the ndsrepair -P -Ad command.

    2. Enter 1 and press Enter.

    3. Enter 5 and press Enter.

  2. Restore certificates back to 3.1 SP4.

    1. In the 3.1 SP4 machine, go to /opt/novell/devman/bin, then run the aminst-certs.sh script.

    2. Enter the credentials and path for the backup file that was originally taken.

  3. Remove the failed server.

    1. In the new 3.2 machine, run the following command:

      /opt/novell/eDirectory/bin/ndsconfig rm /etc/opt/novell/eDirectory/conf/nds.conf

    2. Enter the admin credentials in the admin.novell format and proceed with deletion.

  4. In the new 3.2 machine, uninstall the Novell Access Manager binaries.

    1. From the novell-access-manager folder, run the./uninstall.sh script.

    2. Select the option 5 and proceed.

    3. Delete the migrate_inputs.sh script under scripts folder.

  5. Delete objects from the eDirectory Configuration Store.

    1. Log in to the 3.1 SP4 Administration Console, then click Auditing > Troubleshooting.

    2. In the Other Known Device Manager Servers section, select the failed primary Administration Console.

    3. Click Remove.

      Few objects in eDirectory require to be deleted. Sometime manual deletion could lead to errors. It is recommended to take a backup of entire eDirectory before you delete the objects.

      Run the following command to back up the eDirectory objects:

      ndsbackup cvf ndsbackupfile -a <user id like admin.novell> -p <password>

      In case of any issue due to manual delete, you can restore the same by running the following command:

      ndsbackup xvf ndsbackupfile

    4. To delete the objects in eDirectory, select View Objects from the iManager menu bar.

    5. In the Tree view, select novell and view the objects.

    6. Delete all objects that refer to the failed primary console. You should find the following types of objects:

      • SAS Service object with the host name of the failed primary console

      • An object that starts with the last octet of the IP address of the failed primary console

      • DNS AG object with the host name of the failed primary console

      • DNS IP object with the host name of the failed primary console

      • SSL CertificateDNS with the host name of the failed primary console

      • SSL CertificateIP with the host name of the failed primary console

      NOTE:You must follow the procedure irrespective of where the migration terminated to ensure that the machine is clean.

  6. On the 3.1 SP4 machine, run the /opt/novell/eDirectory/bin ndsstat -r command to verify if there are any replicas in eDirectory caused due to failure while migrating. Ensure that you remove them.

  7. In the 3.2 machine, run the install_and_migate_3.2.sh script the novell-access-manager folder and proceed with the installation steps.