Juniper NETWORKS 24.1R1 Junos Space Network Management Platform User Guide

User Guide for Juniper NETWORKS models including: 24.1R1, 24.1R2, 24.1R3, 24.1R1 Junos Space Network Management Platform, 24.1R1, Junos Space Network Management Platform, Network Management Platform, Management Platform, Platform

Release Notes 24.1

Junos Space is a comprehensive network management solution that simplifies and automates management of Juniper Networks switching, routing, and security devices.The terms Junos Space Network Management Platform and Junos Space Platform are used interchangeably in this document.

Juniper Networks, Inc.

Release Notes 24.1

5 мая 2025 г. — If they do not match, the status shows Out of Sync. Installation Instructions. Junos Space Network Management Platform Release 24.1R1 can be installed on a ...

[PDF] Release Notes 24.1 | Juniper Networks

May 29, 2025 · These release notes accompany Junos Space Network Management Platform Release 24.1R1, R2 and. R3. New and Changed Features. New and Changed ...

File Info : application/pdf, 58 Pages, 606.77KB

release-note-24.1

Release Notes
Release Notes 24.1

2025-05-05

Juniper Business Use Only

1
Introduction
Junos Space is a comprehensive network management solution that simplifies and automates management of Juniper Networks switching, routing, and security devices. Junos Space Management Applications optimize network management by extending the breadth of the Junos Space solution for various domains in service provider and enterprise environments. These release notes accompany Junos Space Network Management Platform Release 24.1R1, R2 and R3.
NOTE: The terms Junos Space Network Management Platform and Junos Space Platform are used interchangeably in this document.
New and Changed Features
IN THIS SECTION New and Changed Features in Junos Space Network Management Platform Release 24.1R1 | 1 New and Changed Features in Junos Space Network Management Platform Release 24.1R3 | 3
New and Changed Features in Junos Space Network Management Platform Release 24.1R1
Junos Space® Network Management Platform Release 24.1R1 supports the following enhancements: · We've upgraded the Junos Space host Linux OS to Rocky Linux 9.2. For more details, see Upgrading
to Junos Space Network Management Platform Release 24.1R1. · Starting in Junos Space Network Management Platform Release 24.1R1, we've upgraded to MySQL
v8.
Juniper Business Use Only

2
· Support for SRX1600 firewall--Starting in Junos Space Network Management Platform Release Hot Patch 23.1R1, we provide support for SRX1600 firewall.
· Support for SRX2300 firewall--Starting in Junos Space Network Management Platform Release Hot Patch 23.1R1, we provide support for SRX2300 firewall.
· Support for insert command in Quick template--Starting in Junos Space Network Management Platform Release 24.1R1, we provide support for the insert command in an existing Quick template. You can use the insert command in any order or in a combination of set, insert, and delete commands. However, the insert command supports only the after keyword.
· Decoupling of OpenNMS from Junos Space Network Management Platform--Starting in Junos Space Network Management Platform Release 24.1R1: · We no longer include the network monitoring software OpenNMS with Junos Space Network Management Platform. You'll need to install OpenNMS on a separate server. However, you can integrate OpenNMS with Junos Space Network Management Platform. The integration provides the following features: · When you add or delete any device from Junos Space Network Management Platform, the device list gets updated on the OpenNMS database. · You can set an SNMP v3 OpenNMS IP trap target on devices managed by Junos Space Network Management Platform. · Enables manual synchronization to avoid any discrepancy between Junos Space Network Management Platform and OpenNMS. For more details, see Integration of OpenNMS with Junos Space Network Management Platform. · We don't support Fault Monitoring and Performance Monitoring (FMPM) nodes.
· Discontinued support for Network Director--Starting in Junos Space Network Management Platform Release 24.1R1, we no longer support Network Director.
NOTE: Junos Space Network Management Platform Release 24.1R1 supports only nonFIPS mode.
Juniper Business Use Only

3
New and Changed Features in Junos Space Network Management Platform Release 24.1R3
Junos Space® Network Management Platform Release 24.1R3 supports the following enhancements: · Support for SRX4700 firewall--Starting in Junos Space Network Management Platform Release
24.1R3, we provide support for SRX4700 firewall. · Configuration comparison using templates--Starting in Junos Space Network Management Platform
Release 24.1R3, we provide support to compare device configurations against templates with variables. When you execute the Compare Template Against Device job successfully, the status indicates In Sync if the device and template configurations match. If they do not match, the status shows Out of Sync.
Installation Instructions
Junos Space Network Management Platform Release 24.1R1 can be installed on a Junos Space Virtual Appliance.
CAUTION: During the Junos Space Network Management Platform installation process, do not modify the filename of the software image that you download from the Juniper Networks support site. If you modify the filename, the installation fails.
NOTE: Junos Space Network Management Platform Release 24.1R2 is qualified and is compatible with Security Director Release 24.1R2. For installation instructions for a Junos Space Virtual Appliance, see the Junos Space Virtual Appliance Deployment Overview section of the Junos Space Virtual Appliance Installation and Configuration Guide. See No Link Title for more information about the hardware supported.
Juniper Business Use Only

4
Upgrade Instructions
IN THIS SECTION Supported Upgrade Path | 4 Upgrade Notes | 6 Instructions for Validating the Junos Space Network Management Platform OVA Image | 6

This section provides information about upgrading the Junos Space Network Management Platform installations running versions earlier than Release 24.1R1. · "Supported Upgrade Path" on page 4
· "Upgrade Notes" on page 6
· "Instructions for Validating the Junos Space Network Management Platform OVA Image" on page 6
NOTE: You can download the supported Junos Space Network Management Platform Applications such as Security Director and Policy Enforcer whenever they are available on the download site.

Supported Upgrade Path

Table 1 on page 4 provides information about the supported upgrade path across Junos Space Network Management Platform releases.
Table 1: Supported Upgrade Path

Upgrade from Junos Space Release

Junos Space Release

21.2

22.1

22.2

22.3

23.1

24.1

Juniper Business Use Only

Table 1: Supported Upgrade Path (Continued)
Upgrade from Junos Space Release

21.1

Yes

21.2

Yes

21.3

Yes

22.1

Yes

22.2

Yes

22.3

Yes

23.1

Yes

Related Information · Upgrading Junos Space Network Management Platform Overview · Juniper Networks Devices Supported by Junos Space Network Management Platform · Upgrading Junos Space Network Management Platform

NOTE: Before you upgrade Junos Space Platform to Release 24.1, ensure that the time on all Junos Space nodes is synchronized. For information about synchronizing time on Junos Space nodes, see Synchronizing Time Across Junos Space Nodes.
You can upgrade to Junos Space Network Management Platform 24.1R1 from the following earlier release:
· Junos Space Network Management Platform Release 23.1R1.

CAUTION: During the Junos Space Network Management Platform upgrade process, do not modify the filename of the software image that you download from the Juniper Networks support site. If you modify the filename, the upgrade fails.

Juniper Business Use Only

6
Upgrade Notes
· Before the upgrade, ensure that the latest backups are available in a location other than the Junos Space server. For more information about backups, see Backing Up the Junos Space Network Management Platform Database.
· To upgrade to Junos Space Network Management Platform Release 24.1R1, follow the procedure mentioned in Upgrade to Junos Space Network Management Platform Release 24.1R1.
· During the upgrade process, do not manually reboot the nodes if the Junos Space user interface does not come up for an extended period of time. Contact the Juniper Networks Support team for help in resolving this issue.
· After you upgrade Junos Space Platform to Release 24.1R1, all previously installed applications are disabled until the applications are upgraded to a version compatible with Junos Space Platform 24.1R1. You must upgrade the applications to releases that are compatible with Junos Space Platform Release 24.1R1, by using the Junos Space Platform UI. For information about application versions compatible with Junos Space Platform 24.1R1, see No Link Title.
Instructions for Validating the Junos Space Network Management Platform OVA Image
From Junos Space Network Management Platform Release 14.1R1 onward, the Junos Space Platform open virtual appliance (OVA) image is securely signed.
NOTE: · Validating the OVA image is optional; you can install or upgrade Junos Space
Network Management Platform without validating the OVA image. · Before you validate the OVA image, ensure that the PC on which you are performing
the validation has the following utilities available: tar, openssl, and ovftool (VMWare Open Virtualization Format (OVF) Tool). You can download VMWare OVF Tool from the following location: https://my.vmware.com/web/vmware/downloads/details? productId=353&downloadGroup=OVFTOOL351.
To validate the Junos Space Network Management Platform OVA image:
Juniper Business Use Only

