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

Create successful ePaper yourself

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

Maintenance Object Interactions<br />

● Packet Bus maintenance<br />

A Packet Interface physically interacts with the PKT-BUS. It may be difficult to isolate faults<br />

to one or the other component for certain types of Packet Interface <strong>error</strong>s. In each of these<br />

cases, Packet Interface maintenance forwards an <strong>error</strong> report to packet bus maintenance,<br />

where it records a packet bus fault in the <strong>error</strong> log <strong>and</strong> runs Packet Bus <strong>test</strong>s.<br />

● Packet Interface maintenance<br />

The operation of the IPSI circuit pack’s Packet Interface module affects the operation <strong>and</strong><br />

maintenance of other circuit packs connected to the packet bus. This includes:<br />

1. BRI applications (BRI-PT)<br />

2. Universal DS1 applications (UDS1) for ISDN/PRI applications<br />

3. S8700-series Fiber-PNC: Expansion Interface circuit pack maintenance (EXP-INTF)<br />

Some packet <strong>error</strong>s require examination of the Packet Interface’s operating status. To obtain<br />

this information:<br />

● Examine the Error <strong>and</strong> Alarm Logs for PKT-INT entries <strong>and</strong> determine which PKT-INT<br />

the link is accessing.<br />

● Use status sys-link to identify the PKT-INT location in this PN, or use status<br />

sys-link to find the PKT-INT hardware used by the faulted link.<br />

● Use <strong>test</strong> sys-link to troubleshoot the component.<br />

● Use status packet-interface to determine the:<br />

- service state of the Packet Interface, for example, in service/out of service<br />

- total number of Packet Interface links assigned to a Packet Interface.<br />

For a st<strong>and</strong>by IPSI’s Packet Interface module in a high- or critical-reliability system<br />

(duplicated IPSIs), the module is shown in st<strong>and</strong>by mode if it is not out-of-service<br />

because of a failure condition. The number of links for a st<strong>and</strong>by Packet Interface<br />

module is always zero.<br />

In general, if every link for an active IPSI’s Packet Interface module is shown as a Failed<br />

Link, there may be a fault on either the Packet Interface module or the packet bus that<br />

caused every link to go down. If only a small percentage of the links are shown as Failed<br />

Links, then the Packet Interface is probably not the source of the problem. Some typical<br />

sources of individual link failures include:<br />

● failed BRI telephone set<br />

● disconnected cord to a BRI set, causes three link failures<br />

● S8700-series Fiber-PNC: failed or removed EI circuit pack in a PN, causes one link failure<br />

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