Known Issues

This section describes known issues with Junos Space Release 1.1.

Upgrade Issues

This section describes issues related to upgrading the Junos Space software from release 1.0 to release 1.1.

• After uploading the new image, the Manage Software inventory page does not appear automatically. You must select it manually. [PR/495783]

Point-to-Point Service Provisioning Issues

This section describes issues related to point-to-point Ethernet services:

• A service order deployed with vlan-ccc physical encapsulation will assign VLAN IDs from VLAN ID 1 instead of 512. As a workaround:
  1. Manually configure the UNI with vlan-ccc physical encapsulation before prestaging devices.
  2. During service order creation, manually assign VLAN IDs above 512.

  [PR/458510]

• When you enable protect-interface in the service definition, Junos Space should allow selecting the backup interface in the service order and should be able to push configurations to both primary and backup interfaces. Configurations are not pushed to the backup interface. Junos Space allows this backup interface to be selected in a different (new) service order, which it should not allow. [PR/495702]

Prestaging Issues

This section describes known device prestaging issues.

• The Manage Device Roles screen allows you to select the Unassign NPE Role action for a device even when the NPE role assignment job has not finished yet for that device. The following error message is generated when trying to unassign such a device: “unassign when role assignment is still running for that device.” This issue occurs only when the device has many services already deployed. [PR/495714]
• The Search option is not implemented in Prestaging Rules page. [PR/495750]

User Interface Issues

This section describes known user interface issues.

• If one of the nodes in a Fabric goes down, web UI sessions connected to that node might not refresh automatically. As a workaround, perform a manual refresh. To restart automatic refresh, log out of the UI session and log back in. [PR/493159]

Administration Issues

This section describes known Administration workspace issues.

• If the appliance or service is restarted, the ribbon icons are not displayed properly for some time for the existing user interface session. [PR/444142]
• If you change the time zone on your client PC you have to refresh the browser to reflect the correct time zone. [PR/495767]

Job Management Issues

This section describes known issues with the Jobs workspace.

• On restoring the database, the corresponding Backup Database job state will be displayed as “Failure.” [PR/477765]
• The Jobs workspace might not display the correct time for "Actual Start Time" and "End Time" of scheduled jobs in the summary view. This issue is seen in the virtual appliance and the resolution is to use the service of an NTP server.

User Management Issues

This section describes issues related to the Administration workspace.

• Clicking the Active Users History chart takes you to the Number of Users by Assigned Role chart. [PR/495713]
• The active user count in the System Health panel could drop after cluster node reboot, although all the users remain connected. In the System Health panel on the system dashboard, the Active Users History chart indicates how many users are currently active in the Junos Space cluster. If a cluster node shuts down, some user sessions could be closed and switch to the remaining running cluster node. However, closing user sessions on the failed node reduces the active user count. The user count could drop to zero if all the user sessions were active on the node which is rebooted. As a workaround, if all users log out and log in again, the active user count will become correct. [PR/495713]

Device Management Issues

This section describes known issues with device management.

• When two large discovery jobs are running at the same time or scheduled to run close to each other, the later job might report some devices failed to be managed with the following message: “Timeout while waiting for device to connect back or to be saved”. These devices are actually added into the system. They are up and their configuration status is “Out of Sync”. As a workaround, after all discovery jobs finish, resynchronize these “Out of Sync” devices. [PR/495732]
• If the you specify a non-preferred management IP address of the device in the Discover Targets task, Junos Space does not automatically switch to the preferred IP address when it adds the device to management. We recommend providing the preferred management IP for the device in the Discovery Targets task. [PR/493116]
• If a bulk device delete operation takes more than 5 minutes, the delete dialog box in the user interface will persist after job completion. You must cancel the dialog box manually. We recommend you do not perform cancel while the delete operation is in progress. To determine the status of the delete job, check the device count at the bottom of the inventory page. PR/495735]
• Device discovery might fail to add a J Series device if a timeout occurs while Junos Space attempts to establish that the device is reachable, even if the device can be successfully pinged. This timeout can occur because the J Series device is a firewall and might block traffic on port 7, which receives the connection attempt from the Junos Space appliance. As a workaround, perform one of the following actions:
  • Rerun device discovery and uncheck the ping option in the probe. Instead, use only SNMP to discover the device.
  • On the device CLI, enter the following command to allow traffic to port 7 in the firewall: “set security zones security-zone trust host-inbound-traffic system-services all”.

CLI Issues

• Junos Space does not support configuring the time zone for an appliance. [PR/495770]

Service Now Issues

This section describes known issues with Service Now.

• Service Now does not support highly available clusters with Space 1.1 applications in a Fabric setup. [PR/490639]
• Service Now users who submit cases may see the message Success - LIC-4004-WARN - Device doesn't have appropriate Service Contract level, but request to open case is accepted. Contact Juniper or Juniper Partner to add device to the appropriate Service Contract.,even though the device is already included in an appropriate service contract. In addition, JSS will reject iJMBs sent from this device. [PR/494769]