Demand test descriptions and error codes - Avaya Support

PKT-INT (Packet Interface)
an out-of-service state, and and raises a WARNING off-board alarm on the Packet Interface
(PKT-INT).
1. See if Error Codes 257, 513, 769, 1025, 1281, or 3841 are present in the error log. If
one or more are present, follow the repair procedures for those errors.
2. If no other Packet Interface errors appear in the error log, and if the Packet Interface is
not in a held reset state as indicated by the absence of a MAJOR or MINOR alarm with
a Service State of OUT, you do not have to take any action. If a Packet Interface
MAJOR or MINOR alarm is present and no other Packet Interface Error Codes are in
the error log, use reset packet-interface location to execute a demand reset, and refer
to the repair procedures for Packet Interface Reset Test (#889).
c. Error Type 10: the Packet Interface maintenance software caused an escalating system
WARM restart as part of a recovery action for certain Packet Interface failures. A present
SYSTEM Error Type 10 indicates that a software-initiated WARM restart occurred.
1. See if Error Types 513, 1025, or 3074 are present in the error log. If any are present,
follow the repair procedures for those errors.
d. Error Type 50: the server is sending more downlink messages than the Packet Interface
module can process. This is an inline error not produced by any test. When this error is
reported, application software is slowed down to allow the module to process existing
downlink messages. If there is a hardware problem, the Packet Interface test causes other
errors to be logged. In rare cases when no other PKT-INT errors are logged but error 50
occurs more than 10 times in the last hour, follow normal escalation procedures.
e. Error Type 257: the Packet Interface module on the IPSI circuit pack detected a fatal
failure. This error is very serious. Maintenance software immediately escalates testing to
the Packet Interface Reset Test (#889). This error can be caused by network connectivity
loss between the Server and the IPSI where the packet interface Module resides.
1. If the Packet Interface module has a WARNING alarm: the alarm is caused by the
connectivity loss between the server and the IPSI.
2. If the Packet Interface module has a MINOR alarm: verify the network reachability of
IPSI from the server.
● If the network is out: try to restore the network connectivity.
● If connected to IPSI: use the reset packet-interface location to reset the Packet
Interface. Refer to the repair procedures for the Packet Interface Reset Test
(#889).
3. If the Packet Interface is not alarmed: you do not have to take any action.
f. Error Type 513: Message Handshake failure. A failure with the message protocol between
the server’s software and the Packet Interface was detected.
1. If the Packet Interface has a MAJOR alarm:
a. Use reset packet-interface location to reset the Packet Interface.
b. Refer to the repair procedures for the Packet Interface Reset Test (#889).
Issue 5 May 2009 739