Escalation Procedures - Avaya S8700 Maintenance Manual

PKT-INT (Packet Interface)
Notes:
a. Error 1 occurs when background maintenance software has reset the
Packet Interface circuit as a fault recovery action. It is used to keep track
of the number of times that the Packet Interface circuit is reset,
independent of whether or not the Reset test passed. Once 3 of these
errors have occurred in the last 15 minutes, maintenance places the
Packet Interface circuit into an out-of-service state, and a MAJOR on-board
alarm is raised on the Packet Interface circuit.
1. Check to see if error codes 257, 513, 769, 1025, 1281, or 3841 are
2. If no other Packet Interface errors appear in the error log, and if the
b. Error 10 indicates that the Packet Interface maintenance software caused
an escalating system WARM restart as part of a recovery action for certain
Packet Interface circuit failures. A SYSTEM error type 10 should also be
present, indicating that a software initiated WARM restart occurred.
1. Check to see if error types 513, 1025, or 3074 are present in the
c. Error 50 indicates that the server is sending more downlink messages than
the Packet Interface circuit can keep up with. This is an in-line error not
produced by any test. When this error is reported, application software is
slowed down to allow the circuit to process existing downlink messages. If
there is a hardware problem, the Packet Interface test normally causes
other errors to be logged. In rare cases where no other PKT-INT errors are
logged but error 50 occurs more than 10 times in the last hour, follow
normal escalation procedures.
d. Error 257 indicates that the circuit pack detected a fatal failure. This error
is a very serious and when it occurs, maintenance software immediately
escalates testing to the Destructive Reset test (#889).
1. If the Packet Interface circuit has a MAJOR alarm:
2. If the Packet Interface circuit is not alarmed, no action is required.
555-233-142
present in the hardware error log. If one or more of those error
codes are present, refer to the information associated with those
errors for the appropriate repair procedures.
Packet Interface is not in a held reset state as indicated by the
absence of a MAJOR alarm with a Service State of OUT, no action
should be taken. If a Packet Interface MAJOR alarm is present and
no other Packet Interface error codes are in the hardware error log,
execute a demand reset by entering reset packet-interface Uc and
refer to the repair procedures for Test #889.
hardware error log. If they are present, refer to the repair
procedures for those errors for further action.
a. Enter reset packet-interface Uc to reset the Packet
Interface circuit.
b. Refer to the repair procedures for the Packet Interface Reset
test (#889).
Issue 1 May 2002 8-933