7
1. Download the Junos Space Platform OVA image and the Juniper Networks Root CA certificate chain file (JuniperRootRSACA.pem) from the Junos Space Network Management Platform - Download Software page at https://www.juniper.net/support/downloads/space.html.
NOTE: You need to download the Juniper Networks Root CA certificate chain file only once; you can use the same file to validate OVA images for future releases of Junos Space Network Management Platform.
2. (Optional) If you downloaded the OVA image and the Root CA certificate chain file to a PC running Windows, copy the two files to a temporary directory on a PC running Linux or Unix. You can also copy the OVA image and the Root CA certificate chain file to a temporary directory (/var/tmp or /tmp) on a Junos Space node.
NOTE: Ensure that the OVA image file and the Juniper Networks Root CA certificate chain file are not modified during the validation procedure. You can do this by providing write access to these files only to the user performing the validation procedure. This is especially important if you use a generally accessible temporary directory, such as /tmp or /var/tmp, because such directories can be accessed by several users.
3. Navigate to the directory containing the OVA image. 4. Unpack the OVA image by executing the following command:
tar xf ova-filename where ova-filename is the filename of the downloaded OVA image. 5. Verify that the unpacked OVA image contains a certificate chain file (junos-space-certchain.pem) and a signature file (.cert extension). 6. Validate the signature in the unpacked OVF file (extension .ovf) by executing the following command: ovftool ovf-filename, where ovf-filename is the filename of the unpacked OVF file. 7. Validate the signing certificate with the Juniper Networks Root CA certificate chain file by executing the following command: openssl verify -CAfile JuniperRootRSACA.pem -untrusted Certificate-Chain-File Signature-file where JuniperRootRSACA.pem is the Juniper Networks Root CA certificate chain file, CertificateChain-File is the filename of the unpacked certificate chain file (extension .pem), and Signature-file is the filename of the unpacked signature file (extension .cert). If the validation is successful, a message indicating that the validation is successful is displayed.
Juniper Business Use Only

A sample of the validation procedure is as follows:

-bash-4.1$ ls

JuniperRootRSACA.pem space-16.1R1.3.ova

-bash-4.1$ mkdir tmp

-bash-4.1$ cd tmp

-bash-4.1$ tar xf ../space-16.1R1.3.ova

-bash-4.1$ ls

junos-space-certchain.pem space-16.1R1.3.cert

space-16.1R1.3-disk1.vmdk.gz space-16.1R1.3.mf

space-16.1R1.3.ovf

-bash-4.1$ ovftool space-16.1R1.3.ovf

OVF version: 1.0

VirtualApp: false

Name:

viso-space-16.1R1.3

Download Size: 1.76 GB

Deployment Sizes: Flat disks: 250.00 GB Sparse disks: 4.68 GB

Networks:

Name:

VM Network

Description: The VM Network network

Virtual Machines:

Name:

viso-space-16.1R1.3

Operating System: rhel5_64guest

Virtual Hardware:

Families:

vmx-04

Number of CPUs: 4

Cores per socket: 1

Memory:

8.00 GB

Disks: Index: Instance ID: Capacity: Disk Types:

0 7 250.00 GB SCSI-lsilogic

NICs:

Juniper Business Use Only

Adapter Type: Connection:

E1000 VM Network

Adapter Type: Connection:

E1000 VM Network

Adapter Type: Connection:

E1000 VM Network

Adapter Type: Connection:

E1000 VM Network

-bash-4.1$ openssl verify -CAfile JuniperRootRSACA.pem -untrusted junos-space-certchain.pem space-16.1R1.3.cert space-16.1R1.3.cert: OK -bash-4.1$

8. (Optional) If the validation is not successful, perform the following tasks:
a. Determine whether the contents of the OVA image are modified. If the contents are modified, download the OVA image from the Junos Space Network Management Platform - Download Software page.
b. Determine whether the Juniper Networks Root CA certificate chain file is corrupted or modified. If it is corrupted or modified, download the Root CA certificate chain file from the Junos Space Network Management Platform - Download Software page.
c. Retry the preceding validation steps by using one or both of the new files.

Management Scalability
We recommend the following API limit for Junos Space Network Management Platform and Security Director: · RAM: 64GB · CPU Cores: 8 · No of API calls per minutes: 500 · Response size: ~ 500 KB

Juniper Business Use Only

10
NOTE: The number of successful API calls and time taken to execute may vary based on the response payload. Extremely large payloads will slow down request completion process. The size of the response you receive from an API may differ based on the endpoint you call. Different endpoints return varying amounts of data depending on their intended functionality and purpose. The number of API calls is limited to 250 requests per minute per source IP address. When you exceed the limit, Junos Space Network Management Platform blocks the IP address for a timespan of two minutes before unblocking the IP again.
Application Compatibility
WARNING: Before you upgrade to Junos Space Network Management Platform Release 24.1R1, ensure that compatible versions of Junos Space applications are available for upgrade by referring to the Junos Space Application Compatibility Junos Space Application Compatibility knowledge base article. If you upgrade to Junos Space Platform Release 24.1R1 and the compatible version of a Junos Space application is not available, the current version of the Junos Space application is deactivated and cannot be used until Juniper Networks release a compatible version of the Junos Space application.
NOTE: Junos Space Network Management Platform Release 24.1R2 is qualified and is compatible with Security Director Release 24.1R2. This release of Junos Space Network Management Platform supports Worldwide (ww) Junos OS Adapter adapter and the following applications. · Security Director 24.1R1
Supported Hardware
Junos Space Network Management Platform Release 24.1R1 can be installed on the following hardware: · VMware ESXi server 8.0.
Juniper Business Use Only

NOTE: Adobe Flash is no longer supported and VMware ESXi server 6.0 and 6.5 are removed.
· Kernel-based virtual machine (KVM) (Release 1.5.3-141.el7_4.4 or later)
NOTE: Starting in Junos Space Network Management Platform Release 22.3R1 onward, we do not support installation on JA2500 Junos Space appliance.
For detailed information about hardware requirements, see the Hardware Documentation section of theJunos Space and Applications page.
NOTE: For information about whether a Junos Space application can be installed on Junos Space Virtual Appliance, see the release notes of the specific Junos Space application release.
NOTE: For detailed information about hardware requirements, see Junos Space Virtual Appliance Deployment Overview.

Supported Devices

Junos Space Network Management Platform Release 24.1R1 supports the following additional Juniper Networks device and components running Junos OS:
Table 2 on page 11 lists all the Juniper Networks product series and devices supported by Junos Space Network Management Platform.
Table 2: Devices Supported by Junos Space Network Management Platform

Product Series

Model

Junos Space Platform Release

ACX Series

ACX710

Junos Space 20.1R1 hot patch v1or later

ACX1000

Junos Space Platform 12.2 or later

Juniper Business Use Only

Table 2: Devices Supported by Junos Space Network Management Platform (Continued)

Product Series

Model

Junos Space Platform Release

ACX1100

Junos Space Platform 12.3 or later

ACX2100

Junos Space Platform 12.3 or later

ACX2200

Junos Space Platform 12.3 or later

ACX5448

Junos Space Platform 18.4 or later

EX Series

EX2300

Junos Space Platform 15.2R2 or later

EX2300-24MP

Junos Space Platform 18.1 or later

EX2300-48MP

Junos Space Platform 17.2 or later

EX3400

Junos Space Platform 15.2R2 or later

EX4100-12T

