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

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

CONTEXT for Error 1:
<current_pcr=1>
<annc_hdr=<ANNC_HDR:processor=1:appl=FCOSPS_DA hdr_id=7656>>
<nappl=OSPSDA>
<hdr_id=7656>
<phrase1=12043>
When the audits run, they create an error log file in the switch that is in binary format and is unreadable. An input
command is provided to read this file and produce readable error messages. The command sends the output to a
user-specified file, which is created under the /rclog/SODD/reports directory. The user can also request a summary
message which gives the number of errors that the audit identified. This summary message is sent to the read-only
printer (ROP). A detailed summary can also be requested by the user. The output is sent to a user-specified file
under the /rclog/SODD/reports directory.
5.14.7.2 Errors vs. Warnings
All assertions in the PRL are provided with a label. A large majority of the cases will have a label with format "_xx",
where xx is a number. This number signifies the assertion number in that population rule file (that is, _39 implies
that it is the 39th assertion in that file). There are a few exceptions to this format. All labels that start with "M" (for
example, Mann8a) signify they have a custom message. All labels that start with "R" or "O" signify they are
Warnings and not Errors.
There are primarily two levels of inconsistencies that are detected by the audits:

Errors which are inconsistencies in the Static Data with respect to the population rules. These need to be
analyzed and corrected.

Warnings which are inconsistencies in the Static Data with respect to the population rules but are due to some
special circumstances. (These are similar to the current ODA warning messages). Some of these
circumstances are as follows:

Hardware growth

Checks applicable to new starts only

RC not enforcing some constraints due to performance limitations.
All audits check for both error and warning inconsistencies in the ODD, however, the user has some control over
how the errors and warnings are treated when printing or counting the number of errors found by the audit. By
default, both errors and warnings are printed/counted when the
OP:AUD-SODD,ERRLOG
command is issued to
either decode an audit's error log or count the number of errors found by the audit.
Further control exists over how warnings are treated. If a PRL check is considered a warning because RC/V or ODA
does not enforce it, the check will contain a label on the line of PRL that is not being enforced. Within the first three
characters of the label, it will contain an 'O' (if ODA is not enforcing the check) or 'R' (if RC/V is not enforcing the
check). If the user has PRL warnings that need special treatment, an ASCII file can be created called
/rclog/SODD/prl_to_ignore in which the warnings that are to be treated differently are specified. The warnings can
be customized on a switch-by-switch basis as follows:
(1) Ignore a specific warning in a specific relation.
(2) Ignore all warnings pertaining to a specified relation.
(3) Ignore all warnings of a given type (RC or ODA).
235-105-210 October 1999
Copyright © 1999 Page 51