DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-1856UDS1-BD (UDS1 Interface Circuit Pack)
9
Red Alarm Inquiry Test (#140)
A UDS1 Interface circuit pac k raises a Red alarm when the framing pattern of the
incoming DS1 bit stream has bee n lost. The Red Alarm Inquiry Test checks the
framing status of a UDS1 Interface circ uit pack. A UDS1 Interface circ uit pack
takes 3 seconds to recog nize and report a Red alarm and 10 seconds to
recognize and repor t the resolution of a Red alarm.
When the UDS1 Interface circuit pac k detects a Red alarm, the c ircuit pack will
transmit a Yellow alarm to the remote DS1 endpoint and send a RED ALARM
message to the maintenance software. After the Red alarm is confirmed, the
maintenance software places all t runks or ports of the circuit p ack into the
1795 FAIL The UDS1 Interface circuit pack detects a Payload Loopback Alarm (PLB). If
the UDS1 Interface circuit pack connects to a leased T1 facility, call the vendor
of the T1 carrier to diagnose the remote DS1 endpoint. If the UDS1 Interface
circuit pack connects d irectly to another DS1 board, call the system technician
of the remote switch to diagnose the DS1 endpoint. If the UDS1 Interface circuit
pack connects directly to a line-side terminating devic e such as a PRI terminal
adapter contact the vendor of the terminating device to d iagnose the
equipment.
PASS Remote DS1 endpoint is in-service. Neither a Blue alarm nor a Line Loopback
alarm nor a Payload Loopback Alarm is detected by the UDS1 Interface circuit
pack.
0NO
BOARD The test could not relate the internal ID to the port (no board). This could be due
to incorrect translations, no board is inserted, an incorrect board is inserted, or
an insane board is insert e d.
1. Ensure that the board translations are correct. Execute the add ds1
UUCSS command to administer the UDS1 interface if it is not already
administered.
2. If the board was already administered correctly, check the error log to
determine whether the board is hyperactive. If this is the case, the b oard is
shut down. Reseating the board will re-initialize the board.
3. If the board was found to be correctly inserted in step 1, then issue the
busyout board command.
4. Issue the reset board command.
5. Issue the release busy board command.
6. Issue the test board long command.
This should re-establish the linkage between the internal ID and the port.
Table 9-688. TEST #139 Blue Alarm Inquiry Test — Continued
Error
Code Test
Result Description/ Recommendation
Continued on next page