Demand test descriptions and error codes - Avaya Support

x. Error Types 3585 to 3601: for later releases of G3V4 and beyond, Error Type 3585 shows
that this board is receiving misframes. The AUX Data contains the last misframe count
reported.
y. Error Type 3840: not service-affecting. No action is required. These errors are reported by
the circuit pack when it receives a bad control chel message from the switch. The auxiliary
data identifies the following error events:
Aux Data Event
4096 Bad major heading
4097 Bad port number
4098 Bad data
4099 Bad sub-qualifier
4100 State inconsistency
4101 Bad logical link
z. Error Type 3841: the UDS1 Interface circuit pack has detected a transient hardware logic
error (for example, program logic inconsistency). This error will disappear when no faults
are detected for 100 minutes. The value in Aux Data indicates the type of hardware
problem.
aa. Error Type 3842: bad translation RAM location found error. This error is not
service-affecting. No action is required. A Bad Translation RAM is detected, but the call
continues by using another translation location.
ab. Error Type 3843: LAN Receive Parity Error. This error occurs when the circuit pack detects
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.
See PKT-INT (Packet Interface) to determine whether the problem is isolated to this circuit
pack or is caused by Packet bus faults.
ac. Error Type 3900: provides status information about a CPE Loopback Jack test. The value
in the Aux Data field indicates the status of the loopback test.
Aux Data Test Status
1 Test is currently running
2 Failed because loopback could not be activated
3 Failed because test pattern could not be detected
4 Test has been terminated
1038 Maintenance Alarms for Communication Manager, Media Gateways and Servers