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 

Cross Provisioning Platform Release 16.1R1 Release Notes

Cross Provisioning Platform Overview

Cross Provisioning Platform (CPP) is an extension of the Network Activate application. It provides a real-time operations support system (OSS) for creating and deploying services across multivendor devices. The CPP software manages the interaction of Service Activation Director (SAD) with a module called Nokia 5620 Service Aware Manager (SAM). With Cross Provisioning Platform, you can:

  • Provision services between Juniper Networks devices and SAM devices
  • Provision services across Juniper Networks devices and NEC’s iPASOLINK devices.
  • Manage Services Activation Director services and SAM 5620 Service Aware Manager services
  • Use the Representational State Transfer (REST) APIs to manage services through Services Activation Director
  • Use the Simple Object Access Protocol (SOAP) API to manage SAM 5620 Service Aware Manager

Creating services for Cross Provisioning Platform requires the coordination of tasks performed in several areas of expertise including script design, system administration, and service provisioning. When you create a Cross Provisioning Platform service definition, you can attach scripts designed for the service.

New Features in Cross Provisioning Platform Release 16.1R1

The following features are introduced in Cross Provisioning Platform Release 16.1R1:

  • With Cross Provisioning Platform Release 16.1R1, you can provision services (microwave links) on the NEC iPASOLINK devices.

    NEC has been involved in developing and providing field-proven, reliable wireless backhaul solutions through the iPASOLINK series of Microwave Radios, for service providers all over the world. The iPASOLINK device provide wireless solutions.

    With Cross Provisioning Platform Release 16.1R1 you can:

    • Provision services across Juniper Networks devices and NEC’s iPASOLINK devices.
    • Provision the microwave links along with the quality of service (QoS) configurations on the iPASOLINK devices.

      For more information on provisioning QoS settings on an iPASOLINK device, see Configuring QoS Settings for iPASOLINK Devices.

    • Provision pseudowire and Layer 3 VPN services across Juniper Networks devices, and use iPASOLINK devices to deliver the services that span a wireless network.

      For more information on provisioning microwave links across Juniper Networks and iPASOLINK devices , see Creating a Cross Provisioning Platform Service Definition for iPASOLINK Devices and Creating a Cross Provisioning Platform Service Order for iPASOLINK Devices.

    Note: The following functions are part of the native CPP functionality, but are not supported for iPASOLINK devices:

    • Interface migration
    • Service resynchronization

    This feature has been tested on iPASOLINK 200, iPASOLINK 400, and iPASOLINK 1000 devices using schema version 1.0.12 and adaptor version 1.0.12.

  • The Cross Provisioning Platform allows you to perform service resynchronization to validate and merge selected services with the current configuration within the same devices or network.

    With Cross Provisioning Platform Release 16.1R1, you can resynchronize the configuration changes made:

    • Within the same Juniper Networks device or Nokia device
    • Within different Juniper Networks devices

    The information about migrated devices is obtained from the latest configuration of a device using virtual circuit identifier (VCID) and the IP address of the neighboring device.

    Note: This feature is supported only on LDP-based point-to-point services, deployed on Juniper Networks and Nokia devices. If the LDP-based point-to-point service is configured for a Layer 2 Ethernet device, Layer 2 Ethernet configurations are not validated.

  • If you want to replicate a service order that is successfully deployed, you need not create a new service order. Cross Provisioning Platform Release 16.1R1 allows you to re-create an existing service order whose order state is Completed.

    Note: The Recreate Service Order option is available for a service order whose order state is Completed only if the Order Type column displays ADD.

    If the Order Type column displays ADD, the output of the GUI script that you attached in the Creation field while creating a service definition is displayed.

  • In releases earlier than Cross Provisioning Platform Release 16.1R1, the Advance Detail tab of the CPP Service Details page displays only the output of the XSLT script.

    With Cross Provisioning Platform Release 16.1R1 you have an option to view and modify the output of the GUI script in the Advance Detail tab of the CPP Service Details page. To provide this flexibility, the Service Type inventory page is added.

    The Service Types inventory page displays table of predefined and customized Cross Provisional Platform service types. The Service Types page displays information in a table categorized by service type name, whether the service type is predefined or customized, creation date, and troubleshooting context path. To view more detailed information about the service type double-click the service type.

    You can perform the following actions on the Service Types inventory page:

    • Create Service Types—See Creating Service Types in Cross Provisioning Platform.
    • Modify Service Types—See Modifying a Service Type in Cross Provisioning Platform.
    • Delete Service Types—See Deleting a Service Type in Cross Provisioning Platform.

    The data that you have specified while you are creating a service type is stored in the database. This data is retrieved when you click an endpoint on the CPP Service Details > Advance Details tab. You can either view the output or modify the parameters.

  • Starting with Cross Provisioning Platform Release 16.1R1, you have an option to modify parameters before you deploy the services in bulk.

    To modify parameters before you deploy the services in bulk, while you are creating a service definition you must attach the script in which the isGUIRequired parameter is set to True.

    To modify parameters before you deploy the services in bulk:

    • On the Bulk Modify page, select the services or devices that you want to modify.

      Based on the script that you have attached, you have the following options:

      • Next—This option is available only if isGUIRequired is set to True in the script you have attached.
      • Deploy—This option is available only if isGUIRequired is set to False in the script you have attached.
    • Click Next to modify services in bulk.

      The Bulk Service Modify page appears.

    • Modify the parameters.

      Note: The script you have attached determines which parameters can be modified.

    • Click Deploy.

      The Job Details dialog box that appears contains the Job ID. You can click the Job ID link to view the status of the modified services on the Job Management page.

  • Starting with Cross Provisioning Platform Release 16.1R1, you can configure network-to-network interface (NNI) ports on a device. You can configure the NNI ports on Juniper Networks and Nokia devices.

    To configure the NNI port for Juniper Networks devices, a new option, Manage Device NNIs, is added to the Prestage Devices > Manage Device Roles page.

    For third-party devices, the NNI ports are automatically added during the device synchronization. A new column, isNNIPort, is added on the View Third Party Devices page. If a device has an NNI port, the isNNIPort value is true.

  • With Cross Provisioning Platform Release 16.1R1, the following action types are supported for point-to-point (E-Line) and multipoint-to-multipoint (E-LAN) Metro-Ethernet Forum (MEF) service operations:
    • createMefService
    • deactivateMefService
    • suspendMefService
    • modifyMefUni
    • statusMefService
    • activateMefService
    • deleteMefService
    • resumeMefService
    • modifyMefEvc
    • addUniToExistingMefService

      Note: This action type is not supported for E-Line service type.

    • removeUniFromExistingMefService

      Note: This action type is not supported for E-Line service type.

    • resumeUni

      Note: This action type is not supported for E-Line service type.

    • suspendUni

      Note: This action type is not supported for E-Line service type.

  • Starting with Cross Provisioning Platform Release 16.1R1, with the newly created helper functions you can validate route distinguisher and service ID values from the Nokia 5620 Service Aware Manager server. For information on newly added helper functions, see Helper Functions in Cross Provisioning Platform Release 16.1R1.
  • Starting with Cross Provisioning Platform Release 16.1R1, you can include the following API with in a script to retrieve the interface details along with the device ID and vendor type:

    http://<IP:PORT>/serviceui/resteasy/cpp-devices/{deviceId}/{vendorType}/interfaces?interfaceType&start=0&limit=5

  • For Cross Provisioning Platform Release 16.1R1, you must upgrade the Junos Space Network Management Platform to Release 16.1R1. For Junos Space Network Management Platform Release 16.1R1, CentOS 6.8 is used as the underlying OS of the Junos Space Platform software.

    To upgrade to Junos Space Platform Release 16.1R1, you must follow the procedure outlined in Upgrading to Junos Space Network Management Platform Release 16.1R1.

