Hot Patch Releases

Installation Instructions

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

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

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

2. Copy the Space-22.1R1-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-22.1R1-Hotpatch-vX.tgz.

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

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

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

   cd Space-22.1R1-Hotpatch-vX

6. . Execute the patchme.sh script from the Space-22.1R1-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-22.1R1-Hotpatch-vX, is created with the list of Red-hat Package Manager (RPM) details in the hot patch.

Note:

• We recommend that you install the latest available hot-patch version, which is the cumulative patch.

• Set the SSH option “ServerAliveInterval” to a minimum value of 300, when connecting to the Applogic VIP via SSH to apply the hotpatch.

  Sample command: ssh admin@x.x.x.x -o ServerAliveInterval=300.

New and Enhanced Features in the Hot Patch

Junos Space® Network Management Platform Release 22.1R1 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 22.1R1 hot patch v1, 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).

Resolved Issues

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

Table 1: Resolved Issues in Hot Patches

PR	Description	Hot Patch Version
PR1665842	Automatic logout from Security Director despite activity.	v1
PR1656477	User sessions does not time out as per the pre-configured timeout in Junos Space Network Management Platform.	v1
PR1658248	Configlet jobs get stuck resulting a delay in all other jobs in Junos Space Network Management Platform.	v1
PR1648129	Issue with the two factor authentication in Junos Space Network Management Platform.	v1
PR1654586	User sessions remain active even after idle timeout.	v1
PR1668786	Junos Space Network Management Platform sends one extra access requests to the radius server.	v1
PR1648704	The user sessions in Junos Space Network Management Platform fail to end correctly, which results in multiple sessions for a single user.	v1
PR1652639	Not enough space in /var/log on Junos OS Space Platform server.	v1