Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Hot Patch Releases

This section describes the installation procedure and resolved issues in Junos Space Network Management Platform Release 23.1R1 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 23.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-23.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-23.1R1-Hotpatch-VX.tgz.

  4. Extract the Space-23.1R1-Hotpatch-VX.tgz file:

    tar -zxvf Space-23.1R1-hotpatch-VX.tgz

  5. Change the directory to Space-23.1R1-Hotpatch-VX.

    cd Space-23.1R1-Hotpatch-VX

  6. . Execute the patchme.sh script from the Space-23.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-23.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.

  • When you configure the Disaster Recovery (DR), make sure that you reset the DR configuration on both the active and the standby sites.

    Once the DR reset is complete, you must remove the user.properties file from the /var/cache/jmp-geo/config path for all the JBoss, database, and Fault Monitoring and Performance Monitoring (FMPM) nodes, if any.

New and Enhanced Features in the Hot Patch

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

  • Support for SRX1600 Firewall—Starting in Junos Space Network Management Platform Release 23.1R1 hot patch V2, we've provided support for SRX1600 firewall.

  • Support for SRX2300 Firewall—Starting in Junos Space Network Management Platform Release 23.1R1 hot patch V2, we've provided support for SRX2300 firewall.

Supported Devices in the Hot Patch

Table 1 lists the devices supported in Junos Space Network Management Platform 23.1R1 Hot Patch Releases.

Table 1: Supported Devices in the Hot Patch

Supported Device

Hot Patch Release Version

SRX1600

Junos Space Network Management Platform Release 23.1R1 Hot Patch V2

SRX2300

Junos Space Network Management Platform Release 23.1R1 Hot Patch V2

Resolved Issues

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

Table 2: Resolved Issues in Junos Space Network Management Platform Release 23.1R1 Hot Patch
PR Description Hot Patch Version
PR1860367

Junos Space Network Management Platform sends authentication requests to TACAS for a local user.

v6
PR1851757

The user is unable to upgrade the Junos firmware image from 23.4R2.13 to 23.4R2-S2.1 in the primary node of an SRX chassis cluster. The upgrade fails with an error.

v5
PR1773076

The user is unable to filter jobs from the job list.

v4
PR1787967

The Junos Space Network Management Platform GUI shows incorrect number of nodes under Network Monitoring.

v4
PR1811273

The user is unable to change Junos Space Network Management Platform GUI password when the original password contains special characters.

v4
PR1814883

When the user clicks the Save Filter option, Junos Space Network Management Platform GUI fails to respond.

v4
PR1817241

While performing Test Connection in Junos Space Network Management Platform, it gets stuck with Testing.... Please wait... message.

v4
PR1818143

The model device configuration remains unaffected when a user adds an extra JBoss node to Junos Space Network Management Platform.

v4
PR1819315

The user is unable to add a new node in Junos Space Network Management Platform GUI.

v4
PR1828027

Multiple DMI sessions are not visible in Junos Space Network Management Platform GUI.

v4
PR1838157

The command jmp-dr toolkit watchdog status disable-automatic-failover duration 0 fails to disable the automatic failover permanently.

v4
PR1838492

SNMPD services stop on all Junos Space nodes after you perform jmp-dr manual failover.

v4
PR1842159

The management sessions in Junos Space Network Management Platform GUI are inconsistent and show incorrect data.

v4
PR1846111

The Junos Space Network Management Platform GUI fails to collect logs as expected.

v4
PR1697264 Synchronization of Logical Systems (LSYS) for SRX Series Firewalls fails with the Exception is thrown during operationalRpcReq devId=### java.nio.channels.ClosedChannelException error message. v3
PR1742243

Archive and purge job under Job Management fails with an error in Junos Space Network Management Platform Release 21.2R1.

Workaround:

  1. In MySQL prompt, run the following command:

    SET FOREIGN_KEY_CHECKS = 0;

  2. Purge all the jobs carried out before 01.02.2023 from Junos Space Network Management Platform GUI.

  3. Return to MySQL prompt and run the following command:
     SET FOREIGN_KEY_CHECKS = 1;
 v3
