Filter
Top Products
Communication Manager Maintenance-Object Repair Procedures
1998 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
4. If the PN’s LEDs are lit and there are multiple fibers to the distant switch node, remove the
SNC that is listed by list fiber-link for this path.
If not, enter list fiber-link to verify that the fiber connections to the PN are consistent
with the administration assignments.
5. Use status sys-link to determine the new path from the IPSI connected PN to the
distant switch.
6. Run test led port-network on the port network connected to the distant switch node,
and verify that the LEDs on the correct PN are lit.
7. Repeat steps 4 – 6 until every SNI-to-SNI fiber connection to the distant switch has been
tested.
Processor Route Audit Test (#760)
This test is nondestructive.
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 up-link 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 in-line errors to the server.
As each SNI receives its processor route, the SNI returns a “board insertion” up-link 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.
Use 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.
Table 737: TEST #760 Processor Route Audit Test
Error
Code
Test
Result
Description / Recommendation
2100 ABRT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 3 times.
2300 ABRT 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 ABRT 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.
1 of 2