Avaya 03-300430 Home Security System User Manual


  Open as PDF
of 2574
 
Communication Manager Maintenance-Object Repair Procedures
1498 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Serial Channel Local Loop-Around Test (#229)
This test checks TN775D on-board circuitry associated with the serial links to the Expansion
Interface circuit packs. A request is sent to the PN’s Maintenance circuit pack over the active
link via the active Expansion Interface circuit pack serial interface circuitry to test the serial
interface circuitry of the standby Expansion Interface circuit pack link. If a response is received,
then by definition the serial interface circuitry associated with the active link is good.
The PN’s Maintenance circuit pack has 3 separate serial interfaces, one to each of the
following:
Management terminal which is tested by Test #228
Active EI circuit pack which is tested by Test #229
Standby EI circuit pack which is tested by Test #229
PASS The serial interface circuitry on the PN’s Maintenance circuit pack which
controls the PN-connected terminal is functioning properly. If there are still
troubles with the PN G3-MT terminal, the problem may be one of the
following:
1. The PN-connected terminal is not configured properly. The
connection between the terminal and the PN’s Maintenance circuit
pack must be set up at 9600 bps.
2. The serial link from the back of carrier A to the PN terminal may be
defective. The serial link consists of the connector on the back of
carrier A labeled TERM and the ribbon cable running to the terminal.
3. The terminal may be defective. Try another terminal.
4. Since this test is not 100 percent accurate, there may still be problems
with the PN’s Maintenance circuit pack.
Table 537: Test #228 Management Terminal Channel Local Loop-Around Test (continued)
Error
Code
Test
Result
Description / Recommendation
2 of 2
Table 538: Test #229 Serial Channel Local Loop-Around Test
Error
Code
Test
Result
Description / Recommendation
1000 ABRT System resources required to run this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 3