09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 557: Active-Standby Peer Link Test (#888) 2 of 3<br />

Error<br />

Code<br />

Active-Standby Peer Link Test (#888)<br />

1337 ABORT The test is not allowed to run because a PNC interchange is in progress.<br />

A PNC interchange may have been initiated with reset pnc<br />

interchange, or as part of a recovery action.<br />

1. Wait 3 minutes and retry the command.<br />

2000 ABORT Response to the test was not received within the allowed time.<br />

2500 Internal system error<br />

1. Retry the command at 1-minute intervals up to 3 times.<br />

1<br />

2<br />

Test<br />

Result<br />

Description / Recommendation<br />

FAIL Setting up peer links between the active and standby IPSI circuit pack’s<br />

Packet Interface modules failed.<br />

Error Code 1: The standby IPSI circuit pack’s Packet Interface module<br />

did not respond to the peer link setup.<br />

Error Code 2: The active IPSI circuit pack’s Packet Interface module did<br />

not respond to the peer link setup<br />

1. This may be the result of old firmware not supporting new software<br />

operation. Verify the IPSI circuit pack’s firmware vintage and<br />

download the new firmware if appropriate.<br />

2. The firmware image on the IPSI circuit pack may have been<br />

corrupted. Download the firmware image.<br />

3. Retry the command.<br />

4. If the same Error Code occurs, use display alarms to display<br />

active alarms.<br />

5. If there are errors related to the packet bus, see PKT-BUS (Packet<br />

Bus) and clear those problems first.<br />

6. Retry the test command after a 1-minute delay.<br />

7. If the test continues to fail, replace the affected IPSI circuit pack.<br />

PASS The server can communicate with the IPSI circuit pack’s Packet<br />

Interface module.<br />

1. If problems are still reported on the Packet Interface, check for<br />

failures using the Private Looparound test (#885) and Maintenance<br />

Looparound test (#886).<br />

2 of 3<br />

Communication Manager Release 5.0 Issue 4 January 2008 1887

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!