Troubleshooting Services in Cross Provisioning Platform
The troubleshooting feature provides an easy and unique way to troubleshoot the services in Cross Provisioning Platform. You do not have to manually login to a device to check the status of services in the Cross Provisioning Platform application, but you can do the same using the functionality of operational scripts and CLI configlet scripts. You do have the flexibility of writing your own scripts to view the results.
Only Juniper Networks devices are supported by this functionality and this is not applicable to the third-party devices.
The operational scripts and the CLI configlet scripts need to be created or imported to the platform from the local machine before you start troubleshooting the services in the Cross Provisioning Platform application.
The following table lists the context in which the OP scripts and CLI configlets are written for different types of services:
Table 1: OP Scripts and CLI Configlets Contexts for Different Service Types
@CONTEXT = "/device/configuration/protocols/l2circuit/neighbor/interface"
Example : /device[name="MX80-NGCE-1"]/configuration/protocols/l2circuit/neighbor[name="188.8.131.52"]/interface[name="ge-0/1/5.784"]
/*@CONTEXT = "/device/configuration/routing-instances/instance/interface" */
Example : /device[name="kochin"]/configuration/routing-instances/instance[name="SO62441630" and instance-type="vrf"]/interface[name="ge-0/1/3.934"]
/* @CONTEXT = "/device/configuration/routing-instances/instance/interface" */
Example : /device[name="kochin"]/configuration/routing-instances/instance[name="SO62441630" and instance-type="vpls"]/interface[name="ge-0/1/3.945"]
P2P or L3VPN with L2E
/* @CONTEXT = "/device/configuration/protocols/connections/interface-switch/interface" */ Example: /device[name="MX80-1"]/configuration/protocols/connections/interface-switch/interface[name="ge-1/0/0.1801"]
P2P (Local switching)
/* @CONTEXT = "/device/configuration/protocols/l2circuit/local-switching/interface/end-interface" */ Example /device[name="MX80-1"]/configuration/protocols/l2circuit/local-switching/interface[name="ge-1/0/0.1801"]/end-interface[interface="ge-1/2/2.1881"]
NPS (Network peering)
/* @CONTEXT = "/device/configuration/protocols/bgp/group" */ Example /device[name="MX80-1"]/configuration/protocols/bgp/group[type="external"]
The following are the options to troubleshoot the services in the Cross Provisioning Platform application:
Troubleshooting Cross Provisioning Platform Services Using Operational Scripts
The operational scripts or the OP scripts are written to view the statistics of a service in the Cross Provisioning Platform application. All the commands in the OP scripts are user-defined. To view the contexts for writing OP scripts for different service types, refer Table 1.
To execute the OP scripts and view the status of any service:
From the Network Management Platform task pane, select Images and Scripts > Scripts.
The Scripts page that appears displays a list of the existing scripts.
From the list of the scripts available in the SLAX format, right-click a script and click Stage Scripts on Devices to push the script onto a device.
The Stage Scripts on Device(s) page that appears displays a list of the devices associated with the script that you selected.
Select the Select Device Manually option and select any number of devices to which you want to push the script.
The Enable Scripts on Devices check box is selected by default.
Click Stage to stage the script on all the devices that you selected.
The Stage Scripts Information dialog box confirms the successful staging of scripts onto the selected devices along with the Job ID.
Click Job ID to view the status of the job on the Job Management page.
You are redirected to the Scripts page.
From the Cross Provisioning Platform task pane, select CPP > Services.
The Services page that appears displays a list of the services in Cross Provisioning Platform.
Double-click any service.
The CPP Services Details page that appears displays a list of the devices associated with the service you selected.
You can view the advanced details of any device in the Advanced Details For Device section by clicking the device from the list.
Right-click any device from the list and select the Execute OP Scripts option.
Select an OP script on the Execute OP Scripts page.
Click the Value column to enter any additional parameter for the selected OP script, besides the ones coded in the script.
The selection of parameters is entirely dependent on the OP scripts. If the OP scripts support parameters, then all the parameters are listed and you need to enter the values. Parameters can be optional, on the basis of the OP scripts.
Click Execute to execute the selected OP scripts with the newly added parameters, if any.
A dialog box confirms the execution of the OP scripts along with the Job ID.
You are redirected to the Execute OP Scripts page.
Click View Last Result to view the previous OP scripts execution results.
This is an optional step.
Troubleshooting Cross Provisioning Platform Services Using CLI Configlet Scripts
The CLI configlet scripts are written to set the user-defined configuration to a device in which the cross provisioning platform services are installed. The commands in the CLI configlet scripts are user-defined. To view the contexts for writing CLI configlet scripts for different service types, refer Table 1. For more information on applying CLI configlet to devices, see Junos Space Network Management Platform User Guide.
The process of providing troubleshooting support to Cross Provisioning Platform services using the CLI configlet scripts is similar to that of the operational scripts. To execute the CLI configlet script and set the configuration to any device:
From the Cross Provisioning Platform task pane, select CPP > Services to view the CPP Service Details page.
The CPP Service Details page appears.
Right-click any device and select the Execute CLI Configlet option.
The Apply CLI Configlet page appears.
Select the Select Device Manually option.
Select the devices onto which you need to apply the CLI configlet script.
Enter the required parameters in the Value column, besides the ones coded in the CLI configlet script.
A preview of the CLI configlet script is shown.
Click Validate to validate the CLI configlet script.
The Validation Result page appears showing the status of the validation.