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

1241543

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

Workaround: None at present.

1248119

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.

1255682

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

Workaround: None at present.

1259449

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.

1255005

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.

1282178

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.

1257293

In VPLS Service, you cannot search a service by its description. This is because the Connectivity Services Director application does not support searching a service by service description. There is currently no workaround.

1287027

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

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

1290708

Some interfaces are listed incorrectly in both NNI and UNI tabs. There is currently no workaround.

1294235

The service recovery process does not recover unmanaged device details such as loopback IP address and UNI Interface if one of the endpoints is configured as unmanaged. There is currently no workaround.

1295268

If you allocate an IP address with a suffix less than 18 to a site in an Layer 3 VPN service, then 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.

There is currently no workaround.

1298805

If nodes having the same route distinguisher value are deleted from a service, then the route distinguisher value is not deleted from the service. There is currently no workaround.

1299605

If a new node along with path is added during modification of an RSVP full mesh service definition that has a custom pattern, then 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.

1299976

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

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

1299969

The ACX5000 line of routers do not support the vlan-id all configuration. There is currently no workaround.

1300966

If you try to create a Layer 3 VPN service order with loopback configuration on Junos Space Platform Release 16.1, 17.1, or 17.2, then the service order creation job fails.

Workaround: When you deploy a loop back interface, attach a template containing loop back configuration to the service order.

Modified: 2017-10-12