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.

Table 260: TDM-CLK Error Log Entries 2 of 2<br />

Error<br />

Type<br />

769 (g) Any Clock Circuit Status<br />

inquiry (#148)<br />

1025 (h) Any Clock Slip inquiry<br />

(#149)<br />

1281<br />

1282 (i)<br />

Aux<br />

Data<br />

Associated Test Alarm<br />

Level<br />

Any MIN OFF<br />

1537 Any Clock PPM inquiry<br />

(#150)<br />

2049 (j) Any St<strong>and</strong>by Reference<br />

Health Check <strong>test</strong><br />

(#651)<br />

On/Off<br />

Board 1<br />

2305 (k) 0 WRN OFF<br />

Recommended Action<br />

MAJ‡ ON <strong>test</strong> tone-clock location r 10<br />

<strong>test</strong> tone-clock location<br />

<strong>test</strong> tone-clock location<br />

MAJ 2 ON <strong>test</strong> tone-clock location<br />

1. As a general rule, any on-board <strong>error</strong>s against the TDM Bus Clock should be resolved before pursuing any<br />

other <strong>error</strong>s against PNC components. Off-board clock <strong>error</strong>s may be caused by other board <strong>error</strong>s, <strong>and</strong><br />

should be addressed after on-board <strong>error</strong>s have been resolved.<br />

2. Major or Minor alarms on this MO may have been downgraded to Warning based on the values in set<br />

options.<br />

Notes:<br />

a. Error Type 0: run the short <strong>test</strong> sequence first. If every <strong>test</strong> passes, run the long <strong>test</strong><br />

sequence. Refer to each appropriate <strong>test</strong>’s description, <strong>and</strong> follow its recommended<br />

procedures.<br />

b. Error Type 1: the IPSI or Tone-Clock circuit pack may have a clock at the edge of its<br />

specified frequency. This can cause Expansion Interface circuit packs <strong>and</strong> SNI circuit packs<br />

to go out-of-frame or report no-neighbor conditions. This can is turn cause EPNs,<br />

Expansion Archangel Links (EALs), Remote Neighbor Links (RNLs), <strong>and</strong>/or Local Neighbor<br />

Links (LNLs) to go down. When this <strong>error</strong> is alarmed, the Clock Health Inquiry <strong>test</strong> (#46) will<br />

fail with an Error Code of 1.<br />

1. Replace the IPSI or Tone-Clock circuit pack identified in the <strong>error</strong> log. See Replacing<br />

the IPSI or Tone-Clock Circuit Pack.<br />

c. Error Type 18: the indicated Tone-Clock circuit has been made unavailable using busyout<br />

tone-clock location. It only applies to systems with the high- or critical-reliability<br />

option administered, because only a st<strong>and</strong>by Tone-Clock circuit may be made busy by that<br />

comm<strong>and</strong>. To resolve this <strong>error</strong>, execute release tone-clock location for the<br />

alarmed circuit pack.<br />

d. Error Type 130: the circuit pack has been removed or has been insane for more than 11<br />

minutes. To clear the <strong>error</strong>, reinsert or replace the circuit pack.<br />

966 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers<br />

2 of 2

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

Saved successfully!

Ooh no, something went wrong!