System Errors and Traffic Pegs 8-31
Octel 200/300 S.4.1PB60019−01
Table 8-2 Hardware Error Types and Remedies (continued)
Error Type:Name PriorityRemedySource
63. Fax Card
Hardware Error
Fax l oopback t est failed
or fa x card didn’t
respond t o command:
TEST X x y z.
Replace the fax card and do the loopback
test again.
2
DATA-1 = 00 = FAX LOOPBACK TEST FAILED
DATA-2 =OTHER CH# (RELATIVE) USED IN TEST
DATA-3 =ERROR CODE RETURNED FROM FAX PROCESSOR
01 = FAX CARD DIDN’T RESPOND TO TEST COMMAND
DATA-2 =1ST CH# (RELATIVE) USED IN TEST
DATA-3 =2ND CH# (RELATIVE) USED IN TEST
64. LAN Hardware
Error
Problem detected by
the LAN card.
Dependent on the Data-1 values described
below.
3
DATA-1 =ERROR CODE:
00 = INVALID LAN CONTROL BUS ID
Problem with LAN card.
REMEDY: Contact your technical support center.
01 = BAD LAN CONTROL BUS CKSUM
Problem with LAN card.
REMEDY: Contact your technical support center.
02 = LOST COMMUNICATION TO LAN BOARD
Communication between the CPU and LAN card across the control
bus was interrupted or failed for some reason.
REMEDY: Verify that the LAN card is properly inserted in the slot
and has not been removed. Try the LANSTAT command
to verify that the LAN card is up and communicating
with the CPU. If the error continues, contact your
technical support center.
DATA-2 values in case of LAN_LOST_COMM:
1 Unable to read card status.
2 Card status is nonoperational.
3 CB timed out at start of read reply.
4 CB timed out during read reply packet.
5 CB time out at start of send request.
6 CB timed out when checked if took request.
7 CB timed out at end of the read reply.
8 CB timed out during write request packet.
9 CB timed out after write request.
10 Complement of replies not match.
11 Checksum wrong after control bus copy.