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.

Identifying a System Link<br />

In order to trace problems associated with a system link, it is necessary to find its location. Use<br />

the following methods to find the location of the system link.<br />

Display Errors/Alarms<br />

The output of display <strong>error</strong>s or display alarms shows the location of the system link for<br />

entries with a Maintenance Name of SYS-LINK. You can restrict the scope of the output of these<br />

comm<strong>and</strong>s by specifying sys-link in the Category field on the input screen. The link type <strong>and</strong><br />

chel number, if any, are listed under the Alt Name field of the report.<br />

List sys-link<br />

The list sys-link comm<strong>and</strong> lists every system link (location, link type, <strong>and</strong> dlci number)<br />

present in the system.<br />

Common Procedure for Repairing Link Problems<br />

The state of a system link is dependent on the state of the various hardware components that it<br />

travels over. To resolve any problems associated with a system link, use the following<br />

procedure.<br />

The switch maintains a list of hardware components over which the link travels, called the<br />

hardware path. There are two hardware paths: the current hardware path <strong>and</strong> the faulted<br />

hardware path for each of the system links. The current hardware path is present only for those<br />

links that are currently up. When a link is down, the current hardware path is empty. The faulted<br />

hardware path is always present once the link has gone down, <strong>and</strong> is not cleared when the link<br />

subsequently recovers. The faulted path preserves the path that the link traversed when it last<br />

went down. The time at which the faulted path was last recorded is preserved <strong>and</strong> is accessible<br />

through status sys-link location <strong>and</strong> list sys-link. Therefore, the focus of<br />

attention for problems which do not involve a link that is down is the current hardware path. If<br />

the link is down, faulted hardware path is the focus of attention.<br />

The status sys-link location comm<strong>and</strong> shows the state of both the hardware paths<br />

(current <strong>and</strong> faulted) along with the state of each of the components in the hardware path. When<br />

analyzing any system link problem:<br />

1. Look for alarms on the components listed under desired hardware path.<br />

2. If any alarms are present, then follow the maintenance procedures for the alarmed<br />

components to clear those alarms first.<br />

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