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 234: SNC-REF Error Log Entries 2 of 2<br />

Error<br />

Type<br />

Aux<br />

Data<br />

SNI<br />

Slot 1<br />

Associated Test Alarm<br />

Level<br />

SNC-REF (Switch Node Clock Reference)<br />

On/Off<br />

Board<br />

3585 (b) Any 19 Failure audit (#777) MAJ OFF <strong>test</strong> board location<br />

3841 (b) Any 20 Failure audit (#777) MAJ OFF <strong>test</strong> board location<br />

1. The slot location of the SNI with which the SNC cot communicate.<br />

Recommended Action<br />

2 of 2<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. This <strong>error</strong> occurs when the active or st<strong>and</strong>by SNC detects problems in its timing reference<br />

with an SNI circuit pack in the same carrier. The slot location of the SNI with which the SNC<br />

cot communicate is given in the previous <strong>error</strong> table.<br />

If duplicated SNCs exist in the carrier:<br />

1. If the SNCs are duplicated in the carrier, use display <strong>error</strong>s to check the <strong>error</strong> log.<br />

If both SNCs have this <strong>error</strong>, replace the SNI that the SNCs are complaining about.<br />

2. If the <strong>error</strong> occurred only on the st<strong>and</strong>by SNC <strong>and</strong> the active SNC in the carrier does<br />

not have this <strong>error</strong>, use reset board to reset the st<strong>and</strong>by SNC. Use status<br />

switch-node to show the active <strong>and</strong> st<strong>and</strong>by SNCs. If the <strong>error</strong> returns after the<br />

st<strong>and</strong>by has been reset, replace the st<strong>and</strong>by SNC.<br />

3. Retry the comm<strong>and</strong>. If this <strong>error</strong> is still in the <strong>error</strong> log, continue with the following<br />

steps.<br />

4. If the active SNC has this <strong>error</strong>, use set switch-node-clock to set the st<strong>and</strong>by<br />

SNC to active. If the new active SNC has this <strong>error</strong>, replace the SNI that the SNC is<br />

complaining about. Otherwise, replace the SNC that originally had this <strong>error</strong>.<br />

If only one SNC exists in the carrier:<br />

5. Replace the SNI that the SNC is complaining about.<br />

6. Retry the comm<strong>and</strong>. If this <strong>error</strong> is still in the <strong>error</strong> log, continue with the following step.<br />

7. Replace the SNC.<br />

Issue 5 May 2009 859

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

Saved successfully!

Ooh no, something went wrong!