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.

. This <strong>error</strong> occurs when the active SNC determines that there is a problem communicating<br />

with an SNI circuit pack in the same carrier via the connecting multiprocessor serial chel<br />

used for transmitting CSCN messages. The slot location of the SNI with which the SNC cot<br />

communicate is given in SNC-LINK Error Log Entries.<br />

1. Use display <strong>error</strong>s to check the <strong>error</strong> log.<br />

2. If a SNI-PEER <strong>error</strong> exists in the <strong>error</strong> log, follow the repair procedures for SNI-PEER<br />

(SNI Peer Link).<br />

3. If the SNC has SNC-LINK <strong>error</strong>s with Aux Data of 1 against other SNIs <strong>and</strong>/or has<br />

SNC-BD <strong>error</strong> 513, replace the SNC circuit pack.<br />

4. If SNIs in the same carrier have SNI-BD <strong>error</strong> 257 logged indicating they are having<br />

trouble communicating with the SNC, replace the SNC circuit pack.<br />

5. Use list configuration carrier to determine whether an SNI is physically<br />

present in the slot pointed to by the SNC-LINK <strong>error</strong>.<br />

● If the Vintage field indicates that a circuit pack is present, proceed to step 6.<br />

● If the Vintage field shows no board:<br />

If an SNI should not be installed in this slot:<br />

- Remove the SNI from circuit pack administration with change circuit-pack.<br />

- If the <strong>error</strong> remains, re-administer the SNI circuit pack <strong>and</strong> then remove it from<br />

administration again.<br />

- If the <strong>error</strong> still remains, replace the active SNC circuit pack.<br />

If an SNI should be installed in this slot, but is missing, insert an SNI circuit pack.<br />

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

7. Retry the comm<strong>and</strong>. If this <strong>error</strong> is still in the <strong>error</strong> log:<br />

8. Replace the SNC circuit pack.<br />

9. If a st<strong>and</strong>by SNC (the one with its yellow LED off) has this <strong>error</strong>, escalate the problem.<br />

Use status switch-node to show the active <strong>and</strong> st<strong>and</strong>by SNCs.<br />

c. This <strong>error</strong> occurs when the active SNC determines that there is a problem communicating<br />

with an SNI circuit pack in the same carrier via the TPN communication chel. The slot<br />

location of the SNI with which the SNC cot communicate is given in Table 233: SNC-LINK<br />

Error Log Entries.<br />

1. Use display <strong>error</strong>s to check the <strong>error</strong> log. If more than one SNI in the same carrier<br />

have SNI-BD <strong>error</strong>s with Error Type 769, replace the SNC.<br />

2. Use display <strong>error</strong>s to check the <strong>error</strong> log. If the SNC has more than one<br />

SNC-LINK <strong>error</strong> with Aux Data of 2, replace the SNC.<br />

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