09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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 529: SNI Circuit Path Test (#755) 3 of 4<br />

Error<br />

Code<br />

102 -<br />

109,<br />

113 -<br />

120<br />

Test<br />

Result<br />

Description / Recommendation<br />

SNI Circuit Path Test (#755)<br />

FAIL The SNI circuit pack cannot communicate with the SNI in a different slot<br />

over the circuit path.<br />

1. Determine the slot number of the other SNI: Subtract 100 from the<br />

Error Code. For example, if the Error Code is 115, the SNI slot<br />

number is 15. This number is referred to as the "specified SNI slot".<br />

2. Fix any on-board SNI-BD errors against this SNI and the SNI in the<br />

specified SNI slot. Enter display errors to find any SNI-BD errors,<br />

and enter display alarms to see if the errors have on-board<br />

alarms. Follow the repair procedures for SNI-BD (SNI Circuit Pack).<br />

3. Enter display errors and check the error log for other SNI circuit<br />

packs with SNI-PEER errors. See Table 530: SNI Slot / Error Type to<br />

determine the Error Type for SNI-PEER. For example, if the specified<br />

SNI slot number is 13, look for SNI-PEER errors with Error Type 2049.<br />

If other SNI circuit packs have SNI-PEER errors with the same Error<br />

Type, replace the SNI in the specified SNI slot. Replacing an SNI may<br />

be service interrupting. See SNI-BD (SNI Circuit Pack) for the<br />

procedure for replacing an SNI.<br />

4. If other SNI circuit packs do not have SNI-PEER errors with the same<br />

Error Type, the problem could be at either of the peer SNI boards. It is<br />

arbitrary as to which SNI is replaced first.<br />

a. Replace this SNI.<br />

b. Replace the SNI in the specified SNI slot.<br />

3 of 4<br />

Communication Manager Release 5.0 Issue 4 January 2008 1799

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

Saved successfully!

Ooh no, something went wrong!