Junos Space Platform 22.3R1 or later

EX4100-24P

Junos Space Platform 23.1R1 or later

EX4100-24T

Junos Space Platform 23.1R1 or later

EX4100-48P

Junos Space Platform 23.1R1 or later

EX4100-24MP

Junos Space Platform 23.1R1 or later

EX4100-48T

Junos Space platform 22.3R1 or later

EX4100-48MP

Junos Space platform 22.3R1 or later

Juniper Business Use Only

Table 2: Devices Supported by Junos Space Network Management Platform (Continued)

Product Series

Model

Junos Space Platform Release

EX4100-F-12P

Junos Space Platform 22.3R1 or later

EX4100-F-12T

Junos Space platform 22.3R1 or later

EX4100-F-24T

Junos Space Platform 22.3R1 or later

EX4100-F-24P

Junos Space Platform 23.1R1 or later

EX4100-F-48P

Junos Space platform 22.3R1 or later

EX4100-F-48T

Junos Space Platform 22.3R1 or later

EX4300

Junos Space Platform 13.1 or later

EX4300-48MP

Junos Space Platform 18.3R1 or later

EX4400-24T

Junos Space Platform 21.1R1 or later

EX4400-48F

Junos Space Platform 21.1R1 or later

EX4400-48P

Junos Space Platform 21.1R1 or later

EX4400-48T

Junos Space Platform 21.1R1 or later

EX4400-24X

Junos Space platform 23.1R1 or later

Juniper Business Use Only

Table 2: Devices Supported by Junos Space Network Management Platform (Continued)

Product Series

Model

Junos Space Platform Release

EX4550-40G

Junos Space Platform 12.2 or later

EX4600

Junos Space Platform 13.3 or later

EX4650

Junos Space Platform 18.4 or later

EX6200

Junos Space Platform 13.2 or later

EX9200

Junos Space Platform 13.1 or later

EX9204

Junos Space Platform 13.1 or later

EX9208

Junos Space Platform 13.1 or later

EX9214

Junos Space Platform 13.1 or later

EX4400-24P

Junos Space Platform 21.1R1 or later

EX4400-24MP

Junos Space Platform 21.2 or later

EX4400-48MP

Junos Space Platform 21.2 or later

EX Virtual Chassis

EX2300-VC

Junos Space Platform 23.1R1

EX3300-VC

Junos Space Platform 15.2 or later

EX3400-VC

Junos Space Platform 23.1R1

EX4100-VC

Junos Space Platform 22.3R1

EX4200-VC

Junos Space Platform 11.4 or later

EX4200-VC

Junos Space Platform 11.4 or later

EX4300-VC

Junos Space Platform 13.1 or later

Juniper Business Use Only

Table 2: Devices Supported by Junos Space Network Management Platform (Continued)

Product Series

Model

Junos Space Platform Release

EX4400-VC

Junos Space Platform 23.1R1

EX4550-VC

Junos Space Platform 13.1 or later

EX4600-VC

Junos Space Platform 16.1 or later

EX-XRE

Junos Space Platform 14.1R2 or later

Firefly

vSRX Virtual Firewall Firefly

Junos Space Platform 15.1 or later

Junos Fusion

Junos Fusion Edge

Junos Space Platform 17.1 or later

MCG Series

MCG5000

Junos Space Platform 11.3 or later

MX Series

MX204

Junos Space Platform 18.2 or later

MX240

Junos Space Platform 13.1 or later

MX480

Junos Space Platform 13.1 or later

MX960

Junos Space Platform 13.1 or later

MX10008

Junos Space Platform 18.4 or later

MX2008

Junos Space Platform 17.1 or later

MX2010

Junos Space Platform 12.3 or later

MX2020

Junos Space Platform 12.3 or later

MX Series Virtual Chassis

MX-VC

Junos Space Platform 14.1 or later

PTX Series

PTX10008

Junos Space Platform 17.2 or later

PTX10016

Junos Space Platform 17.2 or later

Juniper Business Use Only

Table 2: Devices Supported by Junos Space Network Management Platform (Continued)

Product Series

Model

Junos Space Platform Release

QFX Series

QFX3000

Junos Space Platform 12.2 or later

QFX3500

Junos Space Platform 12.3 or later

QFX3600

Junos Space Platform 13.1 or later

QFX5110-32Q

Junos Space Platform 17.1 or later

QFX5110-48S

Junos Space Platform 17.1 or later

QFX5120-32C

Junos Space Platform 19.4 or later

QFX5120

Junos Space Platform 18.4 or later

QFX5210

Junos Space Platform 18.4 or later

QFX5200

Junos Space Platform 15.1R2 or later

QFX5200-48Y

Junos Space Platform 18.1 or later

QFX5210-64C

Junos Space Platform 18.1 or later

QFX10002-36Q

Junos Space Platform 15.1 or later

QFX10002-36Q-DC

Junos Space Platform 15.1 or later

QFX10002-60C

Junos Space Platform 18.1 or later

QFX10002-72Q

Junos Space Platform 15.1 or later

QFX10002-72Q-DC

Junos Space Platform 15.1 or later

QFX10008

Junos Space Platform 15.1R2 or later

Juniper Business Use Only

Table 2: Devices Supported by Junos Space Network Management Platform (Continued)

Product Series

Model

Junos Space Platform Release

QFX10016

Junos Space Platform 15.1R2 or later

QFX5120-48YM-8C

Junos Space Platform 21.1R1 or later

QFX Series Virtual Chassis

QFX-VC

Junos Space Platform 14.1 or later

SRX Series

SRX240H

Junos Space Platform 14.1R1 or later

SRX300

Junos Space Platform 15.1R2 or later

SRX320

Junos Space Platform 15.1R2 or later

SRX320-PoE

Junos Space Platform 15.1R2 or later

SRX340

Junos Space Platform 15.1R2 or later

SRX345

Junos Space Platform 15.1R2 or later

SRX380

Junos Space 20.1R1 hot patch v1or later

SRX550-M

Junos Space Platform 15.1R2 or later

SRX1500

Junos Space Platform 15.1R2 or later

SRX1600

Junos Space Platform 24.1R1 or later

Juniper Business Use Only

Table 2: Devices Supported by Junos Space Network Management Platform (Continued)

Product Series

Model

Junos Space Platform Release

SRX2300

Junos Space Platform 24.1R1 or later

SRX4100

Junos Space Platform 16.1 or later

SRX4200

Junos Space Platform 16.1 or later

SRX4600

Junos Space Platform 17.2 or later

SRX5400

Junos Space Platform 13.2 or later

SRX5600

Junos Space Platform 18.2 or later

SRX5800

Junos Space Platform 13.3 or later

Virtual SRX Series

vSRX Virtual Firewall 3.0

Junos Space Platform 18.2 or later

Virtual route reflector (VRR)

VRR

Junos Space Platform 14.1R2 or later

WLC Series

WLC device

Junos Space Platform 14.1 or later

NOTE: Ensure that you install the exact matching or closest matching of Junos OS schema on the Junos Space Platform. For more information, see Table 3 on page 18.

Table 3 on page 18 lists the devices supported by Junos Space Network Management Platform with compatible Junos OS Releases:
Table 3: Devices Supported by Junos Space Platform with Compatible Junos OS Releases

Product Series

Model

Supported Junos Operating System (Junos OS) Releases

Qualified Schema Version

ACX Series

ACX710

20.2R1

Juniper Business Use Only

Table 3: Devices Supported by Junos Space Platform with Compatible Junos OS Releases (Continued)

Product Series

Model

Supported Junos Operating System (Junos OS) Releases

Qualified Schema Version

ACX5448

18.3R1 18.4R1.8 or later

18.4R1.8 18.4R1.8

EX Series

EX2300

18.1R3.3 18.4R1.8 or later 20.4R3-Sx

18.1R3.3 18.4R1.8 20.2R3

EX2300-24T EX3400

21.4R3-S1 18.1R3.3 18.4R1.8 or later

21.4R3-S1.5 18.1R3.3 18.4R1.8

