- play_arrow Overview
- play_arrow Introduction
-
- play_arrow Devices
- play_arrow Device Management
- play_arrow Systems of Record
- play_arrow Device Discovery Profiles
- play_arrow Modeling Devices
- Rapid Deployment Overview
- Zero Touch Deployment Using Autoinstallation and Junos Space Network Management Platform on ACX Series and SRX Series Devices
- Model Devices Overview
- Creating a Connection Profile
- Creating a Modeled Instance
- Activating a Modeled or Cloned Device in Junos Space Network Management Platform
- Downloading a Configlet
- Viewing and Copying Configlet Data
- Activating Devices by Using Configlets
- Viewing a Modeled Instance
- Adding More Devices to an Existing Modeled Instance
- Viewing the Status of Modeled Devices
- Deleting Modeled Instances
- Viewing a Connection Profile
- Cloning a Connection Profile
- Modifying a Connection Profile
- Deleting Connection Profiles
- play_arrow Device Authentication in Junos Space
- play_arrow Viewing Device Inventory
- play_arrow Exporting Device Inventory
- play_arrow Configuring Juniper Networks Devices
- Modifying the Configuration on the Device
- Reviewing and Deploying the Device Configuration
- Junos OS Releases Supported in Junos Space Network Management Platform
- Configuration Guides Overview
- Saving the Configuration Created using the Configuration Guides
- Previewing the Configuration Created using the Configuration Guides
- Deploying the Configuration Created using the Configuration Guides
- Viewing and Assigning Shared Objects
- Applying a CLI Configlet to Devices
- Applying a CLI Configlet to a Physical Inventory Element
- Applying a CLI Configlet to a Physical Interface
- Applying a CLI Configlet to a Logical Interface
- Executing a Script on the Devices
- Executing a Script on a Physical Inventory Component
- Executing a Script on a Logical Interface
- Executing a Script on the Physical Interfaces
- play_arrow Device Adapter
- play_arrow Device Configuration Management
- play_arrow Adding and Managing Non Juniper Networks Devices
- play_arrow Accessing Devices
- Launching a Device’s Web User Interface
- Looking Glass Overview
- Executing Commands by Using Looking Glass
- Exporting Looking Glass Results in Junos Space Network Management Platform
- Secure Console Overview
- Connecting to a Device by Using Secure Console
- Configuring SRX Device Clusters in Junos Space using Secure Console
- play_arrow Logical Systems (LSYS)
- play_arrow Tenant System (TSYS)
- play_arrow Device Partitions
- play_arrow Custom Labels
- play_arrow Verifying Template, Image Deployment, Script Execution, and Staged Images on Devices
- play_arrow Device Monitoring
- play_arrow Device Maintenance
- Viewing Device Statistics
- Viewing Devices and Logical Systems with QuickView
- Resynchronizing Managed Devices with the Network
- Putting a Device in RMA State and Reactivating Its Replacement
- Modifying the Target IP Address of a Device
- Modifying the Serial Number of a Device
- Rebooting Devices
- Deleting Staged Images on a Device
- Cloning a Device in Junos Space Network Management Platform
- Deleting Devices
-
- play_arrow Device Templates
- play_arrow Overview
- play_arrow Template Definitions
- Creating a Template Definition
- Finding Configuration Options in a Template Definition
- Working with Rules in a Template Definition
- Specifying Device-Specific Values in Template Definitions
- Managing CSV Files for a Template Definition
- Publishing a Template Definition
- Viewing a Template Definition
- Modifying a Template Definition
- Cloning a Template Definition
- Importing a Template Definition
- Exporting a Template Definition
- Unpublishing a Template Definition
- Deleting a Template Definition
- play_arrow Configuring Devices using Device Templates
- play_arrow Configuring Devices using Quick Templates
- play_arrow Device Template Administration
- Viewing Template Details
- Viewing the Device-Template Association (Device Templates)
- Viewing Template Definition Statistics
- Viewing Device Template Statistics
- Comparing Templates or Template Versions
- Comparing a Device Template Configuration with a Device Configuration
- Cloning a Template in Junos Space Network Management Platform
- Exporting and Importing a Quick Template in Junos Space Network Management Platform
- Deleting Device Templates from Junos Space Network Management Platform
-
- play_arrow CLI Configlets
- play_arrow Overview
- play_arrow CLI Configlets
- Creating a CLI Configlet
- Modifying a CLI Configlet
- Viewing CLI Configlet Statistics
- Viewing a CLI Configlet
- Exporting CLI Configlets
- CLI Configlet Examples
- Deleting CLI configlets
- Cloning a CLI Configlet
- Importing CLI Configlets
- Applying a CLI Configlet to Devices
- Comparing CLI Configet Versions
- Marking and Unmarking CLI Configlets as Favorite
- play_arrow Configuration Views
- Configuration Views Overview
- Configuration View Variables
- Configuration View Workflow
- XML Extensions
- Creating a Configuration View
- Viewing a Configuration View
- Modifying a Configuration View
- Deleting Configuration Views
- Exporting and Importing Configuration Views
- Viewing Configuration Views Statistics
- Default Configuration Views Examples
- play_arrow XPath and Regular Expressions
- play_arrow Configuration Filters
-
- play_arrow Images and Scripts
- play_arrow Overview
- play_arrow Managing Device Images
- Device Images Overview
- Importing Device Images to Junos Space
- Viewing Device Images
- Modifying Device Image Details
- Staging Device Images
- Staging Satellite Software Packages on Aggregation Devices
- Verifying the Checksum
- Viewing and Deleting MD5 Validation Results
- Deploying Device Images
- Deploying Satellite Software Packages on Aggregation and Satellite Devices
- Viewing Device Image Deployment Results
- Viewing Device Association of Images
- Undeploying JAM Packages from Devices
- Removing Device Images from Devices
- Deleting Device Images
- play_arrow Managing Scripts
- Scripts Overview
- Promoting Scripts Overview
- Importing Scripts to Junos Space
- Viewing Script Details
- Modifying Scripts
- Modifying Script Types
- Comparing Script Versions
- Staging Scripts on Devices
- Verifying the Checksum of Scripts on Devices
- Viewing Verification Results
- Enabling Scripts on Devices
- Executing Scripts on Devices
- Executing Scripts on Devices Locally with JUISE
- Viewing Execution Results
- Exporting Scripts in .tar Format
- Viewing Device Association of Scripts
- Marking and Unmarking Scripts as Favorite
- Disabling Scripts on Devices
- Removing Scripts from Devices
- Deleting Scripts
- Script Annotations
- Script Example
- play_arrow Managing Operations
- play_arrow Managing Script Bundles
- Script Bundles Overview
- Creating a Script Bundle
- Viewing Script Bundles
- Modifying a Script Bundle
- Staging Script Bundles on Devices
- Enabling Scripts in Script Bundles on Devices
- Executing Script Bundles on Devices
- Disabling Scripts in Script Bundles on Devices
- Viewing Device Associations of Scripts in Script Bundles
- Deleting Script Bundles
-
- play_arrow Reports
- play_arrow Reports Overview
- play_arrow Report Definitions
- play_arrow Reports
-
- play_arrow Network Monitoring
- play_arrow Overview
- play_arrow Managing Nodes
- play_arrow Searching for Nodes and Assets
- play_arrow Managing Outages
- play_arrow Using the Network Monitoring Dashboard
- play_arrow Managing and Configuring Events
- play_arrow Managing and Configuring Alarms
- play_arrow Managing and Configuring Notifications
- play_arrow Managing Reports and Charts
- play_arrow Network Monitoring Topology
- play_arrow Network Monitoring Administration
- Configuring Network Monitoring System Settings
- Updating Network Monitoring After Upgrading the Junos Space Network Management Platform
- Configuring SNMP Community Names by IP
- Configuring SNMP Data Collection per Interface
- Managing Thresholds
- Compiling SNMP MIBs
- Managing SNMP Collections
- Managing SNMPv3 Trap Configuration
- Managing Data Collection Groups
- Managing and Unmanaging Interfaces and Services
- Starting, Stopping, and Restarting Services
-
- play_arrow Configuration Files
- play_arrow Overview
- play_arrow Managing Configuration Files
-
- play_arrow Jobs
- play_arrow Overview
- play_arrow Managing Jobs
- Viewing Statistics for Jobs
- Viewing Your Jobs
- Viewing Jobs
- Viewing Objects on Which a Job is Executed
- Viewing Job Recurrence
- Rescheduling and Modifying the Recurrence Settings of Jobs
- Retrying a Job on Failed Devices
- Reassigning Jobs
- Canceling Jobs
- Clearing Your Jobs
- Archiving and Purging Jobs
- Common Error Messages in Device-Related Operations
-
- play_arrow Role-Based Access Control
- play_arrow Overview
- play_arrow Roles
- Roles Overview
- Predefined Roles Overview
- Creating a User-Defined Role
- Managing Roles
- Modifying User-Defined Roles
- Deleting User-Defined Roles
- Cloning Predefined and User-Defined Roles
- Exporting User-Defined Roles from Junos Space Network Management Platform
- Importing Roles to Junos Space Network Management Platform
- play_arrow User Accounts
- Configuring Users to Manage Objects in Junos Space Overview
- Creating Users in Junos Space Network Management Platform
- Modifying a User
- Deleting Users
- Disabling and Enabling Users
- Unlocking Users
- Viewing Users
- Exporting User Accounts from Junos Space Network Management Platform
- Changing Your Password on Junos Space
- Clearing User Local Passwords
- Viewing User Statistics
- play_arrow User Groups
- play_arrow Domains
- play_arrow Remote Profiles
- play_arrow API Access Profiles
- play_arrow User Sessions
-
- play_arrow Audit Logs
- play_arrow Troubleshooting
- play_arrow Knowledge Base
-
Upgrading to Junos Space Network Management Platform Release 21.1R1
In Junos Space Network Management Platform Release 21.1R1, CentOS 7.4 is used as the underlying OS. As a direct upgrade of the OS from CentOS 6.8 (used in Junos Space Platform releases before 20.3R1) to CentOS 7.4 is not supported, a direct upgrade to Junos Space Platform Release 21.1R1 by using the Junos Space Platform UI is also not supported. You must follow a multi-step procedure to upgrade to Junos Space Platform Release 21.1R1.
Upgrading to Junos Space Platform Release 21.1R1 involves backing up data from the nodes in the Junos Space Platform setup, installing Junos Space Platform Release 21.1R1 on the nodes, and restoring backed up data to the nodes. After Junos Space Platform is upgraded, you can upgrade previously installed Junos Space applications.
You can upgrade to Junos Space Platform Release 21.1R1 only from Junos Space Platform Release 20.3R1. To upgrade to Junos Space Platform Release 21.1R1 from releases earlier than Junos Space Platform Release 20.3R1, you must first upgrade to Junos Space Platform Release 20.3R1 and then follow the procedures specified in this topic.
For more information about upgrading to Junos Space Platform Release 20.3R1, see the Junos Space Network Management Platform Release 20.3R1 Release Notes.
To upgrade from Junos Space Platform Release 20.3R1 to Junos Space Platform Release 21.1R1, complete the tasks in the sequence below. The Appendix provides sample data of time taken for backing up and restoring data while upgrading to Junos Space Platform Release 21.1R1.
Before You Begin
In Junos Space Network Management release 20.3R1 and before, the Junos Space database(DB) backup restore with Unicast mode of communication is restored in the setup which is visible in domain.xml file.
Since Junos Space Network Management 21.1R1 release includes CentOs upgrade, the DB backup from Junos Space Network Management release 20.3R1 with Unicast mode of communication is not restored. You need to reconfigure the data in Junos Space Network Management 21.1R1 release.
This particular upgrade procedure is complex and requires switching between the Junos Space Platform GUI and the Junos Space Platform command line. In case of problems, 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, please arrange for that access through the appropriate internal channels, and have the needed personnel available during the entire process.
Table 1 shows various physical and network elements that are needed in order to perform this upgrade procedure.
Item | Purpose | Comments |
---|---|---|
Access to the Junos Space Platform GUI using the super user’s credentials | To establish and confirm proper configuration, device connection, database state, and backup prior to upgrade | |
Access to the Junos Space 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 that is created during this upgrade:
| 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. Not needed if the USB storage device option is used. |
A USB storage device with at least 8GB of free space | To store the following files that are created as part of the backup that is created during this upgrade:
| Not needed if the SCP option is used. |
Access to the hypervisor that hosts the Junos Space Platform VM | To deploy the 21.1R1 ova file |
Disabling Device Communication
Before taking backup from the Junos Space Network Management Platform Release 20.3R1, disable device communication to ensure that the discovered devices stop communicating with the Junos Space Server.
To disable device communication:
Follow the existing upgrade procedure when an environment is present with the below nodes or node combinations:
- Single node
- JBoss cluster
- JBoss cluster and dedicated database (DB) node
- JBoss cluster, dedicated database (DB) node and FMPM node.
Downloading and Installing the Junos Space Platform 20.3R1 Patch
Before you begin upgrading Junos Space Platform Release 20.3R1 to Junos Space Platform Release 21.1R1, download and install the Junos Space Platform Release 20.3R1 patch from the link Junos Space 20.3R1 Backup Patch for Upgrade to 21.1R1 on the Junos Space Network Management Platform – Download Software page for Version 21.1R1.
To download and install the patch:
Executing the Data Back Up Procedure
To back up Junos Space Platform and Junos Space Application data from the Junos Space nodes, execute the backup script, backup.sh that is provided by the 20.3R1 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, and the database dump files of the MySQL databases 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 or USB:
space-backup.tgz
space-readme.txt
md5.txt
backupStatus.log
In order 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 in response.
Backup script will not take backup for OpenNMS, PostgreSQL Data Base content, as the restoration is not supported in Junos Space Network Management Platform 21.1R1 and are disabled by default. Take a regular backup of these contents from the Junos Space Network Management Platform User Interface 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.
Connectivity Services Director (CSD) application is not supported from Junos Space Network Management Platform Release 21.1R1. Incase CSD application is installed in Junos Space Network Management Platform Release 20.3R1, the database backup operation will terminated, asking the user to uninstall the CSD application from the Junos Space Network Management Platform GUI.
To run the backup script:
Validating 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 Platform Release 20.3R1 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 Platform Release 21.1R1 setup when you upgrade.
To validate the backup file, complete one of the following procedures:
To validate the backup file stored on a remote SCP server:
Log in to the remote SCP server.
Navigate to the directory where the backup file is stored.
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.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 Executing the Data Back Up Procedure.
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.
To validate the backup file stored on a USB storage device:
Note:Ensure that the USB storage device is plugged-in to the Junos Space Appliance and mounted to the path /tmp/pendrive.
Type the following command and press Enter to generate the MD5 value for the backup file:
[root@space-20.3R1-node ~]# md5sum /tmp/pendrive/space-backup.tgz
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:
[root@space-20.3R1-node]# 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 Executing the Data Back Up Procedure.
Type the following command and press Enter to verify the files in the backup tar file:
[root@space-20.3R1-node]# tar -tf /tmp/pendrive/space-20.3R1.4.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.
Installing Junos Space Platform Release 21.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 nodes, install the Junos Space Platform Release 21.1R1 software image, using the following procedure:
If you are upgrading a standalone node, back up all data on the node to a remote server before you install the Junos Space Platform Release 21.1R1 software image. You cannot retrieve previously saved data after the Junos Space Platform Release 21.1R1 software image is installed.
When you configure the Junos Space Platform Release 21.1R1 node, ensure that you use the same network configuration (network interfaces and IP adresses) as the Junos Space Platform Release 20.3R1 node. If you configure different network settings, device connectivity and SNMP traps are affected.
Rolling Back to Junos Space Platform Release 20.3R1 if Upgrade Fails
While upgrading to Junos Space Platform Release 21.1R1, if you are unable to restore the data backed up before you began upgrading Junos Space Platform, you can roll back to Junos Space Platform Release 20.3R1.
If data restore fails, complete one of the following procedures:
If the Junos Space node is a standalone node:
Complete one of the following procedures:
For a Junos Space Appliance , reimage the node to install the Junos Space Platform Release 20.3R1 software image, by using one of the following procedures:
For a Junos Space Virtual Appliance, roll back to the Junos Space Platform Release 20.3R1 setup by powering off the Junos Space Platform Release 21.1R1 node and powering on the Junos Space Platform Release 20.3R1 node.
The roll back of the Junos Space Virtual Appliance to Release 20.3R1 is complete.
Download and apply the Junos Space Platform Release 20.3R1 patch. See Downloading and Installing the Junos Space Platform 20.3R1 Patch to install the patch.
Install the same Junos Space applications that were installed on the Junos Space Platform Release 20.3R1setup that you attempted to upgrade.
Type the following command to navigate to the /var/cache/space-backup-restore directory:
[root@space-20.3R1-node ~]# cd /var/cache/space-backup-restore
Type the following command to restore the backup:
[root@space-20.3R1-node /var/cache/space-backup-restore]# sh restore-20.3R1.sh
You are prompted to specify the location from where you want to restore the backup.
content_copy zoom_out_map1> Remote Server 2> USB 3> Local M> Return to Main Menu R> Redraw Menu Choice [1-3 MR]:
Select one of the following options depending on where the backup file is stored:
To restore from a remote Secure Copy Protocol (SCP) server:
Type 1 and press Enter.
You are prompted to confirm whether you want to continue.
content_copy zoom_out_mapYou have selected [ Remote Server ]. Do you want to Continue? [Y/N]
Based on whether you want to continue or exit, perform one of the following actions:
Type Y.
You are prompted to enter the IPv4 address of the remote SCP server.
content_copy zoom_out_mapPlease enter Remote Server IP:
Type the IPv4 address of the remote SCP server and press Enter.
You are prompted to enter the port number for the remote server.
content_copy zoom_out_mapPlease enter port number for Remote Server REMOTE_SERVER_IP:
Type the port number of the remote SCP server and press Enter.
You are prompted to enter the username to access the remote server.
content_copy zoom_out_mapPlease enter Remote Server REMOTE_SERVER_IP user:
Type the username and press Enter.
You are prompted to enter the password of the user.
content_copy zoom_out_mapPlease enter Remote Server user REMOTE_SERVER_USER password:
Type the password and press Enter.
You are prompted to enter the full path of the directory where the backup file is stored.
content_copy zoom_out_mapEnter the path of the directory containing backup files:
Type the full path of the directory and press Enter.
Note:Ensure that the directory path does not contain any space characters.
The messages displayed on the console indicate whether the data is restored successfully to the Junos Space node.
Type N to exit.
To restore from a USB storage device:
Note:Before you restore from a USB storage device, ensure that the USB device is plugged in. The restore procedure will try to mount the device to the path /tmp/pendrive.
For data backup and restore, identify the USB storage device using the
fdisk -l
command and format the device using themkfs.ext2 <physical device>
command. For example,mkfs.ext2 /dev/sdb
. This ensures that the USB device has the correct disk layout for the execution of the backup and restore procedures and prevents loss of data.
Type 2 and press Enter to restore the backup from the USB storage device.
The messages displayed on the console indicate whether the data is restored successfully to the Junos Space node.
Unmount the USB storage device by typing the following command:
[root@space-20.3R1-node /var/cache/space-backup-restore]# umount /tmp/pendrive
You can unplug the USB storage device after you unmount it.
To restore data from the backup file stored on the Junos Space node:
Note:To restore data from the backup file stored on the Junos Space node, you must first copy the file from the backup location to the Junos Space node.
Type 3 and press Enter.
You are prompted to enter the full path of the directory where the backup file is stored.
content_copy zoom_out_mapEnter the tar file path to restore from local:
Type the full path of the directory and press Enter.
The messages displayed on the node indicate whether the data is restored successfully to the Junos Space node.
If the messages displayed on the console indicate that the data is restored successfully and JBoss services are started on the node, you can access the Junos Space Platform UI through a browser by using the VIP address configured for Web access. You can now use this Junos Space Platform Release 20.3R1 installation.
If the restore fails, save the troubleshooting log file, /var/log/restoreStatus.log to your computer; power off the node; and contact Juniper Networks support for assistance.
If the node is a Junos Space Appliance and the first node of a Junos Space fabric, complete the following procedure:
Power off the node.
Power on the remaining nodes of the cluster, to bring up the cluster with the Junos Space Platform Release 20.3R1 installation.
Delete the first node (on which upgrade failed) from the cluster, using the Junos Space Platform GUI. For more information about deleting the node, see Deleting a Node from the Junos Space Fabric.
Power on and reimage the node that you attempted to upgrade, to install the Junos Space Platform Release 20.3R1 software image. To reimage the node, follow one of the procedures listed in 1.
Add the node to the fabric by using the Junos Space Platform GUI. For information about adding nodes to the Junos Space fabric, see Adding a Node to an Existing Junos Space Fabric.
Installing Junos Space Platform Release 21.1R1 on the Remaining Nodes of the Fabric
When you upgrade from Junos Space Platform Release 20.3R1 to Junos Space Platform Release 21.1R1, if you have dedicated database nodes or Fault Monitoring and Performance Monitoring (FMPM) nodes configured for the Junos Space 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 and FMPM nodes to the fabric by using the Junos Space Platform GUI. You can configure the nodes as Junos Space nodes or Fault Monitoring and Performance Monitoring (FMPM) nodes, by using one of the following procedures:
After you configure the nodes from the Junos Space Platform command line, you can add the nodes to the Junos Space fabric as JBoss nodes, dedicated database nodes, FMPM nodes, by using the Junos Space Platform UI. For information about adding nodes to the Junos Space fabric, see Adding a Node to an Existing Junos Space Fabric.
To install and configure the Junos Space Platform Release 21.1R1 software image on a Junos Space Virtual Appliance, see the Deploying the Junos Space Virtual Appliance, Configuring a Junos Space Virtual Appliance as a Junos Space Node and Configuring a Junos Space Virtual Appliance as a Standalone or Primary FMPM Node topics in the Junos Space Virtual Appliance Installation and Configuration Guide.
Enabling Device Communication
After you upgrade to the Junos Space Platform Release 21.1R1, you must configure device communication to ensure that discovered devices can communicate with the Junos Space server.
To configure device communication:
Devices discovered in Junos Space Platform can now communicate with the Junos Space server.
Managing Disaster Recovery Configuration after Upgrade to 21.1
If you have disaster recovery configured for the Junos Space Platform Release 20.3R1 setup that you are upgrading, you must upgrade both the active and standby sites to Junos Space Platform Release 21.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.