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.

The switch sent a message to the endpoint that did not respond in the allotted time. This<br />

can happen occasionally due to failure of the point-to-point signaling link or because of a<br />

problem in the BRI endpoint or ASAI adjunct or <strong>Avaya</strong> adjunct. Execute <strong>test</strong> station<br />

extension sh <strong>and</strong> note the results of the BRI Layer 3 Query <strong>test</strong> (#629). If this <strong>test</strong> fails,<br />

follow the repair procedure for BRI Layer 3 Query Test (#629).<br />

c. Error Type 130: the circuit pack has been removed or has been insane for more than 11<br />

minutes. To clear the <strong>error</strong>, replace or reinsert the circuit pack.<br />

d. Error Type 257: the endpoint does not respond to the service state query message sent to<br />

the adjunct or the endpoint. This <strong>error</strong> causes an alarm to be raised. The alarm is retired<br />

when the switch receives a response to the service state query to the endpoint or the<br />

adjunct.<br />

For BRI endpoints, the Aux Data field for this <strong>error</strong> contains “0.” When it occurs, execute<br />

<strong>test</strong> station extension sh <strong>and</strong> note the results of the BRI Layer 3 Query <strong>test</strong><br />

(#629). If this <strong>test</strong> fails, follow the repair procedure for BRI Layer 3 Query Test (#629)<br />

When this <strong>error</strong> occurs for an ASAI or <strong>Avaya</strong> adjunct, the Aux Data field indicates the state<br />

of the ASAI link or <strong>Avaya</strong> link <strong>and</strong> whether an invalid response or no response was<br />

received to the query from the switch, as shown in the following table:<br />

Aux Data ASAI Link State Error<br />

102 13-restarting No response to RESTART message<br />

104 13-restarting Invalid response to RESTART message<br />

152 13-restarted No response to layer-3 query<br />

154 13-restarted Invalid response to layer-3 query<br />

202 13-established No response to layer-3 query<br />

204 13-established Invalid response to layer-3 query<br />

See Maintenance SAT Comm<strong>and</strong>s in Maintenance Comm<strong>and</strong>s for <strong>Avaya</strong> Aura<br />

Communication Manager, Media Gateways <strong>and</strong> Servers (03-300431) for an explanation of<br />

the ASAI link states.<br />

For ASAI or <strong>Avaya</strong> adjuncts, the switch automatically queries the adjunct every two<br />

minutes (<strong>and</strong> therefore the Layer 3 Query <strong>test</strong> is not executed for ASAI or <strong>Avaya</strong> adjuncts<br />

via a comm<strong>and</strong> entered from the G3MT terminal). While alarmed for this <strong>error</strong>, the switch<br />

momentarily (for five seconds) takes the associated port out-of-service every 15 minutes.<br />

This action is taken in an attempt to stimulate recovery actions to be taken by the adjunct.<br />

When this <strong>error</strong> occurs for an ASAI or <strong>Avaya</strong> adjunct:<br />

1. Execute <strong>test</strong> station extension <strong>and</strong> note <strong>test</strong>s that fail. Perform the associated<br />

repair procedures for those <strong>test</strong>s.<br />

2. Check the health of the adjunct by following the recommended repair procedures of<br />

the manufacturer of the adjunct if the preceding step does not resolve the problem.<br />

226 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!