DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures

9-1481SNI-BD (SNI Circuit Pack)

9
Clear Firmware Counters (#982)

This test number is used to report unsuc cessful results of the clear

firmware-counters command. This is not an actual d emand maintenance test. If

the command aborts, refer to th e error codes listed for Test #777.

SNI Fiber Out of Frame Query (#989)
This test is non-destructive.
FAIL The SNI circuit pack reported failures or retransmitted a cleared failure
message.
1. If this is the first time this test was run, run the test again. If there were any
previous failure messages that software did not acknowledge, this test will
FAIL even if the failure messages indicate a FAIL to PASS transition, i.e., a
problem has gone away. If this test is run twice and FAILs both times, then
at least one problem still exists.
2. Fix any SNI-BD, SNI-PEER, and FIBER-LK errors by following the
associated repair procedures. Use the display errors and display alarms
commands with category PNC for SNI-BD and FIBER-LK and category
PNC-PEER for SNI-PEER. Fix any problems found by referring to the SNI
Board or SNI Peer Error Log Entries tables in this section or F iber Link E rror
Log Entries tables in the ‘‘FIBER-LK (Fiber Link)’’ section.
3. If n o SNI-BD , SNI-PEER, o r FIBER-LK e ntries exist i n the er ror and alarm
logs, retry the command.
PASS No problems are detected on the board.
0NO
BOARD No board was detected by the test.
1. Check that board is properly translated and inserted.
2. Run the test again. If it fails, reset the board. An SNI should be reset
instead of reseating the c ircuit pack. The reset board command should
almost never be used on an SNI. It may be necessary to use the reset
board command if the SNI circuit pack gets into a mode where it cannot
communicate with software. If an SNI with active errors and alarms is reset,
the errors and alarms may take a while to come back, therefore the reset
board command can mask real problems.
3. Run the test again. If it fails, the ID chip on board may be bad. Replac e the
board and retest.
Table 9-565. TEST #777 Failure Audit — Continued
Error
Code Test
Result Description/ Recommendation
Continued on next page