Service Troubleshooting Overview
Common reasons for the failure of a service are that a PE device configured for that service is down, or that device has had its service configuration changed so that it no longer matches the service configuration in the Junos Space database.
The primary tools in the Junos Space product for troubleshooting service problems are:
- Functional audit
- Configuration audit
- Job manager
Overview information is provided here. For step-by-step instructions on recommended troubleshooting procedures, see Troubleshooting Service Problems.
Functional Audit
A functional audit can help you determine whether a device is down.
A functional audit checks the control plane only. It does not check the data plane. It checks for connectivity by running and analyzing the output of the following commands:
- For point-to-point services:
show l2circuit connections - For multipoint services:
show vpls connections
You can view the results of a functional audit from the Manage Services inventory screen.
Configuration Audit
A configuration audit can help you determine whether the service configuration on the device has been changed out of band. To this end, you can compare the results of a configuration audit with the service configuration in the Junos Space database. The following example shows a sample comparison:

You can view the results of a configuration audit from the Manage Services inventory screen. You can view the service configuration in the Junos Space database from the service instance details screen for a specific service.
Job Manager
In the Job manager, use the Summary column to obtain information about failed deployments and failed audits. For deployments in general, the Summary column contains useful service information such as the VC ID and endpoint information. For some failed deployments, this column also contains information about why the deployment failed. An example of a failed deployment in the Job manager follows:

For details on using the Job manager, see Viewing Scheduled Jobs.

