Viewing Configuration Audit Results of Recovered Services

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 [edit] 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.