Getting Started with Cross Provisioning Platform
Based on your network deployment requirements and configuration settings, you may require a service to be applied on devices in your topology. It is essential to discover or add the devices that you want to be administered using Cross Provisioning Platform (CPP) to the Junos Space Platform application database, before you can enable and define the service. The devices must be configured with the basic and mandatory device settings before the devices are discovered for additional modifications, such as the configuration of a service. These settings include routing instances, routing protocols, interfaces, and administrative groups.
The following workflow describes the tasks that you need to perform after the installation of CPP to enable effective and streamlined management, provisioning, and troubleshooting of devices and services configured using CPP.
Discover devices using the Cross Provisioning Platform GUI or the Junos Space Platform workspace. For instructions on discovering devices with CPP, see Discovering and Assigning All N-PE Devices. For instructions on discovering devices using the Junos Space Platform workspace, see Discovering Devices in the Junos Space Network Application Platform User Guide.
Before you can add a device to the Junos Space Platform database using device discovery, the following conditions must be met:
SSH v2 is enabled on the device. To enable SSH v2 on a device, issue the following CLI command:
set system services ssh protocol-version v2
The NETCONF protocol over SSH is enabled on the device. To enable the NETCONF protocol over SSH on a device, issue the following CLI command:
set system services netconf ssh
The device is configured with a static management IP address that is reachable from the Junos Space server. The IP address can be an in-band address or an out-of-band address.
A user with full administrative privileges is created on the device for the Junos Space administrator.
If you plan to use SNMP to probe devices as part of device discovery, ensure that SNMP is enabled on the device with appropriate read-only V1, V2C, or V3 credentials.
Discover the roles of devices and assign network-provider edge (N-PE) roles as necessary. To prestage devices and assign device roles, see Discovering Device Roles and Discovering and Assigning N-PE Devices with Exceptions.
Create service templates. Templates provide a powerful mechanism to configure advanced service-related options that are not exposed through the service order creation workflow. Templates are attached to a service definition. To work with service templates, see Service Templates Overview and Applying a Service Template to a Service Definition.
Review the predefined service definitions that are available by default and determine whether you want to create a new customized service definition. A service definition specifies the attributes that are common among a group of service orders that have similar service requirements. To work with service definitions, see Predefined Service Definitions and Creating a Cross Provisioning Platform Service Definition.
Create customers that denote the users to be associated with service orders. New customers must be identified to the system before you can provision and activate a service order for customers. To create customers, see Adding a New Customer.
Create service orders. A service order is an instance of the service definition that completes the definition for a specific customer’s use. To work with service orders, see Creating a Cross Provisioning Platform Service Order.
Deploy service orders to propagate the service configuration to the corresponding devices. To transfer service order configurations to devices and apply the settings on the devices, see Deploying a Service Order.
Perform audit operations, such as functional and configuration audit, to examine the status of interfaces, neighbor links, and endpoints. You can also identify whether the service configuration on the device has been changed out of band. In addition, you can use op scripts to perform any function available through remote procedure calls (RPCs) supported by either the Junos XML management protocol or the Junos XML API. See Performing a Functional Audit, Performing a Configuration Audit, and Troubleshooting N-PE Devices Before Provisioning a Service for further information.