Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Known Issues

The following issues are still outstanding in the Junos Space Network Management Platform Release 17.1R1. For each entry, the identifier following the description is the tracking number in the Juniper Networks Problem Report (PR) tracking system.

  • Old SNMP trap targets are not removed from the device when the network settings on the Junos Space Appliance are modified. [PR689042]
  • Users without Assign/Unassign Template permissions are allowed to add templates to and delete templates from the View Assigned Shared Objects wizard. [PR816788]
  • Group settings that are applied on the device are not displayed in the Basic Setup Wizard. [PR884068]
  • When Junos Space Platform is configured to use remote local authentication with a RADIUS server that uses Microsoft Challenge Handshake Authentication Protocol version 2 (MS-CHAP v2) and the RADIUS server is integrated with an RSA Authentication Manager Server, the Access Challenge requests between the RSA server and the RADIUS server do not work correctly.

    Workaround: Use RADIUS servers configured with the Password Authentication Protocol (PAP) when you are using an RSA Authentication Manager Server. [PR1009543]

  • In some cases, the Execute Operation job displays a negative percentage completion rate. [PR1083829]
  • On a multinode setup, when you install more than one DMI schema simultaneously or within a short time span and try to create a template definition or modify the device configuration, depending on the Junos Space node that is serving the UI session, Junos Space Platform sometimes displays an error message indicating that the schema could not be loaded or that the device configuration could not be loaded.

    Workaround:

    1. Find out which Junos Space node is serving the UI session.

      For more information, see the How Do I Determine Which Node in the Cluster Is Handling My Junos Space Platform UI Session? in FAQ: Junos Space High Availability.

    2. Log in to the CLI of the Junos Space node that is serving the UI session and open a debug (command) prompt.
    3. Execute the service jboss restart command to restart the JBoss service.
    4. Log out of the Junos Space node.

    [PR1112025]

  • 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.

    Workaround:

    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. [PR1178264]
  • 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.

    [PR1175587]

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

    Workaround: None. [PR1213430]

  • 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.

    Workaround: None. [PR1214022]

  • 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.

    [PR1214215]

  • 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.

    Workaround: None. [PR1217708]

  • 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:

    ifAlias: %parm[ifAlias]%
    ifDescr: %parm[ifDescr]% 
    ifName: %parm[ifName]%
    eventid: %eventid%
    severity: %severity%
    time: %time%
    notice: %noticeid%
    nodelabel: %nodelabel%
    interface: %interface% 
    service: %service%
    interfaceresolve: %interfaceresolve%

    [PR1226885]

  • 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.

    [PR1227196]

  • 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. [PR1227595]

  • Junos Space Platform upgrade from Release 15.1 to 15.2 generates the following error message and fails:
    Use of uninitialized value in concatenation (.) or string at /var/cache/jboss/jmp/payloads/15.2R2.4/daemons/upgradeNma.pl line 402, <$fh> line 2. 

    [PR1228049]

  • When you try to upgrade a low-end SRX series cluster device that has the upgrade dual-root partition and ISSU/ICU options enabled, the image upgrade is executed successfully for both the nodes (node0, node1) and deployment job is successful. However, for one of the nodes (either node0 or node1), the primary partition snapshot is not copied to alternate root partition.

    Workaround: Log in to the VIP node of the SRX series cluster and execute the request system snapshot slice alternate command; this takes a snapshot from the primary partition and copies it to alternate partition on both nodes. [PR1228763]

  • 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. [PR1231409]

  • When you execute local scripts, the scripts run only on the VIP node in the cluster. There is no known workaround for this issue. [PR1238558]
  • 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). There is no known workaround for this issue. [PR1238995]
  • 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. [PR1262104]

  • 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. [PR1262239]

  • 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. There is no known workaround for this issue. [PR1263258]
  • Junos Space Platform supports only Junos Space-initiated discovery of QFX devices. There is no known workaround for this issue. [PR1267622]
  • 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.

    As a workaround, you can add the following string 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 [PR1269891]

  • The Import Script and Modify Script operations fail when the script content has the special character slanted double quotation marks (“), which causes lexical errors. [PR1270670]
  • 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. There is no known workaround for this issue. [PR1272125]
  • Rapid increase in the size of the file /root/dead.letter. This problem occurs when AIDE mail notification settings are configured.

    Workaround: Disable AIDE mail notification settings. [PR1272931]

  • 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. There is no known workaround for this issue. [PR1273346]
  • 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. There is no known workaround for this issue. [PR1273620]
  • 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. There is no known workaround for this issue. [PR1273937]
  • 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. There is no known workaround for this issue. [PR1276974]
  • Junos Space Platform does not allow you to purge jobs that are in the Pending state. There is no known workaround for this issue. [PR1279931]
  • When you perform an ISSU upgrade on high-end SRX Series cluster devices, the Deploy Image job returns the command is not valid error and fails.

    Workaround: Instead of ISSU, perform a normal software upgrade for high-end SRX Series cluster devices. [PR1280913]

  • 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. There is no known workaround for this issue. [PR1281485]
  • 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. There is no known workaround for this issue. [PR1282190]
  • Node addition fails when unicast communication is enabled on the master node. This problem occurs because the entries corresponding to the newly-added node are not updated in the initial_host configuration of domain.xml and this causes jboss initialization on the newly-added nodes to fail.

    Workaround:

    To prevent this issue, you can follow this procedure while adding new nodes to a cluster if the cluster already has the first node added and the jboss communication mode changed from multicast to unicast using the script # /var/www/cgi-bin/changeSettings2StaticIP.sh multicast2unicast :

    1. Install the required image on node 2 and add it to the cluster.
    2. After the node has been added successfully, check the status of the node and confirm that all services are up on the newly-added node (Platform UI > Administration > Fabric).
    3. On the primary VIP node, which is the first node added to the cluster, restart the jboss-dc service by using the service jboss-dc restart command.
    4. Repeat these steps for each additional node that you want to add.

    However, if you did not follow the preceding procedure and the node addition does not go beyond the Deploying state, follow these steps to complete the node addition:

    1. On the primary VIP node, which is the first node that was added to the cluster, run the following commands to restart the jboss-dc service:

      service jboss-dc restart

    2. Run the following commands to restart services on the newly-added node:

      service jmp-watchdog stop; service jboss stop; service jboss-dc stop

      service jmp-watchdog start

    [1283889]

  • 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. [PR1294610]

Modified: 2017-08-22