status audits

Last Updated : Sep 03, 2020 |

Use status audits to see the results of Data Relation Audits that are built into the switch. Data Relation Audits check for inconsistencies between selected data items in the switch and report inconsistencies. Data Relation Audits are useful during development and testing phases of projects to discover software errors. On field, Data Relation Audits help the switch to recover from data corruption before the service is interrupted.

The status audits command displays the date and time that the requested interval begins, the number of times that the full sequence of audits executes (audit cycles), and status information about each audit that detected a problem or aborted during the interval. The status information contains:

  • The name of the audit.

  • The number of times an audit ran and corrected an error.

  • The number of times an audit ran and detected an irreparable error.

  • The number of times an audit ran and aborted.

  • For cumulative: The date and time that the audit first detected a problem.

  • For cumulative: The time of the most recent error detected by the audit.

Audit data information cumulates from the last reboot or the last clear audits cumulative command, and for peak hours since the last reboot or the last clear audits command.

The status audits screen does not automatically update, but reflects the system at the time of request.

Syntax

status audits [cumulative] [peak-hour]
cumulative

The data collected for the peak hour since the last reboot or the last time the clear audits command was run.

peak-hour
The data collected since the last reboot or the last time the clear audits command was run.

status audits field descriptions

Field

Descriptions

Start Date

  • For cumulative: The date and time of the last reboot or the last time the clear audits cumulative command was run.

  • For peak-hour: The date and time of the beginning of the peak hour since the last reboot or when the last clear audits command is run.

# of Audit Cycles Completed

The number of audit cycles completed in the specified interval (0–999999). Asterisks indicate numbers that exceed 999999. The switch executes audits in a set order. After all audits are executed, the switch restarts the sequence. Individual audit values can be larger if the switch is partially through another audit cycle. Audit cycle numbers do not apply to these audits that execute as part of scheduled maintenance.

Audit Name

The audit name that detected an error or aborted. A few audits do not run in the normal audit sequence. Instead, they execute as part of scheduled maintenance and are marked with “(SCH)” following the audit name.

# Cycles Fixed Data

The number of times the audit was run in a specified interval and found a fixable problem. Asterisks are used from numbers that exceed 65534.

# Cycles Could Not Fix Data

The number of times the audit was run in a specified interval and found a problem that could not be fixed. The audited switch data is inconsistent when this happens. Asterisks are used for numbers that exceed 65534.

# Cycles Audit Aborted

The number of times that the audit was run in a specified interval and aborted due to an internal error. Asterisks are for numbers that exceed 65534.

First Error

The date and time when the audit first detected fixed data, could not fix data, or aborted problems since the last clear audits cumulative command.

Most Recent Error

The date and time when the audit last detected fixed data, could not fix data, or aborted problems since the last clear audits cumulative command.