Hot Patch Releases

Installation Instructions

Perform the following steps in the CLI of the JBoss-VIP node only:

1. Download the Junos Space Platform 21.3R1 Patch vX from the download site.

   Here, X is the hot patch version. For example, v1, v2, and so on.

2. Copy the Space-21.3R1-Hotpatch-vX.tgz file to the /home/admin location of the VIP node.

3. Verify the checksum of the hot patch for data integrity:

   md5sum Space-21.3R1-Hotpatch-vX.tgz.

4. Extract the Space-21.3R1-Hotpatch-vX.tgz file:

   tar -zxvf Space-21.3R1-hotpatch-vX.tgz

5. Change the directory to Space-21.3R1-Hotpatch-vX.

   cd Space-21.3R1-Hotpatch-vX

6. . Execute the patchme.sh script from the Space-21.3R1-Hotpatch-vX folder:

   sh patchme.sh

   The script detects whether the deployment is a standalone deployment or a cluster deployment and installs the patch accordingly.

A marker file, /etc/.Space-21.3R1-Hotpatch-vX, is created with the list of Red-hat Package Manager (RPM) details in the hot patch.

New and Enhanced Features in the Hot Patch

Junos Space® Network Management Platform Release 21.3R1 hotpatch includes the following enhancements:

• Support for Junos Space Platform UI user to override an active CLI session— Starting in Junos Space Network Management Platform Release 21.3R1 hot patch v3, we've provided an option for Junos Space Platform UI users to override an active CLI session while configuring a device in edit mode. When you configure a device through UI, and a CLI session is also active on the same device, the system shows an error. When you retry the update job on failed devices caused due to device lock failures, you can log the user out who locked the configuration database, from the device CLI.

  Navigate to Jobs > Job Management to select the failed job and right click to select Retry on Failed Devices. On the Retry Job for Deploy Consolidated Config page, enable Evict CLI/J-Web edit mode users option.

  The option to evict a CLI user is provided in the following modules in the UI, you can navigate to the respective paths to access the option:

  • Modify configuration for a device— Navigate to Devices > Device Management > Device configuration >Modify configuration.
  • Assigning or deploying a device template— Navigate to Device Template > Template > Assign/Deploy Template.
  • Undeploying a device template— Navigate to Device Template > Template > Undeploy Template.
  • Applying configlets— Navigate to CLI configlets > Configlets.
  • Restoring a configuration file— Navigate to Configuration Files > Config Files Management > Restore Config Files(s).

Known Behavior

• When you modify the administrator password using CLI on both active and standby sites, update to the DR configuration on the standby site fails with an error.

  Workaround: To change the administrator password and update the DR configuration on both the sites, perform the following steps:

  1. Enter passwd admin command to change the password for all the nodes in the active site cluster.

  2. Update the DR configuration on the active site using the following command: jmp-dr toolkit config update --user-core

  3. Repeat Step 2 to update the DR configuration on the standby site.

Known Issues

This section lists the known issues in Junos Space Network Management Platform Release 21.3R1 hot patch.

• During the Disaster Recovery (DR) initialization process, when you try to retrieve information for all the arbiter devices, it fails with an error. PR1702232

• Validation check option is missing when arbiter devices are not selected in Configure Disaster Recovery Wizard page. PR1654835

• Validation issue with device selection disables the NEXT button. PR1628290

• Junos Space Network Management Platform sends multiple access requests to the server, resulting in accounts being locked. PR1668786

Resolved Issues

Table 1 lists the resolved issues in Junos Space Network Management Platform Release 21.3R1 hot patch.