Filter
Top Products
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-1262TAPE-DAT (Tape Consistency)
10
TAPE-DAT (Tape Consistency)
In High and Critical Reliability systems, the system software translations, as well
as other information, can be stored on two tapes: one in the Active SPE and one
in the Standby SPE. In order to flag a problem when these tapes become
mismatched, Tape Consistency monitors the translations, announcements,
update files, and software vintage number on both tapes in a High or Critical
Reliability PPN system. If the translation time stamp, announcement time stamp,
and update file time stamp and identifiers on the two tapes are not the same
and/or if the software vintage numbers do not match, an alarm is raised. The
software vintage can be displayed via the list configuration software-vintage
command. The Tape Consistency Test is run on system technician command
and once a week as part of daily Standby SPE maintenance. Tape Consistency
does not apply and does not exist in Standard systems.
Error Log Entries and Test to Clear Values
Notes:
a. An "8" in the log refers to carrier A and a "16" refers to carrier B. The Aux
Data field records which SPE was active at the time the Tape Consistency
Test failed.
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the
appropriate test description and follow the recommended procedures.
MO Name (in
Alarm Log)
Alarm
Level Initial Command to Run Full Name of MO
TAPE-DAT MINOR test tape a|b l Tape Consistency
Table 10-436. Tape Consistency Error Log Entries
Error
Type
Aux
Data Associated Test
Alarm
Level
On/Off
Board Test to Clear Value
0
1
0 Any Any Any test tape a/b l
8 or 16 8 or 16 Tape Consistency
Test (#421)
WARNING OFF test tape a/b l
1-7,
9-15, 8 or 16 Tape Consistency
Test (#421)
MINOR OFF test tape a/b l
17-86