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

Maintenance Object Repair Procedures
555-233-123 10-1316 Issue 4 May 2002
256
512
768 FAIL
(cont’d.) 2. If error code 512 or 768 is reported for a Packet Interface on
an active SPE, the receive FIFO in the Packet Interface has
overflowed. This may be an indication that additional Packet
Interface capacity is required. For the current hardware
configuration, only two Packet Interfaces are provided, so the
problem should be escalated if the repair steps presented
below do not correct the problem. Retry the command after a
one minute delay and if the test continues to fail:
a. If the system is equipped with the High Reliability or
Critical Reliability Configuration and if the Packet
Interface is on the active SPE, perform a planned SPE
interchange by entering the command reset system
interchange. Replace the TN2401/TN794 NetPkt circuit
pack
b. ) Otherwise, (the system is not equipped with the High
Reliability or Critical Reliability Configuration) replace the
TN2401/TN794 NetPkt circuit pack at a time that would
cause the least service disruption.
3. If error code 512 or 768 is reported for a Packet Interface on
a standby SPE, replace the standby TN2401/TN794 NetPkt
circuit pack.
1024-
1096 FAIL The Packet Interface on the standby SPE has bad Translation
RAM locations. A MINOR alarm is generated when the number of
bad locations is from 1 and 4. A MAJOR alarm is generated if the
number of bad locations is 5 or more. The MAJOR alarm
prevents a planned SPE interchange. (A planned interchange
may be administered to occur automatically every 24 hours or it
may be requested by using the reset system interchange
command.)
1. If a MAJOR alarm is associated with this error, replace the
alarmed Packet Interface’s TN2401/TN794 NetPkt circuit
pack.
2. If a MINOR alarm is associated with this error, replace the
alarmed Packet Interface’s TN2401/TN794 NetPkt circuit
pack at a time that would cause the least disruption to
service.
PASS The SPE is able to communicate with the Packet Interface. If
problems are still reported on the Packet Interface, check for
failures using the Private Looparound test (#885) and
Maintenance Looparound test (#886).
Table 10-487. TEST #887 Read and Clear Board Counters — Continued
Error
Code Test
Result Description/Recommendation
Continued on next page