Server Alarms - Avaya Support

Table 542: TPN Test (#779) 3 of 3
Error
Code
Test
Result
0 NO
BOARD
Description / Recommendation
Switch Node Clock Reset Test (#780)
Switch Node Clock Reset Test (#780)
No board was detected by the test.
1. Check that SNC board is properly translated and inserted.
2. Run the test again. If it fails, reset the board. An SNC should be reset
instead of reseating the circuit pack. The reset board command
should almost never be used on an SNC. It may be necessary to use
reset board if the SNC circuit pack gets into a mode where it
cannot communicate with software. If an SNC with active errors and
alarms is reset, the errors and alarms may take a while to come back,
therefore reset board can mask real problems.
3. Run the test again. If it fails, the ID chip on board may be bad.
Replace the board and retest.
3 of 3
This test is destructive.
This test resets the SNC circuit pack using reset board location when an SNC circuit
pack location is entered. If the system has PNC duplication, the active SNC on the active PNC
cannot be reset.
If the SNC is active and reset board is executed, an SNI in the same carrier as the SNC will
be told by software to reset the SNC via the TPN link. If no inserted SNIs in the same carrier as
the SNC can successfully reset the SNC, software will send a “reset” message directly to the
SNC. Software first tries to reset the SNC via an SNI in case the SNC is insane because the
latter method (sending the “reset” message directly to the SNC) will not work if the SNC is
insane.
If an active SNC is reset and a standby SNC exists in the same switch node carrier, the standby
SNC becomes active. Enter set switch-node-clock location to make a standby SNC
active.
If the SNC is standby and reset board is executed, the active SNC is told by software to
reset the standby SNC via the TPN link.
An SNC should be reset instead of reseating the circuit pack. The reset board command
should almost never be used on an SNC. It may be necessary to use reset board if the SNC
circuit pack gets into a mode where it cannot communicate with software.
Communication Manager Release 5.0 Issue 4 January 2008 1847