Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

New and Changed Features

 

This section describes the new features and enhancements to existing features in Junos Space Cross Provisioning Platform Release 17.1R1.

Hardware Features

  • There are no new hardware features in Cross Provisioning Platform Release 17.1R1.

Software Features

  • Starting with Release 17.1R1, Cross Provisioning Platform has been redesigned to support devices from multiple vendors such as Canoga Perkins and Nokia, and the user operations have been simplified. With the redesigned Cross Provisioning Platform application, you can:

    • Create service definitions with scripts that belong to multiple vendors.

    • Modify an existing service definition to add a new script specific to a vendor.

    • Provision services across Juniper Networks, Nokia, and Canoga Perkins.

    • Perform third-party operations. For example, you can synchronize third-party devices with the Cross Provisioning Platform application by selecting a specific vendor or all vendors on the OSS Synchronization page.

    • Select the Execute Op-Sript option to troubleshoot a service that is associated with Canoga Perkins devices.

  • With Cross Provisioning Platform Release 17.1R1, you can provision services between Juniper Networks devices and Canoga Perkins NIDs.

    To provision end-to-end services across Juniper Networks devices and Canoga Perkins NIDs, Cross Provisioning Platform integrates with an Element Management System, called CanogaView. The CanogaView has a customized software for Bell Canada—Bell Interface Module.

    The Cross Provisioning Platform application integrates with CanogaView and uses Bell Interface Module’s REST APIs to provision end-to-end service across Juniper Networks devices and Canoga Perkins NIDs.

    In Cross Provisioning Platform Release 17.1R1, a new vendor type—Canoga—and a new device role—NID—are introduced.

  • With Release 17.1R1, a new port type—Hybrid—is supported for Nokia devices. To display the port type, a new column Mode is added on the Device Details page. If the port type is Access or Hybrid, the interface type is considered as UNI. If the port type is Network, the interface type is considered as NNI.

    You can fetch the interface details through APIs based on the port type.

    For example, https://<IP Address>/serviceui/resteasy/devices/flex

    /<PEDeviceID>/interfaces?vendorType=Alcatel&Mode=hybrid.