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

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

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

As any <strong>error</strong> conditions are encountered during the <strong>test</strong>, they are logged against the INADS Link<br />

MO.<br />

● If the initial <strong>test</strong> result was Comm<strong>and</strong> successfully completed, any logged <strong>error</strong><br />

<strong>codes</strong> would range from 1–9.<br />

● If the initial <strong>test</strong> result was Comm<strong>and</strong> failed, any logged <strong>error</strong> <strong>codes</strong> would be 10 or 11.<br />

An <strong>error</strong> is logged at the alarm receiver even if the call to the alarm receiver finally succeeds.<br />

The alarm receiver’s software:<br />

1. Recognizes this special “<strong>test</strong> inads” alarm type<br />

2. Automatically opens <strong>and</strong> closes a trouble ticket<br />

Within the trouble ticket, a field containing the description TESTING INADS LINK indicates<br />

that the ticket was initiated by <strong>test</strong> inads-link.<br />

After entering the comm<strong>and</strong>, up to 9 minutes can elapse before the switch places the call <strong>and</strong><br />

the alarm receiver responds. To determine whether the call was successful, the Error Log<br />

should be examined by using the inads category 10 minutes after successfully entering the<br />

comm<strong>and</strong>. Table 139: INADS Link Test Error Log Entries explains the <strong>error</strong> <strong>codes</strong>.<br />

Error log entries <strong>and</strong> recommended actions<br />

Table 139: INADS Link Test Error Log Entries 1 of 3<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1 0 A <strong>test</strong> call was successfully placed to the alarm receiver. No trouble found.<br />

2 0 Informative <strong>error</strong> indicating that alarm origination was disabled at the time of<br />

the <strong>test</strong>. The <strong>test</strong> runs even though alarm origination is disabled.<br />

1. If desired, enable Alarm Origination via the Maintenance-Related<br />

System Parameters screen.<br />

2. Repeat the <strong>test</strong>.<br />

3 0 The alarm receiver’s connection is currently in use.<br />

1. Wait 10 minutes, <strong>and</strong> retry the comm<strong>and</strong>.<br />

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

1 of 3

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

Saved successfully!

Ooh no, something went wrong!