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

PKT-INT (Packet Interface)
Issue 4 May 2002 10-1307 555-233-123
■
Broadcast Link Looparound
Each ISDN BRI port has two associated broadcast signaling links, one for
call control and one for maintenance and management. Since these links
have separate routing circuitry from the Level 2 Looparound, this test
forces a CRC error to verify the CRC hardware associated with the
broadcast data path.
■
Level 3 Link Looparound
Level 3 Links support the X.25 Data Phase protocol used with the Packet
Gateway to support X.25 links such as those used for AUDIX. This test
verifies the health of the Level 3 firmware. Since soft errors are possible,
the Packet Interface retries the test before reporting an error.
These tests are also run as part of the reset tests. If the Level 2 or Level 3
looparound test fail as background tests, a “fatal error” message will be sent to the
Packet Interface maintenance software and the Packet Interface will be put in the
“out-of-service” state. Therefore, it is expected that the repair procedures
associated with Abort Code 1137 (out-of-service) would normally be followed
when failures with the Level 2 and Level 3 tests occur.
Test #885 executes differently depending on which instance of Packet Interface is
tested:
1. Packet Interface 1 (TDM Bus-based) - No hardware is tested. Only
operational firmware is tested.
2. Packet Interface 2 (Packet Bus-based) - All three tests are executed.
Table 10-485. TEST #885 Private Looparound Tests
Error
Code Test
Result Description/Recommendation
1006
1137 ABORT Packet Interface is in the out-of-service state so normal
maintenance tests will not run on it.
1. Request a Packet Interface reset using reset
packet-interface CS. Refer to the Packet Interface Reset
Test (#889) repair procedures for further action.
1334 ABORT The Packet Interface command queue is full. This should be a
temporary condition caused by a high rate of commands being
sent to a Packet Interface. Continued operation with a full
command queue will cause a system WARM restart that may
escalate to more severe restart levels.
1. Retry the command at 10-second intervals, a maximum of 5
times.
Continued on next page