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 
  
[+] Expand All
[-] Collapse All

Known Limitations

This section lists the known limitations in Connectivity Services Director:

  • Job details displayed on the Config Deployment Jobs Status page do not contain complete information about failed jobs. To get complete information about failed jobs, including the reason for job failure, you need to verify the server logs stored on the server.
  • Connectivity Services Director supports role-based access control (RBAC) only at the task category level. There is no support for object-level or task-level access control.
  • If an interface or the logical unit of an interface is deactivated, the configuration audit operation fails and a message about a mismatch between the interface configuration on the device and the interface configuration in the Connectivity Services Director database is displayed under the Show Results tab of the Configuration Audit dialog box. However, configuration audit is successful if you deactivate the interface at the [edit interfaces interface-name unit logical-unit-number family vpls] hierarchy level of the CLI configuration.

    When you disable an interface from the CLI, a new tag, <disable>, is added to the configuration on the device. When you perform a configuration audit, Connectivity Services Director sends the list of XPath attributes to be verified in the XML configuration present on the device before the configuration changes are propagated to the device. Because the <disable> attribute is not one of the tags that are sent to the device, the Connectivity Services Director application cannot determine whether the tag has been added to the XML configuration. As a result, a configuration audit is successful in such a scenario.

  • When you edit a service order, the auto-pick option that you enabled during the creation of the service order that is associated with a service definition is not preserved. Also, the parameters for which you enabled automatic selection by the system, such as Unit ID and Route Target, require you to enter values, and the Autopick check boxes do not remain selected.
  • When you edit an existing service order by clicking the Edit button on the Manage Network Services or Manage Service Deployment pages in Deploy mode of the Service view on the Connectivity Services Director GUI, a fresh service order is created with the name you specified. Only the changed node details are stored in the new service order and the previous details are lost.

    This is an expected behavior because only a subset of the configuration settings are required to be propagated to a device from Connectivity Services Director, whenever a service order is modified. As a result, an existing service order is not saved when you modify it; instead, a fresh service order is created. Also, a service order related to a failed or invalid modified service cannot be modified. You need to delete the failed or invalid service order and modify the service again.

  • Sometimes, the validation of a point-to-point 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 you launch the Chassis view of a device, device labels are missing from the Google Chrome browser. The interface numbers are not displayed beneath the ports and the device name is not shown in the front view of the chassis image. Also, when you click the Perspective button to view the three-dimensional, advanced view of the chassis, the quality of the chassis image displayed is reduced slightly. This behavior with image quality is expected in the Google Chrome browser.
  • In Monitor mode of the Service view, for the Service Monitoring Summary page, the Traffic Trend data is displayed without a unit of measurement (UOM), a tooltip, or an option to zoom in or zoom out.
  • When you select the Service Traffic tab in Monitor mode for a specific point-to-point LDP resiliency service, the connection status between the source device and other devices is denoted as NA (not available) in the Service Traffic monitor if any of the following conditions occur:
    • The device does not have Layer 2 circuit data.
    • Remote procedure call (RPC) commands are failing.
    • The NETCONF connection fails to be established.

    On the pseudowire graph in the Service Traffic monitor, a gray line is displayed for the NA state. After the next polling cycle, the monitoring mechanism of Connectivity Services Director marks the connections status as NA for all connections from the endpoints on which the Layer 2 circuit configuration is deleted.

    The connection status value in the Service Traffic monitor is refreshed depending on the polling interval configured on the Monitoring tab of the Preferences page (which you can launch by clicking the down arrow beside the System button on the Connectivity Services Director banner and selecting Preferences).

  • On the Service Monitoring Summary page that is displayed when you select a service from the Network Services > Connectivity > P2P Services tree, Network Services > Connectivity > L3VPN Services tree, or Network Services > Connectivity > VPLS Services tree in the Tasks pane, and select the Service Traffic tab in Monitor mode of Service view, the Traffic Trend (bps) column displays only the rate of egress traffic in the form of a line graph. The rate at which ingress packets are received is not displayed.
  • When you attempt to validate or provision a service order, the "Service Order Deployed OK" pop-up message is displayed, regardless of the result of the action. This is an incorrect behavior. The same message is displayed even if the validation and provisioning attempts fail. A job ID with a link must be displayed that you can click to navigate to the Job Management page for the results.

    The status of the service order that you validated or provisioned does not change from Scheduled to Validated or Deployed. When a subsequent action is triggered on the service order, a status change is reflected. After the service order is deployed, you are not taken back to the Services landing page in Deploy mode of the Service view.

  • When a configuration audit is performed, the XPath attributes in the service configuration are used. Only the addition, modification, and deletion of the XPath attributes are detected, but the creation of a new attribute (child XPath ) on a device is ignored. This behavior is expected because Junos Space Platform audits only the settings in a user template. If the template has a container, Junos Space Platform audits only to determine whether the device is configured with this container. If you want to audit any container child, you need to add it into the template. This scenario is similar to an out-of-band configuration change on the device, which Junos Space Platform can determine only whether System of Record mode is set for Junos Space Platform.
  • In a scaled environment, the VLAN ID resource pool is not properly considered during the deployment of a Layer 3 VPN service. After being deployed, the service moves to the invalid state because the service generates the same VLAN ID for different interfaces. This problem can arise when the device already contains a service with a VLAN ID and you select the auto-pick option for VLAN ID configuration in the service provisioning workflow for the same device. In such a scenario, the Connectivity Services Director application can generate the VLAN ID, which is already available as part of some other service on the device. At the time of validation, an error message is generated and the service order moves to the invalid state.

    Workaround: Select the option to configure the VLAN ID manually (and enter a VLAN ID that is not present as part of any service in the device), instead of selecting the auto-pick option.

  • Several delete statements are observed in the service settings on the Service Configuration tab of the Configuration dialog box. The delete statements indicate deleted policy attributes from a corresponding service on a device. When a service is created or modified, its policy options are deleted from the device to prevent the previously existing policies from interfering with the service. The presence of the delete statements is an expected behavior and does not indicate any incorrect service configuration.
  • You cannot view details of a device prestaging job on the Job Management page. You need to view the Prestage Devices page in Build mode to view the device prestaging details.
  • When you modify a Layer 3 VPN service order for which multicast VPN has been enabled during the creation of the service order, the MVPN check box is disabled on the Service Parameters page of the Layer 3 VPN service modification wizard. You cannot modify MVPN settings during the editing of a service order if MVPN is already enabled in the service order.
  • You cannot select a multihomed group on the Node Settings page of the VPLS service order creation wizard with the signaling type as BGP.
  • On the Manage Network Services page, you can search for services using only the service name. For the other fields displayed on this page, the search utility is not supported. You can filter the table by clicking the arrow to display the column drop-down menu in the table and selecting the Filters option.
  • The search function is supported only for the elements of the tree that are displayed on the page; the global search facility that analyzes all configured elements in the database is not supported.
  • While prestaging a device, you cannot modify a loopback address or add multiple loopback addresses.
  • At times, when you attempt to validate a VPLS service, an error message is displayed stating that the route target is not in the prescribed format of x:y. This error occurs when an autonomous system (AS) number is defined in the device or when the routing options table does not have the AS number of the device stored in it (that is, the AS number is not synchronized properly).
  • In a scaled environment, thousands of services, each assigned to a different virtual circuit ID (VC ID), the Resource Allocation Details page from the Prestage Devices workspace in Build mode of the Service view contains too many details. It is difficult to determine whether a VC ID has been assigned to a device or not. This is because VC IDs are sorted on the basis of strings and not numbers.
  • You cannot view the pending service order configuration for an invalid service order.
  • The Decommissioned Service Orders option is available on the Tasks pane only when you select the Connectivity node or the Tunnel node from the Network Services tree on the View pane. This option is not available if you select the Network Services node on the View pane. Also, this option is not available if you expand the Connectivity tree and select P2P Services, VPLS Services, or L3VPN Services, or if you expand the Tunnel tree and select RSVP LSPs.
  • From the Service Monitoring Summary page, which is displayed if you do not select a particular service from the Service view pane and select the Network Services, Connectivity, P2P Services, L3VPN Services, or VPN Services node on the Service view pane and you want to navigate to the Service Summary page of a specific service, select the corresponding service from the Network Services > Connectivity tree on the View pane.
  • When you perform a functional audit with the DMI schema as JUNOS 13.2 on the Junos Space Platform server that is running Connectivity Services Director, the functional audit job fails because the configuration is propagated to devices without the accept and reject tags, which prevents the routes from coming up.

    Workaround: Upgrade the DMI schema to JUNOS 14.2, which causes functional audit to succeed and the routes to come up properly.

  • Sometimes, when you attempt to discovery devices from the Connectivity Services Director GUI after the installation of a new image, the "Service is not available due to resource loading, please retry later." message is displayed. This condition occurs because it takes more time than expected for the resources and schema to be loaded from Junos Space Platform. As a result, adequate resources are not available to initiate the discovery of devices.
  • For each VPLS service order, multiple entries are created in the Edge Services Director database. This behavior is expected because a service with "n" endpoints creates "n" entries in the ELANVplsConnectivity table of the database and for each endpoint, data is saved separately with different route distinguishers.
  • For some fields, such as Interface and LSP Status, that are displayed in the different widgets on the Service Traffic, Service Transport, and Service Summary pages in Monitor mode of the Service view, the values or statuses that are shown are updated based on the polling interval for retrieving data from the devices. As a result, the values or statuses for such fields are reflected in the widgets of the monitoring pages with a delay of a few minutes.
  • Tags, which enable you to categorize and organize managed devices, are not supported in Connectivity Services Director. Because tags are not supported, you cannot use tags for provisioning LSPs in cases where an ingress device is a router and an egress device is a device tag, which denotes multiple spokes in a full-mesh or hub-and-spoke topology.
  • In a scaled environment with approximately 3000 services configured, it is observed that the size of the file descriptor increases to the range of 16,000 to 17,000 and remains within this range.
  • When you edit a service order, you cannot modify the parameters of the MAC Settings and Advanced Settings sections of the service order wizard.
  • When you edit a VPLS service order, you cannot modify the device roles. For example, you cannot modify a VPLS spoke to be a P2P spoke.
  • You must clear the browser cache when you need to view and work with the VPLS service order pages. Otherwise, the webpage is not loaded properly.
  • To view only MX Series routers on the Assign Quick Templates page, you select MX from the Device Family list. However, you do not have an option to view only ACX Series routers on the Assign Quick Templates page. You select Common from the Device Family list to display all device families, which also includes ACX Series routers.
  • The deletion of a service order that is in the decommissioned state fails with the following error message:

    An error occurred deleting this service order:
    Bad Request org.hibernate.exception.ConstraintViolationException: could not delete:
    [net.juniper.jmp.provisioning.jpa.services.ServiceElementEntity#1311450

    To correct this problem, enter the following commands at the shell prompt to delete the service order on the device associated with the service order (To run shell commands, from the Junos Space Appliance Settings menu, enter 7 at the prompt):

    delete from EthernetUni where the service order ID is in the range 1311440–1311445

    delete from EthernetUni where the service order ID is in the range 1311466–11311471

  • For the discovery of LSPs, Connectivity Services Director creates router profiles on CSD-Topology. Connectivity Services Director uses the same username that it uses to discover devices to discover LSPs. If the user account has privileges for shell access, LSP discovery fails on CSD-Topology. This failure occurs because the CSD-Topology requires the user account to have only CLI-access privilege and not shell-access privilege. Also, if Connectivity Services Director has discovered devices using the root account (with native access), LSP discovery fails on CSD-Topology.

    Workaround: Perform the following steps for CSD-Topology to successfully discover LSPs:

    1. Initiate an SSH or Telnet session to the CSD-Topology VM external IP address.
    2. Modify the following CLI command files to be executed to add the cli command before any other command is executed so that access to the CLI shell is obtained. This modification does not impact non-root (non-superuser accounts) because the output of the additional command is ignored. For root users, the CLI shell is invoked first and all other commands (such show configuration and show mpls lsp) are executed correctly:
      [root@hostname~]# /opt/pcs/db/command/juniper.config [root@hostname~]# /opt/pcs/db/command/juniper.interface [root@hostname~]# /opt/pcs/db/command/juniper.tunnel_path [root@hostname~]# /opt/pcs/db/command/juniper.transit_tunnel

      The contents of the preceding files have the CLI command to be executed on the routers. For example, the original contents of juniper.config file are as follows:

      !Silent
      set cli screen-width 0
      show config|display inheritance|no-more
      

      You must modify this file as follows to include the cli command:

      @P
      cli
      !P
      !Silent
      set cli screen-width 0
      show config|display inheritance|no-more
      
  • In a scaled environment, the Connectivity Services Director application may allow multiple users to modify a large service at the same time from different browsers or machines. As a result you may see more than one instances of a single validated service order.
  • On the Service Summary page for VPLS services, the Connections matrix does not show the exact VPLS connection present on the device for all endpoints. This problem occurs because the remote procedure calls and CLI commands do not return the remote device IP address when the connection is down.
  • The monitoring framework polls data from devices based on the serial number of the chassis, rather than the hostname or IP address of the device, which is unique in a network deployment. With the existing monitoring mechanism, when a chassis contains a new serial number, the device chassis is considered a different entity and all historical data (collected for the same host or IP address of the chassis) saved is lost.
  • The outer and inner tag protocol IDs that you want to configure in a service definition must be preconfigured on the device associated with the service definition for a successful validation and provisioning of the service order.
  • In certain scenarios, such as after an upgrade from Services Activation Director 14.3R1 to Connectivity Services Director Release 1.0, you might observe that alarms related to services are not properly cleared on the Connectivity Services Director GUI. This problem occurs because of the manner in which alarms are transmitted from OpenNMS to Junos Space Platform.

    Workaround: Manually clear the appropriate alarm from the Alarm Details page in Fault mode of Service view after examining the alarm and associated events, and taking any action needed to resolve the condition that triggered the event on the corresponding device.

  • During creation of a set of a point-to-point service with pseudowires, which are doubly tagged on the ingress router and singly tagged on the egress router, it is observed that an additional VLAN swap operation occurs on the Z side. This is effectively a null operation because both the input and output VLAN IDs are set as 133 in this case. This behavior also occurs with a local-switching service.
  • If you attempt to create a service order with a point-to-point LDP service definition, you cannot view the non-editable parameters in service template during service deployment. This problem occurs when you create and publish the service definition with local-stitching by associating it with a service template that contains the circuit cross-connect (CCC) family set, such as set interfaces xe-0/2/0 unit 0 family ccc.
  • The ILA adapter fails to upgrade if you install the Connectivity Services Director application in a setup where an ILA adapter already exists.

    Workaround: Before you install the Connectivity Services Director application you must delete the existing ILA adapter. You can delete the existing ILA adapter at Network Management Platform > Devices > Device Adapter.

  • If you migrate from Services Activation Director to Connectivity Services Director Release 2.0R3 or earlier, Enable Tunnel services and Enable Local Switching parameters cause functional issues.

    In order to overcome these issues and maintain consistency across products, in Connectivity Services Director Release 2.0R4, Enable Tunnel services and Enable Local Switching parameters are renamed Disable Tunnel services and Disable Local Switching respectively.

    As a result of this renaming, you may encounter issues when you are migrating from Connectivity Services Director Release 2.0R2 to Connectivity Services Director Release 2.0R4.

    Workaround: Use the Modify Service workflow to modify the service according to the new naming convention. For example, if you prefer to enable tunnel services while modifying the existing service, clear the Disable Tunnel services check box.

  • In specific cases, in a VPLS service, multiple sites might have same interface, UnitID, and VLAN ID. Any subsequent addition of a site results in a redundant site addition along with the original site. Though deployment is successful extra redundant configuration is pushed to the devices.

    Workaround: Perform the following steps:

    1. Disable deploy to device.
    2. Delete one UNI which is duplicate and deploy the service order.
    3. Delete the other UNI and deploy again.
    4. Add the required UNI and deploy.
    5. Enable deploy to device.

Modified: 2017-08-14