Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Upgrade to Junos Space Network Management Platform Release 24.1R1

In Junos Space Network Management Platform Release 24.1R1, Rocky Linux release 9.2 (Blue Onyx) is used as the underlying OS. Direct upgrade of the OS from CentOS 7.4 (used in Junos Space Network Management Platform releases before 23.1R1) to Rocky Linux release 9.2 (Blue Onyx) is not supported. Also, direct upgrade to Junos Space Network Management Platform Release 24.1R1 by using the Junos Space Network Management Platform UI is not supported. You must follow a multi-step procedure to upgrade to Junos Space Network Management Platform Release 24.1R1.

Upgrading to Junos Space Network Management Platform Release 24.1R1 involves backing up data from Junos Space Network Management Platform Release 23.1R1, deploying Junos Space Network Management Platform Release 24.1R1 on the nodes, and restoring backed up data to the nodes. After Junos Space Network Management Platform is upgraded, you can upgrade previously installed Junos Space applications (Security Director).

Note:

For more information about upgrading to Junos Space Network Management Platform Release 23.1R1, see the Junos Space Network Management Platform Release 23.1R1 Release Notes.

Note:

Before backing up from Junos Space Network Management Platform Release 23.1R1, you must cleanup any large tables by purging the audit log and the job data from the GUI, to reduce the maintenance time during the upgrade.

To upgrade from Junos Space Network Management Platform Release 23.1R1 to Junos Space Network Management Platform Release 24.1R1, complete the tasks in the sequence below.

Before You Begin

Note:

This particular upgrade procedure is complex and requires switching between the Junos Space Network Management Platform GUI and the Junos Space Network Management Platform command line. In case of any issues, access to the hypervisor that hosts the Junos Space virtual machine may be needed. If you are not comfortable running Linux commands at the command line, or you do not have access to the virtual platform, the GUI, or the command line, request for the access through the appropriate internal channels, and have the required personnel available during the entire process.

Table 1 shows various network elements that are needed in order to perform this upgrade procedure.

Table 1: Items needed for upgrade

Item

Purpose

Comments

Access to the Junos Space Network Management Platform GUI using the super user’s credentials

To establish and confirm proper configuration, device connection, database state, and backup prior to the upgrade

 

Access to the Junos Space Network Management Platform command line using the admin user’s credentials over SSH (TCP port 22)

To run various scripts and Linux commands during the upgrade

Once authenticated over ssh, select the “(Debug) run shell” option from the menu. On a virtual appliance, (Debug) is option 7.

Access to a network secure copy protocol (SCP) server

To store the following files that are created as part of the backup created during this upgrade:

  • backupStatus.log

  • md5.txt

  • space-backup.tgz

  • space-readme.txt

SCP connections default to TCP port 22.

Ports other than TCP port 22 can be used for SCP, but the server must already be set to accept the connection on the non-default port.

Access to the hypervisor that hosts the Junos Space Network Management Platform VM (Virtual Machine)

To deploy the 24.1R1 ova file

 

Disable Device Communication

Before taking backup from the Junos Space Network Management Platform Release 23.1R1, disable device communication to ensure that the discovered devices stop communicating with the Junos Space Server.

To disable device communication:

  1. Select Administration > Applications.
  2. Click Network Management Platform and select Modify Application Settings from the Actions menu.

    You can also right click on Network Management Platform and select Modify Application Settings. The Modify Application Settings (Modify Network Management Platform Settings) page is displayed and by default, the Device section is selected.

  3. Uncheck the Allow Device Communication option.
  4. Select Modify to modify the settings.

    The discovered devices in Junos Space Network Management Platform stops communicating with the Junos Space Server.

Download and Install the Patch for any Release Prior to Junos Space Network Management Platform 23.1R1

Note:

Before you begin to upgrade any Junos Space Network Management Platform Release prior to Junos Space Network Management Platform Release 23.1R1 to Junos Space Network Management Platform Release 24.1R1, download and install the Junos Space Config Restore Patch for Upgrade to 24.1R1 from Junos Space Config Restore Patch for Upgrade to 24.1R1 on the Junos Space Network Management Platform – Download Software page.

