4.1.10 Migrating the DAMP Server

Perform the below steps to migrate 8.6.X DAMP BM to 9.0.X VM.

Note:

This procedure can be performed on 20% of DAMPs at once.
  1. Remove DAMP from topology.
    1. Log in to Active NOAM DSR GUI.
    2. Navigate to Status & Manage from Main Menu, then select HA.
    3. To change HA state of DAMP to Out of Service (OOS), perform the following steps:
      1. To change DAMP HA state to OOS, perform the following steps:
        1. Navigate to Status & Manage from Main Menu, then select HA.
        2. Click Edit and change Max Allowed HA Role of DAMP to OOS.
      2. To remove the DAMP instance from DAMP Server group, perform the following steps:
        1. Navigate to Configuration from Main Menu, then select Server Groups.
        2. Select DAMP (Level C) Server Group and click Edit.
        3. Uncheck the required DAMP instance from Server Group and click OK.
      3. Navigate to Configuration from Main Menu, then select Servers. Then, select the DAMP instance which was removed from server group in last step and click Delete.
  2. Shut down DAMP by running the following command:
    sudo shutdown -h now
  3. Install OL8 and KVM on the shutdown BM server.
  4. Create vDSR 9.0.1.

    Note:

    Create DAMP on the same host where NOAM, SOAM VM was created.
  5. Assign XMI IP to new vDSR 9.0.1.
    To configure netmask and XMI IP address values, run the following command:
    sudo /usr/TKLC/plat/bin/netAdm set --onboot=yes --netmask=<netmask> --device=eth0 --address=<IP address>
  6. Log in to DSR Active vDSR 9.0.1 NOAM using XMI.
  7. Navigate to Configuration from Main Menu, then select Servers.
  8. Click Insert.
  9. Add the following details for DAMP server:
    • Enter DAMP hostname
    • Update Role as MP
    • Hardware Profile as DSR Guest
    • Configure XMI and IMI, XSI IP's and NTP server IP
  10. Click Ok.
  11. Select the required DAMP server (which was created in the previous step).
  12. Click Export, to export server configuration file to the file management folder on the Active NOAM.
  13. Now ssh to Active DSR 9.0.X NOAM and copy the TKLCConfigData.<hostname>.sh file to the DAMP. After copying the file wait for 5 minutes.
    cd $FILE_MGMT_AREA
    sudo scp TKLCConfigData.<hostname>.sh admusr@<XMI IP of newly added vDSR DAMP>:/var/tmp/TKLCConfigData.sh
  14. ssh to DAMP XMI IP and verify the /var/TKLC/appw/logs/Process/install.log log file for successfully running of TKLCConfigData.sh file. You can run following command to check logs.
    sudo tail -f /var/TKLC/appw/logs/Process/install.log
    Output:
    + sed -i s/WALLET_KEY_TO_BE_REPLACED_DURING_SERVER_EXPORT/bc332acff044aa6bcc7871c0742b0b89abd658efc23549acc70d857279a1ee3bb31e04f2e85fcc50fe2fad0c6aa69d3596ecb68f84983b44d7805d98a994ad96/g/usr/TKLC/appworks/prod/maint/loaders/install/postInstall/load.AppworksSecConfig
    + /usr/sbin/chpasswd
    ++ aw.wallet credential get tpdProvd tpdProvd
    + /usr/TKLC/appworks/sbin/updateMylogincnf
    Imysql: [Warning] Using a password on the command line interface can be insecure.
    Imysql: [Warning] Using a password on the command line interface can be insecure.
    + pm.kill apwSoapServer cmsoapa
    + /bin/touch /var/TKLC/appw/TKLCinitcfg
    + /bin/sleep 1
    [SUCCESS] script completed successfully!
  15. Wait for 10 minutes for server to configure with the IP configuration, then reboot the VM using sudo init 6 command on CLI.
  16. Log in to Active vDSR NOAM GUI.
  17. Navigate to Configuration from Main Menu, then select Server Groups.
  18. Select the DAMP (Level C) Server group and click Edit.
  19. Select the DAMP instance, which was added while updating DAMP server details, to add to the DAMP Server group. Click Ok to save the changes and wait for 5 minutes.
  20. If the Max Allowed HA Role of that DAMP instance, which was added to server group in previous step, is not Active then navigate to Status & Manage from Main Menu. Then, select HA and change Max Allowed HA Role of DAMP to Active.
  21. ssh to newly added vDSR 9.0.X DAMP.
  22. Run the following commands to disable the upgrade barrier feature:
    iset -fvalue=1 IdbParamDef where "param='IdbDisableUpgBarrier'"
    sudo init 6
  23. Log in to Active vDSR NOAM GUI.
  24. Navigate to Status & Manage from Main Menu, then select Server and select the newly added DAMP instance. Click Restart.
  25. Run following command on DAMP:
    /usr/TKLC/dsr/bin/updateConfigData 8.6

    Note:

    • Ignore the following error while running on DAMP error:
      "disallowed write on replicated table"
    • To configure remaining DAMPs, repeat procedure Migrating the DAMP Server for each 20% of DAMP until you reach 100% of DAMP server.
    • DAMP leader must be migrated last. DC and MP leaders should not be planned in the same migration cycle.