PR1744314 Add More Device under Model Device takes longer than usual to open. v3
PR1754247 The Disaster Recovery page does not load in Junos Space Network Management Platform. v3
PR1758864

The max_log_file_action is not set to ROTATE by default. Hence, the audit file logs are not purged and /var/log/audit is completely filled.

Workaround: You can set the value for max_log_file_action in /etc/audit/auditd.conf file as ROTATE or KEEP_LOGS as per your requirement.

 v3
PR1759990 Archive and purge jobs do not delete the following tasks:

  • Uninstall Application, and,

  • ICEAAA Manager clean up historic entries

 v3
PR1765032 Junos Space Network Management Paltform goes into maintenance mode frequently and displays Junos space is starting up, please wait message. v3
PR1769758 Disaster recovery fails to synchronize sites. v3
PR1770973 After Disaster Recovery failover, the jmp-dr health command intermittently shows jboss-dc: chkconfig(off!!) FAIL message. v3
PR1771233 Junos Space Network Management Platform GUI becomes unresponsive unless restarted. v3
PR1771300 When you try to assign a template to a device in Junos Space Network Management Platform, it fails with Failed to release the lock on the device error message. v3
PR1778019 Large fileHandleLeak.log is caused by large number of python processes. v3
PR1779392 After jmp-dr starts, there is high network traffic on both active and standby sites and database logs display 1062 error repetitively. v3
PR1781356 Multiple jobs are stuck in in-progress state. v3
PR1782835 The Disaster Recovery manual failover test fails with fatal error 1236. v3
PR1785850 After upgrading to Junos Space Network Management Platform Release 22.2R1 hot patch v3, when user cancels the Modify Template window without any changes, the Last Modified By name changes to the current user and the Last Update Time changes to the current time. Templates created on older versions also increment the latest version number. v3
PR1787517

When the user sets Out of Sync filter for Managed Status in the Device Inventory Report the system fails to generate any result.

Workaround: Export all the values for Managed Status to CSV, and then set the Out of Sync filter.

 v3
PR1788172 Archive and purge jobs fail with An error occurred while purging the information from JobInstance and its reference tables error. v3
PR1659947 Junos Space Network Management Platform GUI shows incorrect number of nodes under Network Monitoring. v1
PR1678536 Junos Space Network Management Platform shows incorrect timestamp in View Configuration Change Log under Device Management. v1
PR1713174 The script @EXECUTIONTYPE = "GROUPEDEXECUTION fails to give the result when executed through API, images or script menu. v1
PR1717146 Starting in Junos Space Network Management Platform Release 22.3R1, user fails to upgrade the ACX1100 and ACX2200 devices as the no-copy option is not available and the devices do not have sufficient space to hold copies of the software. v1
PR1731540 Users sees Fail in load selections data error while changing domains in the Device Management page and Job Management page. v1
PR1732817 When you try to discover a device using the FIPS mode or SNMP, it fails with SNMPv3 AuthType should be SHA1 when the server is in FIPS mode error message. v1
PR1734126 The database purging policy gets stuck in Junos Space Network Management Platform resulting in no data backup. v1
PR1735659 Deleted devices continue to appear in the Network Monitoring node list even after deletion. v1
PR1737025 The restart command on the Network Monitoring page, fails to restart the services. v1
PR1738821 Resync Nodes job in OpenNMS page does not update the device progress in Junos Space Network Management Platform. v1
PR1739065 Junos Space Platform Web GUI shows an error at times, when you upload PKCS12 format certificate. v1
PR1740818 Resynchronization with the network fails with java.nio.channels.ClosedChannelException error. v1
PR1748467

After upgrading to Junos Space Network Management Platform 23.1R1, database status shows Out of Sync because of MySQL disk space utilization.

Workaround:

  1. Log in to Junos Space Network Management Platform CLI.

  2. Edit the /var/chroot/mysql/etc/my.cnf file, to add:

    expire_log_days=3

  3. Restart MySQL service using the following command:

    service mysqld restart
 v1