Blue Alarm Inquiry Test (#139)

The Blue Alarm is a signal sent by the remote DS1 endpoint when it is out-of-service. The Blue Alarm Inquiry Test checks the blue alarm status of the remote DS1 endpoint.

When the DS1-MM Interface Media Module detects a Blue Alarm signal from the remote DS1 endpoint, the Media Module transmits a Yellow alarm to the remote DS1 endpoint and sends a BLUE ALARM message to the maintenance software. When the Blue alarm is confirmed, the maintenance software places all trunks or ports of the DS1-MM Interface Media Module into the out-of-service state. The inquiry test runs every 10 minutes until the Blue alarm is cleared.

The DS1-MM Interface Media Module takes one second to recognize and report a Blue alarm and 16 seconds to recognize and report the resolution of a Blue alarm. When the Blue alarm is cleared, the DS1-MM Interface Media Module stops transmitting the Yellow alarm and places the trunks or ports back into the service state before the Blue alarm occurs.

Line Loopback Alarm

The Line Loopback (LLB) is used by the remote DS1 endpoint to put the DS1 board into a loopback mode. When the DS1 board is in the LLB mode, the arriving bit pattern is regenerated and sent back. The Line Loopback (LLB) Alarm activates when the in-band activate LLB bit pattern arrives continuously for 5 seconds on the DS1 line. The LLB deactivates when the in-band deactivate LLB bit pattern arrives continuously for 5 seconds on the DS1 line.

Since LLB is a maintenance condition rendering all DS0 channels unavailable for signaling or bearer traffic, maintenance software treats this the same as a Blue Alarm.

Payload Loopback Alarm

The Payload Loopback (PLB) is used by the remote DS1 endpoint to put the switch DS1 into a loopback mode. The PLB Alarm activates when a network protocol activate bit pattern arrives over the 4Kbps ESF data link on the DS1 line. The PLB deactivates when a network protocol deactivate bit pattern arrives over the 4Kbps ESF data link on the DS1 line.

Since PLB is a maintenance condition rendering all DS0 channels unavailable for signaling or bearer traffic, maintenance software treats this the same as a Blue Alarm

Table 66. TEST #139 Blue Alarm Inquiry Test �
Error Code	Test Result	Description/ Recommendation
	ABORT	Internal system error Retry the command at 1-minute intervals for a maximum of 5 times.
2000	ABORT	Response to the test was not received within the allowable time period. This may be due to hyperactivity. Error Type 1538 in the error log indicates hyperactivity. The hyperactive Media Module is out of service and one or more of the following symptoms may be exhibited. The DS1-MM tests (such as Test #138 and Test #139) are aborting with error code 2000. The tests run on the ports of this Media Module are returning a no board result. A busyout or a release command has no affect on the test results. A list config command shows that the Media Module and the ports are properly installed. When hyperactivity occurs, the Media Module is isolated from the system, and all of the trunks for this Media Module are placed into the out of service state. The system will try to restore the Media Module within 15 minutes. When no faults are detected for 15 minutes, the DS1-MM interface Media Module is restored to normal operation. All of the trunks for the DS1-MM interface Media Module are then returned to the in service state. Hyperactivity is often caused by the associated facility. In such a case, faults (such as slips, misframes, or blue alarms) would be entered in the error log. In addition, many hardware errors would be logged against the associated trunk circuits. If the facility is OK and the error occurs again after 15 minutes, replace the Media Module.
2100	ABORT	Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times.
	FAIL	The remote DS1 endpoint is out-of-service.
1 1794	FAIL	The DS1-MM Interface Media Module detects a Line Loopback Alarm (LLB). If the DS1-M interface Media Module connects to a T1 facility, call the vendor of the T1 carrier to diagnose the remote DS1 endpoint. If the DS1-mm interface Media Module connects directly to a switch, call the system technician of the remote switch to diagnose the DS1 endpoint. If theDS1-MM interface Media Module connects directly to a line-side terminating device (for example, a PRI terminal adapter), call the vendor of the terminating device to diagnose the equipment.
1795	FAIL	The DS1-MM Interface Media Module detects a Payload Loopback Alarm (PLB). If the DS1-MM Interface Media Module connects to a leased T1 facility, call the vendor of the T1 carrier to diagnose the remote DS1 endpoint. If the DS1-MM Interface Media Module connects directly to another DS1 board, call the system technician of the remote switch to diagnose the DS1 endpoint. If the DS1-MM Interface Media Module connects directly to a line-side terminating device such as a PRI terminal adapter contact the vendor of the terminating device to diagnose 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 DS1-MM Interface Media Module.
Any	NO 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 inserted. Ensure that the board translations are correct. Execute the add ds1 GGGVS command to administer the MM-DS1 interface if it is not already administered. If the board was already administered correctly, check the error log to determine whether the board is hyperactive. If this is the case, the board is shut down. Reseating the board will re-initialize the board. If the board was found to be correctly inserted in step 1, then issue the busyout board command. Issue the reset board command. Issue the release busy board command. Issue the test board long command. This should re-establish the linkage between the internal ID and the port.