Table of Contents
Integrity Checks Report
The Integrity Checks report contains the results of syntactical and global semantic checking performed on the Cisco router configuration files used to create the current baseline.
To view the Integrity Checks report that was generated when the baseline was opened, choose the Reports tab in the navigation panel (left pane) of the Cisco Netsys Baseliner software's main window, expand the Reports list, and click the Integrity Checks entry. The Integrity Checks report will be displayed in the right panel of the window. (If you have edited your configuration files while using the Cisco Netsys Baseliner software, you should reopen the baseline in order to check the syntax of your edits.)
You can also generate a subsidiary report, the Integrity Checks Summary, which summarizes the violations listed in the Integrity Checks report. This summary tells how many violations of each kind, and how many of each specific violation within a particular group, were found.
See the appendix "Baseline Integrity Checks" for a definition of each of the checks performed on the router configuration files.
Figure 6-1: Integrity Checks Report
The Integrity Checks report contains a list of all of the problems that were found within your baseline's configuration files at the time the baseline was opened. The report is displayed in the right panel of the main window of the Cisco Netsys Baseliner software when the Integrity Checks item is selected in the navigation panel.
Initially, the entries displayed in this panel are sorted by severity, with high severity problems listed first. Click on a specific column header to sort the list of problems according to that column's contents.
This window also provides you with:
- a summary and total count of the problems found in the baseline router configuration files via the Summary Report button.
- access to detailed descriptions of each integrity check via the Explanation button.
- ability to highlight the device icons in all currently displayed topology windows.
The controls available while the Integrity Checks report is displayed are:
The name of the report is displayed in bold across the top of the display panel.
Displays the section of online help about the Integrity Checks report, in your default browser. Online help is an HTML version of the printed reference guide.
This button, adjacent to the report title, remains dimmed and unavailable while the Integrity Checks report is displayed. It becomes activated when you click the Summary Report button to display the Integrity Checks Summary report. The Parent button is used to return to the Integrity Checks report (the parent of the summary report).
This window lists in a spreadsheet-like grid the problems that were detected in your baseline router configuration files. Each entry provides the following information:
- the name of the primary router whose router configuration file contained the problem
- the name of the secondary router (when applicable) affected by the problem
- the protocol violated (such as IP, IPX, SRB, APPLE, DECnet, or VINES)
- the problem's severity (high, warning, or user related errors/warnings)
- the type of problem that was detected
When the Integrity Checks report is initially displayed, the report entries are sorted by severity (followed by warning, followed by configuration file warnings/errors.) You can click on a column header in the Results pane to sort the information displayed in the report according to the contents of that column. For example, when you click on the Primary Device column header, the information displayed in the Results pane is sorted by the primary device names.
The results grid is divided into the following columns:
- Primary Device---the name of the primary router associated with this problem.
- Secondary Device---the name of the secondary router (when applicable) associated this problem. This column has an entry only when the problem corresponds to two routers.
- Protocol---the protocol (IP, IPX, APPLE, SRB, DECnet, VINES) this problem is related to.
- Severity---the problem's severity:
- High severity problems are thought to cause major network problems and should be fixed as soon as possible.
- Warning problems are considered significant, but not severe to your network's health. Network performance is not likely to be completely halted by the existence of these problems. However, they could cause inadvertent side effects and performance degradation.
- User Warning problems indicate router configuration file entries considered to be unusual and which, if done inadvertently, might cause a problem.
- Problem Type---A brief synopsis of the problem (a more complete description of the problem is displayed in the Detail pane).
The Filter field immediately beneath the Results Grid allows you to specify search words or character strings, to filter the reports so that only a subset of entries is displayed. Use an asterisk (*) as a separator of indefinite length between character strings. The search mechanism will locate those reports which contain the search strings, in the order specified. For example, if you enter SRB*high in the Filter field and press Enter, the report will display only those devices with SRB and high somewhere in their data fields, in that order. The search mechanism is not case sensitive (srb and SRB are considered to be the same).
Adjacent to the Filter field, a status report shows how many items are displayed, how many were filtered out of the display, and how many are represented in your baseline.
When you select an entry in the Results grid, the Details panel describes the problem at greater length than can be shown in the Problem Type column.
You click on this button to view the Integrity Checks Summary report, a summary and total count of the problems discovered when the baseline was opened. For more information about the Integrity Checks Summary report, see the section "Integrity Checks Summary Report" elsewhere in this chapter.
When you click on a listing in the Results grid, the Highlight Primary button becomes active. When you click on this button, the icon of the router in the Primary Device column of the selected row is highlighted in all currently displayed topology windows.
When you click on a listing in the Results grid and there is a secondary device listed, the Highlight Secondary button becomes active. When you click on this button, the icon of the router in the Secondary Device column of the selected row is highlighted in all currently displayed topology windows.
A highlighted icon has a thick, yellow (default color) box drawn around it. Highlighted icons are easier to identify in the topology window.
Click on this button to obtain a detailed explanation of why the currently selected entry (highlighted in the Results grid) was added to the Integrity Check report. The explanation text also tells you how many times this particular integrity violation occurs in your baseline, and when pertinent to a particular message the number of other elements in the baseline. (For example, the explanation of the (Sub)Net Mask Creates Hostid of Zero IP check also tells you how many router interfaces, and how many interface IP addresses, are in all of the configuration files of your baseline. The message for the Undefined Access List Referenced check tells the total number of IP Access Lists defined by your baseline's configuration files in addition to the total number of this kind of violation).
See the appendix "Baseline Integrity Checks" for a list of all of the integrity checks performed by the Cisco Netsys Baseliner software, and the text of the explanations given for each.
The Integrity Checks Summary report is displayed in the right panel of the main window when you click on the Summary Reports button in the Integrity Checks report. This summary report tells you at a glance how many of each kind of problem was detected in the router configuration files during the generation of the Integrity Checks report.
The components of this window are as follows:
The name of the report is displayed in bold across the top of the display panel.
Displays the section of online help about the Integrity Checks Summary report, in your default browser. Online help is an HTML version of the printed reference guide.
Click the Parent button, adjacent to the report title, to redisplay the Integrity Checks report.
This pane provides a list of the problems detected in your baseline router configuration files when the Integrity Checks report was generated. The problems are categorized by protocol (IP, IPX, SRB, APPLE, DECnet, and VINES), severity (High, followed by Warning, followed by configuration file warnings/errors), major problem type (Access List, IP Address/Mask/Network Class, or Address Mismatch: IPX Out of Sync), and specific problem type (such as Access List: Undefined, or Interface: Bad IP Address/Mask).
Figure 6-2: Integrity Checks Summary Report Window
For example, the first entry shown informs you that three IP-specific, high priority IP Address/Mask/Network Class type problems were detected in the baseline router configuration files. These three problems were then further categorized as one each of:
- Interface: (Sub)Net Mask Creates Hostid of Zero
- Interface: NonContiguous IP Mask
- Interface: Bad IP Address/Mask
See the appendix "Baseline Integrity Checks" for a listing of the major problem types and their associated specific problem types. The problem types are categorized by protocol and severity.
The text in the Results pane is divided under the following column headings:
- Protocol---the protocol (IP, IPX, APPLE, SRB, DECnet, VINES) this problem is related to is displayed in this column.
- Severity---the problem's severity:
- High---thought to cause major network problems and should be fixed as soon as possible.
- Warning---problems are considered significant, but not severe to your network's health. Network performance is not likely to be completely halted. However, they could cause inadvertent side effects and performance degradation.
- User Warning---router configuration file entries are considered to be unusual and might cause a problem (though what the software detects as unusual may have actually been done intentionally).
- Problem Type---major problem types, categorized by protocol and severity (for details about this column's contents, see the section, "Problem Types"), are displayed in this column. When multiple problems exist within a major problem type category, the specific problem types are indented under the major problem type category.
- Count---the number of problems within each major problem category and specific problem type categories.
The Filter field immediately beneath the Results Grid allows you to specify search words or character strings, to filter the reports so that only a subset of entries is displayed. Use an asterisk (*) as a separator of indefinite length between character strings. The search mechanism will locate those reports which contain the search strings, in the order specified. For example, if you enter SRB*high in the Filter field and press Enter, the report will display only those devices with SRB and high somewhere in their data fields, in that order. The search mechanism is not case sensitive (srb and SRB are considered to be the same).
Adjacent to the Filter field, a status report shows how many items are displayed, how many were filtered out of the display, and how many are represented in your baseline.
When you click the Find in Detail button, the parent Integrity Checks report will be redisplayed. The first instance of the line that was highlighted in the summary will now be highlighted in the parent (or detail) report. Some rows in the summary report represent categories of problems (which do not appear in the detail report), with nested entries representing the actual problems. The Find in Detail button will remain disabled when the selected row identifies a category rather than a specific problem.
Click the Explanation button for a detailed explanation of the problem in the highlighted row. If this button is disabled, there is no explanation available for the selected row.
The Problem Types column in the Results grid if the Integrity Check Summary report shows the major problem types, categorized by protocol and severity (as shown below). when multiple problems exist within a category (bulleted items), the specific problem types are indented under the major problem type category in the Results grid.
- Access List Problems
- Bad Masking in Access List (high severity)
- Non-utilized Rule in Access List (high severity or warning level)
- Undefined Access List Referenced (high severity)
- Dialer: Unbalanced Map Command
- Unbalanced Dialer Mapping (high severity)
- Dialer: Unknown Address in Map Command
- Unknown Address in Dialer Mapping (warning level)
- Frame-Relay: Unbalanced Map Command
- Unbalanced Frame-Relay Mapping (high severity)
- Frame-Relay: Unknown Address in Map Command
- Unknown Address in Frame-Relay Mapping (warning level)
- IP Address/Mask/Network Class Problems
- Bad Address/Mask on Router Interface (high severity)
- Bad Default Network Specification (warning level)
- Bad Network Address Specified in Routing Process (warning level)
- Bad Target in Static Route Definition (warning level)
- Noncontiguous Mask on Router Interface (high severity)
- (Sub)Net Mask Creates Hostid of Zero (high severity)
- ISIS: Duplicate System IDs
- ISIS Duplicate System IDs Found (high severity)
- IP Subnet Zero with Classful Protocol
- IP Subnet Zero Configured with Classful Protocol (warning level)
- Mismatch: Encapsulation
- Encapsulation Mismatch Among Connected Interfaces (high severity)
- Mismatch: IGRP/EIGRP Bandwidth/Delay Metric
- IGRP/EIGRP Metric Mismatch Between Connected Interfaces (warning level)
- Mismatch: ISIS Hello Interval
- ISIS Hello Interval Mismatch Between Connected Interfaces (warning level)
- Mismatch: ISIS Link State Metric
- ISIS Link State Metric Mismatch Between Connected Interfaces (warning level)
- Mismatch: MTU
- MTU Mismatch Among Connected Interfaces (high severity)
- Mismatch: OSPF Hello Interval
- OSPF Hello Interval Mismatch Between Connected Interfaces (high severity)
- Mismatch: OSPF Interface Costs
- OSPF Metric Cost Mismatch Between Connected Interfaces (warning level)
- Mismatch: TCP Header Compression
- Mismatched TCP Header Compression (warning level)
- Overlapping IP Subnets
- Overlapping IP Subnets Check (high severity)
- Possible Performance Enhancements
- Fast Switching Low Speed Serial Interface (warning level)
- Missed Opportunity for a Passive Interface (warning level)
- Opportunity for Autonomous/Optimum/Flow Switching (warning level)
- Potential Routing Table Update Problems
- Addresses of an Interface in Different OSPF Areas (high severity)
- Connected IP (Sub)Net not Advertised by RIP/IGRP/EIGRP/OSPF/BGP/Static (warning level)
- IBGP Neighbors Not Fully Meshed (high severity)
- Indirectly Connected EBGP Neighbor (high severity)
- Network Timers Mismatch Among Connected Routers (warning level)
- OSPF Area Does Not Border Area Zero (high severity)
- Primary and Secondary Addresses Map to Same Subnet (warning level)
- Redistribution: Metric Value Missing Where No Default (warning level)
- Subnet Not Consistently Assigned to an OSPF Area (high severity)
- Unbalanced BGP Neighbors (high severity)
- Unconnected Net in network Command of RIP/IGRP/EIGRP (warning level)
- Undefined Route-Map (high severity)
- Unguaranteed BGP Network Origination (warning level)
- Unknown BGP Neighbor (warning level)
- Unthrottled Redistribution of Routes (high severity or warning level)
- Unused distance Command (warning level)
- Unused EIGRP summary-address Command (warning level)
- Unused OSPF area range Command (warning level)
- Unused OSPF network area Command (warning level)
- Unused OSPF summary-address Command (warning level)
- Useless BGP Network Origination (warning level)
- Redundant Addresses Assigned to Router Interfaces
- Duplicate Address Check (high severity)
- SMDS: Unbalanced Static Map
- Unbalanced SMDS Static-Mapping (high severity)
- SMDS: Unknown Address in Static Map
- Unknown SMDS Address in Mapping (high severity or warning level)
- Static Route Problems
- Static Route Next Hop is Indirectly Connected (warning level)
- Static Route Next Hop is a Shutdown Interface (high severity)
- Static Route Next Hop is an Unresolved Address (warning level)
- X25: Unbalanced Map Command
- Unbalanced X25 Mapping (high severity)
- X25: Unknown Address in Map Command
- Unknown Address in X25 Mapping (high severity or warning level)
- Access List Problems
- Non-utilized Rule in Access List (high severity or warning level)
- Undefined Access List Referenced (high severity)
- Address Mismatch: IPX Out of Sync
- IPX Logical Topology Out of Sync (high severity)
- Mismatch: IPX Network Encapsulation
- IPX Network Encapsulation Mismatch (high severity)
- Mismatch: IPX Delay
- IPX Delay Mismatch Amongst Connected Interfaces (warning level)
- Mismatch: IPX SAP Interval
- IPX SAP Update Interval Mismatch Amongst Connected Interfaces (warning level)
- Mismatch: IPX Update Time
- IPX Update Interval Mismatch Amongst Connected Interfaces (warning level)
- Redundant Addresses Assigned to Router Interfaces
- Duplicate Address Check (high severity)
- Same IPX Network Restriction
- Same IPX Net Restriction (high severity)
- Source-Route Bridging Remote Peer Problems
- Local SRB Peer Definition Problem (high severity)
- Multiple SRB Remote Peer References to a Router (high severity)
- Referenced Remote Peer Not the Local Peer (high severity)
- SRB Remote Peers Encapsulation Mismatch (high severity)
- Unbalanced SRB Remote Peers (high severity)
- Unresolved DLSw Local Peer Address Referenced (high severity)
- Unresolved DLSw Remote Peer Address Referenced (warning level)
- Unresolved SRB Remote Peer Address Referenced (warning level)
- STUN Problems
- STUN Needs Local Peername (high severity)
- STUN Route Does Not Reference STUN Peername (high severity)
- STUN Route References Unknown Address (warning level)
- Mismatch: Token Ring Speeds
- Ring Speed Mismatch Between Connected Interfaces (high severity)
- Mismatch: Ring Numbering Out of Sync
- Ring Numbering Causes Addressing Inconsistencies (high severity)
- Address Mismatch: AppleTalk Out of Sync
- AppleTalk Logical Topology Out of Sync (high severity)
- AppleTalk Zone Misconfiguration (high severity)
- Overlapping AppleTalk Cable Ranges (high severity)
- Redundant Addresses Assigned to Router Interfaces
- Duplicate Address Check (warning level)
- Mismatch: DECnet Cost
- DECnet Cost Mismatch Amongst Connected Interfaces (high severity)
- Redundant Addresses Assigned to Router Interfaces
- Duplicate Address Check (high severity)
- Mismatch: Vines Metric
- VINES Metric Mismatch Amongst Connected Interfaces (high severity)
- Mismatch: Vines Serverless
- VINES Serverless Mismatch Amongst Connected Interfaces (high severity)
Posted: Tue Apr 27 11:55:43 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.
