Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Hot Patch Releases

This section describes the installation procedure and resolved issues in Junos Space Network Management Platform Release 21.3R1 hot patches.

During hot patch installation, the script performs the following operations:

  • Blocks the device communication.
  • Stops JBoss, JBoss-dc, and watchdog services.
  • Backs up existing configuration files and Enterprise Application Archive (EAR) files.
  • Updates the Red Hat Package Manager (RPM) files.
  • Restarts the watchdog process, which restarts JBoss and JBoss-dc services.
  • Unblocks device communication after restarting the watchdog process for device load balancing.

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.

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 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 Issues

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

  • Junos Space Network Management Platform is sending one extra access requests to the radius server. PR1668786.

Resolved Issues

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

Table 1: Resolved Issues
PR Description Hot Patch Version
PR1638525

Image upload fails with Software validation failure, check certificate keys error message in Network Director.

v1
PR1654586

User sessions remain active even after idle timeout.

v2
PR1654497

Resynchronization with Junos Space Network Management Platform fails.

v2
PR1648704

The user sessions in Junos Space Network Management Platform fail to end correctlywhich results in multiple sessions for a single user.

v2
PR1648129

Issue with the two factor authentication in Junos Space Network Management Platform.

v2
PR1641759

Inactive timeout API fails in Junos Space Network Management Platform.

v2
PR1637162

The execution of the device inventory clean up script cleanUpDeviceInvStaleEntries.sh fails.

v2
PR1646459 Network Time Protocol (NTP) activation fails after user reboots Junos Space Network Management Platform node. v3
PR1665842 User is automatically logged out from Security Director despite activity. v4
PR1656477 User sessions do not time out as per the pre-configured timeout in Junos Space Network Management Platform. v4
PR1657647 Purge jobs do not work as expected in Junos Space Management Platform. v4
PR1658248 Configlet jobs get stuck resulting a delay in all other jobs in Junos Space Network Management Platform. v4
PR1664301 Disaster recovery manual failover causes MySQL errors. v4
PR1664964 Junos Space Network Management Platformm /tmp directory floods with 100K zero byte isFIPSModeEnabled.xxxxxxxxxx files. v4
PR1652639 Insufficient space in /var/log in Junos Space Network Management Platform Server. v4
PR1677100 User is unable to deploy config template due to internal server error. v4
PR1685214

Purging of MySQL bin files does not happen correctly.

v5
PR1673696

The performance graphs for the MX series devices are missing from the FPC cards after upgrading to Junos Space Network Management Platform 21.3R1.

v6
PR1684165

Junos Space Network Management Platform does not close the SSH sessions properly.

v6
PR1693209 User is unable to power off the MX series devices via Junos Space Network Management Platform. v6
PR1699230

Few of the Logical System (LSYS) devices display the status as DOWN while the root device displays the status as UP.

Workaround: Perform RMA for the device to trigger the Junos Space Network Management Platform to reconnect. Most of the devices get connected and display the status as UP but at least one device needs to be performed RMA for the second time. After performing the RMA, some devices does not display in-sync in a timely manner until you run a resync with the network.

v6
PR1700218

REST API fails with errors.

v6
PR1701653

JUNOS Enhanced Services (JUNOS-ES) device logs contain a matching term "GRES" that matches with the terms "INGRESS" and "EGRESS".

Note:
  • Junos Space Network Management Platform 21.3R1 Hot Patch V6 updates the match pattern to receive messages matching with “_GRES” besides "GRES" for JUNOS-ES devices. This update drops the unwanted messages received from the devices.

  • Devices discovered from Junos Space Network Management Platform after the above mentioned fix will have the changes as the pattern gets pushed to the devices during device discovery.

  • Perform the following steps to modify the system log configuration of devices that are discovered before upgrading to Junos Space Network Management Platform 21.3R1 Hot Patch V6:

    1. Login to Junos Space Network Management Platform UI and select Device Templates > Templates.

    2. Right click on COMMIT_SYNC_CONFIG_JUNOS_ES and select Modify Quick template.

    3. Select Preview to verify the occurrence of _GRES at the end of the template.

    4. Click Save and Assign/Deploy. The screen displays all the JUNOS-ES devices.

    5. Select the devices where you want to update the pattern and click Next.

    6. Click Validate on Device to validate the templates for the devices.

    7. Click Deploy now to complete the update immediately or click Deploy later to schedule it later.

    8. Click Finish and wait for the update to complete.

v6