BSC Alarm List and Its Description
BSC Alarm List and Its Description
BSC Alarm List and Its Description
Possible Causes The E1/T1 links on the Ater interface are fault The interface boards are running abnormally. The configuration of the internal signaling links are modified.
Possible Causes The E1 port where the HDLC is configured is faulty. The board where the HDLC is configured is faulty. The interface board for BTS transmission is faulty.
Possible Causes The GEPUG is faulty. The NSVC is blocked. The bearer channel is inaccessible. The configuration of the BSC and SGSN is faulty.
Possible Causes The GFGUG is faulty; The IP communication between the BSC and the SGSN is disconnected; The configuration of the BSC and SGSN is faulty.
Possible Causes The transmission device or transmission link between the BSC and the BTS is faulty. The Abis interfaced board of the BSC is faulty. The BTS experiences power failure. The TMU board or E1 lightning protection board of the BTS is faulty
Possible Causes The network is unstable and the intermittent link is caused. The E1 cable is faulty. The BTS or the PCU at the peer end is faulty.
Possible Causes If the GOMU is faulty, the possible causes are as follows: A pair of GOMUs is configured for the BSC, but only one GOMU is operating. A pair of GOMUs is configured for the BSC, but on the operating standby GOMU, the OMU software is stopped or the startup of the OMU software fails. A pair of GOMUs is configured for the BSC, but the standby GOMU is reset. A pair of GOMUs is configured for the BSC and the OMU software on the operating standby GOMU runs normally, but the communication link between the active GOMU and the standby GOMU is faulty. If the board other than the GOMU is faulty, the possible causes are as follows:
If all boards in a subrack are faulty, the Ethernet cable between this subrack and the GMPS may be disconnected. If all boards in the TC subrack are faulty, the OML on the Ater interface may be disconnected or the Ethernet cable between the main subrack and the extension subrack may be disconnected. If an individual board in a subrack is faulty, the board may be manually removed from the subrack, switched over, or reset. If an individual board in a subrack is faulty, the board is reset because hardware or software fault occurs on the board.
Possible Causes The communication between the CPUs of the service boards is abnormal. The CPU is faulty.
Possible Causes This alarm is reported when the duration that ASP protection section uses different channels to send the K1 byte and to receive the K2 byte exceeds the five seconds.
Possible Causes The boards in the GTCS on the Ater interface are reset or faulty. The physical line carrying the OML on the Ater interface is faulty.
Possible Causes The link code of the port of the BSC interface board is inconsistent with that of the interface board of the peer NE. The E1/T1 cable of the BSC interface board is connected improperly. The clock source of the BSC and that of the peer equipment are different. The BSC subracks are grounded improperly.
Alcatel-Lucent Proprietary and Confidential
The transmission equipment or transmission link between the BSC and the peer equipment is faulty.
Possible Causes No signal is detected between the peer equipment (BTS or BSC) and the transmission equipment, whereas the transmission equipment is normally connected with the local equipment.