Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Upgrade Procedure

You must reset the disaster recovery configuration on both the active and the standby sites to stop the disaster recovery process and clean up the disaster recovery configuration from both the sites. You can upgrade the Junos Space Platform software at both the active and the standby sites at the time of deployment. Since the disaster recovery upgrade procedure is time consuming, we recommend you to reset the disaster recovery configuration and upgrade the sites to the required version.

The upgrade procedure comprises of the following tasks:

  1. Back up the Current Disaster Recovery Configuration

  2. Reset the Disaster Recovery Configuration

  3. Upgrade the Junos Space Network Management Platform and Application

  4. Configure and Perform Disaster Recovery

1. Back up the Current Disaster Recovery Configuration

Backup the current disaster recovery configuration on both the sites to refer the parameters when configuring the disaster recovery again after upgrade. Run the following command to create a backup for current configuration on both sites:

$ jmp-dr api v1 config --include role,failover,states,core,deviceManagement,mysql,pgsql,file,watchdog > /home/admin/dr-config.txt

Note:

Enter the following command in a separate shell prompt on the VIP nodes of both the sites to check log errors:$tail-f /var/log/jmp-geo/dr-cli-reset.log

2. Reset the Disaster Recovery Configuration

Reset the current disaster recovery configuration to ensure that both the active and the passive sites refer to the same parameters, when you configure the disaster recovery, post the upgrade.

Execute the following command to create a backup for the current configuration.

$ jmp-dr api v1 config --include role,failover,states,core,deviceManagement,mysql,pgsql,file,watchdog > /home/admin/dr-config.txt

Execute the following commands to reset disaster recovery on both sites running the jmp-dr reset commands on VIP nodes of both sites.

After executing this commands, the sites become standalone sites. Junos Space Platform comes up and you can access the UI from both the sites.

3. Upgrade the Junos Space Network Management Platform and Application

You can upgrade the Junos Space Platform and the application on both the active and the standby sites simultaneously, as both the sites are in standalone mode.

To upgrade the Junos Space Network Management Platform:

  1. Login to the Junos Space Network Management Platform.

    The dashboard appears.

  2. Upload the software image to the active and standby sites.
    1. Select Network Management Platform from the Applications drop-down menu.
    2. Click Upgrade.

      The upgrade window appears.

    3. Upload the image.
      Note:

      The system takes approximately 5 minutes to upload the new image. Enter the following command in a separate shell prompt at each node of current active and standby sites to check the logs for errors.

      $tail-f /var/log/install.log

  3. Upgrade the Junos Space software at the active and standby sites.

    Reboot occurs as part of post upgrade.

    1. Select Network Management Platform > Administration > Application > Network Management Platform.
    2. Click Upgrade.

      The upgrade window appears.

    3. In the Upload Platform menu, select the specific row and click Upgrade.

      The maintenance mode screen displays the upgrade progress. The reboot screen appears, once the upgrade is completed.

      Note:

      Type the following command in the separate shell prompt on each node of current active and standby sites to check the error logs.

      $tail-f /var/log/install.log .

      Note:

      Type the following command in a separate shell prompt at each node on the active and standby sites to check the upgrade progress.

      $tail-f /var/jmp_upgrade/slave/log/<oldRelease_newRelease>

    4. Click Reboot.

      The nodes starts to reboot.

      Note:

      Execute the following command to check for boot to complete.

      $tail -f /tmp/systemStartup.log

      Log Example:2018/03/07 10:05:51.207 Appmgt is now deploying ... [ 9 of 9 ] 2018/03/07 10:05:57.607 Appmgt

  4. Upload the Junos Space application in active and the standby site.
    1. Select Network Management Platform > Administration > Application ><application-name>> Upgrade > Action.
    2. Click Upload.

      The upload window appears.

    3. Upload the selected Junos Space application.
      Note:

      Enter the following command in the separate shell prompt on each node of current active and standby sites to check the logs for errors.

      $tail-f /var/log/install.log

  5. Upgrade the Junos Space application in the active and standby site.
    1. Select Network Management Platform > Administration > Application ><application-name>> Upgrade > Action.
    2. Click Upgrade.

      The Upgrade window appears.

    3. In the Upgrade Application menu, select the specific row and click Upgrade.
      Note:

      Enter the following command in a separate shell prompt on each node of current active and standby sites to check the logs for error.

      $tail-f /var/log/install.log

    4. Select Network Management Platform > Administration > Application.

      The Application window displays the expected upgrade version.

4. Configure and Perform Disaster Recovery

Note:

This is an optional procedure. If you plan to configure multiple upgrade paths: upgrade the Junos Space Network Management Platform and the application to the required version, before you configure disaster recovery.

To configure and start the disaster recovery process on both the active and the passive sites:

  1. Configure the disaster recovery process.
    1. Execute the following command in the VIP node of active site to configure disaster recovery.
    2. Execute the following command in the VIP node of standby site to configure disaster recovery.
    Note:

    Ensure that you initialize the disaster recovery process on the standby site, only after the disaster recovery initialization is complete on the active site. For more information about configuring the disaster recovery process, see Configuring the Disaster Recovery Process Between an Active and a Standby Site.

  2. Execute the following command to start the disaster recovery process from the active site.
    Note:

    Execute the following command in the separate shell prompt on each of the VIP nodes of the site to check the logs for errors.

    If the standby node is not updated, stop and the start the disaster recovery process over again.

    Execute the command again for verify the update.

  3. Execute the following command to check the disaster recovery process health:

    Note:

    Execute the following command in a separate shell prompt on each site VIP nodes to check the logs for errors:

  4. Execute the following command to stop the disaster recovery process on both the sites from the active site:
    Note:

    Execute the following command in the separate shell prompt on each VIP nodes of the site to check the logs for errors:

  5. Execute the following command on the current standby site, to verify the functionality on standby site by manually fail-over from active site:
    Note:

    Execute the following command in the separate shell prompt on VIP node of the standby site to check the logs for error:

    Note:

    Execute the following command to verify is the application starts normally, by checking the JBoss log:

    The Application page shows the upgrade version.

  6. Execute the following command on the current standby site VIP node to apply manual fail-over to the active site from the standby site:
    Note:

    Execute the following command in the separate shell prompt on VIP node of the current standby site to check the logs for errors.

    Note:

    Execute the following command to check for the application start by checking the JBoss log:

  7. Execute the following command to check the disaster recovery health on both the sites.
    Note:

    Execute the following command in the separate shell prompt on each VIP nodes of the site to check the logs for errors.

  8. Execute the following command to start the disaster recovery process on both the sites from active site.
    Note:

    Execute the following command in the separate shell prompt on each VIP nodes of the site to check the logs for errors.

  9. Execute the following command to check the disaster recovery process health on both sites.
    Note:

    Execute the following command in the separate shell prompt on each VIP nodes of the site to check the logs for errors.

Related Documentation