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

Junos Space Network Management Platform 24.1R1 Hot Patch Release

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

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

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

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

    cd Space-24.1R1-Hotpatch-vX

  6. . Execute the patchme.sh script from the Space-24.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-24.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 through SSH to apply the hotpatch.

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

Resolved Issues

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

Table 1: Resolved Issues in Junos Space Network Management Platform Release 24.1R1 Hot Patch
PR Description Hot Patch Version

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.

v2

PR1791603

Last monitoring time for nodes fail to update on the fabric page.

v2

PR1808536

The Junos Space Network Management Platform GUI is stuck and doesn't load. Displays appmgt is waiting for opennms to complete application initialization message.

v2

PR1814543

The REST API for Junos Space Network Management Platform Release 21.2R1 is not in accordance with Junos Space Network Management Platform Release 24.1R1.

v2

PR1815872

 When you access Junos Space Network Management Platform 24.1R1 GUI through a browser, the ICEAAA session gets terminated with Your session has been terminated by the Administrator message.

v2

PR1816840

Services fail when deployed with a single Jboss node in Junos Space Network Management Platform. Works when Jboss is started on the second load balancer.

v2

PR1817241

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

v2
PR1817571

Gateway of eth3 interface changes to eth0 interface post installtion of Junos Space Network Management Platform.

Workaround: When you are using a different netmask from that of eth0 interface:

  1. You must manually update the correct netmask from the GUI.

  2. Save and let the node reboot after the patch installation.

v2

PR1817824

Initial database backup in Junos Space Network Management Platform fails with Failed to backup configuration files error message.

v2

PR1819181

Device re-synchronization in ICEAAA Manager fails when the user is not assigned to Global domain in Junos Space Network Management Platform.

v2

PR1821198

When eth0 interface fails on the App Logic master node, the SSH connection between the devices and the failed node does not get disconnected. Whereas the actual App Logic master node function is replaced by another node in the cluster.

v2

PR1822500

jmp-firewall takes longer than usual to restart in Junos Space Network Management Platform Release 24.1R1.

v2

PR1822712

While editing the user group, the number of assigned users disappears in Junos Space Network Management Platform.

v2

PR1822987

Incorrect RAM configuration in host.xml.slave.

Note:

To change the RAM size from the default calculated values:

    1. Navigate to the file located at /usr/local/jboss/domain/configuration/host.xml.slave.
    2. Under jvm name="platform", locate jvm-options.
    3. Change the following values within the jvm-options: 
      xml <option value="-XX:PermSize=<existing value>"/> 
<option value="-XX:MaxPermSize=<new value>"/>

v2

PR1822993

Script management and job management requests are different on application nodes when the API calls are made without specifying any header in Junos Space Network Management Platform Release 24.1R1.

v2

PR1826265

The scrpits used to resolve device synchronization issue do not work as expected.

v2

PR1828027

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

v2

PR1832791

The default gateway for eth3 is empty after the initial setup is complete.

v2
PR1687708

The user is unable to upgrade the QFX5200-32C-32Q device from Junos Space Network Management Platform.

v1
PR1779130

Device discovery fails in Junos Space Network Management Platform when you configure the eth3 interface, and the device status shows connecting in Device Management.

v1

Known Issues in the Hot Patch

Junos Space Network Management Platform Release 24.1R1 hot patch includes the following known issue:

The progress bar fails to appear when the server is in maintenance mode. PR1836787

Junos Space Network Management Platform 24.1R2 Hot Patch Release

This section describes the installation procedure and resolved issues in Junos Space Network Management Platform Release 24.1R2 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 24.1R2 Patch vX from the download site.

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

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

  4. Extract the Space-24.1R2-Hotpatch-vX.tgz file:

    tar -zxvf Space-24.1R2-hotpatch-vX.tgz

  5. Change the directory to Space-24.1R2-Hotpatch-vX.

    cd Space-24.1R2-Hotpatch-vX

  6. . Execute the patchme.sh script from the Space-24.1R2-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-24.1R2-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 through SSH to apply the hotpatch.

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

Resolved Issues

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

Table 2: Resolved Issues in Junos Space Network Management Platform Release 24.1R2 Hot Patch
PR Description Hot Patch Version

PR1861079

Security Director application image fails to update in Junos Space Network Management Platorm Release 24.1R2.15 FIPS enabled setup with an error message.

v1

Junos Space Network Management Platform 24.1R3 Hot Patch Release

This section describes the installation procedure and resolved issues in Junos Space Network Management Platform Release 24.1R3 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 24.1R3 Patch vX from the download site.

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

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

  4. Extract the Space-24.1R3-Hotpatch-vX.tgz file:

    tar -zxvf Space-24.1R3-hotpatch-vX.tgz

  5. Change the directory to Space-24.1R3-Hotpatch-vX.

    cd Space-24.1R3-Hotpatch-vX

  6. . Execute the patchme.sh script from the Space-24.1R3-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-24.1R3-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 through SSH to apply the hotpatch.

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

  • You must install Junos Space Network Management Platform Release 24.1R3 HPv1 only on Junos Space Network Management Platform Release 24.1R3.

Resolved Issues

Table 3 lists the resolved issues in Junos Space Network Management Platform Release 24.1R3 hot patch.

Table 3: Resolved Issues in Junos Space Network Management Platform Release 24.1R3 Hot Patch
PR Description Hot Patch Version

PR1860312

When the user switches to a different window in Junos Space Network Management Platform, the delete user functionality gets disabled under User Groups.

v1

PR1860367

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

v1

PR1860507

SSH connection to the nodes fails with an error in Junos Space Network Management Platform Release 24.1R2.

v1

PR1849459

The scripts used to perform checks on the MX Series Router do not work as expected.

v1

PR1864861

Junos Space Network Management Platform Release 24.1R3 fails to display the Summary and End Time details for Put Device in RMA State type jobs. It directly shows the status as Success.

v1

PR1826265

The scripts used to resolve device synchronization issue do not work as expected.

v1