Lucent Technologies 5ESS-2000, Инструкции по эксплуатации и техническому обслуживанию

Страница: 152 / 1421

older than these criteria.
5.14.3 USER PERSPECTIVES

When the audit is first deployed in an office, a default schedule will be automatically established to cause the
Full audit to run continuously. The user may enter an input message to reestablish the daily start/suspend
schedule of the Full audit. After the schedule is established, the audit runs indefinitely.

The Incremental audit is automatically scheduled for execution after each successful
BKUP:ODD
.

The user can enter input commands to inhibit the Full and Incremental audits. The user can also enter input
commands to re-allow these audits.

An input message is provided to request immediate execution of an Entity audit.

An input message is provided to determine the current status of the audits including the active and scheduled
audits, progress information, etc.

A summary message indicating how many errors were detected is provided after the conclusion of each audit
execution. Another input message is provided for printing the detailed error logs.

An input message is provided to stop any audit at any time while running.

An input message is provided to print the Full Audit's schedule.

An input message is provided to clear the schedule.

An input message is provided to remove all error logs generated from the previous cycle of both the Full and
Incremental audits. (This message should be used when the /rclog file system becomes low on space.)
5.14.4 RUNNING THE AUDIT
5.14.4.1 General
Refer to the 235-600-700/750, Input/Output Messages Manuals for complete descriptions of the input and output
messages used in this document.
There can be a maximum of 7 audits (1 Full, 1 Incremental and 5 Entity) running at any given time.
SODD audits the ODD on the backup disk along with the data in the log files. Note it does not audit the random
access memory (RAM) copy of the data. The Full and the Incremental audit primarily use the backed up copy of the
ODD with as little log file as is needed. The Entity audit on the other hand uses the backed up copy of the ODD with
as much log file as possible.
The view of the ODD that will be audited by the Full, Incremental, and Processor Entity audits is established after
each ODD backup. The view of the ODD that will be audited by the other Entity audits is established when the Entity
audit is requested; therefore, each Entity audit will have its own current view of the ODD. Note, however, that this
does NOT apply to the Processor Entity audit.
5.14.4.2 Full Audit
The Full audit can be scheduled to run any time of the day, and any day of the week. The default is to schedule it to
run continually; however, the schedule can be changed using an input command. Once the scheduled start time is
reached for that day, the Full audit automatically starts from where it left off on the previous run. (It will restart at the
235-105-210 October 1999
Copyright © 1999 Page 44