EX4100-12T EX4100-24P EX4100-24T

22.3R1.12 23.1R1.2 23.1R1.2

EX4100-24MP

23.1R1.2

EX4100-48P

23.1R1.2

EX4100-48T

22.3R1.12

EX4100-48MP

22.3R1.12

EX4100-F-12P

22.3R1.12

EX4100-F-12T

22.3R1.12

Juniper Business Use Only

Table 3: Devices Supported by Junos Space Platform with Compatible Junos OS Releases (Continued)

Product Series

Model

Supported Junos Operating System (Junos OS) Releases

Qualified Schema Version

EX4100-F-24P

23.1R1.2

EX4100-F-24T

22.3R1.12

EX4100-F-48P

22.3R1.12

EX4100-F-48T

22.3R1.12

EX4300-MP

21.2R3.8

EX4650

21.2R3.8

EX4400

21.3R2

21.1/R1

EX4300

17.3R3-S1.5 18.4R1.8 or later

17.3R3-S1.5 18.4R1.8

EX4300-48MP

17.3R3-S1.5 18.4R1.8 or later

18.4R1.8

EX4400-24P EX4400-24MP

21.1R1.11 or later 21.2R1.10 or later

21.1R1.11 21.2R1.10

EX4400-48MP

21.2R1.10 or later

21.2R1.10

EX4400-24T

21.1R1.11 or later

EX4400-48F

21.1R1.11 or later

Juniper Business Use Only

Table 3: Devices Supported by Junos Space Platform with Compatible Junos OS Releases (Continued)

Product Series

Model

Supported Junos Operating System (Junos OS) Releases

Qualified Schema Version

EX4400-48P

21.1R1.11 or later 21.4R3-S1

21.1R1.11 or later 21.4R3-S1.5

EX4400-48T

21.1R1.11 or later

EX4400-24X

22.3R1.2

EX4600

17.3R3-S1.5 18.4R1.8 or later

17.3R3-S1.5 18.4R1.8

EX4650

18.4R1.8 or later 20.4/R3

18.4R1.8 20.2R3-S1

EX4650-48Y-8C

21.4R3-S1

21.4R3-S1.5

EX9200

17.3R3-S1.5 18.3R1.9 or later

17.3R3-S1.5 18.3R1.9

EX9204

20.3R1.3 or later

20.3R1.3

EX9208

20.3R1.3 or later

20.3R1.3

EX9208-BASE3A

20.4R3

17.3R3-S4

EX9214

20.3R1.3 or later

20.3R1.3

EX Virtual Chassis

EX4200-VC

12.2R1 or later

15.1R7.9

Juniper Business Use Only

Table 3: Devices Supported by Junos Space Platform with Compatible Junos OS Releases (Continued)

Product Series

Model

Supported Junos Operating System (Junos OS) Releases

Qualified Schema Version

EX3400-VC

20.2R2.8 or later

20.2R2.8

EX4100-48T-VC

22.3R1.12

EX4100-48MP-VC

22.3R1.12

EX4100-F-48P-VC

22.3R1.12

MX Series

MX204

18.4R1 or later

18.4R1.8

MX240

13.2R2.4 or later

17.3R3.9 18.4R1.8

MX480

13.2R2.4 or later

17.3R3-S2.2 17.3R3.9 19.1R1.6

MX10008

18.4R1.8 or later

18.4R1.8

MX960

21.2R1.6 or later 21.2R1.8 or later

21.2R1.6 21.2R1.8

SRX Series Firewall

SRX380

20.2R1

SRX300

20.2R3-S2

20.2R3-S2.5

SRX320

20.2R3-S2 21.2R3-S2.9

20.2R3-S2.5 21.2R3.8

Juniper Business Use Only

Table 3: Devices Supported by Junos Space Platform with Compatible Junos OS Releases (Continued)

Product Series

Model

Supported Junos Operating System (Junos OS) Releases

Qualified Schema Version

SRX340

21.2R3-S2.9

21.2R3.8

SRX345

21.2R3-S2.9

21.2R3.8

SRX550M

21.2R3-S2.9

21.2R3.8

SRX1500

21.2R1 and later

23.4R2

SRX1600

23.3R1.8

SRX2300

23.4R1.6

SRX4100

20.4R3-S1

20.2R3-S2.5

SRX4200

20.4R3-S1

20.2R3-S2.5

SRX5600

20.4R3-S1 21.2R3-S2.9

20.4R3-S1 21.2R3.8

SRX5800

20.4R3-S1 21.2R3-S2.9

20.4R3-S1 21.2R3.8

SRX550-645AP-M

20.2R3-S2.5

QFX Series

QFX5100

17.3R3 or later

17.3R3-S1.5 18.4R1.8

Juniper Business Use Only

Table 3: Devices Supported by Junos Space Platform with Compatible Junos OS Releases (Continued)

Product Series

Model

Supported Junos Operating System (Junos OS) Releases

Qualified Schema Version

QFX5110-32Q

17.3R3 or later

17.3R3-S1.5 19.1R1.6

QFX5110-48S

17.3R3-S1.5 19.1R1.6 or later

17.3R3-S1.5 19.1R1.6

QFX5120

18.4R1.8 or later

18.4R1.8

QFX5210

19.1R1.6 or later

19.1R1.6

QFX5200

17.3R3 or later

17.3R3.9 18.4R1.8

QFX5200-32C-32Q

21.2R3.8

QFX10002-36Q

17.3R3 or later

17.3R3-S1.5 19.1R1.6

QFX10002-36Q-DC

17.3R3 or later

17.3R3-S1.5 19.1R1.6

QFX10002-60C

17.3R3 or later

17.3R3-S1.5 19.1R1.6

QFX10002-72Q

17.3R3 or later 21.2R3.8

17.3R3-S1.5 19.1R1.6 21.2R3.8

Juniper Business Use Only

Table 3: Devices Supported by Junos Space Platform with Compatible Junos OS Releases (Continued)

Product Series

Model

Supported Junos Operating System (Junos OS) Releases

Qualified Schema Version

QFX10002-72Q-DC

17.3R3-S1.5 or later

17.3R3-S1.5

QFX10008

17.3R3 or later

17.3R3.9 18.4R1.8

QFX5120-48T-6C

20.2R1.10 or later

20.2R1.10

QFX5120-48YM-8C

20.4R1.12

NOTE: When Junos Space Platform discovers EX Series switches running Layer 2 next generation software, the device family for these devices is displayed (on the Device Management page) as junos and not as junos-ex. This behavior is currently observed on EX4300 and EX9200 switches running Layer 2 next generation software.
NOTE: Previous versions of Junos OS releases are also supported. If you are using previous versions of Junos OS releases, you can continue to use the same versions. For a complete list of Junos OS compatibility and support information, see "Supported Junos OS Releases" on page 25.

Supported Junos OS Releases

IN THIS SECTION Supported Junos OS Releases for Junos Space Network Management Platform Release 24.1R1 | 26 Supported Junos OS Releases for Junos Space Network Management Platform Release 24.1R2 | 27

Juniper Business Use Only

Supported Junos OS Releases for Junos Space Network Management Platform Release 24.1R1

Junos Space Network Management Platform Release 24.1R1 supports the following Junos OS releases: · Junos OS Release 21.2 · Junos OS Release 22.1 · Junos OS Release 22.2 · Junos OS Release 22.3 · Junos OS Release 23.1 · Junos OS Release 24.1 Table 4: Release History

Release value

Description

24.1

Junos OS Release 24.1

23.1

Junos OS Release 23.1

22.3

Junos OS Release 22.3

22.2

Junos OS Release 22.2

22.1

Junos OS Release 22.1

21.2

Junos OS Release 21.2

Juniper Business Use Only

Supported Junos OS Releases for Junos Space Network Management Platform Release 24.1R2

Junos Space Network Management Platform Release 24.1R2 supports the following Junos OS releases: · Junos OS Release 21.2 · Junos OS Release 22.1 · Junos OS Release 22.2 · Junos OS Release 22.3 · Junos OS Release 23.1 · Junos OS Release 24.2 Table 5: Release History

