Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

New and Changed Features

 
  • Renaming services to comply with MEF standards—Starting from Junos Space Connectivity Services Director Release 3.0R1 onward, VPLS, Point-to-Point, and Layer 3 VPN services are renamed as E-LAN, E-Line, and IP services, respectively, to comply with Metro Ethernet Forum (MEF) standards.

  • New device support—Starting from Release 3.0R1 onward, Connectivity Services Director supports the following devices:

    • ACX5448

    • MX150

    • MX204

    • MX10003

  • New attributes on E-LAN Service Definition page—In Connectivity Services Director Release 3.0R1, the following fields are added on the E-LAN Service Definition page:

    • Instance Type list, under the General Settings tab, to select the type of routing instance to be used for the E-LAN service.

      You can select one of the following options for the routing instance—vpls, evpn, or virtual-switch.

    • Protocol list, under the General Settings tab, to select the protocol to be used for the E-LAN service.

      You can select one of the following options as the protocol, based on the Instance type selected—vpls, evpn, or evpn e-tree.

      • If you select vpls as the instance type, only vpls protocol is available.

      • If you select evpn as the instance type, evpn and evpn e-tree protocol types are available.

      • If you select virtual-switch as the instance type, vpls, evpn, and evpn e-tree protocol types are available.

    • Enable Multihoming check box, under the BGP Connectivity Settings section, to pair any two NPE devices, for providing redundant connectivity.

      If you select this check box, a Multihoming Mode list appears.

      You can select either Single-active or All-active as the multihoming mode.

    • Transport vlan list option in the Traffic Type list, under the Site Settings tab.

      If you select this option, the service transports traffic across the network based on a list of VLANs that you enter manually while configuring a service order.

  • New attributes on E-Line Service Definition page—In Connectivity Services Director Release 3.0R1 , the following fields are added on the E-Line Service Definition page:

    • Transport vlan list option in the Customer Traffic Type list, under the UNI Settings tab.

      If you select this option, the service transports traffic across the network based on a list of VLANs that you enter manually while configuring a service order.

    • Enable Multihoming check box, under the Service Extension section of the General Settings tab, to pair any two NPE devices, for providing redundant connectivity.

      If you select this check box, a Multihoming Mode list appears.

      You can select either Single-active or All-active as the multihoming mode.

    • Instance Type list, under the General Settings tab, to select the type of routing instance to be used for the E-Line service.

      You can select either l2vpn or evpn-vpws as the routing instance type.

      The Instance Type list is available only if you choose BGP as the signaling type.

Note

From Connectivity Services Director Release 3.0R1 onward, the existing REST APIs have been updated to include the Instance Type and Protocol fields.

  • Integrating NorthStar Controller 3.2.0 with Connectivity Services Director Release 3.0R1—Starting in Connectivity Services Director Release 3.0R1 onward, you can choose NorthStar Controller to manage label-switched paths (LSPs) from the Connectivity Services Director user interface.

    The integration of NorthStar and Connectivity Services Director provides a single configuration window that enables you to create, modify, and delete RSVP LSPs and segment routing LSPs by using REST APIs.

    With the integration, you can create segment routing LSPs by using NorthStar Controller, as Connectivity Services Director currently supports the creation of RSVP LSPs only.