Validation Report Export Service
The Validation Report Export Service exports a subset of NetIM reports called validation reports. These exported validation reports can be used in analysis software to assist in determining network model completeness. See
Exported validation reports to learn more about the reports exported by the Validation Report Export Service.
You must run the Validation Report Export Service if you want to use the Model Completeness Report feature in analysis software.
This section includes the following topics:
Configuration properties for Validation Report Export Service
This section describes the properties for the Validation Report Export Service.
Many of the properties for the Validation Report Export Service are read-only. The only properties that you can configure are
• Output file directory
• Max number of timestamped archive subdirectories
The Validation Report Export Service properties are listed in the following table.
Service property | Description |
Report selection | This property is read-only. The set of reports included in the export is defined in the
report list > Troubleshooting property tree. |
report list > Troubleshooting | This property tree is read-only. The reports that are exported are described in
Exported validation reports. |
Output file directory | Points to the top level directory where exported validation reports are written. The default is <temp dir>\Reports_Validation. |
Export file format | This property is read-only. The file format for exported validation reports is csv. |
Max number of timestamped archive subdirectories | Controls the maximum number of subdirectories in the output file directory. When the “max number of timestamped archive subdirectories” is reached, the previously exported subfolders are overwritten, starting with the oldest. The default is 2. |
Exported validation reports
Validation reports are provided to assist in determining which CLI data contribute to device data in the NetIM database. The validation reports are also helpful in determining when data may be missing, resulting in an incorrect or incomplete topology.
The following validation reports are exported when you run the Validation Report Export Service:
Neighbors Not Found in Model
The Neighbors Not Found in Model Report provides a list of devices that are referenced as neighbor nodes in the neighbor discovery protocol (CDP, EDP, and so on) configuration of one or more devices in the NetIM database. When a neighbor device is missing, it may indicate that the network data is incomplete and/or the topology inferred by NetIM will not be fully connected.
Invalid Files
An invalid file does not contribute data to the NetIM database. The Invalid Files report provides a list of the invalid files for each CLI Data Import adapter for the most recent import cycle and the reason why the file was deemed invalid. Select the name of a file (shown in blue text in the “File Name” column) to open and examine that file in a file viewer.
Device File Archive Imports
The Device File Archive Imports report provides access to a list of the CLI data files that were successfully imported and contribute to the network data for each device in the NetIM database. When you open the report you are presented with a list of devices. When you select a node name (shown in blue text in the “Node Name” column), you open a detailed version of the report that provides information about the imported CLI data for this device.
The Device File Archive Imports indicates the following:
• If and when a certain type of data was imported for this device.
– CLI data types that are not listed in the Device File Archive Imports Detail report are not contributing to the device data in NetIM.
The age of device data.
– In other words the last time data was imported for this node and when it last refreshed. For each CLI data type, this can be deduced from the Last Full Import Iteration or the Most Recent Optimized Iteration column, whichever is later. For the entire device, this can be deduced from the Last Full Import Iteration or the Most Recent Optimized Iteration column across the entire report, whichever is later.
Unsupported Command Logs
The Unsupported Command Logs report provides access to the commands that were ignored by the CLI Data Import adapter when it imported a CLI data file (.cfg, .interface, .cdp, and so on).
The information in the file viewer is a list of the lines from the input file that do not contribute to the data in the NetIM database.
If there are commands in the unsupported commands log file that you believe would be useful to import and represent in the NetIM database, you can request that it be supported in a future version of NetIM by contacting technical support and providing the following: the device vendor, model, and operating system, the specific command that was ignored and an example file containing the command output.
Device Collection Configuration Discrepancies
The Device Collection Configuration Discrepancies report can be used to determine the following:
• Certain data defined in a device driver is not being collected
• Certain data defined in a device driver is collected but not imported
The Collection Recommended column is selected when collection is enabled by default for a device driver.
The Collection Enabled column indicates whether collection is currently enabled for that device driver.
The Corresponding Import Adapter Active column indicates whether the CLI Data import adapter for that data type is currently active in the adapter schedule.
If collection of a CLI data type is recommended for a particular device driver but it is not currently enabled, NetIM may be missing data that is needed to correctly represent devices that have been assigned that device driver. If collection is enabled, but the corresponding import adapter is not active, data is being collected but not imported. Again, NetIM may be missing data.