Viewing Configuration Audit Results
After performing a configuration audit, check the detailed results of the audit:
- From the View selector, select Service View. The workspaces that are applicable to routing and tunnel services are displayed.
- Click the Build icon in the Service View of the Connectivity Services Director banner. The functionalities that you can configure in this mode are displayed in the task pane.
- Click the plus sign (+) beside Connectivity to view services
based on protocols.
Expand the IP Services tree to select an IP Ethernet service.
Expand the E-Line Services tree to select an E-Line service.
Expand the E-LAN Services tree to select an E-LAN service.
- In the Network Services > Connectivity task
pane, select Service Provisioning > Audit/Results > Configuration Audit.
The configuration audit results are displayed if an audit operation was previously performed on the selected service.
Examine the audit results for missing configuration information, and keep the window open for later comparison with the service configuration in the Junos Space database.
You can validate policies for the hub and spoke (1 interface).
In the Service Configuration tab of the Configuration Audit dialog box, you can observe several lines with the delete statement in the service settings. These delete statements indicate the policy attributes that are deleted from the corresponding service on a device. Whenever a service is created or modified, the policy options are always deleted from the device to prevent the previously existing policies from interfering with the service. The presence of the delete statements is an expected behavior and does not indicate any incorrect service configuration.
- To view the service configuration in the Junos Space database,
in Deploy mode, from the Network Services > Connectivity task pane, select Service Provisioning > Deploy
Services. The Manage Service Deployment page is displayed on
the bottom part of the right pane. Select a service from the Manage Service Deployment page, then in the Actions menu, select View Service Configuration.
A new window opens and shows the service configuration.
If a CFM is configured in E-Line service or E-LAN service, the configuration audit result displays the CFM configuration details.
- Compare the contents of the Service Configuration with
those of the Configuration Audit Results window for each
device in turn. If you see discrepancies, then it is likely that the
service configuration was modified out-of-band. If so, you might need
to synchronize the device with the Junos Space database.
For step-by-step instructions about synchronizing devices, see Resynchronizing Managed Devices with the Network for details.
After the audit job is completed, you can view the output of the operation in the Configuration Audit Results window that is displayed on the right pane. The left pane displays a tree of devices associated with the specified service. You can select a Service-name > Interface-name Device-name in the left pane of the window. The attribute definitions and parameters defined in the service are displayed in the right pane. The right pane contains three tabs— Service Configuration, Template Configuration, and Audit Results. The Service Configuration tab displays the settings specified for the service on the device in CLI format. This tab displays the elements or components specified for a service template in the form of configuration stanzas and hierarchy levels. This display is similar to the show command that you can use at a certain  hierarchy level to view the defined settings. The Template Configuration tab displays the service attributes and options defined in the service template, if any, that is associated with the service. The Audit Results tab displays the status of the audit job that was run, such as whether the job succeeded or failed. You can also view the service definition and associated template details under the Service Config and Template Config tabs in Junos OS XML API format, instead of the CLI format.
Click the Show XML Config button at the top-right corner of the window to view the audit results in XML API format. Alternatively, click the Show Set button to view the audit results in the manner in which they are displayed in the Junos OS CLI interface. The Show XML/Set button is a toggle button.
The Junos OS command-line interface (CLI) and the Junos OS infrastructure communicate using XML. When you issue an operational mode command in the CLI, the CLI converts the command into XML format for processing. After processing, Junos OS returns the output in the form of an XML document, which the CLI converts back into a readable format for display. Remote client applications also use XML-based data encoding for operational and configuration requests on devices running Junos OS. The Junos XML API is an XML representation of Junos configuration statements and operational mode commands. It defines an XML equivalent for all statements in the Junos configuration hierarchy and many of the commands that you issue in CLI operational mode. Each operational mode command with a Junos XML counterpart maps to a request tag element and, if necessary, a response tag element.
Click Reload Result at the top-right corner of the window to refresh and display the results of the audit. When you click this button, only the output of the audit operation is displayed afresh and the audit job is not run again. You can refresh the results only for completed audit instances. When you select Service-name in the left pane of the window, service status information is displayed in the right pane. Click Run Configuration Audit after selecting the services you need to run the audit job again.
Configuration audit can be run for multiple services from Build mode of Service View of the Connectivity Services Director GUI. From the Manage Network Services page, select the check boxes beside multiple srvices, click the Audit button at the top of the table of configured services, and select Run Configuration Audit from the drop-down menu.
We recommend that you configure a script as a local script for effective and optimal debugging and analysis of the configuration settings contained in the script. The main advantage of a local script is that you need not download the script to a device (because a connection is established with the device by the GUI application and the script is run) and you need not remove the script from a device after you decommision a service.