DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Alarms, Errors, and Troubleshooting
5-17Executing a Planned SPE Interchange
5
Notes for SYSTEM Er ror 60 5 AUX Da ta:
1. Follow repair instructions in ‘‘STBY-SPE (Standby SPE Maintenance)’’ for
the p artic ular stan dby SPE prob lem. After fixin g tha t pro blem , try t he
interchange again.
2. Mass Storage System is in use. Check Disk and Tape LEDs for activity.
Wait until all MSS activity completes, then try the interchang e again. If the
problem persists, c heck for alarms and errors ag ainst MSS components
and follow repair proce dures for each Maintenance Ob ject.
3. Test the PKT-INT on both carriers with the long tes t sequence. Follow
procedures for ‘‘PKT-INT (Packet Interface Ci rcuit Pack)’’. Once
all
tests of
both PKT-INTs pass, try the interchange again.
4. Consult SW-CTL service documentation. Test SW-CTL on both carriers
with the long test sequenc e. Follow repair instructions for any failures.
Once
all
tests of both SW-CTLs pass, try the interchange ag ain.
5. Mak e sure the st andb y SPE is refres hed Then tr y the i nterc hang e ag ain.
6. Examine alarm log to determine which of PKT-INT or SYSAM circuit packs
has a minor alarm against it. Consult servic e documentation of whichev er
is alarm to clear
7. Check for errors/alarms against ac tive SPE’s SYSAM. If you fi nd an y,
consult the ‘‘SYSAM (Circuit Pack)’’ documentation. If yo u find none, and if
all te sts of the SYSAM long sequ enc e pas s, try the in terc hang e aga in.
8. Run test duplication-interface long and follow instructions for any test
that does not pass.
1406 3Active SPE’s PKT-INT in held-reset state
1418 8Active Duplication I nterface circuit p ack is in a bad state
and needs to be reset.
2500 5Internal Software failure1 (sometimes)
1 A WARM restart is required.
Table 5-1. SYSTEM Error 605 Planned Interchange Failure — Continued
Aux
Data See
Note Explanation
Continued on next page