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

Maintenance Object Repair Procedures
555-233-123 10-1298 Issue 4 May 2002
Notes:
a. Error 1 occurs when background maintenance software has reset the
Packet Interface as a fault recovery action. It is used to keep track of the
number of times that the Packet Interface is reset, independent of whether
or not the Reset test passed. Once three of these errors have occurred in
the last 15 minutes, the next such error will cause maintenance to place the
Packet Interface into an out-of-service state, raise a MAJOR on-board
alarm against the Packet Interface, and automatically reset the
io-processor on the TN2401/TN794 NetPkt circuit pack. If the io-processor
reset does not restore to service the alarmed Packet Interface, then the
io-processor reset attempt fails, and the software will continue to attempt to
reset the io-processor. When three of these attempts have failed within a
15 minute period, maintenance software puts the io-processor into a
held-reset state and continues to attempt io-processor resets every three
(3) minutes as long as the io-processor resets continue to fail.
NOTE:
Whenever the io-processor is reset, both Packet Interface instances
and all 8 data channels (DATA-CHL) are reset as well, and service is
interrupted for any calls using these MOs. Refer to the IO-PROCR
section for more information concerning io-processor resets.
1. Check to see if Error Types 257, 513, 769, 1025, 1281, or 3841 are
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.
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, no action
should be taken.
3. 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 of the IO Processor by entering reset io-processor.
This command resets both Packet Interface instances as well as the
IO Processor. Refer to the repair procedures for Test #704.
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 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
hardware error log. If they are present, refer to the repair procedures
for those errors for further action.
c. Error 23 along with an associated MAJOR alarm indicates that Packet
Interface translation data was loaded at boot time but the Packet Interface
was not detected to be physically present
1. Reboot the SPE. If the error persists, replace the active
TN2401/TN794 NetPkt circuit pack.