Filter
Top Products
SYSTEM (System)
Issue 1 June 2005 2189
Notes for SYSTEM Error Type 605 Aux Data:
a. Aux Data 1352, 1353, 1355, 1356, 1357, 1360: from the Linux command line, execute
almdisplay and follow the troubleshooting procedures listed there for “media server
alarms.” After fixing that problem, try the interchange again.
b. Aux Data 1358: Mass Storage System is in use. Check disk for activity. Wait until every
MSS activity completes, then retry the interchange again. If the problem persists, check for
alarms and errors against MSS components.
c. Aux Data 1359, 1396, 1397, 1398, 1399, 1406: test the PKT-INT on both carriers with the
long test sequence. Follow procedures for PKT-INT (Packet Interface)
on page 1799. Once
every test of both PKT-INTs passes, try the interchange again.
1361 (d
) 4 SW-CTL failure
1369 (g
) 7 Could not suspend G3-MT connectivity *
1370 (d
) 4 Could not freeze active SW-CTL *
1371 (e
) 5 Internal Error associated with processor interrupts *
1372 (f
) 6 Minor alarm on standby SYSAM or PKT-INT
1395 Server Duplication not administered
1396 (c
) 3 PKT-INT Link Migration failure in Begin Step *
1397 (c
) 3 PKT-INT Link Migration denied, (peer test in progress)
1398 (c
) 3 PKT-INT Link Migration failure in Completion Step *
1399 (c
) 3 PKT-INT Link Migration failure in Finish Step *
1400 (d
) 4 Could Not Idle SW-CTL dual port RAM *
1401 (d
) 4 Could Not Refresh SW-CTL dual port RAM *
1402 (e
) 5 Internal Error (could not get duplication status)
1403 (e
) 5 Unable to inhibit standby Maintenance Monitor
1404 (e
) 5 Failure to determine standby server’s alarm status
1406 (c
) 3 Active server’s PKT-INT in held-reset state
1418 8 Active Duplication Interface circuit pack is in a bad state and
needs to be reset.
2500 (e
) 5 Internal Software failure (* sometimes)
Table 781: SYSTEM Error 605 Aux Data, Failure of Planned Interchange (continued)
2 of 2