To download and install the patch:

  1. Download the Junos Space Backup Restore Patch to your local computer from the following location:

    https://www.juniper.net/support/downloads/?p=space#sw

  2. Log in to the Junos Space Jboss VIP node as the admin user using SSH.
  3. Transfer the patch to the Junos Space node by using Secure Copy Protocol (SCP).

    For example, to pull the file from the SCP server to a temporary location, such as /tmp/patch on the Junos Space node, the commands would be:

    Create the temporary storage location on the Junos Space node:

    Pull the file from the SCP server located at IP address 192.0.2.10:

  4. Navigate to the location on the Junos Space node where you stored the patch.
  5. (Optional) To verify the checksum for the downloaded file, type the following command:

    The md5 hash value is displayed on the screen. Compare this value with the md5sum value available at the download site by clicking the MD5 SHA1 link.

  6. Extract the patch by using the following command:

    Extracting the patch creates a directory named SpaceConfigBackupRestore and puts the individual files in it, including the patch script, patchme.sh.

  7. Change directory into the new directory:
  8. Type the following command to install the patch:

    If the patch is successful, the message “Hot Patch installed Successfully” is displayed. Otherwise, error is displayed.

  9. Take a backup of the database from the Junos Space Network Management Platform GUI.

  10. To create a backup of the production configuration, run the following command sh /var/cache/space-backup-restore/backup.sh from CLI.

  11. Create a new single node Junos Space VM with a version same as your production version and install the same patch on it.

  12. After installation, run the sh /var/cache/space-backup-restore/restore.sh command and select the file generated from the backup in step 10.

    When the configuration is restored and the application is up, you can restore the database backup taken earlier and available under Database Backup and Restore in the Junos Space Network Management Platform GUI.

    Once the application is up after the database restore on the single node Junos Space VM, you can continue to upgrade till Junos Space Network Management Platform 23.1R1.

  13. To download and install the Junos Space Network Management Platform 23.1R1 patch, follow the steps mentioned in Download and Install the Junos Space Network Management Platform 23.1R1 Patch.

Download and Install the Junos Space Network Management Platform 23.1R1 Patch

Before you begin to upgrade Junos Space Network Management Platform Release 23.1R1 to Junos Space Network Management Platform Release 24.1R1, download and install the Junos Space Network Management Platform Release 23.1R1 patch from Junos Space 23.1R1 Backup Patch for Upgrade to 24.1R1 on the Junos Space Network Management Platform – Download Software page.

To download and install the patch:

  1. Download the Junos Space 23.1R1 Backup Patch for Upgrade to 24.1R1 patch to your local computer from the following location:

    https://www.juniper.net/support/downloads/?p=space#sw

  2. Log in to the Junos Space Jboss VIP node as the admin user using SSH.
  3. Transfer the patch to the Junos Space node by using Secure Copy Protocol (SCP).

    For example, to pull the file from the SCP server to a temporary location, such as /tmp/patch on the Junos Space node, the commands would be:

    Create the temporary storage location on the Junos Space node:

    Pull the file from the SCP server located at IP address 192.0.2.10:

  4. Navigate to the location on the Junos Space node where you stored the patch.
    1. (Optional) To verify the checksum for the downloaded file, type the following command:

      The md5 hash value is displayed on the screen. Compare this value with the md5sum value available at the download site by clicking the MD5 SHA1 link.

  5. Extract the patch by using the following command:

    Extracting the patch creates a directory named 23.1R1-SpaceUpgradeBackup and puts the individual files in it, including the patch script, patchme.sh.

  6. Change directory into the new directory:
  7. Type the following command to install the patch:

    If the patch is successful, the message “Hot Patch installed Successfully” is displayed. Otherwise, error is displayed.

  8. After successful installation of the hotpatch, if you want to continue to run the production on 23.1R1 you must restart the services and the Disaster Recovery (if configured).

    • To restart the services, run systemctl start jmp-watchdog command on all the nodes.

    • To restart the DR run jmp-dr start command on the VIP node of the active site.

Execute the Data Back Up Procedure

To back up Junos Space Network Management Platform and Junos Space Application data from the Junos Space nodes, execute the backup script, backup.sh that is provided by the 23.1R1 patch that you installed. The backup.sh script is stored in the directory /var/cache/space-backup-restore.

The backup script backs up the required configuration files, data files, from the Junos Space nodes. Data files of the installed Junos Space Applications are also backed up. The backup script generates a compressed tar file containing the backed up data. The following files are copied to a remote server:

  • space-backup.tgz

  • space-readme.txt

  • md5.txt

  • backupStatus.log

Warning:

For the upgrade process to succeed, the backup script must run to completion without errors. Read all warnings and notices generated by the backup script carefully and respond appropriately. Seek assistance for any message that is unclear to you before taking any action.

