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.1R2 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.1R2

There are no new features in Cross Provisioning Platform Release 16.1R2.

API Enhancements in Cross Provisioning Platform Release 16.1R2

There are no new API enhancements in Cross Provisioning Platform Release 16.1R2.

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.1R2.

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

  2. Install NetworkAppsAPI Release 16.1R2.

Helper Functions in Cross Provisioning Platform Release 16.1R2

There are no new helper functions created in Cross Provisioning Platform Release 16.1R2.

Supported Platforms for Cross Provisioning Platform Release 16.1R2

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.1R2

  • The devices must be running Junos Space Platform Release 16.1R1 before you install Cross Provisioning Platform Release 16.1R2.
  • 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.1R2

  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.

    Note: You can skip this step if you prefer to install Cross Provisioning Platform Release 16.1R2, directly.

  4. Install or upgrade Cross Provisioning Platform Release 16.1R2.
  5. 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.

    Note: You can skip this step if you prefer to install Cross Provisioning Platform Release 16.1R2, directly.

  10. Upgrade Cross Provisioning Platform to Release 16.1R2.
  11. Upgrade NetworkAppsAPI Release 16.1R2.

Uninstalling

  1. Uninstall NetworkAppsAPI Release 16.1R2.
  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.1R2 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

The following issue is resolved in Cross Provisioning Platform Release 16.1R2:

PR Number

Problem Description

PR-1258542

If you run the Advanced Attribute API with in a script, only one record of Advanced Detail information is returned.

Starting with Cross Provisioning Platform Release 16.1R2, if you create multiple services with the same customer ID, device IDand interface name, the Advanced Attribute API retrieves multiple records of Advanced Detail information with pagination.

For example, you can include the following API in the script:

http://<IPAddress>/serviceui/resteasy/cpp-service
/advance-details/360793&Interface=ge-0/0/1
&ossCustomerId=1234&start=0&limit=2

Modified: 2017-11-02