ON THIS PAGE
Junos Space Network Management Platform Release Notes
These release notes accompany Junos Space Network Management Platform Release 19.3R1.
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 19.3R1 includes the following enhancements:
New filter criteria for Device Physical Inventory report type—Starting with this release, Junos Space Network Management Platform supports the following two new types of filter criteria:
Upgraded Disaster Recovery scripts—Disaster Recovery scripts are updated for compatibility with Node.js version 8.4.0.
Upgraded Red Hat Enterprise Linux kernel—The Red Hat Enterprise Linux kernel is updated from version 2.6.32-754.12.1.el6.x86_64 to version 2.6.32-754.15.3.el6.x86_64 to improve security.
Options header removed from HTTP protocol—The
Optionsheader is removed from HTTP protocol to address a vulnerability issue.
Domain information included in application alert e-mails—From and to e-mail addresses are displayed in the alert e-mails sent by Junos Space Network Management Platform. The From address is the e-mail address provided in the From Email Address field on the Administration > SMTP Servers page. The To address is the e-mail address (or addresses) configured on the Administration > Email Listeners page.
Automatic detection of dynamic IP address of a device—Starting with this release, OpenNMS automatically detects the dynamic IP address of a device that uses Dynamic Host Configuration Protocol (DHCP). The dynamic IP address of a device is detected automatically only when the device is discovered through a device-initiated connection in Junos Space Network Management Platform.
User groups—Starting with this release, Junos Space Network Management Platform supports the creation and management of user groups. A user group is a collection of users who can view the jobs of all the users assigned to the user group.
The following new task, tab, and columns have been introduced as part of this feature:
User Groups task is added to under the Role-Based Access Control window.
Groups column is added in the Job Management page.
Assigned Groups column is added in the User Accounts page.
Assigned Groups column is added in the User Accounts and Job Inventory reports.
Group Visibility tab is added in the User settings page.
For more information about user groups, see the User Groups Overview section in the Workspaces Feature Guide.
Junos Space Network Management Platform Release 19.3R1 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.
Login to Space CLI and execute the command sed -i -e 's/testrun.pl/dbReplChecker.pl/g' /var/www/cgi-bin/afterSwitchingVIP.sh.
Currently, due to the wrong file reference, when HA fail-over/VIP switchover happens then the correct script was not called to correct the DB replication (out of sync) automatically.
A 19.3R1 hot-patch has also been planned to be delivered to address the issue. User either has to run this command or apply the 19.3 Hot-patch v1.
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 19.3R1.
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 19.3, 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 19.3R1 from Junos Space Network Management Platform 19.2R1 or 19.1R1.
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.
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.
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.
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.
After you upgrade Junos Space Platform to Release 19.3R1, all previously installed applications are disabled until the applications are upgraded to a version compatible with Junos Space Platform 19.3R1. You must upgrade the applications to releases that are compatible with Junos Space Platform Release 19.3R1, by using the Junos Space Platform UI. For information about application versions compatible with Junos Space Platform 19.3R1, see Supported Junos Space Applications and Adapters.
Before you upgrade to Junos Space Network Management Platform Release 19.3R1, 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 19.3R1 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.
Supported Junos Space Applications and Adapters
This release of Junos Space Network Management Platform supports Worldwide (ww) Junos OS Adapter adapter.
This release of Junos Space Network Management Platform supports the following applications:
Service Now 17.2 and 18.1 and Service Insight 17.2 and 18.1
Network Director 3.8R1
Connectivity Services Director 5.0R1
Cross Provisioning Platform 19.3R1
Security Director 19.3R1
Intelligent Customer Extendable authentication, authorization, and accounting (ICE-AAA) Framework 19.3R1
For the latest information, see the Junos Space Application Compatibility knowledge base article.
Junos Space Network Management Platform Release 19.3R1 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 19.3R1, see Juniper Networks Devices Supported by Junos Space Network Management Platform.
Table 2 shows the supported Juniper Networks line cards in Junos Space Network Management Platform Release 19.3R1.
Table 2: Supported Line Cards
Power Entry Module (PEM)/Power Supply Module (PSM)
ACX5448-D (Optical SKU)
ACX5448-M (MACSEC SKU)
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
Junos OS Compatibility
The following tables explain how the Device Management Interface (DMI) schemas are chosen for devices running Junos OS Service releases.
If a Junos OS Service Release is installed on your device with a major release version of DMI schema installed on Junos Space Network Management Platform, then Junos Space chooses the latest corresponding major release of DMI schemas, as shown in Table 3.
Table 3: Device with Service Release and Junos Space with FRS Release
Junos OS Version on Device
Junos Space DMI Schemas Installed
Junos Space Default Version
Junos Space Version Chosen for Platform
If a Junos OS Service Release is installed on your device without a matching DMI schema version in Junos Space Network Management Platform, then Junos Space chooses a default DMI schema version, as shown in Table 4.
Table 4: Device with Service Release and Junos Space without matching DMI Schema
Junos OS Version on Device
Junos Space DMI Schemas Installed
Junos Space Default Version
Junos Space Version Chosen for Platform
If more than one version of the DMI schemas are installed in the Junos Space Platform for a single Junos OS Service release version, Junos Space chooses the latest version of the DMI schema, as shown in Table 5.
Table 5: Device with Service Release and Junos Space with more than one DMI Schemas
Junos OS Version on Device
Junos Space DMI Schemas Installed
Junos Space Default Version
Junos Space Version Chosen for Platform
If a Junos OS Service Release is installed on your device without a corresponding DMI schema version in Junos Space Network Management Platform, then Junos Space chooses a default DMI schema version, as shown in Table 6.
Table 6: Device with Service Release and Junos Space without more DMI Schemas
Junos OS Version on Device
Junos Space DMI Schemas Installed
Junos Space Default Version
Junos Space Version Chosen for Platform
In Junos Space Network Management Platform Release 19.3R1, no new Junos OS releases are supported. For information about Junos OS compatibility for releases up to and including Junos Space Platform Release 19.3R1, 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.
The following issues are still outstanding in Junos Space Network Management Platform Release 19.3R1.
For the most complete and latest information about known defects, use the Juniper Networks online Junos Problem Report Search application.
A few of the schema configuration knobs are missing for an MX10008 device, on the Device Configuration page of Junos Space Network Management Platform 19.3R1. [PR1455383]
Users are not being unassigned from a user group when all items across all pages are selected. [PR1460251]
A user session is not terminated when a user group is deleted. [PR1454507]
OpenNMS is not restored after database restore, and the secondary database node is out-of-sync. [PR1461619]
Junos OS device image upload fails when dedicated Cassandra nodes are present. [PR1460744]
Poe and unified-edge schema configuration knobs are missing for ACX5448-M and ACX5448-D devices on the Device Configuration page of Junos Space Network Management Platform 19.3R1. [PR1456262]
Vlans schema configuration knob is missing for a PTX10008 device on the Device Configuration page of Junos Space Network Management Platform 19.3R1. [PR1455653]
PgSQL replication between fault monitoring and performance monitoring (FMPM) primary nodes added to an existing disaster recovery setup fails after bringing it up. [PR1460850]
Device discovery profile clone operation is not listed as CLONED in the audit log. [PR1446275]
The SNMPv2 authentication failure traps for devices running Junos OS are discovered using SNMPv3. [PR1436584]
Device interfaces are not displayed in Network Monitoring / OpenNMS. [PR1437453]
Network Monitoring topology is not displayed for all devices. [PR1447899]
Network Monitoring - Topology Map with neighbors does not display links for EX4300. [PR1450387]
Application settings for Network Management Platform is locked and is does not allow the user to add a cert parameter. [PR1453883]
Sub-jobs fail to start. [PR1454284]
No Configlets were found for a selected context and the BaseX folder was corrupted on the Standby node of the Junos Space Network Management Platform cluster setup. [PR1454747]
SNMPv2 authentication failure alarms are triggered for SNMPv3 devices. [PR1458647]
The Network Monitoring GUI slows down when user tries to view information for Events, Outages, Topology and Admin > Notify. [PR1458683]
Device search using API has problems. A filter criterion is needed that corresponds to the Customized Attribute device alias. [PR1459104]
Network Monitoring is not accessible in some cases depending on how the user logs in. [PR1459155]
Disaster Recovery is not synchronizing mysql database. [PR1460105]
This section lists the resolved issues in Junos Space Network Management Platform Release 19.3R1.
For the most complete and latest information about resolved defects, use the Juniper Networks online Junos Problem Report Search application.
Device search does not list devices that were removed and added back to Junos Space Platform. [PR1428357]
Dynamic IP address changes are not updated in OpenNMS, and SNMP incoming traps do not get associated with the Junos Space node in the expected manner. [PR1428953]
The interfaces corresponding to discovered devices are not listed, and devices do not synchronize with OpenNMS after discovery. [PR1433733]
The application settings for Junos Space Network Management Platform are locked because of changes in the authentication method. [PR1435101]
The OpenNMS topology takes a longer time to load than expected. [PR1438338]
The Disaster Recovery functionality is not working as expected when you power off the Disaster Recovery primary or active site. [PR1439136]
During device profile creation, an empty entry in the CSV field throws an error. [PR1444093]
Dynamic IP address is not updated in Open NMS after device reload. [PR1453576]
Not able to visually differentiate whether the Set Active SMTP server button on the Administration > SMTP Servers page is active or inactive. [PR1459343]
Junos Space Network Management Platform Report Generation: Model Number and Status options do not appear in the Filter field. [PR1430275]
Disk space allocation for root partition is corrected in the Junos Space Network Management Platform OVA file.[PR1446986]
Received the Received unformatted enterprise event event under Network Monitoring when sending the events jnxSpSvcSetCpuOk and jnxSpSvcSetCpuExceeded from an MX960 device. [PR1447815]
Unable to modify the authentication of the device from the web UI of Junos Space Network Management Platform, if using a dot in the password. [PR1451084]
Not able to delete any device from Junos Space Network Management Platform. [PR1456348]
Hot Patch Releases
This section describes the installation procedure and resolved issues in Junos Space Network Management Platform Release 19.3R1 hot patches.
During hot patch installation, the script performs the following operations:
Blocks the device communication
Stops JBoss, JBoss-dc, and watchdog services.
Backs up existing configuration files and Enterprise Application Archive (EAR) files.
Updates the Red Hat Package Manager (RPM) files.
Restarts the watchdog process, which restarts JBoss and JBoss-dc services.
Unblocks 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 19.3R1.3 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 19.3R1 Patch vX from the Downloads site.
X is the hot patch version. For example, v1, v2, and so on.
- Copy the Space-19.3R1-Hotpatch-vX.tgz file to the /home/admin folder of the VIP node.
- Verify the checksum of the hot patch:
- Extract the Space-19.3R1-Hotpatch-vX tar file:
tar -zxvf Space-19.3R1-Hotpatch-vX.tgz
- Change the directory to Space-19.3R1-Hotpatch-vX.
- Execute the patchme.sh script from the Space-19.3R1-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/.19.3R1-hotpatch-Space-vX is created with the list of RPMs and
PRs that are fixed in the hot patch release.
We recommend that you install the latest available hot patch version, which is the cumulative patch.
Resolved Issues in Junos Space Platform Release 19.3R1 Hot Patches
Table 7 lists the resolved issues in Junos Space Platform Release 19.3R1 hot patches.
Table 7: Resolved Issues in Junos Space Platform Release 19.3R1 Hot Patches
Hot Patch Version
When you reboot the primary database node, it goes to out-of-sync state and doesn’t come up.
Unable to delete the custom users and roles from Security Director.
Unable to select templates while deploying a model device.
The physical inventory report of a device is empty when you filter the report with the domain name in the Add Filter criteria.
You cannot deploy the MX240 device through the modeled device template from Junos Space, because of the root authentication failure error.
Deadlock error messages are found in the Junos Space message logs because of multiple automatic resynchronization operations.
When you create a security policy template using CSV files, unusable configurations are generated.
From the Junos Space Platform user interface, if you try to connect to a modeled device using SSH, an Invalid request error message is displayed.
The Resolve Key Conflict and Modify Device Authentication jobs do not work for devices running Junos OS Release 17.3. The jobs end successfully but there is no change in the key.
If the device goes offline or comes back online, Junos Space does not update the device inventory.
Adding a detailed description support for the REST APIs triggers the Apply CLI and Validate CLI configlets.
The URL is being validated in the back end to prevent any malicious attacks such as those that try to retrieve sensitive file information.
The application settings for Junos Space Network Management Platform is locked.
The Disk Usage threshold is not applied correctly in the SNMP configuration.
Error at the SSL Certificate Port 9443.
When any remote database backup restoration job fails, only the Remote IP is not reachable error is displayed.
After successfully deleting a database backup, unable to delete other database backups from the Junos Space UI. The page keeps loading and the only option left is to navigate to another page to refresh the UI.
Jobs are failing with the Pessimistic Lock Exception error message.
MySQL database errors are found in the disaster recovery health status.
Username is missing in the Audit Log.
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 19.3R1 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.