API Enhancements in Cross Provisioning Platform Release 16.1R1

Cross Provisioning Platform Release 16.1R1 includes the following API enhancements:

  • For modifying the CPP service definitions in bulk:
    • Deploy Bulk Modify Service (Version:2)
    • Deploy Bulk Modify Device (Version:2)
  • For service type:
    • Get Service Type By Id
    • Get All Service Type
    • Create Service Type
    • Modify Service Type
    • Delete Service Type

For more information about the APIs, go to https://Junos Space GUI IP Address/api/space/nsas/apihelp/, where you replace Junos Space GUI IP Address with the IP address of the system that is running the Junos Space application.

Note: You must install the API package to access the API Help files.

To install the API package:

  1. Install Cross Provisioning Platform Release 16.1R1.

    For more information on installing Cross Provisioning Platform Release 16.1R1, see Installation and Upgrade Instructions.

  2. Install NetworkAppsAPI Release 16.1R1.

Helper Functions in Cross Provisioning Platform Release 16.1R1

The following table lists the helper functions created in Cross Provisioning Platform Release 16.1R1:

Helper Function

Description

isValidRD (String Rd)

Based on the route distinguisher, this function validates the route distinguisher value from the Nokia 5620 Service Aware Manager server.

isValidServiceId (String serviceId)

