09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 632: Long IP 2-Way Transmission Test (#1506) 2 of 3<br />

Error<br />

Code<br />

2000<br />

2012<br />

2100<br />

2500<br />

Long IP 2-Way Transmission Test (#1506)<br />

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

Internal system error.<br />

Could not allocate the necessary system resources to run this test.<br />

Internal system error.<br />

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

2801 ABORT The IP Media Processor has not been administered on the<br />

ip-interfaces form.<br />

1. Administer the IP Media Processor on the ip-interfaces form.<br />

2806 ABORT The system could not find any in-service IP Media Processors to use as<br />

a destination for this test.<br />

2807 ABORT The specified IP Media Processor has been disabled on the<br />

ip-interfaces screen.<br />

10XX<br />

XX = PN #<br />

20XX<br />

XX = PN #<br />

Test<br />

Result<br />

Description / Recommendation<br />

FAIL The test tone was not successfully sent from the IP Media Processor<br />

specified in the test command, and not successfully received by an IP<br />

Media Processor in the PN specified in the error code XX. Source to<br />

destination direction failed. Destination to source direction not tested.<br />

1. Resolve all other board alarms for the specified source IP Media<br />

Processor.<br />

2. Resolve all other board alarms for the IP Media Processors in the<br />

destination PN.<br />

3. Use ping and traceroute to localize the problem to the customer’s<br />

LAN/WAN IP network.<br />

FAIL The test tone was successfully sent from the IP Media Processor<br />

specified in the test command and received by an IP Media Processor<br />

in the PN specified in the error code XX.<br />

The test tone was not successfully sent in the reverse direction.<br />

Destination to source direction failed. Source to destination direction<br />

passed.<br />

1. Resolve all other board alarms for the specified source IP Media<br />

Processor.<br />

2. Resolve all other board alarms for the IP Media Processors in the<br />

destination PN.<br />

3. Use ping and traceroute to localize the problem to the<br />

customer’s LAN/WAN IP network.<br />

2 of 3<br />

Communication Manager Release 5.0 Issue 4 January 2008 2025

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

Saved successfully!

Ooh no, something went wrong!