DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-150BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)
10
k. A critical failure has been detected in the Packet Bus interface of the
circuit pack. This failure may be due to either a Packet Bus fault or an
on-board fault. If the Packet Bus is alarmed, refer to the "PKT-BUS (Packet
Bus)" section and Chapter 9, "Packet Bus Fault Isolation and Correction"
for recommended repair procedures. The probability of this error being
related to Packet bus problems increases with the number of ISDN-BRI
circuit packs displaying this error.
If the Packet Bus is not alarmed, reset the circuit pack via the busyout
board PCSS and reset board PCSS commands. If the Circuit Pack
Restart Test (#594) passes, then the on-board circuitry is healthy. Retire
the alarm via the test board PCSS long clear command. If the Circuit
Pack Restart Test (#594) fails, replace the circuit pack. If the problem
persists after complying with the above instructions, then follow normal
escalation procedures.
l. These errors are not service-affecting. No action is required. These errors
are reported by the circuit pack when it receives a bad control channel
message from the switch. The auxiliary data identifies the following error
events:
m. This error is not service-affecting. No action is required.
n. Error type 3999
Indicates that the circuit pack sent a large number of
control channel messages to the switch within a short period of time. If
error type 1538 is also present, then the circuit pack was taken
out-of-service due to hyperactivity. If error type 1538 is not present, then
the circuit pack has not been taken out-of-service, but it has generated
50% of the messages necessary to be considered hyperactive. This may
be completely normal during heavy traffic periods. However, if this error
type is logged when the circuit pack is being lightly used, it may indicate a
problem with the circuit pack or the equipment attached to it.
4096 Bad major heading
4097 Bad port number
4098 Bad data
4099 Bad sub-qualifier
4100 State inconsistency
4101 Inconsistent downlink message
3843 Bad translation RAM detected, but call continues by using
another translation location.