
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Alarms, Errors, and Troubleshooting
5-16Executing a Planned SPE Interchange
5
If the SPE is locked by means of the SPE-SELECT switches, error 607, auxiliary
data 1153, is logged against SYSTEM. If the switches are not locked and the
interchange fails, an unalarmed error 605 is logged against SYSTEM. The
auxiliary code associated with this error indicates which aspect of the
interchange failed. Table 5-1
explains the meaning of the auxiliary codes and
what corrective action to take.
Table 5-1. SYSTEM Error 605 Planned Interchange Failure
Aux
Data
See
Note Explanation
1352 1
Standby SOH “non-functional”
1353
1
Standby SOH not “functional”
1355
1
Handshake Communication with Standby SPE is down
1356
1
Memory Shadowing not enabled
1357
1
Standby memory not refreshed
1358
2
Mass Storage System was in use
1359
3
PKT-INT link migration failed
1360
1
Interchange failed
1
1361
4
SW-CTL failure
1369
7
Could not suspend G3-MT connectivity
1
1370
4
Could not freeze active SW-CTL
1
1371 5 Internal Error associated with processor interrupts
1
1372
6
Minor alarm on standby SYSAM or PKT-INT
1395 SPE Duplication not administered
1396
3
PKT-INT Link Migration failure in Begin Step
1
1397
3
PKT-INT Link Migration denied, (peer test in progress)
1398
3
PKT-INT Link Migration failure in Completion Step
1
1399
3
PKT-INT Link Migration failure in Finish Step
1
1400 4 Could Not Idle SW-CTL dual port RAM
1
1401 4 Could Not Refresh SW-CTL dual port RAM
1
1402 5 Internal Error (could not get duplication status)
1403 5 Unable to inhibit Standby Maintenance Monitor
1404 5
Failure to determine Standby SPE alarm status
Continued on next page