Compliance Assessment Results
Table 1: Detailed Tab
Detailed Tab Column | Description |
|---|---|
Message | Displays information such as the general type of conformance match, mismatch, or partial match. If there is a mismatch, the line missing from the configuration is included in the Message. "not ordered" indicates that the lines are present in the configuration file but their ordering is not consistent with that of the template. "hardware type mismatch" indicates that the template type (Cisco IOS or Juniper JUNOS) does not match the configuration file type. |
Severity | There are five levels. Warning shows that compliance has failed for a given line, for example if a line is missing or failed to match. Info indicates a match or partial match. The user can also change these levels to be displayed as Minor, Major, or Critical. |
Hostname | Device hostname |
Config File | Displays the configuration file for which this entry applies. Double-clicking on a row will open this configuration file in the Main Pane. |
Block | The exact block of the configuration of the message |
Lines | Displays the corresponding start line and end line where the results entry applies. |
Template | Displays the template that was used for this compliance assessment |
Rule | Template Rule Name |
Template Lines | Range of Line numbers in which template rule occurs |
Template Line | For conform command, indicates the content of the line with violation |
Template Line # | For conform command, indicates the line number with violation |
Category | Template rule’s category (if specified) |
Vendor | Device vendor (e.g., Cisco, Juniper) |
OS | Device Operating System |
Version | Operating System Version, e.g., 12.2(53)SE |
Table 2: Summary By Device Tab
Summary By Device Column | Description |
|---|---|
Hostname | Device name converted into IP/MPLSView format |
Rules Applied | Number of template rules applied to the device |
Config Blocks Applied | Number of config blocks for which the rule was applied |
Issues | Number of issues |
Criticals | Number of critical issues |
Majors | Number of major issues |
Minors | Number of minor issues |
Warnings | Number of warnings |
Infos | Number of informational messages |
Score | Compliance score = 100 - (#criticals * 1/#rules * critical_weight) - (#majors * 1/#rules * major_weight) - (#minors * 1/#rules * minor_weight) - (#warnings * 1/#rules * warning_weight) - (#infos * 1/#rules * info_weight) |
Table 3: By Rule Tab
By Rule Column | Description |
|---|---|
File | Template Rule Name |
Rules Applied | Template File Name |
Routers Applied | Number of routers for which the rule was applied |
Config Blocks Applied | Number of config blocks for which the rule was applied |
Issues | Number of issues |
Criticals | Number of critical issues |
Majors | Number of major issues |
Minors | Number of minor issues |
Warnings | Number of warnings |
Infos | Number of informational messages |
Score | Compliance score = 100 - (#criticals * 1/#rules * critical_weight) - (#majors * 1/#rules * major_weight) - (#minors * 1/#rules * minor_weight) - (#warnings * 1/#rules * warning_weight) - (#infos * 1/#rules * info_weight) |
To save the contents in the results tab, select the Export to CSV icon in the toolbar to export to a CSV file, which can be opened in Microsoft Excel. Enter in a filename. Note that 3 CSV files will be created -- one for each tab.
- filename_result.csv -- Detailed tab
- filename_Result_NODE.csv -- Summary By Device tab
- filename_Result_RULE.csv. -- By Rule tab
