Demand test descriptions and error codes - Avaya Support

Switch Node Interface Reset Test (#761)
Switch Node Interface Reset Test (#761)
This test is destructive.
This test resets the SNI circuit pack using reset board location when an SNI circuit
pack’s location is entered. The SNI is reset via the active SNC circuit pack in the carrier. If the
SNI is connected to an IPSI-connected PN’s EI, the SNI is reset via its IPSI-connected PN’s EI
neighbor. If an SNI with a non IPSI-connected PN’s EI or another SNI as its neighbor cot be
reset via the active SNC (i.e., if no software communication exists between the active SNC and
the server), an attempt will be made to reset the SNI via its neighbor.
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 cot 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.
This test runs on SNI-BD (SNI Circuit Pack) and SNI-PEER (SNI Peer Link).
Table 442: Switch Node Interface Reset Test (#761) 1 of 3
Error
Code
Test
Result
Description / Recommendation
2100 ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 3 times.
2300 ABORT The downlink message necessary to run this test could not be sent.
1. Retry the command at 1-minute intervals up to 3 times.
2301 ABORT The software timer could not be set before sending the downlink
message necessary to run this test.
1. Retry the command at 1-minute intervals up to 3 times.
2302 ABORT Software received incorrect message data from the SNI circuit pack.
1. Retry the command at 1-minute intervals up to 3 times.
2303 ABORT The SNI circuit pack responded that the test requested is invalid.
1. Retry the command at 1-minute intervals up to 3 times.
2304 ABORT SNI circuit pack is not able to run the test requested by software.
1. Retry the command at 1-minute intervals up to 3 times.
1 of 3
Issue 5 May 2009 1481