Avaya Definity SI, Руководство по обслуживанию, Страница: 2085 / 2968

PKT-INT (Packet Interface)
Issue 4 May 2002 10-1299 555-233-123
d. Error 50 indicates that the SPE is sending more downlink messages than
the Packet Interface 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 Packet Interface to process existing downlink messages.
If there is a hardware problem, the Packet Interface test will normally cause
other errors to be logged. In the rare case where there are no other
PKT-INT errors logged but error 50 occurs more than 10 times in the last
hour, follow normal escalation procedures.
e. Error 100 indicates that the SPE requested a reset of Packet Interfaces on
the active SPE as part of a Packet Interface recovery action. High or
Critical Reliability systems request a SPE interchange instead of a Packet
Interface reset, if the health of the standby SPE allows an interchange.
1. If no other PKT-INT errors except Error Type 1 are present, this
means that the Packet Interface was in a fatal fault state at the time
of system initialization or SPE interchange and it was reset
successfully. No other actions are required.
2. If PKT-INT error codes other than Error Type 1 are present, refer to
the repair procedures for those errors to correct the failure.
f. Error 257 indicates that maintenance has detected a Packet Interface 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, reset the Packet
Interface (reset io-processor).
2. If the Packet Interface is not alarmed, no action is required.
g. Errors 267 and 217 indicate that the number of Packet Interfaces detected
as being physically present exceeds number of Packet Interfaces
supported by the software configuration.
h. Error 513 is a Message Handshake failure, indicating that a failure with the
message protocol between the SPE software and the Packet Interface.
1. If the Packet Interface circuit has a MAJOR alarm, reset the Packet
Interface (reset io-processor).
2. If the Packet Interface is not alarmed, no action is required.
i. Error 769 indicates that there was a failure in the Maintenance Looparound
test (Test #886). A maintenance looparound link cannot be established or
the Packet Interface cannot send and receive data correctly as part of the
looparound test. If the number of errors exceeds a defined threshold, a
MAJOR alarm is raised. In a system equipped with duplicated SPEs, a
failure of the Maintenance Looparound test may have caused a SPE
interchange which results in an alarm associated with Error Type 769
against a Packet Interface circuit pack that is currently on the standby SPE.
If so, it may be necessary to force the standby SPE to go active by using
the SPE-SELECT switches on the DUPINT circuit packs to run the
Maintenance Looparound test to make sure the problem is cleared. For
more information, refer to the repair procedures for Test #886.