Table of Contents
Viewing Reports
Viewing the System Info Report
Viewing the Event Report
Viewing Reports
Reports provide you with useful information about AUS; for example, you can view reports that show how busy AUS is, show if any errors have occurred, or that display information about devices that have contacted AUS.
These topics help you understand AUS reports:
Viewing the System Info Report
From the Reports tab, click the System Info Report option to display the System Info Report table. The table shows general information about AUS and also shows how busy the server is. The report contains information such as how many devices have contacted AUS and how many configuration files have been downloaded within the last 24 hours.
Click on a column name to sort the table by column information. You can also filter and search the table (Table 6-1).
Table 6-1 System Info Report
| Row |
Description |
|
Auto Update Server URL
|
URL that devices use to connect to AUS.
|
|
No. of Devices Managed
|
Number of devices in the AUS database.
|
|
No. of Devices Never Contacted AUS
|
Number of devices in the AUS database that have never contacted AUS.
|
|
No. of Files
|
Number of files in the AUS database.
|
|
No. of Assignments
|
Number of image to device assignments and device to image assignments.
|
|
Most Downloaded Config File
|
Configuration file that AUS downloaded most often during the last 24 hours.
|
|
No. of Unique Config Files Downloaded
|
Number of unique configuration files that AUS downloaded during the last 24 hours.
|
|
No. of Successful Config File Downloads
|
Number of configuration file downloads that did not complete successfully during last 24 hours.
|
|
No. of Failed Config File Downloads
|
Number of times an error occurred while a device was performing an Auto Update during the last 24 hours.
|
|
No. of Successful Auto Updates
|
Number of times that devices successfully contacted AUS during the last 24 hours.
|
|
No. of Failed Auto Updates
|
Number of times that devices did not contact AUS during the last 24 hours.
|
|
Device That Contacted Server Most
|
The device that contacted AUS most often during the last 24 hours.
|
|
No Bytes (Config) Downloaded
|
Number of bytes that have been downloaded for configuration files during the last 24 hours.
|
|
No. of New Assignments
|
Number of new image to device and device to image assignments during the last 24 hours.
|
Viewing the Event Report
From the Reports tab, click the Event Report option to display the Event Report table. The table shows information about devices that have contacted AUS. The table describes information such as the event type and result of the event. It also shows information about notifications sent from PIX Firewall devices to AUS. For example, if a PIX Firewall device downloads a configuration file and discovers errors, it sends an alert to AUS, which the table displays. Entries are added each time a device contacts AUS or a file is downloaded.
Click on a column name to sort the table by column information. When you click on the Device ID column, the table is sorted first by device ID, then by timestamp. You can also filter the table and search the table for a specified device ID (Table 6-2).
See Table 6-3 for descriptions of event types available from the Event Type list.
Table 6-2 Event Type Report
| Element |
Description |
|
Severity at or Higher list
|
The severity of the event.
Select the severity type from the list to filter the table according to severity. The table lists events at the specified severity plus all events that occurred at a higher severity.
|
|
Event Type list
|
Type of event that occurred.
Select the type from the list to filter the table according to event type.
See Table 6-3 for errors and their descriptions.
|
|
Device Filter field
|
Text field into which you enter the Device ID to search for within the table. The table is sorted first by Device ID, then by timestamp.
|
|
Go button
|
Begins a search for information entered into the Device Filter field.
|
|
Date list
|
The day on which the event occurred. You can see events that occurred during the past 7 days.
Select the date to filter the table according to the date on which the event occurred.
|
|
Device ID row
|
Name the device uses when identifying itself to AUS. May be different from hostname.
|
|
Event Type row
|
Type of event that occurred.
See Table 6-3 for events and their descriptions.
|
|
Severity row
|
Severity of the event.
|
|
Timestamp row
|
The time during which the event occurred.
|
|
Description row
|
Brief description of the event.
|
|
Rows per page list
|
Specifies the number of rows per page you want displayed.
|
Table 6-3 Event Type Descriptions
| Event Type |
Description |
|
All
|
Displays all errors.
|
|
CONNECT_SUCCESS
|
Device contacted AUS successfully and reported its inventory details.
|
|
CONNECT_FAILURE
|
A problem occurred during an auto update attempt. Possible causes are:
- Error while parsing XML
- Invalid credentials
- Device has not been added to AUS
- Connectivity problems
- Database down while trying to add record
|
|
DEVICE_CONFIG_ERROR
|
Errors reported to the server from the device or errors that occurred while loading the configuration file that is assigned to the device.
These errors should be used for debugging configuration problems.
|
|
GENERAL_DEVICE_ERROR
|
Non-configuration file error reported to AUS from the device. Possible causes are:
- Problems connecting to the Auto Update servlet
- Problems with the downloaded image (invalid checksum)
|
|
DOWNLOAD_SUCCESS
|
File was successfully sent to the remote device without error. This does not mean that the device is running the image successfully; this message could be followed by either DEVICE_CONFIG_ERROR or GENERAL_DEVICE_ERROR.
|
|
DOWNLOAD_FAILURE
|
An error occurred while an image or configuration file was being downloaded. Possible causes are:
- Invalid credentials.
- Communication problems.
- Database problem.
|
|
AUS_IMMEDIATE_SUCCESS
|
AUS successfully contacted and updated the device.
|
|
AUS_IMMEDIATE_FAILURE
|
An error occurred while the device was being updated. Possible causes are:
- The server does not have direct connectivity to the device (for example, it is behind a NAT boundary)
- The enable or TACACS username and password that the device uses to authenticate AUS are incorrect.
- An internal error occurred.
|
|
SYSTEM_ERROR
|
An internal error occurred.
|
