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.

Note: 2561<br />

CLAN-BD (Control LAN Circuit Pack)<br />

Aux Data Any: Bad DLCI.<br />

3. Reset circuit pack with the busyout board location, reset board location,<br />

<strong>and</strong> release board location comm<strong>and</strong>s.<br />

4. Clear alarms using the <strong>test</strong> board long clear comm<strong>and</strong>.<br />

5. If the <strong>error</strong> returns within 15 minutes, replace the circuit pack.<br />

k. Error Type 1797: Invalid layer 2 frame received.<br />

l. Error Type 1798: Unable to write translation RAM.<br />

1. Attempt to clear alarm with reset board location.<br />

2. If the alarm recurs within 15 minutes, replace the circuit pack.<br />

m. Error Type 2049: Packet Interface <strong>test</strong> (#598) failed.<br />

1. Attempt to clear the alarm (<strong>test</strong> board location l r 3).<br />

2. If alarm does not clear, reset the circuit pack with reset board location.<br />

3. If circuit pack resets successfully, execute the Packet Interface <strong>test</strong> (#598) several<br />

times.<br />

4. If the Packet Interface <strong>test</strong> (#598) continues to fail, replace the circuit pack.<br />

n. Error Type 2305-2306: Error in a received frame from the packet bus.<br />

Error Type Description<br />

2305 Received invalid LAPD frame.<br />

2306 Detected parity <strong>error</strong> on received frame.<br />

1. Enter <strong>test</strong> board location <strong>and</strong> see if the condition clears.<br />

2. If the condition persists, execute the Packet Interface <strong>test</strong> (#598) to verify circuit pack<br />

integrity.<br />

3. If the Packet Interface <strong>test</strong> (#598) fails, see Packet Interface Test (#598).<br />

o. Error Type 2561-2668: System software received an indication that the socket was closed<br />

due to an <strong>error</strong>. Errors are reported as log only. Errors logged here are for the sockets that<br />

had no processor chels associated with them, for example, sockets to read SNMP data.<br />

The counter base is offset by the application type of the application associated with this<br />

socket that is down. The Aux Data field of the log entry contains this application’s number,<br />

for example, a SNMP application would have its application number in the Aux Data field.<br />

Note:<br />

- 2668 is a range of reserved numbers for future applications.<br />

2570 represents an SNMP socket failure.<br />

Issue 5 May 2009 269

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

Saved successfully!

Ooh no, something went wrong!