Based on the service ID, this function validates the service ID value from the Nokia 5620 Service Aware Manager server.

isValidServiceIdandRd (String serviceId, String rd)

Based on the route distinguisher and service ID, this function validates the route distinguisher and service ID value from the Nokia 5620 Service Aware Manager server.

isValidResource (String key, String value)

Based on input parameters of the customer, this function retrieves the object’s full name from the Nokia 5620 Service Aware Manager server.

Supported Platforms for Cross Provisioning Platform Release 16.1R1

The following table lists the supported platforms and the corresponding qualified Junos OS release:

Supported Platforms

Qualified Junos OS Release

ACX Series Universal Access Routers:

  • ACX1000 router
  • ACX1100 router
  • ACX2000 router
  • ACX2100 router
  • ACX4000 router

Note: Only the Network Activate functionality is qualified for these platforms.

Release 12.3R1 through Release 12.3X54-D10 for ACX1000, ACX1100, ACX2000, ACX2100, and ACX4000 routers

MX Series 3D Universal Edge Routers

Release 12.2R1 through Release 14.2R4 for MX80, MX104, MX240, MX480, and MX960 routers

M Series Multiservice Edge Routers

Release 10.0 through Release 12.2R1.8 for M320 router

Release 10.0 through Release 14.2R4.12 for M7i and M10i routers

SRX Series Services Gateways

Note: Only the Network Activate functionality is qualified for this platform.

Release 12.1, Release 12.1X45, and Release 12.1X45 for SRX100, SRX110, SRX210, SRX240, SRX550, SRX650, and LN2600 devices

Release 12.1X46-D25 for SRX220 device

Installation and Upgrade Instructions

Prerequisites for Installing Cross Provisioning Platform Release 16.1R1

  • The devices must be running Junos Space Platform Release 16.1R1 before you install Cross Provisioning Platform Release 16.1R1.
  • You must uninstall the Network Activate application before you install the Cross Provisioning Platform application.

Note: If you have installed the Network Activate application, you cannot install the Cross Provisioning Platform application. Likewise, if you have installed the Cross Provisioning Platform application, you cannot install the Network Activate application.

A prescribed order is always required for the installation of Cross Provisioning Platform. Use the following table to determine the order required for the installation or upgrade:

Type of Upgrade or Installation

Order of Installation Required