Release value

Description

24.1

Junos OS Release 24.2

23.1

Junos OS Release 23.1

22.3

Junos OS Release 22.3

22.2

Junos OS Release 22.2

22.1

Junos OS Release 22.1

21.2

Junos OS Release 21.2

Juniper Business Use Only

28
Changes in Default Behavior
· From Release 17.2R1 onward, Junos Space Platform does not sort configurations while comparing templates. In releases earlier than 17.2R1, Junos Space Platform sorts configurations while comparing templates, and this causes Junos Space Platform to trigger incorrect deviation reports because of a change in the order of configuration statements caused by the sorting.
· From Release 17.2R1 onward, Junos Space Platform does not support the click action in the Top 10 Active Users in 24 Hours chart. In releases earlier than 17.2R1, you can click within the chart to view details of the selected item on the corresponding page.
· From Junos Space Platform Release 17.1R1 onward, the VLAN field in reports supports both integer and string values. In releases earlier than 17.1R1, the VLAN field in reports supports only integer values, whereas the VLAN field for logical interfaces accepts both integer and string values. This mismatch causes issues in displaying VLAN information for logical interfaces in reports. From Release 17.1R1 onward, the VLAN option in the Add Filter Criteria section of the Create Report Definition page and the filter support for the VLAN column on the View Logical Interface page are removed.
· From Junos Space Platform Release 16.1R2 onward, the upgrade-related logs at /var/jmp_upgrade are added to the troubleshooting logs.
· From Release 17.1R1 onward, Junos Space Platform boot menu accepts text inputs, such as reinstall, when you install the Junos Space Platform software from USB drives. In versions earlier than Release 17.1R1, the boot menu supports only numerical values. From Release 17.1R1 onward, when you do a reinstall, the software restarts and a local reboot occurs by default. Previously, you had to connect to the console and manually trigger a reboot.
· From Junos Space Platform Release 16.1R2 onward, validation messages are provided for tasks where CSV files are used for device selection, and all devices that are listed in the CSV file are not selected when the task is performed. Validation messages are provided when devices are selected using CSV files from the following pages and dialog boxes: · Deploy Device Image dialog box · Deploy Satellite Device Image dialog box · Stage Image on Device page · Stage Image on Satellite Device page · Remove Image from Staged Device dialog box · Undeploy JAM Package from Device dialog box
Juniper Business Use Only

29
· Verifying checksum of image on device(s) dialog box · Stage Scripts on Device(s) page · Disable Scripts on Device(s) page · Execute Script on Device(s) page · Remove Scripts from Device(s) dialog box · Verify Checksum of Scripts on Device(s) dialog box From Release 17.1R1 onward, validation messages are provided for the following pages and dialog boxes, too: · Run Operation page · Stage Script Bundle on Devices dialog box · Enable Script Bundle on Devices page · Disable Script Bundle on Devices page · Execute Script Bundle on Devices dialog box · Starting in Junos Space Network Management Platform Release 21.3R1, unicast Junos Space cluster is the default mode for Junos Space Network Management Platform. · Starting in Junos Space Network Management Platform Release 21.3R1, the AppLogic node restarts, when the Add Node jobs for JBoss and database nodes are successful. This is not applicable for Fault Monitoring and Performance Monitoring (FMPM) node. · While upgrading from Junos Space Network Management Platform Release 21.1R1 (with Junos Space Network Management Platform Release 21.1R1 supported applications) or Junos Space Network Management Platform Release 21.2R1 (with Junos Space Network Management Platform Release 21.1R1 supported applications) to Junos Space Network Management Platform Release 21.3R1, the deployment status is displayed only for the Junos Space Network Management Platform and not for the applications. · Starting in Junos Space Network Management Platform Release 21.3R1, the scripts with existing Network Configuration protocol (NETCONF) Remote Procedure Calls (RPC) commands needs to be replaced with CLI commands with display xml option. · Starting in Junos Space Network Management Platform Release 21.3R1, the AppLogic service restarts after the application upgrade or installation job is successful.
Juniper Business Use Only

30
· Starting in Junos Space Network Management Platform Release 21.3R1, before initiating any operation like configuration change, configlet or template push to the device, make sure that the nodes are not in Deploying / Parsing Schema state.
Known Behavior
CAUTION: To avoid a BEAST TLS 1.0 attack, whenever you log in to Junos Space through a browser tab or window, make sure that the tab or window was not previously used to access a non-HTTPS website. The best practice is to close your browser and relaunch it before logging in to Junos Space.
NOTE: In Junos Space Network Management Platform Release 24.1R3, the last monitoring time does not get updated post disaster recovery reset on the standby site.
· For EX Series Switches, an explicit reboot is required, using the device CLI to complete the image deployment and upgrade process.
· Starting from Junos Space Network Management Platform Release 18.1R1 onwards, to view and edit firewall policies, users must have permissions or roles corresponding to all the attributes present under the Firewall Policies and Shared Objects predefined roles. Go to Network Management Platform>Role Based Access Control>Roles to view and assign the relevant roles.
· Tag names can be alphanumeric strings. The tag name can also contain underscores, hyphens, and spaces. However, a tag name must not: · Exceed 255 characters · Start with a space · Contain special characters such as commas, double quotation marks, or parentheses.
NOTE: "Untagged" is a reserved term and, therefore, you cannot create a tag with this name.
· The right-click menu is not available on the Import Licenses (Administration > Licenses > Import License) page. You can use either the browser menu options or the keyboard shortcuts to copy and paste onto the page.
Juniper Business Use Only

31
· Device-initiated connections to Junos Space can have different IP addresses from those listed in Junos Space. For example, if you use a loopback address to discover a device, you can source the SSH session of the device from its interface address (Junos OS default behavior is to select the default address) instead. This can lead to firewall conflicts.
· You might observe the following limitations on the Topology page: · The tooltip on the node displays the status as Active/Managed even when the node is down. · For an SRX Series cluster, topology links are displayed only for the primary member of the cluster and not for the secondary member.
· When unified in-service software upgrade (ISSU) is performed from the Manage Operations workflow, the Routing Engines are not rebooted. The Routing Engines must be manually rebooted for the image to be loaded.
· For LSYS (logical, nonroot) devices, when there are pending out-of-band changes on the root device, the Resolve out-of-band changes menu option is disabled for those child LSYS devices, even though Device Managed Status displays Device Changed. This is by design.
· RMA is not supported on devices running ww Junos OS, and devices that are not running Junos OS. · Script Manager supports only Junos OS Release 10.x and later. · A stage device script or image supports only devices running Junos OS Release 10.x and later. · For unified ISSU support for both device-initiated and Junos Space-initiated dual Routing Engine
connections, we strongly recommend that you configure the virtual IP (VIP) on the dual Routing Engine device. Dual Routing Engine devices without VIP configuration are not fully supported on Junos Space. · In a single node or multiple nodes, changes to the user (for example, password, roles, and disable or enable user) take effect only at the next login. · Looking Glass functionality is not supported on logical systems. · For devices running Junos OS Release 12.1 or later, the following parameters do not display any data in the Network Monitoring workspace because the corresponding MIB objects have been deprecated: · jnxJsSPUMonitoringFlowSessIPv4 · jnxJsSPUMonitoringFlowSessIPv6 · jnxJsSPUMonitoringCPSessIPv4 · jnxJsSPUMonitoringCPSessIPv6 · jnxJsNodeSessCreationPerSecIPv4
Juniper Business Use Only

