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.

. Error Type 257: the link has experienced uplink flow control, <strong>and</strong> the endpoint may be<br />

hyperactive. The system link is alarmed if 4 or more <strong>error</strong>s of this type are detected within<br />

10 minutes.<br />

1. Follow the information in Common Procedure for Repairing Link Problems.<br />

2. Clear <strong>error</strong>s <strong>and</strong> wait for 10 minutes.<br />

c. Error Type 513: the link has experienced downlink flow control, meaning that some<br />

information packets from the packet interface board have been lost. The link is reset on first<br />

occurrence <strong>and</strong> Error 1025 is also logged. The system link is alarmed if 2 or more <strong>error</strong>s of<br />

this type are detected within 10 minutes.<br />

1. Follow the information in Common Procedure for Repairing Link Problems.<br />

2. Clear <strong>error</strong>s <strong>and</strong> wait for 10 minutes.<br />

d. Error Type 772: the link experienced a temporary disconnect due to excessive resets or<br />

state transitions, meaning that the link is taken down <strong>and</strong> then brought up again. The<br />

system link is alarmed if 2 or more <strong>error</strong>s of this type are detected within 10 minutes.<br />

1. Follow the information in Common Procedure for Repairing Link Problems.<br />

2. Clear <strong>error</strong>s <strong>and</strong> wait for 10 minutes.<br />

e. Error Type 1025: the link has been reset, meaning that information packets queued at the<br />

time of reset are lost. The system link is alarmed if 20 or more <strong>error</strong>s of this type are<br />

detected within 10 minutes.<br />

1. Follow the information in Common Procedure for Repairing Link Problems.<br />

2. Clear <strong>error</strong>s <strong>and</strong> wait for 10 minutes.<br />

f. Error Type 1281: the link has experienced slow transmit rate because the remote endpoint<br />

is busy. The effect of this <strong>error</strong> is that the endpoint location may experience slower<br />

throughput rate <strong>and</strong>/or noisy transmission. The system link is alarmed if 4 or more <strong>error</strong>s of<br />

this type are detected within 10 minutes.<br />

1. Ensure that the remote endpoint is functioning properly.<br />

2. Follow the information in Common Procedure for Repairing Link Problems.<br />

3. Clear <strong>error</strong>s <strong>and</strong> wait for 10 minutes.<br />

g. Error Type 1537: the link has experienced slow transmit rate due to excessive<br />

retransmission. Possible causes may be that the switch is overrunning the endpoint, or that<br />

the endpoint is not operating properly. The effect is that the endpoint location may<br />

experience slower throughput rate. The system link is alarmed if 4 or more <strong>error</strong>s of this<br />

type are detected within 10 minutes.<br />

1. Follow the information in Common Procedure for Repairing Link Problems.<br />

2. Clear <strong>error</strong>s <strong>and</strong> wait for 10 minutes.<br />

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