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.

2. Use change circuit-pack to reassign the slot to match the existing circuit pack. If<br />

a fiber is assigned for the existing circuit pack, remove the fiber from translations<br />

before changing the circuit pack’s translations.<br />

d. Error Type 131: an EI circuit pack has been removed from a slot for 5 minutes. The alarm<br />

will be resolved when the EI circuit pack is physically inserted into this slot <strong>and</strong> becomes<br />

recognized by software.<br />

Another way to resolve this alarm is to use change circuit pack to remove the EI<br />

circuit pack administrative entry for this slot after the EI circuit pack has been removed<br />

from the slot.<br />

It is also possible that the EI could be held in reset by the PN’s Maintenance board<br />

(MAINT) <strong>and</strong> is not inserted in the system. Enter <strong>test</strong> maint P long on the<br />

Maintenance board in the same PN.<br />

e. Error Type 257: this EI circuit pack is detecting incorrect data on the incoming fiber bit<br />

stream. The data is originating at the connected circuit pack (DS1 converter circuit pack, EI<br />

circuit pack, or SNI circuit pack).<br />

1. Enter display <strong>error</strong>s <strong>and</strong> save a copy of the <strong>error</strong> log for use in later steps.<br />

Intervening repair procedures are likely to alter the contents of the <strong>error</strong> log <strong>and</strong> this<br />

information may be needed in later steps.<br />

2. Perform the Fiber link fault isolation procedures described in Maintenance Procedures<br />

for <strong>Avaya</strong> Aura Communication Manager, Media Gateways <strong>and</strong> Servers<br />

(03-300432).<br />

3. If <strong>error</strong>s are still present or if this <strong>error</strong> occurs intermittently, replace the EI circuit<br />

packs, SNI circuit packs, DS1 converter circuit packs, or the transceivers on this link.<br />

4. These <strong>error</strong>s could result from a bad timing reference on the network or switch node<br />

that contains the DS1 converter, EI, or SNI circuit pack on the opposite end of the fiber.<br />

Refer to the <strong>error</strong> log that was saved in step 1 <strong>and</strong> follow the associated repair<br />

procedure for EXP-INTF (Expansion Interface Circuit Pack) <strong>error</strong> 2305 to resolve this<br />

<strong>error</strong>. If there are any TONE-BD (Tone-Clock Circuit Pack), TDM-CLK (TDM Bus<br />

Clock), or SYNC (Port Network Synchronization) <strong>error</strong>s, resolve these <strong>error</strong>s as well.<br />

f. Error Type 513 with Aux Data 5–7: an ON BOARD hardware failure of the circuit pack’s<br />

RAM or ROM. Replace the EI circuit pack.<br />

g. Error Type 769: Besides running the <strong>test</strong> sequence <strong>and</strong> following procedures outlined for<br />

Expansion Interface Fiber Out-of-Frame Query Test (#238), perform the Fiber link fault<br />

isolation procedures described in Maintenance Procedures for <strong>Avaya</strong> Aura<br />

Communication Manager, Media Gateways <strong>and</strong> Servers (03-300432).<br />

h. Error type 1281: The link to the neighbor circuit pack is broken or the fibers have been<br />

connected incorrectly. Enter <strong>test</strong> board location <strong>and</strong> follow repair procedures for the<br />

<strong>test</strong>s.<br />

i. Error Type 1538: a hyperactive EI circuit pack is generating an abnormal amount of control<br />

messages to the Processor. When this <strong>error</strong> was generated, the EI was automatically reset<br />

by the system. If this system does not have duplicated Port Network Connectivity, service to<br />

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