Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Known Issues

 

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

  • The following issues are seen when layer 3 (L3) access is enabled for an ethernet-LAN (eLAN) service definition:

    • Port tagging is not supported

    • If tagging is Dot1q, vLAN normalization only normalizes to the Dot1q tag.

    • If tagging is QinQ or asymmetric tag depth, vLAN normalization only normalizes to the QinQ tags.

  • Cannot create a service order with a custom path for a label switched path (LSP) with point-to-point (P2P) path and local protection. When you try to create a custom path, the creation of the service order fails with the error “Fast Reroute is not required”.

    Workaround: First, create an LSP service definition with P2P path and local protection. Then, create a service order by importing the newly created service definition, and continue to create the custom path.

  • When a UNI is deleted using the Service Modify functionality, the deleted UNI information is still shown as part of the service configuration.

  • ACX5448 supports provisioning of only basic E-Line and LSP services on Junos OS Release 18.2.

    ACX5448 does not support provisioning of E-LAN and IP service types on Junos OS Release 18.2. [PR 1367398]

  • The fault status of an E-LAN BGP or E-LAN LDP service is not displayed correctly on the user Interface. [PR 1344103]

  • While creating an IP service, if you select more than one interface from the same device, the interfaces appear in the same row, separated by commas. [PR 1345660]

  • When you use an IFD template with a tag-based role to push configuration on a VLAN-based service and then later delete the VLAN-based service to create a service by using the same IFD template with the role changed to port-based, the service creation fails. [PR 1346264]

  • You are unable to delete an IP service that has at least one node configured with an Integrated Routing and Bridging (IRB) Interface. [PR 1347272]

  • The Fault status on the Manage Network Services page is unavailable for an E-LAN service with Transport vlan list as the traffic type. [PR 1350669]

  • If you delete the peer node of a device while editing the node settings of an E-LAN service order and later revert the changes, then the peer node is not displayed on the Edit E-LAN Service page. [PR 1366732]

  • When an EVPN service, with ESI and multihoming set to single-active or all-active, is recovered, the Service Details page does not list peer interfaces.

    Also, when the service is modified, the Node Settings and Site Settings pages of the Service do not show the mapping between interfaces of the peer nodes. [PR 1362288]

  • The fault status is unavailable on the Connectivity Services Director GUI for an E-LAN service with evpn or evpn e-tree as the protocol type, when an interface goes down. [PR 1355928]