Demand test descriptions and error codes - Avaya Support
19.12.2012 • Views
Share Embed Flag

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
ePAPER READ
DOWNLOAD ePAPER
support.avaya.com

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

START NOW

SYS-LINK (System Links)<br />

h. Error Type 1793: This <strong>error</strong> indicates that the link has experienced slow transmit rate due to<br />

unknown causes, meaning that the endpoint location may experience slower throughput<br />

rate <strong>and</strong> the Packet Interface may experience backup or congestion. The system link is<br />

alarmed if 4 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 />

i. Error Type 2049: the link has transmitted an excess amount of packets. The transmit<br />

buffers of this link have been purged. The system link is alarmed if 4 or more <strong>error</strong>s of this<br />

type are detected within 10 min.<br />

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

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

<strong>Dem<strong>and</strong></strong> <strong>test</strong> <strong>descriptions</strong> <strong>and</strong> <strong>error</strong> <strong>codes</strong><br />

Testing for system links is different from the st<strong>and</strong>ard <strong>test</strong> procedures for MOs. In addition to<br />

<strong>test</strong>ing the system link MO, the user can <strong>test</strong> every component in the path of the system link.<br />

There are two paths preserved for the link. The current path, if present, represents the path<br />

traversed by the link currently. This path is absent when the link is down. The other path, the<br />

faulted path, is present if the link has ever gone down or never come up. If the link came up <strong>and</strong><br />

went down, then the Faulted Path is marked present. If the link never came up, the Faulted<br />

Path is marked default. In either case, it represents the path on which the link was attempted or<br />

established unsuccessfully.<br />

Test comm<strong>and</strong> for the system links, <strong>test</strong> sys-link location, can be specified with current<br />

or faulted as an optional argument if the user wishes to <strong>test</strong> every component in the specified<br />

path. The <strong>test</strong>s executed are the same if the user <strong>test</strong>s each component manually. In the event<br />

that the user does not specify any path, then only the <strong>test</strong>s specified for the system links are<br />

executed.<br />

Order of Investigation Short Test<br />

Sequence<br />

System Link Status Test<br />

(#985)<br />

Long Test<br />

Sequence<br />

D/ND<br />

X X Non-Destructive<br />

Issue 5 May 2009 929

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!