Operational Notes

• The minimum supported screen resolution is 1280 x 1024. If your screen resolution is less than the supported resolution, the Connectivity Services Director UI might not be displayed properly. For example, icons might not be displayed on the Connectivity Services Director banner, pages might appear truncated, or scroll bars might not work correctly.

• The supported Web browsers are Google Chrome 17 and later, Mozilla Firefox 14.0 and later, and Microsoft Internet Explorer 9.0, 10.0, and 11.0.

• If you have been logged in to Connectivity Services Director for a long period of time, the connection to the server might time out. Monitoring pages might go blank or you might not be able to access tasks. To resolve this, log out of Connectivity Services Director and then log in again.

• If you receive a Java exception error message when you perform an operation, retry the operation. The error condition is usually temporary and harmless.

• Only user accounts with administrator (admin) privileges can use the Connectivity Services Director API.

• For Connectivity Services Director to be able to discover and manage devices, the following protocol ports must be open between the Junos Space Platform server and the devices:

  • Port 22 for SSH connections. If you have changed the SSH port to a port other than port 22 on your Junos Space Platform, you must change the SSH ports on your managed devices to the port that the Junos Space Platform is using.

  • Port 10162 for device-level SNMP traps. Connectivity Services Director receives traps from managed devices on this port. (After you install Connectivity Services Director, use Connectivity Services Director to configure SNMP on your devices to send traps to Connectivity Services Director on this port.)

  • Port 162 for service-level SNMP traps. Connectivity Services Director uses OpenNMS for SNMP trap collection and correlation.

  • Port 21 (TCP) and port 69 (UDP). Connectivity Services Director uses these for uploading the software image and configuration file to the FTP server.

• When a switchover from the active Junos Space server to the standby server occurs in a clustered Junos Space appliance environment, cleared alarms are not notified to the Junos Space server, although OpenNMS receives the clear-alarm notification. To work around this problem, you must manually clear the appropriate alarm from the Alarm Detail monitor in Fault mode of Service view of the Connectivity Services Director GUI.

• Rest API timeout has been increased to 1 minute for View Pending Configuration to avoid timeout.

• If OpenNMS is restarted, the OpenNMS service loses all the data in its cache repository and the multisite alarm status calculation goes wrong. In such a scenario, you must manually analyze the network and take corrective actions, as necessary, on the alarms.

• When you add or delete a Fault Monitoring and Performance Monitoring (FMPM) node to a Junos Space cluster, the following message is displayed:

  You must restart all the Junos Space nodes in such a scenario.

• After a device is prestaged in Connectivity Services Director, the prestaging job is not initiated on the same device again. When a device notification is received by the application, Connectivity Services Director synchronizes the prestaging database on the user-to-network interfaces (UNI). If a mismatch is detected in the UNI status of the interface in the Connectivity Services Director database and the UNI status of the interface on the device (caused by the application being down or network accessibility problems), the synchronization of the UNI interface might not occur. In such a case, the synchronization operation occurs when a configuration-commit on the device is performed the next time. To manually resolve this discrepancy in the UNI status of the interface, you can unassign the UNI role of the interface, which causes prestaging to perform a synchronization.

• In a scaled environment, you can disable the monitoring functionality, which causes the Connectivity Services Director application to poll the specified devices and retrieve details to be displayed in the widgets in Monitor mode of Service view. You might require the monitoring functionality to be disabled to prevent the slowness in loading the GUI pages. To disable the monitoring mechanism, you can run a script on the Junos Space Appliance. You must stage the script on the device with administrative and execute permissions for the script file before executing the script.

  To enable or disable monitoring, enter the following command at the shell prompt (To run shell commands, from the Junos Space Appliance Settings menu, enter 7 at the prompt):

  where:

  • db_user_name is the username of the user for the Connectivity Services Director database.

  • db_password is the password of the user for the database.

  • collectorName is the name of the collector for which you want to enable or disable retrieval of statistics. You can enter one of the following collector names:

    • ProvisioningMonitorInterfaceStatusCollector—Defines the polling interval for monitoring the interface status

    • ProvisioningMonitorInterfaceStatsCollector—Defines the polling interval for monitoring the interface statistics

    • ProvisioningMonitorServiceStatusCollector—Defines the polling interval for monitoring the service status

    • ProvisioningMonitorLDPStatsCollector—Defines the polling interval for monitoring the LDP statistics

    • ProvisioningMonitorY1731PMCollector—Defines the polling interval for monitoring the performance management or Y.1731 statistics

    • ProvisioningMonitorLSPStatsCollector—Defines the polling interval for monitoring the LSP statistics

    • EquipmentMonitorDeviceStatusCollector—Defines the polling interval for monitoring the status of a device

    The collectorName parameter is optional. If you do not specify a collector name, monitoring is enabled or disabled for all the collectors. If you enter an incorrect collector name, the list of collector names is displayed and you are prompted to select from the list.

  • enable is the keyword to enable the monitoring functionality and collection of statistics.

  • disable is the keyword to disable the monitoring functionality and collection of statistics.

  We recommend that you use the script to disable the monitoring functionality only with the assistance of a Juniper Technical Assistance Center (JTAC) representative.

• For IP services, data plane validation is not performed when you run functional audit for a service that does not contain the vrf-table-label attribute, which maps the inner label of a packet to a specific VRF instance. The Functional Audit Results window displays a message about the vrf-table-label configuration attribute not enabled in the service in such a scenario.

• Sometimes, the validation of an E-Line service order fails with an error message stating that a duplicate virtual circuit ID exists, even when you have selected the option to automatically assign a VC ID from the VC ID pool in the service order. This condition occurs because of a resource pool allocation failure—that is, when the same device is managed by more than one Junos Space Platform application. Consider a device that is added and discovered by two Junos Space Platform servers. Assume that on one server running Junos Space Platform, Connectivity Services Director is also installed. The resource pool management functionality on that server reserves resources for devices that are managed only by using that server. If a resource, such as an IP address pool, VLAN ID, or a route target is reserved by both the Junos Space Platform servers, the reservation on one server is not reflected in the other server. If the same resource is marked for use in a service by multiple Junos Space instances or servers that manage the same device, you must perform a service recovery operation. This operation recovers services that are present on devices that Junos Space is not managing. Auto-discovery of services is not supported; therefore, resources used by other Junos Space servers or modified on a managed device using the CLI are not reserved and displayed in the resource pool. The device configuration must be validated to check for duplicate resources before deploying or validating a service.

  When a device is configured from the CLI, apart from the application, service recovery must be performed on CSD. This is required so that CSD can learn all the consumed resources in the network and auto-allocation allocates free resources and also restricts manual configuration of consumed resources.