Junos Space Network Management Platform Release Notes
These release notes accompany Junos Space Network Management Platform Release 20.1R1.
The terms Junos Space Network Management Platform and Junos Space Platform are used interchangeably in this document.
New and Changed Features
Junos Space Network Management Platform Release 20.1R1 includes the following enhancements:
NETCONF channel tuning—We’ve increased the NETCONF channel limit from 32 to 64 to have an uninterrupted device communication on heavy loads. The increase in the NETCONF channel limit resolves the All channels are busy production environment error.
BaseX database refresh—Starting in Junos Space Network Management Platform Release 20.1R1, the BaseX DB size does not increase every time device resynchronization happens, unlike the behavior in all releases before Release 20.1.
Troubleshooting log bundles—In earlier release of Junos Space, important files required for debugging are missing from log bundles. In Junos Space Release 20.1, we’ve updated the existing file set to include more files and commands for better debugging.
Junos Space Network Management Platform Release 20.1R1 can be installed on a Junos Space Appliance or a Junos Space Virtual Appliance.
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.
For installation instructions for a Junos Space Virtual Appliance, see the Deploying the Junos Space Virtual Appliance section of the Junos Space Virtual Appliance Installation and Configuration Guide.
See Supported Hardware for more information about the hardware supported.
This section provides information about upgrading the Junos Space Network Management Platform installations running versions earlier than Release 20.1R1.
Supported Upgrade Path
Table 1 provides information about the supported upgrade path across Junos Space Network Management Platform releases.
Table 1: Supported Upgrade Path
Upgrade from Junos Space Release
Upgrade to Junos Space Release
Junos Space Release
Before you upgrade Junos Space Platform to Release 20.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 the existing Junos Space Platform running on your appliance to the immediate next release. You can also choose to skip a release and upgrade to the next release. For example, you can upgrade to Junos Space Network Management Platform 20.1R1 from Junos Space Network Management Platform 19.4R1 or 19.3R1.
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.
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.
Before upgrading Junos Space Platform Release 19.4 to Junos Space Platform Release 20.1, you must install the
Junos Space Platform 19.4 hot patch v1 and v2version.
If you have proceeded with the upgrade to Junos Space Platform Release 20.1 from Junos Space Platform Release 19.4 without installing the Juno Space Platform 19.4 hot patch v1 and v2 version, perform the following steps as a workaround:
/etc/httpd/conf/httpd.conffile by adding the following PATCH entry:
<Location /> <LimitExcept GET POST PUT PATCH DELETE> order deny,allow deny from all </LimitExcept> </Location>
Restart the HTTPD service using the service httpd restart command.
To upgrade Junos Space Platform to Release 20.1, follow the instructions provided here.
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 20.1R1, all previously installed applications are disabled until the applications are upgraded to a version compatible with Junos Space Platform 20.1R1. You must upgrade the applications to releases that are compatible with Junos Space Platform Release 20.1R1, by using the Junos Space Platform UI. For information about application versions compatible with Junos Space Platform 20.1R1, see Application Compatibility.
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.
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/details? productId=353&downloadGroup=OVFTOOL351.
To validate the Junos Space Network Management Platform OVA image:
- 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.
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.
- (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
/tmp) on a Junos Space node.
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
/var/tmp, because such directories can be accessed by several users.
- Navigate to the directory containing the OVA image.
- Unpack the OVA image by executing the following command:
tar xf ova-filename
where ova-filename is the filename of the downloaded OVA image.
- Verify that the unpacked OVA image contains a certificate
chain file (
junos-space-certchain.pem) and a signature file (
- Validate the signature in the unpacked OVF file (extension
.ovf) by executing the following command:
where ovf-filename is the filename of the unpacked OVF file.
- 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
JuniperRootRSACA.pemis the Juniper Networks Root CA certificate chain file, Certificate-Chain-File is the filename of the unpacked certificate chain file (extension
.pem), and Signature-file is the filename of the unpacked signature file (extension
If the validation is successful, a message indicating that the validation is successful is displayed.
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: 0 Instance ID: 7 Capacity: 250.00 GB Disk Types: SCSI-lsilogic NICs: Adapter Type: E1000 Connection: VM Network Adapter Type: E1000 Connection: VM Network Adapter Type: E1000 Connection: VM Network Adapter Type: E1000 Connection: 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$
- (Optional) If the validation is not successful, perform
the following tasks:
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.
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.
Retry the preceding validation steps by using one or both of the new files.
Before you upgrade to Junos Space Network Management Platform Release20.1R1, ensure that compatible versions of Junos Space applications are available for upgrade by referring to the Junos Space Application Compatibility knowledge base article. If you upgrade to Junos Space Platform Release 20.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 releases a compatible version of the Junos Space application.
This release of Junos Space Network Management Platform supports Worldwide (ww) Junos OS Adapter adapter and the following application:.
Network Director 4.0R1
Connectivity Services Director 5.2R1
Cross Provisioning Platform 20.1R1
Security Director 20.1R1
Junos Space Network Management Platform Release 20.1R1 can be installed on the following hardware:
JA2500 Junos Space Appliance
VMware ESXi server 5.5, 6.0, 6.5, 6.7
Kernel-based virtual machine (KVM) (Release 1.5.3-141.el7_4.4 or later)
For detailed information about hardware requirements, see the Hardware Documentation section of the Junos Space and Applications page.
For information about whether a Junos Space application can be installed on a particular Junos Space Appliance (JA2500) or Junos Space Virtual Appliance, see the release notes of the specific Junos Space application release.
For detailed information about hardware requirements, see Junos Space Virtual Appliance Deployment Overview .
For a list of supported devices up to and including Junos Space Platform Release 20.1R1, see Juniper Networks Devices Supported by Junos Space Network Management Platform.
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.
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 Junos OS Releases Supported in Junos Space Network Management Platform
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_upgradeare 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
Verifying checksum of image on device(s) dialog box
Stage Scripts on Device(s) page
Enable 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
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.
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.
“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.
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.
When a remote user with the FMPM Manager role uses the API to access Junos Space Platform, the user details are not updated in the
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:
For SNMPv3 traps, if more than one trap setting is configured in the
/opt/opennms/etc/trapd-configuration.xmlfile, then the
security-nameattribute for the
snmpv3-userelement must be unique for each configuration entry. If a unique
security-nameattribute 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.xmlfile 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 modify the IP address of a Fault Monitoring and Performance Monitoring (FMPM) node using the Junos Space CLI, the FMPM node is displayed on the Fabric page but cannot be monitored by Junos Space Platform because of a mismatch in the certificate.
Workaround: After modifying the IP address of the FMPM node using the Junos Space CLI, generate a new certificate on the Junos Space VIP node and copy the certificate to the FMPM node by executing the following scripts on the Junos Space VIP node:
curl -k https://127.0.0.1:8002/cgi-bin/createCertSignReq.pl? ip='fmpm-node-ip'\&user='admin'\&password='password'
curl -k https://127.0.0.1:8002/cgi-bin/authenticateCertification.pl? ip='fmpm-node-ip'\&user='admin'\&password='password'\&mvCertToDestn='Y'
where fmpm-node-ip is the IP address of the FMPM node and password is the administrator's password.
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 rest 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
SystemStatusLog.*) are not purged from the dedicated database nodes.
If the Junos Space fabric is configured with one or two FMPM nodes, the log files (mainly in the
/var/log/directory with the filenames
SystemStatusLog.*) are not purged from the FMPM 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.
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.
For more information about compiling SNMP MIBs, see Compiling SNMP MIBs.
When a physical hard drive is removed from a Junos Space hardware appliance (JA2500) 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 the administrator password for a Fault Monitoring and Performance Monitoring (FMPM) node is modified using the Junos Space CLI, the disaster recovery with the FMPM node fails and new users added in Junos Space (after the password is modified) are not synchronized to the FMPM node. This is because the modified administrator password is not automatically updated in the Junos Space MySQL database.
To ensure that the synchronization to the FMPM node takes place, you must run the
/var/www/cgi-bin/changeSpecialNodepassword.plscript so that the modified FMPM node password is updated in the Junos Space MySQL database. The syntax for the script is as follows:
/var/www/cgi-bin/changeSpecialNodePassword.plfmpm-node-ip fmpm-node-password, where fmpm-node-ip is the IP address of the FMPM node, and fmpm-node-password is the modified password for the FMPM node.
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 add or delete a Fault Monitoring and Performance Monitoring (FMPM) 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.xmlfile. 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.
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 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.
This section lists the resolved issues in Junos Space Network Management Platform Release 20.1R1.
For the most complete and latest information about resolved defects, use the Juniper Networks online Junos Problem Report Search application.
When devices are managed in large numbers, jobs may fail to start correctly and may slow down in multinode Junos Space fabric. [PR1454284]
During automatic failover from the Active DR site to the Standby DR site, the Standby DR site does not take the role of the active server. [PR1471325]
When an SNMP community string containing @, $, or & is added to the device, Junos Space discovers the device using SNMP, but during polling, it discards anything that appears after these characters, resulting in failure of events. [PR1474017]
Some of the jobs do not run as expected when Junos Space fabric is configured in unicast mode.. [PR1480947]
Most of the devices initiated in Junos Space are displayed as down when unicast mode is configured for cluster communication. [PR1481417]
Error when you try to upgrade the device images for SRX Series cluster device through ISSU or ICU. [PR1481645]
When Space DR initialization fails on the Standby DR site, MySQL error 2005 is displayed in the mysqld.logs. [PR1482591]
Jobs failing with the error message Pessimistic Lock Exception. [PR1485443]
When you try to upgrade an EX2300 device from Network Management Platform, the image for the device is not available in the list. [PR1488363]
When you try to stage or deploy an ACX Series device image, MX Series devices are also visible in the list under Network Management Platform. [PR1491168]
Received unformatted enterprise event under Network Monitoring for CHASSISD_SNMP_TRAP10. [PR1493697]
Hot Patch Releases
This section describes the installation procedure and resolved issues in Junos Space Network Management Platform Release 20.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 the device communication after the watchdog process is restarted for device load balancing.
You must install the hot patch on Junos Space Network Management Platform Release 20.1R1 or on any previously installed hot patch. The hot patch installer backs up all the files that are modified or replaced during hot patch installation.
Perform the following steps on the CLI of the JBoss-VIP node only:
- Download the Junos Space Platform 20.1R1 Patch vX from the Downloads site.
X is the hot patch version. For example, v1, v2, and so on.
- Copy the Space-20.1R1-Hotpatch-vX.tgz file to the /home/admin folder of the VIP node.
- Verify the md5sum of the hot patch:
- Extract the Space-20.1R1-Hotpatch-vX tar file:
tar -zxvf Space-20.1R1-Hotpatch-vX.tgz
- Change the directory to Space-20.1R1-Hotpatch-vX.
- Execute the patchme.sh script from the Space-20.1R1-Hotpatch-vX folder:
The script detects whether the deployment is standalone deployment or a cluster deployment and installs the patch accordingly.
A marker file
/etc/.20.1R1-hotpatch-Space-vX is created with the list of RPMs that
are fixed in the hot patch release.
We recommend that you install the latest available hot patch version, which is the cumulative patch.
New and Enhanced Features in Junos Space Platform Release 20.1R1 Hot Patches
Junos Space Platform Release 20.1R1 hot patches include the following enhancements:
License inventory support for cSRX series devices on Junos Space Network Management Platform 20.1R1 hot patch v1 and Security Director Release 20.1R1.
Resolved Issues in Junos Space Platform Release 20.1R1 Hot Patches
Table 2 lists the resolved issues in Junos Space Platform Release 20.1R1 hot patches.
Table 2: Resolved Issues in Junos Space Platform Release 20.1R1 Hot Patches
Hot Patch Version
When you try to delete Logical Systems (LSYS) from all the root devices in the Security Director all at the same time, LSYS gets deleted only from a single device.
You cannot upload all scripts together.
SRX Series virtual chassis ICU upgrades fail intermittently.
While upgrading the VIP nodes, the upgrade gets stuck at 42% as the /tmp folder is filled by DMI Schema Compressed files.
However, the upgrade completes when the file is deleted but when you try to reboot, both the VIP nodes become unbootable in both active and standby sites.
When you try to download applications from JunOS Space store, it fails with Failed at LOGIN_VERIFY_URL error.
If the hot patch contains a UI fix, you must clear the Web browser’s cache for the latest changes to take effect.
This section lists the errata and changes in Junos Space Network Management Platform Release 20.1R1 documentation:
From Junos Space Platform Release 16.1, the Frequently Asked Questions are migrated to FAQ: Junos Space Network Management Platform on the Juniper Networks TechWiki and are not available on the TechLibrary.
The Complete Software Guide no longer contains the Frequently Asked Questions.