Yellow Alarm Inquiry Test (#141)

Receiving a Yellow alarm from a remote DS1 endpoint indicates that the remote DS1 endpoint has an out-of-frame condition. The Yellow Alarm Inquiry Test is used to determine whether the remote DS1 endpoint is transmitting a Yellow alarm. The MG-DS1 Interface Media Module takes 500 msec to recognize and report a Yellow alarm and 500 msec to recognize and report that a Yellow alarm condition is cleared.

When the MM-DS1 Interface Media Module detects a Yellow alarm from the remote DS1 endpoint, it sends a YELLOW-ALARM uplink message to the maintenance software. After the maintenance software receives the YELLOW-ALARM message, the Yellow Alarm Inquiry Test is run to confirm the Yellow alarm. Once the Yellow alarm is confirmed, the maintenance software places all trunks or ports on the Media Module into the out-of-service state. The Inquiry Test runs every 10 minutes until the Yellow alarm is cleared.

When the Yellow alarm is cleared, the maintenance software restores all trunks or ports on the MG-DS1 Interface Media Module back to their previous service state before the Yellow alarm was raised.

This Yellow alarm corresponds to the yellow F2 state documented in CCITT Recommendation I.431.

Remote Multiframe Alarm

Remote Multiframe Alarm (RMA) indicates that the remote DS1 endpoint is in a Loss of Multiframe Alarm condition while the MG-DS1 Interface Media Module is administered using the DMI-BOS common channel signaling. The RMA is handled as a Yellow alarm.

Yellow F5 Fault Alarm

For 32-channel E1 operation with CRC4 on, the F5 fault state is defined as a fault in the user-network interface, specifically in the direction from the user (PBX) to the network. Refer to CCITT recommendation I.431.

Table 155. TEST #141 Yellow Alarm Inquiry Test
Error Code	Test Result	Description/ Recommendation
	ABORT	Internal system error Retry the command at 1-minute intervals 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 MG-DS1 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 MG-DS1 interface Media Module is restored to normal operation. All of the trunks for the MG-DS1 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.
	FAIL	The MG-DS1 interface Media Module detected a yellow alarm sent by the remote DS1 endpoint. An out of frame condition occurred at the DS1 endpoint. If the MM-DS1 connects to a T1 network facility or to another switch, do the following: Verify that both endpoints of the DS1 link are administered using the same signaling mode, framing mode, and line coding. Contact T1 Network Service or a technician at the far-end switch to diagnose the remote DS1 endpoint. Check the physical connectivity of the MG-DS1 packs and of the cable. Replace the local MG-DS1 interface Media Module, and repeat the test. If the MG-DS1 connects to a line-side terminating device (for example, a PRI terminal adapter), do the following: Verify that the switch DS1 and the line-side terminating device are administered using the same signaling mode, framing mode, and line coding. Investigate the maintenance status of the line-side terminating device. Refer to the 'Line-Side Terminating Device Operating Manual' for information. Contact the vendor of the line-side terminating device to diagnose the equipment. Check the physical connection of the MG-DS1 interface Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures. Replace the local MG-DS1 interface Media Module and repeat the test.
1	FAIL	The MG-DS1 interface Media Module detected a remote multiframe alarm (RMA) sent by the remote DS1 endpoint. An out of frame condition occurred at the DS1 endpoint. If the MG-DS1 connects to a T1 network facility or to another switch, do the following: Verify that both endpoints of the DS1 link are administered using the same signaling mode, framing mode, and line coding. Contact T1 Network Service or a technician at the far-end switch to diagnose the remote DS1 endpoint. Check the physical connectivity of the MG-DS1 packs and of the cable. Replace the local MG-DS1 interface Media Module, and repeat the test. If the MG-DS1 connects to a line-side terminating device (for example, a PRI terminal adapter), do the following: Verify that the switch DS1 and the line-side terminating device are administered using the same signaling mode, framing mode, and line coding. Investigate the maintenance status of the line-side terminating device. Refer to the 'Line-Side Terminating Device Operating Manual' for information. Contact the vendor of the line-side terminating device to diagnose the equipment. Check the physical connection of the MG-DS1 interface Media Module to the terminating device, and check the premise distribution system (or the intra-premise wiring) for physical connection failures. Replace the local MG-DS1 interface Media Module and repeat the test.
2	FAIL	The MG-DS1 interface Media Module is reporting a Yellow F5 fault alarm. There is a fault in the User-Network interface from the user (PBX) to the network. An out-of-frame condition occurs on the remote DS1 endpoint. If the MG-DS1 connects to a T1 network facility: Verify that both endpoints of the DS1 link are administered using the same signaling mode, framing mode, and line coding. Contact T1 Network Service to diagnose the remote DS1 endpoint. Check the physical connectivity of the DS1 Interface Media Modules and cable. Replace the local MG-DS1 Interface Media Module and repeat the test. If the MG-DS1 connects to a line-side terminating device such as a PRI terminal adapter: Verify that the switch DS1 and the line-side terminating device are administered using the same signaling mode, framing mode, and line coding. Investigate the maintenance status of the line-side terminating device. Refer to the 'Line-Side Terminating Device Operating Manual' for information. Contact the vendor of the line-side terminating device to diagnose the equipment. Check the physical connection of the MG-DS1 Interface Media Module to the terminating device. Check premise distribution system (or intra-premise wiring) for physical connection failures. Replace the local MG-DS1 Interface Media Module and repeat the test.
	PASS	Neither a Yellow alarm nor a Remote Multiframe Alarm nor a F5 state alarm is being received from the remote DS1 endpoint.
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 MG-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.