32
· jnxJsNodeSessCreationPerSecIPv6
· jnxJsNodeCurrentTotalSessIPv4
· jnxJsNodeCurrentTotalSessIPv6
· For SNMPv3 traps, if more than one trap setting is configured in the /opt/opennms/etc/trapdconfiguration.xml file, then the security-name attribute for the snmpv3-user element must be unique for each configuration entry. If a unique security-name attribute is not provided, then SNMP traps are not received by Network Monitoring. The following is a sample snippet of the /opt/opennms/etc/trapd-configuration.xml file with two configuration entries:
<?xml version="1.0"?> <trapd-configuration snmp-trap-port="162" new-suspect-on-trap="false">
<snmpv3-user security-name="Space-SNMP-1" auth-passphrase="abcD123!" auth-protocol="MD5"/> <snmpv3-user security-name="Space-SNMP-2" auth-passphrase="abcD123!" auth-protocol="MD5"
privacy-passphrase="zyxW321!" privacy-protocol="DES"/> </trapd-configuration>
· On the Network Monitoring > Node List > Node page, the ifIndex parameter is not displayed for IPv6 interfaces if the version of Junos OS running on the device is Release 13.1 or earlier. This is because IPv6 MIBs are supported only on Junos OS Release 13.2 and later.
· When you execute a script and click the View Results link on the Script Management Job Status page, the details of the script execution results are displayed up to a maximum of 16,777,215 characters; the rests of the results are truncated. This might affect users who execute the show configuration command on devices with large configurations or if the output of a Junos OS operational command (executed on a device) is large.
· When you configure a Junos Space fabric with dedicated database nodes, the Junos Space Platform database is moved from the Junos Space nodes to the database nodes. You cannot move the database back to the Junos Space nodes.
· For a purging policy triggered by a cron job: · If the Junos Space fabric is configured with MySQL on one or two dedicated database nodes, the database backup files and log files (mainly in the /var/log/ directory with the filenames *.log.*, messages.*, or SystemStatusLog.*) are not purged from the dedicated database nodes.
· If Network Monitoring receives two traps within the same second--that is, one for a trigger alarm and another for a clear alarm--then the triggered alarm is not cleared because the clear alarm is not processed by Network Monitoring.
Juniper Business Use Only

33
· If you use Internet Explorer versions 8.0 or 9.0 to access the Junos Space Platform GUI, you cannot import multiple scripts or CLI Configlets at the same time.
Workaround: Use Internet Explorer Version 10.0 or later, or use a different supported browser (Mozilla Firefox or Google Chrome) to import multiple scripts or CLI Configlets at the same time.
· If you access the Junos Space Platform UI in two tabs of the same browser with two different domains selected and access the same page in both tabs, the information displayed on the page is based on the latest domain selected. To view pages that are accessible only in the Global domain, ensure that you are in the Global domain in the most recent tab in which you are accessing the UI.
· If you select the Add SNMP configuration to device check box on the Administration > Applications > Modify Network Management Platform Settings page and discover a device whose trap target is updated, clicking Resync Node from the Network Monitoring workspace does not reset the trap target for the device.
· If you clear the Add SNMP configuration to device check box on the Administration > Applications > Modify Network Management Platform Settings page, the trap target is not set for the device during device discovery and resynchronizing node operations.
· If you want to perform a global search by using partial keywords, append "*" to the search keywords.
· To perform a partial keyword search on tags on the Tags page (Administration > Tags) or the Apply Tags dialog box (right-click a device on the Device Management page and select Tag It), append * to the search keyword.
· Internet Explorer slows down because some scripts can take an excessive amount of time to run. The browser prompts you to decide whether to continue running the slow script. see http:// support.microsoft.com/kb/175500 for instructions on how to fix this issue.
· When you switch from Space as system of record mode to Network as system of record mode, devices with the Managed Status Device Changed or Space & Device Changed are automatically synchronized after 900 seconds. To reduce this time period, modify the Polling time period secs setting for Network Management Platform (Administration > Applications > Modify Application Settings) to a lower value such as 150 seconds.
· In Space as System of Record (SSoR) mode on Junos Space, when a new authentication key is generated, devices discovered and managed using RSA keys whose management status is Device Changed move to the Key Conflict Authentication status. To resolve the conflict on the devices and bring them back to a key-based state, upload the RSA keys manually (Devices > Upload Keys to Devices).
· The EnterpriseDefault (uei.opennms.org/generic/trap/EnterpriseDefault) event appears on the Events page in the Network Monitoring workspace only if there is no associated event definition for a received event. To create the required event definition, compile the MIB corresponding to the object ID (OID). You can find the OID by reviewing the details of the EnterpriseDefault event.
Juniper Business Use Only

34
For more information about compiling SNMP MIBs, see Compiling SNMP MIBs.
· When a physical hard drive is removed from a Junos Space hardware appliance or a logical hard drive is degraded, the corresponding SNMP traps (jnxSpaceHardDiskPhysicalDriveRemoved and jnxSpaceHardDiskLogicalDeviceDegraded respectively) are generated and displayed as events in the Network Monitoring workspace. Later, when the physical hard drive is reinserted, the corresponding events (jnxSpaceHardDiskPhysicalDriveAdded and jnxSpaceHardDiskLogicalDeviceRebulding) are generated and displayed in the Network Monitoring workspace; however, the alarms previously raised for the removal of the physical hard drive are not cleared automatically. You can clear these alarms manually, if required. The alarms for the reinsertion of the physical hard drive are automatically cleared after a few minutes because they are of the Normal type.
· If you clear the Add SNMP configuration to device check box (on the Modify Network Management Platform Settings page under Administration > Applications > Network Management Platform > Modify Application Settings) and discover devices, and subsequently select the Add SNMP configuration to device check box and resynchronize nodes (Network Monitoring > Node List > Resync Nodes), the SNMPv2 trap target is updated on the devices.
· If you discover devices with the SNMP probing enabled, the correct version of the SNMP trap target is updated on the devices for the following cases: · When you modify the virtual IP (VIP) address or the device management interface IP address
· When a separate interface for device management is configured and there is a failover of the VIP node
· When you discover devices when the Network Monitoring service is stopped and subsequently start the Network Monitoring service and resynchronize nodes (Network Monitoring > Node List > Resync Nodes)
In all other cases, the default SNMP trap target (SNMPv2) is updated on the devices. If needed, you can use the predefined SNMPv3 Configlets (CLI Configlets > CLI Configlets) to update the trap settings on the device.
· In Junos Space Platform Release 16.1R1, Network Monitoring supports only a single set of SNMPv3 trap parameters.
· In Junos Space Platform Release 16.1R1, you cannot modify the trap settings for the SNMPv3 manager on the Network Monitoring GUI. You can modify the trap settings manually in the /opt/ opennms/etc/trapd-configuration.xml file. After modifying the trap settings manually, restart the Network Monitoring service.
· With default SNMPv3 trap settings, the discovery of devices running worldwide Junos OS (wwJunos OS devices) fails as the default SNMPv3 trap settings cannot be updated to wwJunos OS devices because wwJunos OS devices do not support privacy settings.
Juniper Business Use Only

