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 Issues

The following are the known issues in Connectivity Services Director Release 2.1R1. For each entry, the identifier in the PR Number column of Table 2 is the tracking number in the Juniper Networks problem report (PR) tracking system.

Table 2: Known Issues in Connectivity Services Director Release 2.1R1

PR Number

Problem Description


In the Topology view, the status of Layer 3 links are not dynamically updated.

Workaround: To update the status of the Layer 3 links you must perform a Refresh Topology job manually.


In the Topology view, optical inline amplifiers (ILAs) are displayed on optical links only after a delay of 15 seconds.

Workaround: None at present.


While modifying a Layer 3 VPN service if you select a device to associate a policy, the policy is listed only if you have associated the policy with a device at the time of policy creation.

Workaround: None at present.


If the AS number is greater than 65535, you must append Route Target or Route Distinguisher values with “L”. Connectivity Services Director fails to recover a service with such Route Target or Route Distinguisher values.

Workaround: None at present.


On the Create Service Definition page, the upper limit of MTU is limited to 9216.

Workaround: None at present.


A device you deleted while modifying a Layer 3 VPN service appears in the Create Policy page.

Workaround: None at present.


A generic error message is displayed if the deployment of a VPLS service with Traffic Type as Transport VLAN fails. The generic error message must be replaced with the following appropriate error message:

Specify CVLAN start and CVLAN end values.

Workaround: None at present.


While you are modifying a VPLS service, you cannot search on the Site Settings page for an endpoint that is not associated with the service.

Workaround: None at present.


If you modify the ASN value on a device, the new ASN value is not updated in the Connectivity Services Director application.

Workaround: None at present.


An Ethernet interface, which is a part of an aggregated Ethernet, is listed as user-to-network interface (UNI).

Workaround: None at present.


For a modified RSVP LSP service, the View Configuration Change page displays only the modified configuration instead of the displaying the entire configuration.

Workaround: To view the entire configuration, you must force-deploy the RSVP LSP service.


If a service template has multiple MD5 key-value rows with different default values and if you attach this service template to a Layer 3 VPN service, the Template Configuration page displays the same default value for each MD5 key-value row.

Workaround: While you are creating a service you can modify the default values for each MD5 key-value row.


You cannot modify a service without modifying at least one endpoint.

Workaround: From the Service Settings tab, modify the comment and UNI description of any of the endpoint and deploy the service.


In VPLS Service, you cannot search service by its description. This is because the Connectivity Services Director application does not support searching a service by service description. This problem is planned to be fixed in a future release.


Service templates are not recovered if they do not contain the complete hierarchy for the attributes or statements that are configured.

Workaround: Recreate the templates by providing the complete hierarchy. The Connectivity Services Director application needs this information to recover and manage the templates.


Some interfaces are listed incorrectly under both NNI and UNI tabs. This problem is planned to be fixed in a future release.


Service Recovery process does not recover unmanaged device details such as loopback IP address and UNI Interface if one of the end points is configured as unmanaged.


When an IP address with a suffix less than 18 is allocated to a site in an L3VPN service, IP address allocation is not done properly.

For IP addresses to be assigned properly, you must allocate an IP address suffix that is greater than 18.


When nodes having the same route distinguisher (RD) value is deleted from a service, the route distinguisher value is not deleted from the service.


When a new node along with path is added during modification of an RSVP full mesh service definition that has custom pattern, an additional LSP configuration is added to the newly added device.

Workaround: Modify the RSVP full mesh service and add a new node without path information. Modify the service and add the path information.


vlan-list configuration is not pushed to devices that has VLAN normalization configured.

Workaround: Use templates to configure vlan-list instead of vlan-range.


ACX5000 Series routers do not support the vlan-id all configuration.

Modified: 2017-08-13