Note:
  • Backup script will not backup for OpenNMS, PostgreSQL database content, as the restoration is not supported in Junos Space Network Management Platform 24.1R1 and is disabled by default. Back up the content from the Junos Space Network Management Platform User Interface regularly in case you need it before executing the backup script.

  • The device image files and Database Backup files will not be backed up from file system as part of the database backup operation.

  • Starting in Junos Space Network Management Platform Release 24.1R1, Network Director (ND) application is not supported. If Network Director application is installed in Junos Space Network Management Platform Release 23.1R1, uninstall the application before taking the backup .

To run the backup script:

  1. Log in to Junos Space Jboss virtual IP (VIP) node as the admin user and select “(Debug) run shell” from the menu.
  2. Type the following command to navigate to the /var/cache/space-backup-restore directory:
  3. Type the following command to run the backup script:

    [root@space-23.1R1-node /var/cache/space-backup-restore]# sh backup.sh

  4. Perform one of the following actions based on whether you want to continue backing up Junos Space data:

    • Type N to continue running the services on the node and exit the backup process.

      CAUTION:

      If you exit the backup process, the backup file required for restoring data on the Junos Space Network Management Platform Release 24.1R1 setup is not generated.

    • Type Y to stop services running on the node and to continue the backup procedure.

      You are prompted to select the location to store the generated backup files:

  5. To store the file on a remote SCP server:

    1. Type 1 and press Enter.

      You are prompted to specify whether you want to continue.

      Type Y to continue.

    2. You are prompted to enter the IP address of the remote SCP server.

      Type the IPv4 address of the remote SCP server.

    3. You are prompted to enter the port number of the remote SCP server.

      Type the port number of the remote SCP server and press Enter.

      Note:

      The IP address and port must be reachable from the Junos Space Network Management Platform server. If the IP is not reachable, or the port is not open, the script will get stuck trying to test the connection. If this happens, only quitting the SSH session, logging in again, and terminating the running script process will stop the script.

    4. You are prompted to enter the username to access the remote SCP server.

      Type the username and press Enter.

    5. You are prompted to enter the password of the user.

      Type the password and press Enter.

    6. You are prompted to enter the full path of the directory on the remote SCP server where you want to store the backup files.

      Type the full path of the directory and press Enter.

      For example, /home/user/space_backup/

      Note:

      Ensure that there is no space character in the specified directory path. Also, ensure that the specified directory already exists on the remote SCP server. If the directory does not exist, you are prompted to enter a valid directory.

Validate the Backup File

After executing the data backup procedure, we recommend that you validate the checksum for the backup file to ensure that the data from the Junos Space Network Management Platform Release 23.1R1 setup is copied to the selected backup location. This ensures that data from the Junos Space nodes is not lost and can be restored on the Junos Space Network Management Platform Release 24.1R1 setup when you upgrade.

To validate the backup file, complete the following procedures:

  1. Log in to the remote SCP server.

  2. Navigate to the directory where the backup file is stored.

  3. Type the following command and press Enter to generate the MD5 value for the backup file:

    [user@scp-server]> md5sum space-backup.tgz

    Note:

    On some systems, there is no md5sum command. On these systems, the md5 <file name> command should print the md5 hash value.

  4. Compare the calculated MD5 value with the value in the md5.txt file stored at the same location as the backup file. You can see the value stored in md5.txt using the following command:

    [user@scp-server]> cat md5.txt

    If the MD5 values are the same, the backup file is copied successfully to the backup location. If the MD5 values do not match, repeat the back up procedure detailed in Execute the Data Back Up Procedure.

  5. You can verify the integrity of the backup tar file to ensure that errors did not result in a corrupt backup file. To do this, type the following command and press Enter to verify the files in the backup tar file:

    [user@scp-server]> tar -tf space-backup.tgz

    The list of files contained in the tar file are displayed. If there are errors in the tar file, the error is displayed and the file listing stops.

Deploy Junos Space Network Management Platform Release 24.1R1 as a Standalone Node or the First Node of the Fabric and Restoring the Backed-Up Data

After you run the backup script and back up data from the Junos Space Network Management Platform Release 23.1R1, deploy the Junos Space Network Management Platform Release 24.1R1 software image using the following procedure:

CAUTION:

