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.

Communication Manager Maintenance Object Repair Procedures<br />

c. Error Type 257: An endpoint is not responding to the service state query message sent to<br />

the adjunct or to 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 to the<br />

adjunct.<br />

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

ASAI link <strong>and</strong> whether an invalid response or no response was received to the query from<br />

the switch, as shown in the following table:<br />

Aux<br />

Data<br />

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 queries the adjunct every two minutes. The Layer<br />

3 Query <strong>test</strong> is not executed for ASAI or <strong>Avaya</strong> adjuncts through a comm<strong>and</strong> entered from<br />

the management terminal. While alarmed for this <strong>error</strong>, the switch takes the associated<br />

port out-of-service for five seconds every 15 minutes. This action attempts to stimulate<br />

recovery actions to be taken by the adjunct.<br />

When this <strong>error</strong> occurs for an ASAI or <strong>Avaya</strong> adjunct, the service technician should:<br />

1. Execute <strong>test</strong> station extension <strong>and</strong> perform the associated repair procedures.<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 />

d. Error Type 351: logged against an ASAI endpoint when the adjunct asks the switch to<br />

suspend maintenance on the ASAI endpoint. Clear with busyout <strong>and</strong> release of the ASAI<br />

station.<br />

e. Error Type 513: the endpoint sent more messages than the switch could h<strong>and</strong>le. The<br />

switch suspends the reception of messages from the endpoint for a short period of time.<br />

There is no repair procedure for this <strong>error</strong>. If the condition persists, replace the endpoint.<br />

f. Error Type 769: an ASAI endpoint’s associated signaling link has too much traffic related to<br />

link establishment. This occurs when the signaling link is alternating between assigned <strong>and</strong><br />

established states. If this problem persists, replace the endpoint.<br />

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