Avaya 03-300430 User Manual

Page of 2574
Communication Manager Maintenance-Object Repair Procedures
2178 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
 
b. Error Type 257: the link has experienced uplink flow control, and the endpoint may be 
hyperactive. The system link is alarmed if 4 or more errors of this type are detected within 
10 minutes.
1. Follow the information in 
2. Clear errors and wait for 10 minutes.
c. Error Type 513: the link has experienced downlink flow control, meaning that some 
information packets from the packet interface board have been lost. The link is reset on first 
occurrence and Error 1025 is also logged. The system link is alarmed if 2 or more errors of 
this type are detected within 10 minutes.
1. Follow the information in 
2. Clear errors and wait for 10 minutes.
d. Error Type 772: the link experienced a temporary disconnect due to excessive resets or 
state transitions, meaning that the link is taken down and then brought up again. The 
system link is alarmed if 2 or more errors of this type are detected within 10 minutes.
1. Follow the information in 
2. Clear errors and wait for 10 minutes.
e. Error Type 1025: the link has been reset, meaning that information packets queued at the 
time of reset are lost. The system link is alarmed if 20 or more errors of this type are 
detected within 10 minutes.
1. Follow the information in 
2. Clear errors and wait for 10 minutes.
f. Error Type 1281: the link has experienced slow transmit rate because the remote endpoint 
is busy. The effect of this error is that the endpoint location may experience slower 
throughput rate and/or noisy transmission. The system link is alarmed if 4 or more errors of 
this type are detected within 10 minutes.
1. Ensure that the remote endpoint is functioning properly.
2. Follow the information in the previous section, 
3. Clear errors and wait for 10 minutes.
g. Error Type 1537: the link has experienced slow transmit rate due to excessive 
retransmission. Possible causes may be that the switch is overrunning the endpoint, or that 
the endpoint is sick. The effect is that the endpoint location may experience slower 
throughput rate. The system link is alarmed if 4 or more errors of this type are detected 
within 10 minutes.
1. Follow the information in 
2. Clear errors and wait for 10 minutes.