New Installation Release 16.1R1

  1. Install Junos Space Platform Release 16.1R1.
  2. Install Junos Space Platform hot patch release 16.1R1-hotpatch-v1. See Installing Junos Space Platform Hot Patch Release 16.1R1-hotpatch-v1 for instructions on installing Junos Space Platform hot patch release 16.1R1-hotpatch-v1.
  3. Install Cross Provisioning Platform Release 16.1R1.
  4. Reboot the JBoss server.

Upgrade from Release 14.1R2 or Release 14.3R1 or Release 15.1R1

  1. Upgrade Junos Space Platform to Release 15.1R1.

    Note: If you are upgrading from Cross Provisioning Platform Release 15.1R1, you can skip this step.

  2. Before upgrading to Junos Space Platform 15.2R2, you must uninstall Red Hat Package Manager. You can use the uninstall_rpm.sh script to uninstall Red Hat Package Manager. For more information about the script, contact the Juniper Networks Technical Assistance Center.
  3. Upgrade Junos Space Platform to 15.2R2.4
  4. Before you reboot the JBoss server, you must install Red Hat Package Manager for the Cross Provisioning Platform application. You can use the install_rpm.sh script to install the Red Hat Package Managers. For more information about the script, contact the Juniper Networks Technical Assistance Center.
  5. Upgrade Junos Space Platform to Release 16.1R1.

    To upgrade to Junos Space Platform Release 16.1R1, you must follow the procedure outlined in Upgrading to Junos Space Network Management Platform Release 16.1R1.

  6. Reboot the JBoss server.
  7. Install Junos Space Platform hot patch release 16.1R1-hotpatch-v1. See Installing Junos Space Platform Hot Patch Release 16.1R1-hotpatch-v1 for instructions on installing Junos Space Platform hot patch release 16.1R1-hotpatch-v1.
  8. Reboot the JBoss server.
  9. Upgrade Cross Provisioning Platform to Release 16.1R1.
  10. Upgrade NetworkAppsAPI Release 16.1R1.

Uninstalling

  1. Uninstall NetworkAppsAPI Release 16.1R1.
  2. Uninstall Cross Provisioning Platform.

Installing Junos Space Platform Hot Patch Release 16.1R1-hotpatch-v1

To install Junos Space Platform hot patch for Release 16.1R1:

  1. Download the Junos Space Platform 16.1R1 Patch v1 (16.1R1-hotpatch-v1.tgz) patch to your local computer from the https://www.juniper.net/support/downloads/?p=space&rel=1489#sw location.
  2. Log in to the Junos Space active VIP node as the admin user.
  3. Create a temporary directory 16.1r1-hotpatch-v1 at var/tmp/.
    mkdir 16.1r1-hotpatch-v1 
  4. Navigate to the location on the node where you stored the patch.
  5. Extract the patch by using the following command:
    tar zxvf 16.1r1-hotpatch-v1.tgz 
  6. On all nodes, you must manually stop all services. Run the following commands:
    service jmp-watchdog stop
    service jboss stop
    service jboss-dc stop
  7. To install patch only from VIP node, run the following command:
    sh patchme.sh

    To install patch individually on all nodes, run the following command:

    sh patchme.sh LOCAL
  8. You are prompted to enter your password. Enter your CLI password.

    The JBoss server is rebooted automatically.

Known Issues

Cross Provisioning Platform Release 16.1R1 has the following known issue:

PR Number

Problem Description

PR-1244365

Even though you delete a device from Junos Space Platform, which has more service associated with it , the deleted device is not removed from the CPP Prestage table.

PR-1255707

For a VLAN_PATH service, in a single request if you try to delete an endpoint and add the same endpoint with the same entry number but different VLAN ID, the QoS information is not updated in the device.

PR-1255715

For a VLAN_PATH service, even though you can perform Configuration Audit successfully, the View Service Configuration window does not show the QoS information when you try to associate same VLAN ID and entry number to a different port in a single request.

Resolved Issues

There are no resolved issues in Junos Space Cross Provisioning Platform Release 16.1R1.

Modified: 2017-11-02