You can configure the Junos Space Network Management Platform Release 24.1R1 node by using any available IP addresses and later switch to production IP address.

  1. Deploy a new Junos Space Network Management Platform Release 24.1R1 virtual appliance instance and configure it as a Junos Space node by following the procedure in step 2.

  2. Install Junos Space Network Management Platform Release 24.1R1 and restore data by using the following procedure:

    Note:

    To ensure that you upgrade Junos Space Network Management Platform and not choose a fresh installation of Junos Space Network Management Platform Release 24.1R1, select the option to restore backed-up data when you are prompted during the configuration of the node.

    To deploy and configure the Junos Space Virtual Appliance, see the Deploying the Junos Space Virtual Appliance and Configuring a Junos Space Virtual Appliance as a Junos Space Node topics in the Junos Space Virtual Appliance Installation and Configuration Guide.

    If the messages displayed on the console indicate that data is restored successfully and JBoss services are started on the node, you can access the Junos Space Network Management Platform GUI through a browser by using the virtual IP (VIP) address configured for Web access.

  3. If the Junos Space Network Management Platform Release 23.1R1 setup had Junos Space applications installed, after the data is restored successfully and the Junos Space Network Management Platform GUI becomes accessible, you may upgrade the applications to releases that are compatible with Junos Space Network Management Platform Release 24.1R1 by using the Junos Space Network Management Platform GUI.
    Note:

    After the upgrade to Junos Space Network Management Platform Release 24.1R1, the Junos Space applications that were installed prior to the upgrade, appear disabled. For more information about upgrading an application, refer to the release notes of the Junos Space application that you want to upgrade.

Install Junos Space Network Management Platform Release 24.1R1 on the Remaining Nodes of the Fabric

When you upgrade from Junos Space Network Management Platform Release 23.1R1 to Junos Space Network Management Platform Release 24.1R1, if you have dedicated database nodes configured for the Junos Space Network Management Platform setup that you are upgrading, after the upgrade and data restoration on the first node of the Junos Space fabric is complete, you must add the dedicated database nodes to the fabric by using the Junos Space Network Management Platform GUI. You can configure the nodes as Junos Space nodes by using one of the following procedures:

Note:
Note:

FMPM node support is disabled from Junos Space Network Management Platform release 24.1R1. For more details see Integration of OpenNMS with Junos Space Network Management Platform.

Note:

Incase you select to restore only configuration during initial setup and skip database, you must contact JTAC for full database restore before enabling device communication. See the following for details Configuring a Junos Space Virtual Appliance as a Junos Space Node

Switch Production to Junos Space Network Management Platform Release 24.1R1

Note:

Before enabling device communication in the Junos Space Network Management Platform Release 24.1R1 node, use the same network configuration (network interfaces and IP addresses) as the Junos Space Network Management Platform Release node which is currently running in the production. If you configure different network settings, then device connectivity gets affected.

Note:

You must perform the below steps to switch production to Junos Space Network Management Platform Release 24.1R1 in the maintenance window.

Perform the following steps to switch production to Junos Space Network Management Platform Release 24.1R1:

  1. Power off the Junos Space Network Management Platform production VMs.

  2. Modify the IP addresses in Junos Space Network Management Platform Release 24.1 from the Junos Space Network Management Platform GUI. For more details, see Modifying the Network Settings of a Node in the Junos Space Fabric.

Enable Device Communication

After you upgrade to the Junos Space Network Management Platform Release 24.1R1, you must configure device communication to ensure that discovered devices can communicate with the Junos Space server.

To configure device communication:

  1. On the Junos Space Network Management Platform GUI, select Administration>Applications.

    The Applications page is displayed.

  2. Click Network Management Platform and select Modify Application Settings from the Actions menu. Alternatively, right-click Network Management Platform and select Modify Application Settings.

    The Modify Application Settings (Modify Network Management Platform Settings) page is displayed and the Device section is selected by default.

  3. Select the Allow Device Communication check box.
  4. Click Modify to modify the settings.

Devices discovered in Junos Space Network Management Platform can now communicate with the Junos Space server.

Manage Disaster Recovery Configuration after Upgrade to 24.1

If you have disaster recovery configured for the Junos Space Network Management Platform Release 23.1R1 setup that you are upgrading, you must upgrade both the active and standby sites to Junos Space Network Management Platform Release 24.1R1 as explained in this topic and then reconfigure disaster recovery. For information about configuring disaster recovery, see Configuring the Disaster Recovery Process Between an Active and a Standby Site.

Roll Back to the previous Junos Space Network Management Platform Release when the Upgrade Fails

After upgrading to Junos Space Network Management Platform Release 24.1R1, if you face any issues, you can roll back to the previous Junos Space Network Management Platform Release you were using.

To roll back to the previous Junos Space Network Management Platform Release, perform the following steps:

  1. Power off the Junos Space Network Management Platform Release 24.1 VM

  2. Power on the VMs that were running on the previous Junos Space Network Management Platform Release

Note:

Contact Juniper Networks support for assistance related to upgrade.