Known Issues

This section describes known issues with Junos Space Release 1.0.

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.

VPLS Issues

This section describes known issues with multipoint Ethernet services:

• Modify VPLS Service is not support if you use a customized service definition.
• MAC security settings are not pushed to the device during deployment.
• The MAC learning security setting is always set to false. This value works for almost all VPLS use cases. The MAC statistics security setting is also always set to false.
• Automatic selection of VLAN IDs does not work correctly in service orders that are based on a customized service definition in which Auto pick is selected in the VLAN ID selection field and the Editable in service order check box is unchecked. These selections in the service definition should create a service order in which the VLAN ID is automatically selected and the Auto pick VLAN ID column in the Endpoint Settings table cannot be edited. Instead, the Endpoint Settings table in the service order shows the Autopick VLAN ID checkbox unchecked and it cannot be edited. As a result, automatic selection of the VLAN ID does not take place.

  As a workaround, in the service definition, select Auto pick in the VLAN ID field as before, but check the Editable in service order checkbox. The Endpoint Settings table for a service order based on this service definition will show the Autopick VLAN ID checkbox checked, causing the VLAN ID to be automatically selected. However, the Autopick VLAN ID check box will be editable in the service order.

• Adding an endpoint to a VPLS service does not work for a service that specifies a VLAN range. After you add the endpoint in the Modify Service screens, the start and end values for the VLAN range change to 0 and 0. The Junos Space software issues an error when you attempt to save the service order.
• Creating a customized service definition does not perform validation on the traffic type.

Prestaging Issues

This section describes known device prestaging issues.

• The Modify Loopback Address action does not show other loopback addresses configured on the same logical interface in the device. It shows a loopback address configured on a different logical interface, but does not change the device loopback address in Junos Space.
• Searching by IP address in the Assign Roles page and searching by UNI name in the Add Device UNIs page are not supported.
• 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.

Other Service Provisioning Issues

This section describes known issues with provisioning services.

• 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.
• The Search option does not work in the Prestaging Rules page.
• Contextual launching does not work from the Role Discovery Status chart.
• Automatic rollback of failed service order deployments is not supported.
• The Modify Service action allows you to change the physical interface MTU value on a service provisioned interface. Changing the physical interface MTU will affect other services provisioned on that interface.
• If vlan-ccc physical encapsulation was configured on a UNI before prestaging, Junos Space will not allow you to use VLAN IDs less than 512 even when deploying a point-to-point or VPLS service order with flexible-ethernet-services physical encapsulation on that UNI. As a workaround, to allow the use of VLAN IDs below 512 for service order deployments with flexible-ethernet-services physical encapsulation:
  1. Go to Manage Device Roles -> Manage Device UNIs and delet the UNI.
  2. On the device, use the CLI to remove encapsulation vlan-ccc from the UNI configuration.
  3. Resynchronize the device.
  4. In the Mange Device Roles page, add the UNI.

Administration Issues

This section describes known Administration workspace issues.

• The Eth0 and Eth3 interface IP addresses cannot be changed.
• If the appliance or service is restarted, the ribbon icons are not displayed properly for some time for the existing user interface session.
• There is no confirmation message for the “Q” option in the configuration summary menu, which is displayed at start up.
• Copying logs to a USB drive is not supported on a Junos Space virtual appliance because of VMware ESX server limitations.
• The clock in Junos Space will not display the time correctly if you change the time zone on your client PC. As a workaround, refresh your browser to display the correct time.
• The Junos Space Appliance Settings menu might erroneously display the Expand VM drive size option for a physical appliance. This option should appear only for the virtual appliance.

Job Management Issues

This section describes known issues with the Jobs workspace.

• 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.
• The “Percent Complete” column in the table view of the Manage Jobs inventory page might not display the “Percentage of job execution completed” for intermediate states.
• On restoring the database, the corresponding Backup Database job state will be displayed as “Failure.”

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

Device Management Issues

This section describes known issues with device management.

• After starting discovery, the status graph might remain blank for about 4 or 5 seconds.
• Specific Junos releases and versions that fully support Junos Space 1.0 are limited to the following:
  • Junos Release 9.3R4
  • Junos Release 9.4R3 and R4
  • Junos Release 9.5R2 and R3
  • Junos Release 9.6R1 and R2
• 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.
• 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.
• 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.
• 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.