MAPD-BD (MAPD Interface Circuit Pack TN802)
Issue 1 May 2002
8-1059
555-233-143
n. Error Type 3330—LAN Critical error; critical failure in the packet-bus
interface to the circuit pack. This failure may be due to an on-board or a
packet-bus fault.
1. If the packet bus is alarmed, see
for
recommended repair procedures.
If not, clear the alarm and restore the board to the packet bus using
the following command sequence:
a. busyout board UUCSS
b. reset board UUCSS
c. test board UUCSS clear
d. release board UUCSS
2. If the problem persists, and there are no PKT-BUS alarms, then
replace the circuit pack. See
‘‘Shutting Down NT on the TN802’’
before removing the circuit pack.
o. Error Type 3585 - 3601—The board received misframe errors; the Aux
Data shows the last reported misframe count.
p. Error Type 3840—The circuit pack received a bad control channel
message from the switch. This error is not service-affecting, and requires
no action. The Aux Data describes the following error events:
q. Error Type 3841—The circuit pack detected a transient hardware logic
error (for example, program logic inconsistency). This error resolves when
no faults are detected for 100 minutes. The value in
Aux Data
field (4358)
indicates the type of hardware problem.
r. Error Type 3842—Bad Translation RAM Location Found error; the call
continues by using another translation location. This error is not
service-affecting and requires no action.
s. Error Type 3843—LAN Receive Parity error; the circuit pack detected an
error in a received frame from the packet bus. These errors are most likely
caused by a packet-bus problem, but may be due to a circuit-pack fault.
1. Determine whether the problem is isolated to this circuit pack or the
problem is caused by packet-bus faults (see the PKT-BUS MO).
4096
Bad major heading
4097
Bad port number
4098
Bad data
4099
Bad sub-qualifier
4100
State inconsistency
4101
Bad logical link
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...