Avaya 03-300430 User Manual
PKT-INT (Packet Interface)
Issue 1 June 2005
1815
When 3 of these errors occur in 15 minutes, maintenance places the Packet Interface into
an out-of-service state, and a MAJOR on-board alarm is raised on the Packet Interface
(PKT-INT).
an out-of-service state, and a MAJOR on-board alarm is raised on the Packet Interface
(PKT-INT).
1. See if Error Codes 257, 513, 769, 1025, 1281, or 3841 are present in the hardware 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 alarm with a Service
State of OUT, take no action. If a Packet Interface MAJOR alarm is present and no other
Packet Interface Error Codes are in the hardware error log, use reset
packet-interface location to execute a demand reset, and refer to the repair
State of OUT, take no action. If a Packet Interface MAJOR alarm is present and no other
Packet Interface Error Codes are in the hardware error log, use reset
packet-interface location to execute a demand reset, and refer to the repair
procedures for 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.
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 hardware error log. If any are
present, follow the repair procedures for those errors.
d. Error Type 50: the media server is sending more downlink messages than the Packet
Interface module can process. This is an in-line 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.
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 a very serious. Maintenance software immediately escalates testing to
the Destructive Reset test (#889).
the Destructive Reset test (#889).
1. If the Packet Interface module 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).
b. Refer to the repair procedures for the Packet Interface Reset test (#889).
2. If the Packet Interface is not alarmed, take no action.
f. Error Type 513: Message Handshake failure. A failure with the message protocol between
the media 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).
b. Refer to the repair procedures for the Packet Interface Reset test (#889).
2. If the Packet Interface is not alarmed, take no action.