Server Alarms - Avaya Support

Communication Manager Maintenance Object Repair Procedures
Table 535: SNI-BD Configuration Audit (#759) 6 of 6
Error
Code
Test
Result
0 NO
BOARD
Description / Recommendation
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 circuit pack. The reset board command
should almost never be used on an SNI. It may be necessary to use
reset board 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
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.
Processor Route Audit Test (#760)
This test sends a processor route to every SNI in the carrier for which test board location
was run. A processor route enables an SNI board to send uplink messages to the server by
providing the board with a specific sequence of boards for routing messages up to the server.
Without a processor route, an SNI cannot send any inline errors to the server.
As each SNI receives its processor route, the SNI returns a “board insertion” uplink message,
and, if not already inserted, the server’s software inserts that board. Depending on the
configuration, each SNI board is sent either one or two processor routes.
Enter test led or list config carrier to see if the boards are inserted.
The processor route test is run as part of the long test sequence for SNC boards. It runs on the
following maintenance objects:
● SN-CONF (Switch Node Configuration)
● SNC-BD (Switch Node Clock Circuit Pack)
● SNC-LINK (Switch Node Clock Link)
● SNC-REF (Switch Node Clock Reference)
1828 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
6 of 6