EasyManua.ls Logo

Lucent 5ESS DRM - Page 375

Default Icon
642 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Note 1: Step 18d assumes that this is a single session multi-volume DAT.
If other session is to be used, enter the correct session number.
Note 2: If the session/volume request PRM is never printed, type and
enter: 43 to clear all application parameters, then repeat this step.
Note 3: If the volume was found, it takes approximately 10 minutes to
load AM ODD. A progression PRM prints while the tape is being loaded. If
the volume is not found, check the values entered or select another
session/volume, or seek technical assistance.
Tape Version PRM_0 E151 54xx xxxx xxxx xx xx xx
Program Version PRM_0 E151 7400 xxxx 0000 hh hh
Tape Load Progression PRM_0 E151 57xx xxxx xxxx xx xx xx
Tape Load Completion PRM_0 E151 59xx xxxx xxxx xx xx xx
Ready for Next Request PRM_0 E151 33xx EEEE EEEE hh hh hh
Tape Load Problem PRM_0 E151 xxxx xxxx xxxx xx xx xx
19. Did the tape load completion PRM follow the progression PRMs?
If YES, AM ODD has been loaded., continue with the next step.
If NO, analyze any failure PRMs. Seek technical assistance.
20. At this point in the procedure, the loading of the AM text and AM ODD tapes is
completed. The next step is to perform a system initialization while requesting a
backout of recent changes. The reason for requesting the backout of AM recent
changes is that any recent change log files which may exist on the disk will be
inconsistent with the Office Dependent Data (ODD) disk image just read into the
system. Before performing the system initialization, be sure that the Backup
Root indicator is SET and the Min Config indicator is clear on the EAI page.
Note: If the system has been thrashing because of switching module
communication problems or if communication to the switching module is known
to be bad, then set hardware and software checks on the EAI page (Poke 34 and
36).
235-200-150
January 2003
SYSTEM RECOVERY
Procedure 7.1.3
Issue 3.00 Page 7.1.3-5

Table of Contents