Lucent Technologies lucent ユーザーズマニュアル
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Commands and Trouble-Clearing Aids
Page 8-221
status audits
8
Field descriptions
Start Date
Date and time that interval begins. “cumulative” = date
and time of the last reboot or execution of the “clear
audits cumulative” command.
“peak-hour” = date and time of the beginning of the peak
hour since the last reboot or execution of a “clear audits
cumulative” or “clear audits peak-hour” command.
and time of the last reboot or execution of the “clear
audits cumulative” command.
“peak-hour” = date and time of the beginning of the peak
hour since the last reboot or execution of a “clear audits
cumulative” or “clear audits peak-hour” command.
# of Audit Cycles Completed
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 execute, the switch restarts the
sequence.
interval. (0 – 999999) Asterisks indicate numbers that
exceed 999999. The switch executes audits in a set
order. After all audits execute, the switch restarts the
sequence.
NOTE:
Since this field shows the number of completed
audit cycles, it is possible that individual audit
values, can be larger than the values described
below (if the switch is partially through another
audit cycle.) Audit Cycles numbers do not apply to
these audits that execute as part of scheduled
maintenance.
Since this field shows the number of completed
audit cycles, it is possible that individual audit
values, can be larger than the values described
below (if the switch is partially through another
audit cycle.) Audit Cycles numbers do not apply to
these audits that execute as part of scheduled
maintenance.
Audit Name
Audit’s 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.
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
Number of times that the audit ran, in the specified
interval, and found a fixable problem. (0–65534)
Asterisks are used form numbers that exceed 65534.
interval, and found a fixable problem. (0–65534)
Asterisks are used form numbers that exceed 65534.
# Cycles Could Not Fix Data
Number of times that the audit ran, in the specified
interval, and found an unfixable problem. The audited
switch data is inconsistent when this happens. (0–65534)
Asterisks are used for numbers that exceed 65534.
interval, and found an unfixable problem. The audited
switch data is inconsistent when this happens. (0–65534)
Asterisks are used for numbers that exceed 65534.
# Cycles Audit Aborted
Number of times that the audit ran, in the specified
interval, and aborted due to an internal error. (0–65534)
Asterisks are for numbers that exceed 65534.
interval, and aborted due to an internal error. (0–65534)
Asterisks are for numbers that exceed 65534.
First Error
Date and time that the audit first detected fixed data,
could not fix data or audit aborted problems since the
last “clear audits cumulative” command. Format:
MM:DD:hh:mm (for example, 03/27/14:31 for 2:31 pm,
March 27th).
could not fix data or audit aborted problems since the
last “clear audits cumulative” command. Format:
MM:DD:hh:mm (for example, 03/27/14:31 for 2:31 pm,
March 27th).
This field appears with the "status audits
cumulative" display.