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 

Resolved Issues

This section lists the resolved issues in Connectivity Services Director Release 2.2R1. For the most complete and latest information about resolved Junos Space Connectivity Services Director defects, use the Juniper Networks online Problem Report Search application.

  • You cannot navigate to the Site Settings page when modifying a Layer 3 VPN service, if policies are attached to the nodes. [PR 1256023]

  • While trying to delete the customer IP address pool, the Delete button is not getting enabled. [PR 1303698]

  • Different policy attributes are added to the same term, even when the term names are different. [PR 1306215]

  • The VLAN field is not retained in the Site Settings page when the OK button is clicked. [PR 1312862]

  • A template created in Services Activation Director cannot be deployed to a device from Connectivity Services Director because of a limitation of the Route Preference value. [PR 1314776]

  • A service created in one Connectivity Services Director server cannot be recovered from another Connectivity Services Director server. [PR 1314903]

  • While creating a VPLS service order by using a default VPLS Service Definition, the Instance Type and Protocol fields have no default values specified. [PR 1316632]

  • When creating a service order, Connectivity Services Director does not accept the device configuration if at least one Juniper Networks device is not defined as a hub. [PR 1324706]

  • The Tag Protocol Identifier (TPID) is associated with an endpoint even after the TPID is removed from a VPLS service definition. [PR 1329037]

  • You cannot create a service order with an integrated routing and bridging interface and static protocol route. [PR 1331545]

  • API queries for the number of interfaces used in a Layer 3 VPN service return inconsistent results. [PR 1337575]

  • You cannot deactivate a VPLS service that has an interface with a different unit and VLAN ID. [PR 1340453]

  • The class-of-service profile configuration is removed from a site on which BGP service is configured with hub and spoke roles, when the site type is changed from hub to spoke or vice versa. [PR 1341499]

  • While creating a VPLS service, the VLAN ID cannot be edited from the Site Settings page. Instead, the existing VLAN ID is deleted if the description is updated. [PR 1344037]

  • While creating a Layer 3 VPN service with policy, a new term cannot be inserted above a selected policy term. [PR 1313422]

  • While creating a Layer 3 VPN service, the service name is not displayed on the Service View pane. [PR 1335873]

  • When a device is deleted, the services associated with that device are not deleted. [PR 1341350]

  • You cannot create a VPLS service with an IRB interface. [PR 1344115]

  • While modifying a VPLS service with TPID configured, the inner TPID and outer TPID fields are editable. [PR 1345103]

  • After modifiying an LSP service, only the modified endpoints are listed on the LSP Service Details page. [PR 1345431]

  • After an LSP service is modified, the LSP Modify page displays only the last updated egress nodes. [PR 1345444]

  • When a service is created by using a customer-specific service definition, all the required configurations are not sent to the device. [PR 1301386]

  • The VLAN maps are applied to point-to-point services even though the VLAN maps for P2P services option is not selected. [PR 1321984]

  • While creating an L2 or L3 service, duplicate UNIs are created on devices. [PR 1330735]

  • While creating an LSP service, the name of a decommissioned service cannot be assigned to the new service. [PR 1343812]

  • Connectivity Services Director incorrectly allows users to select SRX Series devices during provisioning of LSP services. [PR 1344119]

  • Connectivity Services Director should allow a minimum packet size of 100 bytes instead of 1 byte for MPLS LSP ping. [PR 1344124]

  • When a point-to-multipoint service is modified by deleting a node and adding another node, the service order details show only the newly added node. Existing nodes in the service are not displayed. [PR 1343805]

  • Connectivity Services Director accepts values for the Adjust Interval parameter only up to 2,147,483,647, while devices accept values up to 315,360,000. [PR 1340156]

  • While creating a VPLS service order, when the 802.1Q tagging is selected, the Inner TPID field should not be editable. [PR 1342523]

  • All the discovered devices listed on the Node Settings page are not listed on the Prestage Devices page while creating a service. Also, the devices qualified for the N_PE role are shown as qualified for the P role. [PR 1344033]

  • Functional Audit fails for a Layer 3 VPN Service if VRF table label and Enable Auto export routes options are set to Editable in service order in an L3 VPN service definition. [PR 1344995]

  • No results are displayed under the Audit Results tab in the Configuration Audit window, when point-to-point spoke is associated with neighbor and backup neighbor in a hub-and-spoke BGP service. [PR 1343143]

  • A term or clause cannot be deleted from a Layer 3 VPN service policy. [PR 1313419]

  • On the Create Service Definition page, the upper limit of MTU is 9216. [PR 1241543]

  • While modifying a VPLS service, you cannot search on the Site Settings page for an endpoint that is not associated with the service. [PR 1248119]

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

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

  • 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. [PR 1255005]

  • You cannot modify a service without modifying at least one endpoint. [PR 1282178]

  • In a 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. [PR 1257293]

  • Service templates are not recovered if they do not contain the complete hierarchy for the attributes or statements that are configured. [PR 1287027]

  • Some interfaces are listed incorrectly in both NNI and UNI tabs. [PR 1290708]

  • 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. [PR 1294235]

  • If you allocate an IP address with a suffix less than 18 to a site in a 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. [PR 1295268]

  • If nodes having the same route distinguisher value are deleted from a service, then the route distinguisher value is not deleted from the service. [PR 1298805]

  • 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. [PR 1299605]

  • vlan-list configuration is not pushed to devices that have VLAN normalization configured. [PR 1299976]

  • The ACX5000 line of routers do not support the vlan-id all configuration. [PR 1299969]

  • 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. [PR 1300966]

Modified: 2018-04-04