19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - 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.

2. If the Packet Interface is not alarmed, take no action.<br />

g. Error Type 769 <strong>and</strong> 770: failure in the Packet Looparound <strong>test</strong>. A maintenance looparound<br />

link cannot be established or the Packet Interface cannot send <strong>and</strong> receive data correctly as<br />

part of the Packet Interface Maintenance Looparound Test (#886). If the number of <strong>error</strong>s<br />

exceeds a defined threshold, a Major alarm is raised.<br />

In a high- or critical-reliability system (duplicated IPSIs), a failure of the Maintenance<br />

Looparound <strong>test</strong> may have caused an IPSI interchange. This results in an alarm<br />

associated with Error Code 769 or 770 being reported against the st<strong>and</strong>by IPSI’s Packet<br />

Interface module.<br />

Test 886 can be run only on the active IPSI. Enter busy ipserver-interface followed<br />

by release ipserver-interface to clear the <strong>error</strong> on the st<strong>and</strong>by IPSI. Then enter<br />

set ipserver-interface to force an IPSI interchange.<br />

Error code 770 indicates that old firmware on the IPSI does not support new software<br />

operation.<br />

For more information, refer to the repair procedures of the Packet Interface Maintenance<br />

Looparound Test (#886)<br />

h. Error Type 1025: failure of the Packet Interface Private Looparound Test (#885).<br />

1. If the Packet Interface has a MAJOR alarm:<br />

a. Use reset packet-interface location to reset the Packet Interface.<br />

b. Refer to the repair procedures for Packet Interface Reset Test (#889).<br />

2. If the Packet Interface is not alarmed, take no action.<br />

i. Error Type 1281: the Packet Interface has Translation RAM failures. PKT-INT Translation<br />

RAM is used to convert the addresses of a packet to the destination endpoint address.<br />

1. If the Packet Interface has a MAJOR alarm:<br />

a. Use reset packet-interface location to reset the Packet Interface.<br />

b. Refer to the repair procedures for the Packet Interface Reset Test (#889).<br />

2. If the Packet Interface is not alarmed, take no action.<br />

j. Error Type 1537: Boot PROM memory failure. The Packet Interface module may still be<br />

operational if no other <strong>error</strong>s are reported. However, the module may report a fatal fault<br />

during board initialization. This may occur during a system recovery level more severe than<br />

a WARM restart. For more information, refer to Packet Interface Memory Checksum Test<br />

(#884).<br />

k. Error Type 1793: FLASH Memory <strong>test</strong> failure. The Packet Interface module may still be<br />

operational if no other <strong>error</strong>s are reported. However, the module may report a fatal fault<br />

during board initialization. This may occur during a system recovery level more severe than<br />

a WARM restart. For more information, refer to the repair procedures of Packet Interface<br />

Memory Checksum Test (#884).<br />

740 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers

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

Saved successfully!

Ooh no, something went wrong!