Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Known Issues


The following issues are still outstanding in the Junos Space Network Management Platform Release 18.3R1.

For the most complete and latest information about known defects Junos Space Network Management Platform defects, use the Juniper Networks online Junos Problem Report Search application.

  • Junos Space Platform does not support RFC-compliant devices. As a result, RFC-compliant devices cannot be discovered or managed from the Junos Space Platform. [PR 1382580]

  • You cannot select NAT and ww Junos OS devices as arbiter devices to detect failure at a site during disaster recovery in Junos Space Platform. [PR 1362305]

  • Junos Space Platform supports only VM host image upgrade for PTX Series devices. It is not possible to upgrade PTX Series devices using normal device images. [PR 1353888]

  • Upload of an Elliptic Curve Digital Signature Algorithm (ECDSA) self-signed certificate to Junos Space Platform fails. This problem occurs because Junos Space Platform is unable to parse the private key of the certificate. [PR 1345038]

  • When you upgrade an SRX Series cluster device that has the upgrade dual-root partition and ISSU/ICU options enabled, the primary partition snapshot for one of the nodes is not copied to an alternate root partition. However, the image upgrade and deployment jobs are successful on both the nodes (node0 and node1).

    Workaround: Log in to the VIP node of the SRX Series cluster and execute the request system snapshot slice alternate command. This command takes a snapshot from the primary partition and copies it to an alternate partition on both nodes. [PR 1228763]

  • Security Director does not work after the failover of Junos Space Platform nodes. This problem occurs because the Security Director image fails to synchronize during node addition if a report filename contains single quotation marks. [PR 1327233]

  • Junos Space Platform supports only Junos Space-initiated discovery of QFX Series devices. [PR 1325596]

  • Junos Space Platform Release 17.2R1 does not support Service Now Release 17.1 or earlier versions. [PR 1321123]

  • Although the EX4200 devices do not support unified ISSU, the ISSU option is enabled for those devices from the Junos Space Platform user interface. [PR 1310184]

  • After upgrading the standby site in a disaster recovery setup through the CLI, database restoration fails.

    Workaround: Remove the upgrade temporary file, /var/jmp_upgrade/slav/log/upgradeMetaData.txt, before you restore the database in the upgraded site. You can use the following command to remove the file:

    rm -rf /var/jmp_upgrade/slav/log/upgradeMetaData.txt [PR 1288130]

  • When a DMI Schema installation is in progress, modifications to the configuration of devices that use the DMI Schema that is being installed fail.

    Workaround: Avoid modifying the device configuration when a DMI schema associated with the device is being installed. [PR 1273620]

  • OpenNMS stops updating the performance graphs. This problem occurs because Junos Space Platform that sends the SNMP requests over the interface eth3 uses the eth0 address as the source IP address. Because the eth0 interface is not reachable from devices, the SNMP requests time out.

    Workaround: Add the following code in /usr/sbin/jmp-firewall:

    ETH3NET=$(ifconfig eth3 | grep 'inet addr:' | cut -d":" -f2 | cut -d" " -f1 | head -1) iptables -t nat -A POSTROUTING -p udp -o eth3 --dport 161 -j SNAT --to $ETH3NET [PR 1269891]

  • The Resolve Out of Band Changes function does not work as expected when there are a large number of out-of-band changes. [PR 1233845]

  • In a disaster recovery setup, database or jboss nodes cannot be added through the Junos Space CLI. [PR 1234860]

  • Junos Space Platform UI does not fit properly in the browser window when the screen resolution is set to a value higher than the recommended value of 1280 x 1024 pixels. This reduces the efficiency of navigation. [PR 1172112]

  • When you upgrade SRX Series chassis cluster devices that have the dual root partition option and ISSU or ICU enabled, the image deployment job succeeds but not all partitions get upgraded. [PR 1228763]

  • Changes made to device configuration through the schema-based configuration editor do not appear in the basic configuration wizard. [PR 1181560]

  • Creation of a Quick Template using the Basic Setup fails if the Template Administrator who is creating the Quick Template does not have the Modify Configuration permission.

    Workaround: Assign Modify Configuration role to the Template Administrator account. [PR 1294610]

  • If a user imports a user certificate that contains an X509 parameter value that was used in a previously imported user certificate for another user, Junos Space Platform locks both the user accounts. [PR 1282190]

  • If you abruptly terminate a browser session or a server while the modification of Application Settings is in progress, Junos Space Platform saves a copy of the running configuration as a draft configuration in the database. Even if you delete the draft configuration, Junos Space Platform creates a new draft configuration whenever you update the configuration. [PR 1281485]

  • Junos Space Platform does not allow you to purge jobs that are in the Pending state. [PR 1279931]

  • The SNMPv3 trap configuration settings in the /opt/opennms/etc/trapd-configuration.xml file and on the managed devices are not updated after you restore the database from the backup. [PR 1276974]

  • If some nodes are unavailable when a DMI schema or hardware catalog is updated on Junos Space Platform, the DMI schema or hardware catalog on such nodes fails to synchronize after the nodes come back online.PR 1273937]

  • If you try to modify the configuration of a device when a DMI schema that the device uses is being installed, the modification of the device configuration fails. [PR 1273620]

  • Updating the OpenNMS keystore with custom certificates causes SSL handshake failure, and thus communication failure, between Junos Space Platform and FMPM nodes. This communication failure causes the network monitoring service to stop. [PR 1273346]

  • If you delete a default DMI schema before you add a node, after the addition of the node, on the DMI Schema page of the Junos Space Platform UI, the deleted schema is marked as Installed but the schema remains unusable, which is because the schema is not available In the file system of the master node. In case of a cluster failover, the schemas fail to synchronize among the nodes. [PR 1272125]

  • The Import Script and Modify Script operations fail when the script content has the special character slanted double quotation marks (“), which causes lexical errors. [PR 1270670]

  • Junos Space Platform supports only Junos Space-initiated discovery of QFX devices. [PR 1267622]

  • DMI schemas that are listed as installed on the DMI Schemas page are missing from the file system. This problem occurs after you restore the database from the backup. [PR 1263258]

  • Instantaneous creation of database reports fails if the time zone specified is in a format other than UTC or UTC offset. This occurs because of an OpenNMS limitation.

    Workaround: To prevent this issue, specify the time zone in the UTC+/-offset format. [PR 1262239]

  • In dual-stack implementations, IPv6 virtual IP binding does not work during master node failover or after a new setup.

    Workaround: To resolve this issue, run the service heartbeat restart command on the master node. [PR 1262104]

  • After the Junos Space Platform does a rescan and restarts the Network Monitoring service, the number of devices associated with a custom category (Network Monitoring > Admin > Node Provisioning > Manage Surveillance Categories) is reset to 0 (zero). [PR 1238995]

  • When you execute local scripts, the scripts run only on the VIP node in the cluster. [PR 1238558]

  • If you discover a device that is authenticated by using a custom key or a Junos Space key encrypted with the Digital Signature Algorithm (DSA) and try to execute a local script on the device, the script execution fails.

    Workaround: Delete the device and rediscover the device using a Junos Space key encrypted using RSA or ECDSA and execute the local script. [PR 1231409]

  • If you configured a Junos Space fabric containing one or two dedicated database nodes and one or two FMPM nodes without configuring NAT and try to configure NAT from the Junos Space CLI of the FMPM node, the job is triggered but the configuration is not updated in the FMPM node or on the devices. In addition, if you configure NAT from the Junos Space Platform UI, the NAT configuration is updated successfully. However, the option to disable NAT is not available in the CLI of the FMPM node and the NAT configuration is shown as NULL in the CLI of the FMPM node.

    Workaround: For FMPM nodes, configure or disable NAT only from the Junos Space Platform UI. [PR 1227595]

  • If some devices managed by the Junos Space fabric are down and you configure disaster recovery with NAT enabled, the disaster recovery configuration for the standby site is not pushed to the devices that are down. However, the job associated with the device updates completes successfully.

    Workaround: Do one of the following:

    • Ensure that all the devices are in the Up state before you add a new node.

    • For the devices that are down, manually configure the outbound-ssh and target-address (SNMP trap target) configuration statements on the device.

    [PR 1227196]

  • Network monitoring e-mail notifications show incorrect syntax without service name and SNMP details.

    Workaround: To prevent this issue, use the following formats to capture special values in the Text message field when you create e-mail notifications for events:

    [PR 1226885]

  • Junos Space Platform fails to discover a device if the device is authenticated with a custom key generated using the openssl genpkey utility and one of the following is true:

    • The key is encrypted using one of the following passphrase ciphers: des, aes128, aes256, or aes 192.

    • The key is encrypted using the ECDSA algorithm.

    Workaround: Do one of the following:

    • Use a custom key generated using the ssh-keygen utility.

    • Use a custom key generated using the openssh genpkey utility, but use DSA or RSA as the encryption algorithm.

    [PR 1214215]

  • When you export operations from the Operations page (using the Export Operations workflow), the options specified for the operation in the Junos Space Platform UI are not exported to the XML file. [PR 1214022]

  • In a Junos Space fabric with both eth0 and eth3 interfaces enabled and only IPv6 addresses configured, if you try to add an FMPM node (configured with both IPv4 and IPv6 addresses) using the IPv6 address, the node addition fails. [PR 1217708]

  • If a device is discovered using a custom key, you cannot execute local scripts on the device. [PR 1213430]

  • If you add X.509 parameters in the Modify Application Settings page (Administration > Applications > Network Management Platform > Modify Application Settings > X509CertificateParameters) and click the Modify button, Junos Space Platform parses the parameters from the certificate associated with users who do not have the parameters already processed. This means that users for whom the parameters were processed previously will not be processed again.

    Workaround: Do one of the following:

    • If you already added the X.509 Certificate Parameters and need to modify them later, execute the /var/www/cgi-bin/parseUserCertificates script on the Junos Space VIP node.

    • If Junos Space Platform is not previously configured to authenticate using X.509 certificate parameters, then remove all the existing X.509 certificate parameters from the Modify Application Settings page and click the Modify button to remove all certificate parameters associated with users. Then, add the X.509 Certificate Parameters and click the Modify button, which triggers the parsing of the certificates associated with users.

    [PR 1175587]

  • In a fabric with IPv4 and IPv6 addresses configured, if you modify the IP address of the VIP node using the Junos Space GUI (Administration > Fabric > Space Node Settings), then, in some cases, the Junos Space GUI is not accessible.


    1. Log in to the VIP node to access the Junos Space CLI and open a debug (command) prompt.
    2. Restart the heartbeat service by using the service heartbeat start command.
    3. Log out of the Junos Space VIP node. [PR 1178264]
  • In some cases, the Execute Operation job displays a negative percentage completion rate. [PR 1083829]