35
· The setting to manage objects from all assigned domains can be enabled globally for all users by selecting the Enable users to manage objects from all allowed domains in aggregated view check box in the Domains section of the Modify Application Settings page (Administration > Applications > Network Management Platform > Modify Application Settings). Alternatively, you can enable the setting to manage objects from all assigned domains at the user level by selecting the Manage objects from all assigned domains check box on the Object Visibility tab of the Change User Settings dialog box, which appears when you click the User Settings (gear) icon on the Junos Space banner.
· The Juniper Networks Device Management Interface (DMI) schema repository (https:// xml.juniper.net/) does not currently support IPv6. If you are running Junos Space on an IPv6 network, you can do one of the following: · Configure Junos Space to use both IPv4 and IPv6 addresses and download the DMI schema by using the Junos Space Platform Web GUI.
· Download the DMI schema by using an IPv4 client and update or install the DMI schema by using the Junos Space Web GUI.
· If you are planning on expanding the disk space for nodes in a Junos Space fabric (cluster) comprising of virtual appliances, you must first expand the disk space on the VIP node and ensure that the VIP node has come up (the status of the JBoss and MySQL services must be "Up") before initiating the disk expansion on the other nodes in the fabric. If you fail to do this, it might cause fabric instability and you might be unable to access to the Junos Space GUI.
· In a Junos Space fabric with two or more nodes configured with both IPv4 and IPv6 addresses (dual stack), the communications between all nodes in the fabric must be enabled for both IPv4 and IPv6 addresses.
· The Network Monitoring Topology feature is not supported on Internet Explorer.
· If the network connectivity at the active disaster recovery site is down and the active site cannot connect to sufficient arbiter devices after resuming network connectivity, both sites become standby disaster recovery sites. Execute the jmp-dr manualFailover -a command at the VIP node of the active disaster recovery site to convert the original site to the active site and start the disaster recovery process.
· When you are discovering devices running the worldwide Junos OS (ww Junos OS devices), ensure that you wait at least 10 minutes after the Add Adapter job for the device worldwide Junos adapter has completed successfully before triggering the device discovery.
· A new pattern (requested 'commit synchronize' operation) is added to the syslog pattern in Junos Space Release 16.1R2. During the syslog registration after a device is discovered or connects back to Junos Space following a Junos Space upgrade from Release 16.1R1 to 16.1R2, the (requested 'commit synchronize' operation) pattern is added to the syslog patterns on the device. When you issue the commit synchronize command, Junos Space automatically resynchronizes only those
Juniper Business Use Only

36
devices that have the (requested 'commit synchronize' operation) pattern added to the syslog patterns. · If you are using Internet Explorer to access the Junos Space Network Platform UI and need to copy the job ID value from the Job ID field of the Job Management page, you must click outside the job ID text to start the selection. · After you upgrade Junos Space Platform from Release 16.1R1 to 17.1R1, the Last Reboot Reason field on the Administration > Fabric > View Node Detail > Reboot Detail page shows the value as Reboot from Shell/Other instead of Space reboot after Software Upgrade. · If the device IP could not be verified, the Add Unmanaged Devices action fails.
Known Issues
IN THIS SECTION Known Issues in Junos Space Network Management Platform Release 24.1R1 | 36 Known Issues in Junos Space Network Management Platform Release 24.1R3 | 37
Known Issues in Junos Space Network Management Platform Release 24.1R1
This section lists the known issues in Junos Space Network Management Platform Release 24.1R1. For the most complete and latest information about known defects, use the Juniper Networks online Junos Problem Report Search application. · When you change the VIP node IP and the device management IP, the toolkit configuration fails to
update the changed IPs. PR1791521 · There are issues in the CLI console during Junos Space Network Management Platform deployment.
PR1798841
Juniper Business Use Only

37
· During Junos Space Network Management Platform installation, when you enter NTP server details, it shows failure in the process even when it is in progress. Workaround: During installation process, you can choose to accept or ignore the configured NTP, DNS, and gateways. PR1783618
· When you run disaster recovery initialization on the standby site, it shows as in-progress in the runtime properties. PR1783788
· The VIP node is not associated to any other node when the primary database goes down while disaster recovery is in start state. For details, see Reimage a Node and Add Back with the Same IP Address. PR1796401
· When you start disaster recovery through Junos Space Network Management Platform GUI, it triggers only in the active site. Workaround: Log in to the CLI and while targetting the standby site, run the jmp-dr start -s command. PR1793727
· In two nodes disaster recovery, when you try to change the IP node, it becomes unreachable. Workaround: · If you want to change any of the VIP nodes, IP nodes or device management IPs in the disaster recovery setup, you must reset the disaster recovery and create them as two independent sites. · Perform the required IP changes either through the CLI menu. Select Change Network Settings. Or, through the Junos Space Network Management Platform GUI under Administration > Fabric. When the required IPs are changed, both setups are stable, and disaster recovery is recreated between the sites. PR1792583
· During disaster recovery operation, if any operation is running at the back-end during database restart, Fail in load selections data window appears. You must select OK and continue. PR1789812
Resolved Issues
IN THIS SECTION Resolved Issues in Junos Space Network Management Platform Release 24.1R1 | 38 Resolved Issues in Junos Space Network Management Platform Release 24.1R2 | 40 Resolved Issues in Junos Space Network Management Platform Release 24.1R3 | 41
Juniper Business Use Only

38
Resolved Issues in Junos Space Network Management Platform Release 24.1R1
This section lists the issues fixed in Junos Space Network Management Platform Release 24.1R1: For the most complete and latest information about known defects, use the Juniper Networks online Junos Problem Report Search application. · Purging jobs fail with An error occurred while purging the information from JobInstance and its reference
tables error. PR1788172 · When user sets Out of Sync filter for Managed Status in the Device Inventory Report the system fails
to generate any result. PR1787517 · 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. PR1785850 · Multiple jobs are stuck in-progress state. PR1781356 · After jmp-dr starts, there is high network traffic on both active and standby sites and database logs display 1062 error repetitively. PR1779392
Juniper Business Use Only

39
· Large fileHandleLeak.log is caused by large number of python processes. PR1778019 · The user is unable to filter jobs from the job list. PR1773076 · Disaster recovery fails to synchronize sites. PR1769758 · The quick template with variable objects does not function as in the earlier schema versions.
PR1767487 · Junos Space Network Management platform goes into maintenance mode frequently and displays
Junos space is starting up, please wait message. PR1765032 · Adding more devices to an existing model device takes longer than usual to open. PR1744314 · When user takes longer time to response after starting the CLI command, the system displays Forgot
a callback but don't know where? Use NODE_DEBUG=fs error. PR1742472 · After running the vulnerability scan, the following vulnerability is displayed for JA2500 ssh-weak-
message-authentication-code-algorithms. PR1731041 · The VIP node failover did not work as expected. PR1729124 · Management sessions are not in line with the GUI data. PR1706934 · The user receives an unexpected SNMP restart from all nodes and is unable to use Junos Space Network Management Platform. PR1704320 · Parallel requests to OpenNMS fails with 500 error. PR1699620 · The user receives 1000 configuration files through API request, but GUI shows more nodes. PR1670255 · After upgrading to Junos Space Network Management Platform 23.1R1, the 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 PR1748467 · Resynchronization with the network fails with java.nio.channels.ClosedChannelException error. PR1740818
Juniper Business Use Only

40
· When you upload PKCS12 format certificate, Junos Space Network Management Platform displays an error. PR1739065
· Deleted devices continue to appear in the Network Monitoring node list even after deletion. PR1735659
· The database purging policy gets stuck in Junos Space Network Management Platform resulting in no data backup. PR1734126
· 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. PR1732817
· The configuration does not match the device in Junos Space Network Management Platform, even after resynchronization with the network. PR1732590
· While the user changes domains in the Device Management page and Job Management page, an error is displayed. PR1731540
· Starting in Junos Space Network Management Platform Release 22.3R1, user fails to upgrade ACX1100 and ACX2200 devices as the no-copy option is unavailable and the devices do not have sufficient space to hold copies of the software. PR1717146
· Junos Space Network Management Platform displays the device status as in-sync besides an option to resolve Out-of-Band (OOB) changes. PR1661072
· Junos Space Network Management Platform GUI shows incorrect number of nodes under Network Monitoring. PR1659947
Resolved Issues in Junos Space Network Management Platform Release 24.1R2
This section lists the issues fixed in Junos Space Network Management Platform Release 24.1R2: For the most complete and latest information about known defects, use the Juniper Networks online Junos Problem Report Search application. · The user is unable to assign a template to a device in Junos Space Network Management Platform.
PR1771300 · When you apply a configlet on Junos Space Network Management Platform Release 24.1R1 through
a North Bound Interface (NBI), the response received is empty with Status Code: 406. PR1813422
Juniper Business Use Only

41
· Wrong description for part no. 750-070866 in Junos Space Network Management Platform inventory. PR1832358
· Crond service is unstable in Junos Space Network Management Platform. It restarts multiple times with several missing data. PR1832921
· The command jmp-dr toolkit watchdog status disable-automatic-failover duration 0 fails to disable the automatic failover permanently. PR1838157
· SNMPD services stop on all Junos Space nodes after you perform jmp-dr manual failover. PR1838492 · The jmp-heartbeat service fails to check for the gateways in Network Manager files. PR1840313 · After upgrading to Junos Space Network Management Platform Release 24.1R1 Hot Patch v2, the
Junos Space Network Management Platform GUI login takes longer than usual. PR1840293 · Audit template fails to perform as expected. PR1831947 · The compare template shows incorrect output. PR1835395 · When the user runs a curl on a slax script, the curl command does not give an output. PR1822448 · The management sessions in Junos Space Network Management Platform GUI are inconsistent and
shows incorrect data. PR1842159 · Disaster Recovery fails to perform as expected. PR1833673 · When the user clicks the Save Filter option, Junos Space Network Management Platform GUI does
not respond. PR1814883
Resolved Issues in Junos Space Network Management Platform Release 24.1R3
This section lists the issues fixed in Junos Space Network Management Platform Release 24.1R3: For the most complete and latest information about known defects, use the Juniper Networks online Junos Problem Report Search application. · Wrong description for part no. 750-070866 in Junos Space Network Management Platform
inventory. PR1832358 · When you run Show ESSM PPPoE L2TP Sessions script against any Broadband Network Gateway (BNG)
device in the ICEAAA workspace, the system displays an error. PR1837248
Juniper Business Use Only

42
· Incorrect values appear on the Resolve Variables page. PR1838384 · When you send a query with /api/space/, the response returns an empty list with no services in
Junos Space Network Management Platform Release 24.1R1. PR1846772 · In Junos Space Network Management Platform Release 24.1R3, the system fails to detect when the
eth3 cable is down and does not move the connection to another space node. PR1847832 · When you send an API query using a tag on a device, the system shows HTTP 500 internal server
error. PR1849998 · Security Director application image fails to update in Junos Space Network Management Platform
Release 24.1R2.15 FIPS enabled setup with an error message. PR1861079 · 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. PR1851757 · Junos Space Network Management Platform GUI fails to collect logs as expected. PR1846111
Hot Patch Releases
IN THIS SECTION Junos Space Network Management Platform 24.1R1 Hot Patch Release | 43 Installation Instructions | 43 Resolved Issues | 44 Known Issues in the Hot Patch | 48 Junos Space Network Management Platform 24.1R2 Hot Patch Release | 48 Installation Instructions | 49 Resolved Issues | 50 Junos Space Network Management Platform 24.1R3 Hot Patch Release | 50 Installation Instructions | 51 Resolved Issues | 52
Juniper Business Use Only

43
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:
Juniper Business Use Only

44
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 6 on page 44 lists the resolved issues in Junos Space Network Management Platform Release 24.1R1 hot patch.
Table 6: Resolved Issues in Junos Space Network Management Platform Release 24.1R1 Hot Patch

Description

Hot Patch Version

PR1758864

The max_log_file_action is not set to ROTATE by v2 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.

PR1791603

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

Juniper Business Use Only

Table 6: Resolved Issues in Junos Space Network Management Platform Release 24.1R1 Hot Patch (Continued)

Description

Hot Patch Version

PR1808536

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

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.

PR1815872 PR1816840

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.

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.

PR1817241

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

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.

Juniper Business Use Only

Table 6: Resolved Issues in Junos Space Network Management Platform Release 24.1R1 Hot Patch (Continued)

Description

Hot Patch Version

PR1817824

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

PR1819181

Device re-synchronization in ICEAAA Manager

fails when the user is not assigned to Global

domain in Junos Space Network Management

Platform.

PR1821198

When eth0 interface fails on the App Logic master v2 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.

PR1822500

jmp-firewall takes longer than usual to restart in

Junos Space Network Management Platform

Release 24.1R1.

PR1822712

While editing the user group, the number of

assigned users disappears in Junos Space

Network Management Platform.

Juniper Business Use Only

Table 6: Resolved Issues in Junos Space Network Management Platform Release 24.1R1 Hot Patch (Continued)

Description

Hot Patch Version

PR1822987

Incorrect RAM configuration in host.xml.slave.

NOTE: To change the RAM size from the default calculated values:
1. a. Navigate to the file located at /usr/local/ jboss/domain/configuration/ host.xml.slave.

b. Under jvm name="platform", locate jvmoptions.

c. Change the following values within the jvm-options:

xml <option value="XX:PermSize=<existing value>"/> <option value="-XX:MaxPermSize=<new value>"/>

PR1822993
PR1826265 PR1828027 PR1832791

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

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

Multiple DMI sessions are not visible in Junos

Space Network Management Platform GUI.

The default gateway for eth3 is empty after the

initial setup is complete.

Juniper Business Use Only

Table 6: Resolved Issues in Junos Space Network Management Platform Release 24.1R1 Hot Patch (Continued)

Description

Hot Patch Version

PR1687708

The user is unable to upgrade the

QFX5200-32C-32Q device from Junos Space

Network Management Platform.

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.

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.

Juniper Business Use Only

49
· 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.
Juniper Business Use Only

50
· 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 7 on page 50 lists the resolved issues in Junos Space Network Management Platform Release 24.1R2 hot patch.
Table 7: Resolved Issues in Junos Space Network Management Platform Release 24.1R2 Hot Patch

Description

Hot Patch Version

PR1861079

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

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.

Juniper Business Use Only

51
· 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.
Juniper Business Use Only

52
· 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 8 on page 52 lists the resolved issues in Junos Space Network Management Platform Release 24.1R3 hot patch.
Table 8: Resolved Issues in Junos Space Network Management Platform Release 24.1R3 Hot Patch

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.

PR1860367

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

PR1860507

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

PR1849459

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

Juniper Business Use Only

Table 8: Resolved Issues in Junos Space Network Management Platform Release 24.1R3 Hot Patch (Continued)

Description

Hot Patch Version

PR1864861

Junos Space Network Management v1 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.

PR1826265

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

PR1849459

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

PR1874673 PR1875604 PR1876027

The slax script NE Support - v2 Disable All Access Interfaces.slax inserted additional authorization in the result output.

The

slax

script v2

NE_FPC_collect_and_restart.slax

included unexpected output in the

result.

The slax script NE_RE-Master- v2 Restart-local.slax added additional authorization strings into the output payload.

Revision History

Release

Release Date

Junos Space Network Management 05 May, 2025--Revision 8 Platform 24.1R3 Hotpatch v2.

Juniper Business Use Only

Updates
Updated the following: · Added Resolved Issues in the Hot Patch

Junos Space Network Management 13 March, 2025--Revision 7 Platform 24.1R3 Hotpatch v1.

54
· PR1793725 removed from 24.1R1 Known Issue
· PR1862025 removed from 24.1R3 Known Issue
· PR1836787 removed from 24.1HPv2 Known Issue
Added Resolved Issues in the Hot Patch

Junos Space Network Management 11 February, 2025--Revision 6 Platform 24.1R2 Hotpatch v1.

Added a Resolved Issue in the Hot Patch

Junos Space Network Management 3 February, 2025--Revision 5 Platform 24.1R3.

Updated the following: · New and Changed Features
section
· Added Resolved Issues
· Added Known Issues
· Removed EOLed devices under Supported Devices section.

Juniper Business Use Only

(Continued)
Release

Release Date

Updates

Junos Space Network Management 7 November, 2024--Revision 4 Platform 24.1R2.

Added Resolved Issues

Junos Space Network Management 19 September, 2024--Revision 3 Platform 24.1R1 Hotpatch v2.

Added the following in the Hot Patch: · Resolved issues
· Known issues

Junos Space Network Management 28 June, 2024--Revision 2 Platform 24.1R1 Hotpatch v1.

Added Resolved Issues

Junos Space Network Management 25 April, 2024--Revision 1 Platform 24.1R1.

Intial Release Notes

Copyright © 2025 Juniper Networks, Inc. All rights reserved.
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. and its affiliates in the United States and other countries. All other trademarks might be property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. Copyright © 2025 Juniper Networks, Inc. All rights reserved.
Juniper Business Use Only

References

Adobe PDF Library 25.1.250