Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Resolved Issues


This section lists the resolved issues in Junos Space Network Management Platform Release 18.3R1.

For the most complete and latest information about resolved defects, use the Juniper Networks online Junos Problem Report Search application.

  • Users are able to delete devices even if they do not have the. [PR 1351713]

  • The HTTP response header discloses information about the server version, middleware components, and application platform framework[PR 1355697]

  • Insufficient controls to prevent unrestricted file uploads. [PR 1355724]

  • The audit logs created while modifying the Junos Space configuration do not provide information about the IP address of the user. [PR 1360451]

  • The EMS inventory view does not display the optical module information. [PR 1363469]

  • The user accounts menu does not display the sorting and filtering functions. [PR 1365122]

  • Device discovery fails for the second node of device clusters in a nonglobal domain. [PR 1366049]

  • When a new node is added into the Space fabric, the ownership of the /var/log/redis directory changes to saslauth:root on the new node. The redis service does not get initiated, as the redis user will not be able to access the log directory. [PR 1367481]

  • Unable to access the Junos Space Web UI by using Chrome because the Web proxy configuration does not synchronize with the installation of the certificate. [PR 1369907]

  • The hostnames for some devices in the physical inventory report (downloadable) are split into two rows. Otherwise, the hostname is correctly placed in the CSV or PDF file. [PR 1374505]

  • While applying Configlets or executing script selection, the selection filters are not persistent. [PR 1376003]

  • Device discovery using the eth3 interface setup fails because the device cannot be reached from the Junos Space Platform. [1376194]

  • The audit log messages do not provide the exact reason for the Internal Server Error 500 message while executing scripts and Configlets. [PR 1376315]

  • Devices in RMA state cannot be reactivated using the Reactivate from RMA function, because the RMA option does not list the devices. [PR 1382187]

  • While enabling Cassandra, the migration of existing device images in Junos Space fails. The Web UI displays the successful migration message, but the log files display the failure messages. [PR 1348763]

  • Rebooting the Junos Space fabric nodes causes the IPv6 VIP binding to fail, thereby losing access to the Web UI. [PR 1349007]

  • Uploading all the scripts together results in the browser not responding. 1352724]

  • Creating new tags with the slash (/) fails.[ PR 1367697]

  • You cannot save new template strings that end with $. [PR 1370804]

  • If the SRX Series device is managed by Junos Space, adding an EX Series switch that is located behind the SRX Series device fails. The SRX Series device performs NAT, which causes the EX Series switch to fail. [PR 1371039]

  • Discovering a new device under Network Monitoring causes the Path Outage page to disappear. [PR 1334634]

  • Deadlock messages appears on all Junos Space nodes when Junos Space tries to update multiple link status system logs. [PR 1372219]