Status Audits - Avaya Definity SI Maintenance Manual

status audits

status audits
This command displays 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 uncover software errors. In
the field they help the switch to recover from data corruption before service is
interrupted.
This 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 that an audit ran and corrected an error
The number of times that an audit ran and detected an irreparable error
The number of times that an audit ran and aborted
The date and time that the audit first detected a problem (only for
cumulative)
The time of the most recent error detected by the audit (only for
cumulative).
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 peak-hour or clear audits cumulative commands.
NOTE:
Single process restarts, warm starts, cold 2 restarts, cold 1 restarts, or
processor interchanges do not clear this data.
Audits can execute directly using the "test MO" command (for example, test MO l
8192 p 512 t 0 executes the Station Connections Audits, audit lnames and
numbers (pnames) included in the Table Of Audits.) When the "test MO"
command executes an audit, report results display on the screen. In general,
errors discovered from a demand tests are not logged in the error logs. To be
consistent with other error logging, and to avoid confusion, errors that are
discovered from a demand test that executes an audit are not displayed.
The screen does not automatically update. It reflects the system at the time of the
request.
555-233-123 Issue 4 May 2002 8-303