PCU Alarm Guide

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling Contents

Issue 05 (2006-10-30) Huawei Technologies Proprietary i

Contents

1 1601 Gb Local End Out-of-sync........................................................................................... 1-1 1.1 Alarm Meaning..............................................................................................................................................1-1 1.2 Impact upon System......................................................................................................................................1-2 1.3 System Self-processing procedures...............................................................................................................1-2 1.4 Alarm Handling.............................................................................................................................................1-2

2 1602 Gb Local End Out-of-sync Removed......................................................................... 2-1 2.1 Alarm Meaning..............................................................................................................................................2-1 2.2 Impact upon System......................................................................................................................................2-1 2.3 System Self-processing procedures...............................................................................................................2-1 2.4 Alarm Handling.............................................................................................................................................2-2

3 1603 Gb Remote End Out-of-sync....................................................................................... 3-1 3.1 Alarm Meaning..............................................................................................................................................3-1 3.2 Impact upon System......................................................................................................................................3-1 3.3 System Self-processing procedures...............................................................................................................3-1 3.4 Alarm Handling.............................................................................................................................................3-2

4 1604 Gb Remote End Out-of-sync Removed .................................................................... 4-1 4.1 Alarm Meaning..............................................................................................................................................4-1 4.2 Impact upon System......................................................................................................................................4-1 4.3 System Self-processing procedures...............................................................................................................4-1 4.4 Alarm Handling.............................................................................................................................................4-2

5 1607 BC Added Failed to Work ........................................................................................... 5-1 5.1 Alarm Meaning..............................................................................................................................................5-1 5.2 Impact upon System......................................................................................................................................5-1 5.3 System Self-processing procedures...............................................................................................................5-1 5.4 Alarm Handling.............................................................................................................................................5-2

6 1609 BC Unavailable.............................................................................................................. 6-1 6.1 Alarm Meaning..............................................................................................................................................6-1 6.2 Impact upon System......................................................................................................................................6-1 6.3 System Self-processing procedures...............................................................................................................6-1 6.4 Alarm Handling.............................................................................................................................................6-2

Contents M900/M1800 Packet Control Unit

Maintenance Manual - Alarm Handling

ii Huawei Technologies Proprietary Issue 05 (2006-10-30)

7 1610 BC Available .................................................................................................................. 7-1 7.1 Alarm Meaning..............................................................................................................................................7-1 7.2 Impact upon System......................................................................................................................................7-1 7.3 System Self-processing procedures...............................................................................................................7-1 7.4 Alarm Handling.............................................................................................................................................7-2

8 1611 More PVCs Configured at Peer End.......................................................................... 8-1 8.1 Alarm Meaning..............................................................................................................................................8-1 8.2 Impact upon System......................................................................................................................................8-1 8.3 System Self-processing procedures...............................................................................................................8-1 8.4 Alarm Handling.............................................................................................................................................8-2

9 1612 More PVCs Configured at Local End ........................................................................... 9-1 9.1 Alarm Meaning..............................................................................................................................................9-1 9.2 Impact upon System......................................................................................................................................9-1 9.3 System Self-processing procedures...............................................................................................................9-1 9.4 Alarm Handling.............................................................................................................................................9-2

10 1670 BSSGP Cell Blocking Failed................................................................................... 10-1 10.1 Alarm Meaning..........................................................................................................................................10-1 10.2 Impact upon System..................................................................................................................................10-1 10.3 System Self-processing procedures...........................................................................................................10-1 10.4 Alarm Handling.........................................................................................................................................10-2

11 1671 BSSGP Cell Unblocking Failed.............................................................................. 11-1 11.1 Alarm Meaning..........................................................................................................................................11-1 11.2 Impact upon System ..................................................................................................................................11-1 11.3 System Self-processing procedures ...........................................................................................................11-1 11.4 Alarm Handling .........................................................................................................................................11-2

12 1672 BVC Resetting Failed ............................................................................................... 12-1 12.1 Alarm Meaning..........................................................................................................................................12-1 12.2 Impact upon System..................................................................................................................................12-1 12.3 System Self-processing procedures...........................................................................................................12-1 12.4 Alarm Handling.........................................................................................................................................12-2

13 1675 NSVC Link Fault....................................................................................................... 13-1 13.1 Alarm meaning ..........................................................................................................................................13-1 13.2 Impact upon System..................................................................................................................................13-1 13.3 System Self-Processing Procedure............................................................................................................13-1 13.4 Alarm Handling.........................................................................................................................................13-2

14 1676 NSVC Link Fault Recovered................................................................................... 14-1 14.1 Alarm meaning ..........................................................................................................................................14-1 14.2 Impact upon System..................................................................................................................................14-1 14.3 System Self-Processing Procedure............................................................................................................14-1


Issue 05 (2006-10-30) Huawei Technologies Proprietary iii

14.4 Alarm Handling.........................................................................................................................................14-1

15 1715 CRC4 Error at Gb Port .............................................................................................. 15-1 15.1 Alarm Meaning..........................................................................................................................................15-1 15.2 Impact upon System..................................................................................................................................15-1 15.3 System Self-processing procedures...........................................................................................................15-1 15.4 Alarm Handling.........................................................................................................................................15-2

16 1717 Slip Frame at Gb E1 Port.......................................................................................... 16-1 16.1 Alarm Meaning..........................................................................................................................................16-1 16.2 Impact upon System..................................................................................................................................16-1 16.3 System Self-processing procedures...........................................................................................................16-1 16.4 Alarm Handling.........................................................................................................................................16-2

17 1721 Slip Frame at Pb Port ................................................................................................ 17-1 17.1 Alarm Meaning..........................................................................................................................................17-1 17.2 Impact upon System..................................................................................................................................17-1 17.3 System Self-processing procedures...........................................................................................................17-1 17.4 Alarm Handling.........................................................................................................................................17-2

18 1722 Error FR Type Config in SLOT Table ................................................................... 18-1 18.1 Alarm Meaning..........................................................................................................................................18-1 18.2 Impact upon System..................................................................................................................................18-1 18.3 System Self-processing procedures...........................................................................................................18-1 18.4 Alarm Handling.........................................................................................................................................18-2

19 1723 Error FR Type Config Recovered ........................................................................... 19-1 19.1 Alarm Meaning..........................................................................................................................................19-1 19.2 Impact upon System..................................................................................................................................19-1 19.3 System Self-processing procedures...........................................................................................................19-1 19.4 Alarm Handling.........................................................................................................................................19-2

20 1730 Cell Resetting Failed ................................................................................................ 20-1 20.1 Alarm Meaning..........................................................................................................................................20-1 20.2 Impact upon System..................................................................................................................................20-1 20.3 System Self-processing procedures...........................................................................................................20-1 20.4 Alarm Handling.........................................................................................................................................20-2

21 1731 Cell Configuration Request Failed........................................................................ 21-1 21.1 Alarm Meaning..........................................................................................................................................21-1 21.2 Impact upon System..................................................................................................................................21-1 21.3 System Self-processing procedures...........................................................................................................21-1 21.4 Alarm Handling.........................................................................................................................................21-2

22 1732 Cell Configuration Error.......................................................................................... 22-1 22.1 Alarm Meaning..........................................................................................................................................22-1



iv Huawei Technologies Proprietary Issue 05 (2006-10-30)

22.2 Impact upon System..................................................................................................................................22-1 22.3 System Self-processing procedures...........................................................................................................22-1 22.4 Alarm Handling.........................................................................................................................................22-2

23 1733 PDCH Configuration Invalid ................................................................................. 23-1 23.1 Alarm Meaning..........................................................................................................................................23-1 23.2 Impact upon System..................................................................................................................................23-1 23.3 System Self-processing procedures...........................................................................................................23-1 23.4 Alarm Handling.........................................................................................................................................23-2

24 1734 PDCH Request Failed .............................................................................................. 24-1 24.1 Alarm Meaning..........................................................................................................................................24-1 24.2 Impact upon System..................................................................................................................................24-1 24.3 System Self-processing procedures...........................................................................................................24-2 24.4 Alarm Handling.........................................................................................................................................24-2

25 1735 PDCH Relay Adjusting Failed ............................................................................... 25-1 25.1 Alarm Meaning..........................................................................................................................................25-1 25.2 Impact upon System..................................................................................................................................25-1 25.3 System Self-processing procedures...........................................................................................................25-1 25.4 Alarm Handling.........................................................................................................................................25-2

26 1738 Cell CCCH Overload................................................................................................ 26-1 26.1 Alarm Meaning..........................................................................................................................................26-1 26.2 Impact upon System..................................................................................................................................26-1 26.3 System Self-processing procedures...........................................................................................................26-1 26.4 Alarm Handling.........................................................................................................................................26-2

27 1739 Cell CCCH Overload Recovered............................................................................ 27-1 27.1 Alarm Meaning..........................................................................................................................................27-1 27.2 Impact upon System..................................................................................................................................27-1 27.3 System Self-processing procedures...........................................................................................................27-1 27.4 Alarm Handling.........................................................................................................................................27-2

28 1740 Cell Transmission Delay Abnormal...................................................................... 28-1 28.1 Alarm Meaning..........................................................................................................................................28-1 28.2 Impact upon System..................................................................................................................................28-1 28.3 System Self-processing procedures...........................................................................................................28-1 28.4 Alarm Handling.........................................................................................................................................28-2

29 1760 LAPD Link Fault ....................................................................................................... 29-1 29.1 Alarm Meaning..........................................................................................................................................29-1 29.2 Impact upon System..................................................................................................................................29-1 29.3 System Self-processing procedures...........................................................................................................29-2 29.4 Alarm Handling.........................................................................................................................................29-2


Issue 05 (2006-10-30) Huawei Technologies Proprietary v

30 1761 LAPD Link Fault Recovery ..................................................................................... 30-1 30.1 Alarm Meaning..........................................................................................................................................30-1 30.2 Impact upon System..................................................................................................................................30-1 30.3 System Self-processing procedures...........................................................................................................30-1 30.4 Alarm Handling.........................................................................................................................................30-2

31 1762 Communication Failed in BSC-PCU ..................................................................... 31-1 31.1 Alarm Meaning..........................................................................................................................................31-1 31.2 Impact upon System..................................................................................................................................31-1 31.3 System Self-processing procedures...........................................................................................................31-2 31.4 Alarm Handling.........................................................................................................................................31-2

32 1763 Communication Recovered in BSC-PCU ............................................................. 32-1 32.1 Alarm Meaning..........................................................................................................................................32-1 32.2 Impact upon System..................................................................................................................................32-1 32.3 System Self-processing procedures...........................................................................................................32-1 32.4 Alarm Handling.........................................................................................................................................32-2

33 1764 Cell BTS Does Not Support GPRS ........................................................................ 33-1 33.1 Alarm Meaning..........................................................................................................................................33-1 33.2 Impact upon System..................................................................................................................................33-1 33.3 System Self-processing procedures...........................................................................................................33-2 33.4 Alarm Handling.........................................................................................................................................33-2

34 1765 No Response When Sends SI13 to BSC................................................................ 34-1 34.1 Alarm Meaning..........................................................................................................................................34-1 34.2 Impact upon System..................................................................................................................................34-1 34.3 System Self-processing procedures...........................................................................................................34-2 34.4 Alarm Handling.........................................................................................................................................34-2

35 1766 Pb E1 Local Port Out-of-syn. ................................................................................... 35-1 35.1 Alarm Meaning..........................................................................................................................................35-1 35.2 Impact upon System..................................................................................................................................35-2 35.3 System Self-processing procedures...........................................................................................................35-2 35.4 Alarm Handling.........................................................................................................................................35-2

36 1767 Pb E1 Local Port Out-of-syn Removed.................................................................. 36-1 36.1 Alarm Meaning..........................................................................................................................................36-1 36.2 Impact upon System..................................................................................................................................36-1 36.3 System Self-processing procedures...........................................................................................................36-1 36.4 Alarm Handling.........................................................................................................................................36-2

37 1768 Pb E1 Peer Port Out-of-syn...................................................................................... 37-1 37.1 Alarm Meaning..........................................................................................................................................37-1 37.2 Impact upon System..................................................................................................................................37-2 37.3 System Self-processing procedures...........................................................................................................37-2



vi Huawei Technologies Proprietary Issue 05 (2006-10-30)

37.4 Alarm Handling.........................................................................................................................................37-2

38 1769 Pb E1 Peer Port Out-of-syn Removed ................................................................... 38-1 38.1 Alarm Meaning..........................................................................................................................................38-1 38.2 Impact upon System..................................................................................................................................38-1 38.3 System Self-processing procedures...........................................................................................................38-1 38.4 Alarm Handling.........................................................................................................................................38-2

39 1771 Low Quality of TRAU Link .................................................................................... 39-1 39.1 Alarm Meaning..........................................................................................................................................39-1 39.2 Impact upon System..................................................................................................................................39-1 39.3 System Self-processing procedures...........................................................................................................39-1 39.4 Alarm Handling.........................................................................................................................................39-2

40 1775 Inconsistent BSC-PCU PCIC Config..................................................................... 40-1 40.1 Alarm Meaning..........................................................................................................................................40-1 40.2 Impact upon System..................................................................................................................................40-1 40.3 System Self-processing procedures...........................................................................................................40-1 40.4 Alarm Handling.........................................................................................................................................40-2

41 1800 PCU-BTS TRAU Link Fault .................................................................................... 41-1 41.1 Alarm Meaning..........................................................................................................................................41-1 41.2 Impact upon System..................................................................................................................................41-1 41.3 System Self-processing procedures...........................................................................................................41-1 41.4 Alarm Handling.........................................................................................................................................41-2

42 1801 PCU-BTS TRAU Link Recovery............................................................................. 42-1 42.1 Alarm Meaning..........................................................................................................................................42-1 42.2 Impact upon System..................................................................................................................................42-1 42.3 System Self-processing procedures...........................................................................................................42-1 42.4 Alarm Handling.........................................................................................................................................42-2

43 1802 TRX Type Configuration Error............................................................................... 43-1 43.1 Alarm Meaning..........................................................................................................................................43-1 43.2 Impact upon System..................................................................................................................................43-1 43.3 System Self-processing procedures...........................................................................................................43-1 43.4 Alarm Handling.........................................................................................................................................43-2

44 1824 CPU Overload ............................................................................................................ 44-1 44.1 Alarm Meaning..........................................................................................................................................44-1 44.2 Impact upon System..................................................................................................................................44-1 44.3 System Self-processing procedures...........................................................................................................44-1 44.4 Alarm Handling.........................................................................................................................................44-2

45 1825 Clock Synchronization Alarm ................................................................................ 45-1 45.1 Alarm Meaning..........................................................................................................................................45-1


Issue 05 (2006-10-30) Huawei Technologies Proprietary vii


46 1850 Active POMU Fault................................................................................................... 46-1 46.1 Alarm Meaning..........................................................................................................................................46-1 46.2 Impact upon System..................................................................................................................................46-1 46.3 System Self-processing procedures...........................................................................................................46-1 46.4 Alarm Handling.........................................................................................................................................46-2

47 1851 Standby POMU Fault ............................................................................................... 47-1 47.1 Alarm Meaning..........................................................................................................................................47-1 47.2 Impact upon System..................................................................................................................................47-1 47.3 System Self-processing procedures...........................................................................................................47-1 47.4 Alarm Handling.........................................................................................................................................47-2

48 1852 Standby POMU Recovered ..................................................................................... 48-1 48.1 Alarm Meaning..........................................................................................................................................48-1 48.2 Impact upon System..................................................................................................................................48-1 48.3 System Self-processing procedures...........................................................................................................48-1 48.4 Alarm Handling.........................................................................................................................................48-2

49 1853 RPPU Hardware Fault .............................................................................................. 49-1 49.1 Alarm Meaning..........................................................................................................................................49-1 49.2 Impact upon System..................................................................................................................................49-1 49.3 System Self-processing procedures...........................................................................................................49-1 49.4 Alarm Handling.........................................................................................................................................49-2

50 1854 RPPU Hardware Fault Recovered .......................................................................... 50-1 50.1 Alarm Meaning..........................................................................................................................................50-1 50.2 Impact upon System..................................................................................................................................50-1 50.3 System Self-processing procedures...........................................................................................................50-1 50.4 Alarm Handling.........................................................................................................................................50-2

51 1855 RPPU Reset................................................................................................................. 51-1 51.1 Alarm Meaning..........................................................................................................................................51-1 51.2 Impact upon System..................................................................................................................................51-1 51.3 System Self-processing procedures...........................................................................................................51-1 51.4 Alarm Handling.........................................................................................................................................51-2

52 1856 RPPU Software Fault ................................................................................................ 52-1 52.1 Alarm Meaning..........................................................................................................................................52-1 52.2 Impact upon System..................................................................................................................................52-1 52.3 System Self-processing procedures...........................................................................................................52-1 52.4 Alarm Handling.........................................................................................................................................52-2



viii Huawei Technologies Proprietary Issue 05 (2006-10-30)

53 1857 RPPU Software Fault Recovered............................................................................ 53-1 53.1 Alarm Meaning..........................................................................................................................................53-1 53.2 Impact upon System..................................................................................................................................53-1 53.3 System Self-processing procedures...........................................................................................................53-1 53.4 Alarm Handling.........................................................................................................................................53-2

54 1858 POMU Switchover .................................................................................................... 54-1 54.1 Alarm Meaning..........................................................................................................................................54-1 54.2 Impact upon System..................................................................................................................................54-1 54.3 System Self-processing procedures...........................................................................................................54-1 54.4 Alarm Handling.........................................................................................................................................54-2

55 1859 POMU Switchover Failed........................................................................................ 55-1 55.1 Alarm Meaning..........................................................................................................................................55-1 55.2 Impact upon System..................................................................................................................................55-1 55.3 System Self-processing procedures...........................................................................................................55-1 55.4 Alarm Handling.........................................................................................................................................55-2

56 1860 Active HSC Fault....................................................................................................... 56-1 56.1 Alarm Meaning..........................................................................................................................................56-1 56.2 Impact upon System..................................................................................................................................56-1 56.3 System Self-processing procedures...........................................................................................................56-1 56.4 Alarm Handling.........................................................................................................................................56-2

57 1861 Active HSC Fault Recovered...................................................................................... 57-1 57.1 Alarm Meaning..........................................................................................................................................57-1 57.2 Impact on System......................................................................................................................................57-1 57.3 System Self-processing procedure ............................................................................................................57-1 57.4 Alarm Handling.........................................................................................................................................57-2

58 1862 Standby HSC Fault ................................................................................................... 58-1 58.1 Alarm Meaning..........................................................................................................................................58-1 58.2 Impact upon System..................................................................................................................................58-1 58.3 System Self-processing procedures...........................................................................................................58-2 58.4 Alarm Handling.........................................................................................................................................58-2

59 1863 Standby HSC Recovered ......................................................................................... 59-1 59.1 Alarm Meaning..........................................................................................................................................59-1 59.2 Impact upon System..................................................................................................................................59-1 59.3 System Self-processing procedures...........................................................................................................59-1 59.4 Alarm Handling.........................................................................................................................................59-2

60 1864 Harddisk Fault ........................................................................................................... 60-1 60.1 Alarm Meaning..........................................................................................................................................60-1 60.2 Impact upon System..................................................................................................................................60-1 60.3 System Self-processing procedures...........................................................................................................60-1


Issue 05 (2006-10-30) Huawei Technologies Proprietary ix

60.4 Alarm Handling.........................................................................................................................................60-2

61 1865 Harddisk Recovered ................................................................................................. 61-1 61.1 Alarm Meaning..........................................................................................................................................61-1 61.2 Impact upon System..................................................................................................................................61-1 61.3 System Self-processing procedures...........................................................................................................61-1 61.4 Alarm Handling.........................................................................................................................................61-2

62 1870 Alarm Box Fault......................................................................................................... 62-1 62.1 Alarm Meaning..........................................................................................................................................62-1 62.2 Impact upon System..................................................................................................................................62-1 62.3 System Self-processing procedures...........................................................................................................62-1 62.4 Alarm Handling.........................................................................................................................................62-2

63 1871 Alarm Box Fault Recovered..................................................................................... 63-1 63.1 Alarm Meaning..........................................................................................................................................63-1 63.2 Impact upon System..................................................................................................................................63-1 63.3 System Self-processing procedures...........................................................................................................63-1 63.4 Alarm Handling.........................................................................................................................................63-2

64 1872 L2PU Fault .................................................................................................................. 64-1 64.1 Alarm Meaning..........................................................................................................................................64-1 64.2 Impact upon System..................................................................................................................................64-1 64.3 System Self-processing procedures...........................................................................................................64-1 64.4 Alarm Handling.........................................................................................................................................64-2

65 1873 L2PU Fault Recovered .............................................................................................. 65-1 65.1 Alarm Meaning..........................................................................................................................................65-1 65.2 Impact upon System..................................................................................................................................65-1 65.3 System Self-processing procedures...........................................................................................................65-1 65.4 Alarm Handling.........................................................................................................................................65-2

66 1874 Cells Successfully Migrated ................................................................................... 66-1 66.1 Alarm Meaning..........................................................................................................................................66-1 66.2 Impact upon System..................................................................................................................................66-1 66.3 System Self-processing procedures...........................................................................................................66-1 66.4 Alarm Handling.........................................................................................................................................66-2

67 1875 Cells Failed to Migrated .......................................................................................... 67-1 67.1 Alarm Meaning..........................................................................................................................................67-1 67.2 Impact upon System..................................................................................................................................67-1 67.3 System Self-processing procedures...........................................................................................................67-1 67.4 Alarm Handling.........................................................................................................................................67-2

68 1876 Cells Successfully Migrated Back.......................................................................... 68-1 68.1 Alarm Meaning..........................................................................................................................................68-1



x Huawei Technologies Proprietary Issue 05 (2006-10-30)


69 1877 Cells Failed to Migrate Back ................................................................................... 69-1 69.1 Alarm Meaning..........................................................................................................................................69-1 69.2 Impact upon System..................................................................................................................................69-1 69.3 System Self-processing procedures...........................................................................................................69-2 69.4 Alarm Handling.........................................................................................................................................69-2

70 1878 Cells Successfully Activated................................................................................... 70-1 70.1 Alarm Meaning..........................................................................................................................................70-1 70.2 Impact upon System..................................................................................................................................70-1 70.3 System Self-processing procedures...........................................................................................................70-1 70.4 Alarm Handling.........................................................................................................................................70-2

71 1879 Invalid SSN Alarm ................................................................................................... 71-1 71.1 Alarm Meaning..........................................................................................................................................71-1 71.2 Impact upon System..................................................................................................................................71-1 71.3 System Self-processing procedures...........................................................................................................71-1 71.4 Alarm Handling.........................................................................................................................................71-2

72 1880 Invalid SSN Alarm Removed ................................................................................. 72-1 72.1 Alarm Meaning..........................................................................................................................................72-1 72.2 Impact upon System..................................................................................................................................72-1 72.3 System Self-processing procedures...........................................................................................................72-1 72.4 Alarm Handling.........................................................................................................................................72-2

73 1881 SSN Hardware Failure Alarm................................................................................. 73-1 73.1 Alarm Meaning..........................................................................................................................................73-1 73.2 Impact upon System..................................................................................................................................73-1 73.3 System Self-processing procedures...........................................................................................................73-1 73.4 Alarm Handling.........................................................................................................................................73-2

74 1882 SSN Hardware Failure Alarm Removed .............................................................. 74-1 74.1 Alarm Meaning..........................................................................................................................................74-1 74.2 Impact upon System..................................................................................................................................74-1 74.3 System Self-processing procedures...........................................................................................................74-1 74.4 Alarm Handling.........................................................................................................................................74-2

75 1883 Standby POMU SSN Alarm.................................................................................... 75-1 75.1 Alarm Meaning..........................................................................................................................................75-1 75.2 Impact upon System..................................................................................................................................75-1 75.3 System Self-processing procedures...........................................................................................................75-1 75.4 Alarm Handling.........................................................................................................................................75-2


Issue 05 (2006-10-30) Huawei Technologies Proprietary xi

76 1884 Standby POMU SSN Alarm Removed ................................................................. 76-1 76.1 Alarm Meaning..........................................................................................................................................76-1 76.2 Impact upon System..................................................................................................................................76-1 76.3 System Self-processing procedures...........................................................................................................76-1 76.4 Alarm Handling.........................................................................................................................................76-2

77 1885 Lost Key Alarm.......................................................................................................... 77-1 77.1 Alarm Meaning..........................................................................................................................................77-1 77.2 Impact upon System..................................................................................................................................77-1 77.3 System Self-processing procedures...........................................................................................................77-1 77.4 Alarm Handling.........................................................................................................................................77-2

78 1886 Lost Key Alarm Removed........................................................................................ 78-1 78.1 Alarm Meaning..........................................................................................................................................78-1 78.2 Impact upon System..................................................................................................................................78-1 78.3 System Self-processing procedures...........................................................................................................78-1 78.4 Alarm Handling.........................................................................................................................................78-2

79 1887 System Overload Alarm........................................................................................... 79-1 79.1 Alarm Meaning..........................................................................................................................................79-1 79.2 Impact upon System..................................................................................................................................79-1 79.3 System Self-processing procedures...........................................................................................................79-1 79.4 Alarm Handling.........................................................................................................................................79-2

80 1888 Cells Successfully Deactivated............................................................................... 80-1 80.1 Alarm Meaning..........................................................................................................................................80-1 80.2 Impact upon System..................................................................................................................................80-1 80.3 System Self-processing procedures...........................................................................................................80-1 80.4 Alarm Handling.........................................................................................................................................80-2

81 1889 SIG Successfully Migrated ..................................................................................... 81-1 81.1 Alarm Meaning..........................................................................................................................................81-1 81.2 Impact upon System..................................................................................................................................81-1 81.3 System Self-processing procedures...........................................................................................................81-1 81.4 Alarm Handling.........................................................................................................................................81-2

82 1890 SIG Successfully Migrated Back............................................................................ 82-1 82.1 Alarm Meaning..........................................................................................................................................82-1 82.2 Impact upon System..................................................................................................................................82-1 82.3 System Self-processing procedures...........................................................................................................82-1 82.4 Alarm Handling.........................................................................................................................................82-2

83 1895 POMUs IP Connection Failed ................................................................................ 83-1 83.1 Alarm Meaning..........................................................................................................................................83-1 83.2 Impact upon System..................................................................................................................................83-1 83.3 System Self-processing procedures...........................................................................................................83-1



xii Huawei Technologies Proprietary Issue 05 (2006-10-30)

83.4 Alarm Handling.........................................................................................................................................83-2

84 1896 POMUs IP Connection Recovered......................................................................... 84-1 84.1 Alarm Meaning..........................................................................................................................................84-1 84.2 Impact upon System..................................................................................................................................84-1 84.3 System Self-processing procedures...........................................................................................................84-1 84.4 Alarm Handling.........................................................................................................................................84-2

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling Figures

Issue 05 (2006-10-30) Huawei Technologies Proprietary xiii

Figures

Figure 1-1 Port connection .................................................................................................................................1-1

Figure 35-1 Port connection .............................................................................................................................35-1

Figure 37-1 Port connection .............................................................................................................................37-1

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 1 1601 Gb Local End Out-of-sync

Issue 05 (2006-10-30) Huawei Technologies Proprietary 1-1

1 1601 Gb Local End Out-of-sync

1.1 Alarm Meaning

Description When Gb interface E1 port local end out-of-sync. is detected, this alarm will be triggered.

Principle of local end out-of-sync. alarm and remote end out-of-sync. alarm are introduced as follows:

Figure 1-1 Port connection

Rx

Tx Rx

Tx

Port A Port B

When port A cannot synchronize correct clock signals from its Rx line, it will report Gb Local End Out-of-sync. alarm. Causes for this alarm could be disconnection of relay or the poor quality of signals. In the meantime, port A will send a special signal to port B through its Tx line, informing port B about the event. After reception of the signal, port B will report Gb Remote End Out-of-sync. alarm.

Alarm Information

Alarm level

Alarm type

NM alarm category

Alarm box alarm category

Alarm ID Recovery alarm ID

Major Fault alarm FR system FR system 1601 1602

Alarm Parameters Number of parameters: 3

1 1601 Gb Local End Out-of-sync M900/M1800 Packet Control Unit


1-2 Huawei Technologies Proprietary Issue 05 (2006-10-30)

Frame No., RPPU board No., and Port No. on RPPU board

1.2 Impact upon System The E1 trunk transmission may be interrupted.

1.3 System Self-processing procedures None.

1.4 Alarm Handling

Probable Cause Step 1 Rx line of PCU to SGSN fails.

Step 2 The clock is unstable.

Step 3 The quality of signal transferred on the cable is poor.

----End

Recommendation Step 1 Check whether the physical connection between PCU and SGSN is normal.

View the ALM indicator (yellow) on the involved L2PU board. If the indicator flashes, it indicates physical connection fault, please check and remove the fault. For example, check and confirm the Tx and Rx ends have not been connected in reverse way, the connection between E1 cable and L2PU board and the connection between E1 cable and PDF are normal, the trunk between PCU and SGSN is normal.

Step 2 Check the configurations of E1 in PCU and SGSN.

The E1 configurations, especially the frame type and the code class, should be consistent in PCU and SGSN. Please check the configurations of the two parameters with the command E1T1 SHOW. In the case of inconsistency, please modify the configurations with the command E1T1 SET on PCU.

Step 3 Check the quality of clock source, for unstable clock will trigger this alarm.

Please check the clock of trunk at the PCU end and SGSN end, and confirm the difference between them is below 0.6Hz, or else please check with the transmission engineer.

Step 4 Please check with the concerned engineer to confirm the transmission path between PCU and SGSN is normal.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 2 1602 Gb Local End Out-of-sync Removed


2 1602 Gb Local End Out-of-sync Removed

2.1 Alarm Meaning

Description This alarm will be triggered when the system detects the Gb Local End Out-of-sync alarm disappears.

Alarm Information

Alarm level

Alarm type NM alarm category


Alarm ID

Recovery alarm ID

Major alarm Recovery alarm

FR system FR system 1602 None



2.2 Impact upon System FR layer communication is recovered.

2.3 System Self-processing procedures None

2 1602 Gb Local End Out-of-sync Removed M900/M1800 Packet Control Unit



2.4 Alarm Handling

Probable Cause Step 1 Rx line of PCU to SGSN return to be normal.

Step 2 The clock return to be stable.

Step 3 The quality of signal transferred on the cable return to be sound.

----End

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 3 1603 Gb Remote End Out-of-sync


3 1603 Gb Remote End Out-of-sync

3.1 Alarm Meaning

Description When remote end alarm information from SGSN is detected, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm Fault alarm FR system FR system 1603 1604



3.2 Impact upon System The cable that transfers signal from PCU to SGSN may be interrupted.


3 1603 Gb Remote End Out-of-sync M900/M1800 Packet Control Unit



3.4 Alarm Handling

Probable Cause Step 1 The Tx cable of PCU to SGSN fails.


Step 3 The quality of signal received from Gb interface is poor.

----End



Step 2 Check the configurations about E1 on PCU and SGSN.

The E1 configurations, especially the frame type and the code class, should be consistent in PCU and SGSN. Please check the configurations of two parameters with the command e1t1 show. In the case of inconsistency, please modify the configurations with the command e1t1 set on PCU.

Step 3 Check the quality of clock source, for unstable clock will trigger this alarm.

Please check the clock of trunk at the PCU end and SGSN end, and confirm the difference between them is below 0.6Hz, or else please ask the transmission engineer for handling.

Step 4 Please ask the related engineer to check and confirm the transmission path between PCU and SGSN is normal.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 4 1604 Gb Remote End Out-of-sync Removed


4 1604 Gb Remote End Out-of-sync Removed

4.1 Alarm Meaning

Description When remote end alarm from SGSN could not be detected, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Recovery alarm



Frame No., RPPU board No., Port No. on RPPU board

4.2 Impact upon System None


4 1604 Gb Remote End Out-of-sync Removed M900/M1800 Packet Control Unit



4.4 Alarm Handling

Probable Cause Step 1 Rx line of PCU to SGSN returns to be normal.

Step 2 The clock return to be stable.

Step 3 The quality of signal transferred on the cable return to be sound.

Step 4 The Rx cable of PCU from SGSN fails, so the information from SGSN could not be detected.

----End

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 5 1607 BC Added Failed to Work


5 1607 BC Added Failed to Work

5.1 Alarm Meaning

Description When the initialization of the added Bearer Channel (BC) fails, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm Event alarm FR system FR system 1607 None


Frame No., RPPU board No., Port No. on RPPU board, BC No. for the port, and failure code.

5.2 Impact upon System Since the BC initialization is failed, the improvement of transmission capability of relevant Gb interface cannot be made.


5 1607 BC Added Failed to Work M900/M1800 Packet Control Unit



5.4 Alarm Handling

Probable Cause Step 1 Data configuration error.

Step 2 The transmission on Gb interface is abnormal.

Step 3 The L2PU board on Gb interface is abnormal.

----End

Recommendation Step 1 Check the configurations about E1 in PCU and SGSN.

The E1 configurations, especially the frame type and the code class, should be consistent in PCU and SGSN. Please check the configurations of the two parameters with the command e1t1 show. In the case of inconsistency, please modify the configurations with the command e1t1 set in PCU.

Step 2 Check whether the BC configured in PCU is consistent with that in SGSN.

The BC configuration, especially the Timeslot configuration and the DLCIType configuration, should be consistent on PCU and SGSN. The Mode parameter on PCU should be configured as DTE. Please check and confirm that they were appropriated , or else, modify the configuration.

Step 3 Check the status of the L2PU board related.

Check the alarm list, and if the alarm L2PU Fault is also reported, take steps according to 1872 L2PU Fault.

Otherwise, view the indicator RUN on the panel of L2PU board, if the indicator is on, it means that this board has not been configured, please delete the configuration of involved RPPU board with the command slot del, and add the configuration with the command slot add.

Step 4 Check whether the plug-in L2PU board and the backboard of RPPU board are associated.

The RPPU board with L2PU board should configured E1TM board as its backboard.

Step 5 Check whether the physical connection between PCU and SGSN is normal.


Step 6 Check the quality of clock source, for unstable clock will lead to alarms.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 6 1609 BC Unavailable


6 1609 BC Unavailable

6.1 Alarm Meaning

Description When the LMI (Local Maintenance Interface) protocol takes the BC status as "BC invalid", or the BC is blocked by O&M, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm Fault alarm FR system FR system 1609 1610

Alarm Parameters Number of Parameters: 7

Frame No., RPPU board No., Port No. on RPPU board, BC No. for the port, number of link reliability errors, number of protocol errors, number of deactivations.

6.2 Impact upon System If no other BC is configured, the GPRS service of the involved cell will be interrupted, or else, the involved cell can keep on providing the service by other BC, but the capacity will be degraded.


6 1609 BC Unavailable M900/M1800 Packet Control Unit



6.4 Alarm Handling

Probable Cause Step 1 The BC is blocked.

Step 2 The physical connection between PCU and SGSN fails.

Step 3 Data configurations error on Gb interface.

----End

Recommendation Step 1 Check whether the BC is blocked by the user.

Check whether the BC is blocked by user with the command mt fr bc show statinfo. If it is blocked by the user, unblock it by executing the command mt fr bc unblock.

Step 2 Confirm the configuration of BC parameter and E1 parameter on Gb interface have not been modified on SGSN.

If the configuration of BC parameter on SGSN was modified, please modify that on PCU with the command bc set accordingly.

If the configuration of E1 parameter on SGSN was modified, please modify that on PCU with the command e1t1 set accordingly.

Step 3 Check whether the related E1 is in loop status.

View the E1 on which the BC is established with the command mt fr port show loop or mt fr port show state, if the E1 is in loop status, please modify it with the command mt fr port stop loop.

Step 4 Check whether the physical connection between PCU and SGSN is normal.

View the ALM indicator (yellow) on the involved L2PU board. If the indicator flashes, it indicates physical connection fault, please check and remove the fault. For example, check and confirm the connection between E1 cable and L2PU board and the connection between E1 cable and PDF are normal, the trunk between PCU and SGSN is normal.

Step 5 Check whether the RPPU (Gb) board matches the back plug-in board.

If the plug-in board in RPPU is L2PU, the E1TM board should be used as the back plug-in board accordingly.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 7 1610 BC Available


7 1610 BC Available

7.1 Alarm Meaning

Description For a BC that generates BC Unavailable alarm, when the BC is returned normal and has not been blocked by O&M, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Recovery alarm



Frame No., RPPU board No., Port No. on RPPU board, BC No. for the port.

7.2 Impact upon System Transmission on this BC is recovered.


7 1610 BC Available M900/M1800 Packet Control Unit



7.4 Alarm Handling

Probable Cause BC is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 8 1611 More PVCs Configured at Peer End


8 1611 More PVCs Configured at Peer End

8.1 Alarm Meaning

Description When the PCU detects that excessive PVCs have been configured in SGSN, this alarm will be triggered.

For a BC, the number of PVCs configured at the two ends of Gb interface should be consistent.

Alarm Information

Alarm level Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor Alarm Event alarm FR system FR system 1611 None


Frame No., RPPU board No., Port No. on RPPU board, BC No. for the port, and DLCI.

8.2 Impact upon System If the PVCs at the two ends are configured inconsistently, they cannot work normally, thus leading to the degradation of transmission capability in Gb interface.


8 1611 More PVCs Configured at Peer End M900/M1800 Packet Control Unit



8.4 Alarm Handling

Probable Cause The configurations about NSVC in PCU and SGSN are not consistent, and more PVCs have been configured in SGSN.

Recommendation Step 1 Check whether PCU and SGSN are consistent in the configuration of DLCI for the same

NSVC.

View the DLCI configured in PCU with the command nsvc show. If it is inconsistent with that configured in SGSN, modify it with the command nsvc set.

Step 2 Check whether the PVCs configured are valid.

If they are valid PVCs, add them with the command nsvc add. If they are invalid, ask the SGSN maintenance engineer to delete them in SGSN.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 9 1612 More PVCs Configured at Local End


9 1612 More PVCs Configured at Local End

9.1 Alarm Meaning

Description When PCU detects that it has configured more PVCs than SGSN, this alarm will be triggered.

For a BC, the number of PVCs configured in PCU and SGSN should be the same.

Alarm Information


NM alarm category


Alarm ID

Recovery alarm ID

Minor Alarm Event alarm FR system FR system 1612 None


Frame No., RPPU board No., Port No. on RPPU board, BC No. for the port, and DLCI.

9.2 Impact upon System If the number of PVCs configured in PCU and SGSN is not the same, the excessive PVCs cannot work normally, thus leading to the degradation of transmission capability in Gb interface.


9 1612 More PVCs Configured at Local End M900/M1800 Packet Control Unit



9.4 Alarm Handling

Probable Cause The configurations about NSVC on PCU and SGSN are not consistent, and more PVCs have been configured in PCU.

Recommendation Step 1 Check whether PCU and SGSN are consistent in the configuration of DLCI for the same

NSVC.

View the DLCI configured in PCU with the command nsvc show. If it is inconsistent with that configured in SGSN, modify it with the command nsvc set.

Step 2 Check whether the PVCs configured are valid.

If they are valid PVCs, ask the SGSN maintenance engineer to add them in SGSN, or else delete the invalid PVCs in PCU with the command nsvc del.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 10 1670 BSSGP Cell Blocking Failed


10 1670 BSSGP Cell Blocking Failed

10.1 Alarm Meaning

Description When a cell is blocked manually, if no response is received from SGSN within a specified period (depending on data configuration), the system will resend the Block message. If the number of Block message resent exceeds the specified number (depending on data configuration), this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category

Subsystem alarm category

Alarm ID

Recovery alarm ID

Warning Event alarm Gb interface Gb interface 1670 None


Frame No., Board No., Module No. (or Module Name), NSEI, and BVCI.

10.2 Impact upon System If this alarm occurs, cell blocking has failed and the cell cannot provide services.


10 1670 BSSGP Cell Blocking Failed M900/M1800 Packet Control Unit



10.4 Alarm Handling

Probable Cause Step 1 The Gb interface is abnormal.

Step 2 BVC is abnormal or the parameters about cell are not configured appropriately.

Step 3 The SGSN is abnormal.

----End



Step 2 Check whether the configurations on cell in PCU and SGSN are consistent.

View the configurations of Gb interface in PCU with the command bc show, nsvc show, nse show, and cell show, if they are not consistent with those configured in SGSN, please modify them.

Step 3 Check to make sure that the SGSN is normal.

Open the OMC console to trace BSSGP SIG messages (or use protocol analyzer such as K1205 or K1297) and then reset the corresponding PTP BVC with the command mt bvc ptp reset. If the PTP BVC RESET ACK message from SGSN has not been traced with the interface message tracing tools, please contact SGSN maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 11 1671 BSSGP Cell Unblocking Failed


11 1671 BSSGP Cell Unblocking Failed

11.1 Alarm Meaning

Description When the system equipment or cell equipment recovers, or when the cell is unblocked manually, if no response is received from SGSN within the specified period (depending on data configuration), the system will resend Unblock message. If the number of message resent exceeds the specified number (depending on data configuration), this alarm will be triggered.

Alarm Information

Alarm level



Alarm ID

Recovery alarm ID




11.2 Impact upon System If this alarm occurs, cell unblocking has failed and the cell cannot provide services.


11 1671 BSSGP Cell Unblocking Failed M900/M1800 Packet Control Unit



11.4 Alarm Handling

Probable Cause Step 1 The Gb interface is abnormal.

Step 2 BVC is abnormal or the parameters about cell are not configured appropriately.


----End



Step 2 Check whether the configurations on cell in PCU and SGSN are consistent.

View the configurations of Gb interface in PCU with the command bc show and cell show, if they are not consistent with those configured in SGSN, please modify them.

Step 3 Check to make sure that the SGSN is normal.

Open the OMC console to trace BSSGP SIG messages (or use protocol analyzer such as K1205 or K1297), and then reset the corresponding PTP BVC with the command mt bvc ptp reset. If the PTP BVC RESET ACK message from SGSN has not been traced with the interface message tracing tools, please contact SGSN maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 12 1672 BVC Resetting Failed


12 1672 BVC Resetting Failed

12.1 Alarm Meaning

Description When the PCU system is reset or data link layer is recovered, the PCU will send BVC reset message to SGSN, if no response is received from SGSN within a specified period (depending on data configuration), the system will resend the Reset message. If the number of message resent exceeds the specified number (depending on data configuration), this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID




12.2 Impact upon System If this alarm occurs, cell reset has failed and the cell cannot provide services.


12 1672 BVC Resetting Failed M900/M1800 Packet Control Unit



12.4 Alarm Handling

Probable Cause Step 1 Data configurations are not appropriate, and SGSN is not configured with the correspondent

NSE.

Step 2 Gb interface is abnormal.


----End

Recommendation Step 1 If the BVCI returned by the system is 0, it indicates SIG BVC reset has failed. Please check

whether SGSN works normally, and whether the corresponding NSEI in SGSN has been configured.

Step 2 If the BVCI returned by the system is greater than 1, it indicates PTP BVC reset has failed. Please check whether SGSN works normally.

Open the OMC console to trace BSSGP SIG messages (or use protocol analyzer such as K1205 or K1297), and then reset the corresponding PTP BVC with the command mt bvc ptp reset. If the PTP BVC RESET ACK message from SGSN has not been traced with the interface message tracing tools, please contact SGSN maintenance engineer for handling.

Step 3 If the SGSN equipment is purchased from Huawei, please check whether corresponding cells has been configured. If not, please add the cells to the configuration.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 13 1675 NSVC Link Fault


13 1675 NSVC Link Fault

13.1 Alarm meaning

Description When a certain NSVC link is disconnected, this alarm will be triggered.

Alarm Information


NM alarm category


Alarm ID

Recovery Alarm ID

Minor Alarm Fault alarm BSSGP BSSGP 1675 1676

Alarm Parameters Number of Parameters：3

NSVCI 、FrameNo、BoardNo.

13.2 Impact upon System None.

13.3 System Self-Processing Procedure None.

13 1675 NSVC Link Fault M900/M1800 Packet Control Unit



13.4 Alarm Handling

Probable Cause: Step 1 Blocked procedure is successful.

Step 2 Reset procedure is successful.

Step 3 Peer end requests blocking procedure.

Step 4 Test procedure is failed.

----End

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 14 1676 NSVC Link Fault Recovered


14 1676 NSVC Link Fault Recovered

14.1 Alarm meaning

Description When the faulty NSVC link has been restored to normal,this alarm will be triggered.

Alarm Information

Alarm level Alarm type NM alarm category


Alarm ID

Recovery Alarm ID

Minor Alarm Recovery alarm

BSSGP BSSGP 1676 none

Alarm Parameters Number of Parameters：3

FrameNo、BoardNo、ModuleNo.


14.3 System Self-Processing Procedure None.

14.4 Alarm Handling

Probable Cause Step 1 Unblocked procedure is successful.

14 1676 NSVC Link Fault Recovered M900/M1800 Packet Control Unit



Step 2 The link between SGSN and PCU is broken.

----End

Recommendation: None.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 15 1715 CRC4 Error at Gb Port


15 1715 CRC4 Error at Gb Port

15.1 Alarm Meaning

Description When the configuration of frame types in PCU and SGSN is inconsistent (only one of the two is configured with CRC4) or the quality of transmission is poor, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor alarm

Event alarm



Frame No., RPPU board No. and Error Code.

15.2 Impact upon System The transmission in Gb interface is abnormal.


15 1715 CRC4 Error at Gb Port M900/M1800 Packet Control Unit



15.4 Alarm Handling

Probable Cause Step 1 The configuration of frame type in PCU and SGSN is not consistent.

Step 2 Poor transmission capacity in Gb interface.

----End

Recommendation Step 1 Check whether the frame types of E1 trunk in Gb interface are consistent.

Check the frame types configured in PCU with the command e1t1 show . If it is inconsistent with that configured in SGSN, please modify the configuration with the command e1t1 set.

Step 2 Check the quality of transmission.

Poor transmission quality will trigger this alarm. If the bit error ratio is greater than 10-5, contact transmission equipment maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 16 1717 Slip Frame at Gb E1 Port


16 1717 Slip Frame at Gb E1 Port

16.1 Alarm Meaning

Description When the E1 port clock at Gb interface is mismatched or when the transmission quality is poor, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor alarm

Event alarm



Frame No., Board No. and Port No.



16 1717 Slip Frame at Gb E1 Port M900/M1800 Packet Control Unit



16.4 Alarm Handling

Probable Cause Step 1 The clock mode configured in PCU or SGSN is not appropriate.

Step 2 The quality of transmission in Gb interface is poor.

----End

Recommendation Step 1 Check the clock configuration in PCU and SGSN.

Check the clock configuration in PCU with the command e1t1 show. The PCU clock should be configured as slave clock, or else modify it with the command e1t1 set. If PCU is directly connected with SGSN, SGSN clock should be configured as master clock. If PCU and SGSN are connected by frame relay network, SGSN clock should be configured as slave clock. In the case of SGSN data configuration error, please contact SGSN maintenance engineers for modification.

Step 2 Check the transmission quality.

If the transmission bit error ratio exceeds 10-5, contact transmission maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 17 1721 Slip Frame at Pb Port


17 1721 Slip Frame at Pb Port

17.1 Alarm Meaning

Description If the clock of E1 is mismatched or the transmission path is of poor quality, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor alarm

Event alarm



Frame No., Board No. and Port No.

17.2 Impact upon System The transmission path of Pb interface may be deteriorated


17 1721 Slip Frame at Pb Port M900/M1800 Packet Control Unit



17.4 Alarm Handling

Probable Cause Step 1 The configuration of clock mode is appropriate in PCU and BSC.

Step 2 The quality of transmission path is poor.

----End

Recommendation Step 1 Check the clock configuration in PCU and BSC.

BSC clock should be configured as master clock, and PCU clock as slave clock. Modify the configuration of PCU clock with the command pcu set e1exchange.

Step 2 Improve the quality of transmission path.

If the transmission bit error ratio exceeds 10-5, contact transmission maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 18 1722 Error FR Type Config in SLOT Table


18 1722 Error FR Type Config in SLOT Table

18.1 Alarm Meaning

Description If the type of plug-in card of the RPPU (Gb) board configured in SLOT table is not consistant with hardware installed, this alarm will be reported.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Important Alarm

Fault alarm

Device system Device system 1722 1723


Frame No., RPPU board No., plug-in card No..

18.2 Impact upon System The plug-in card which is not appropriated configured cannot perform functions.


18 1722 Error FR Type Config in SLOT Table M900/M1800 Packet Control Unit



18.4 Alarm Handling

Probable Cause None.

Recommendation Check the plug-in card configured in the SLOT table to make sure that it is consistent with the really installed.

If it is the L2PU board, it should be configured as l2pufr.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 19 1723 Error FR Type Config Recovered


19 1723 Error FR Type Config Recovered

19.1 Alarm Meaning

Description If the type of plug-in card of the RPPU (Gb) board configured in SLOT table returns to be consistent with hardware installed, this alarm will be reported.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Important Alarm

Fault alarm recover

Device system

Device system 1723 None


Frame No., RPPU board No., FR Board No..



19 1723 Error FR Type Config Recovered M900/M1800 Packet Control Unit



19.4 Alarm Handling


Recommendation None.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 20 1730 Cell Resetting Failed


20 1730 Cell Resetting Failed

20.1 Alarm Meaning

Description During initialization, PCU sends a Cell Reset message to BSC so that the cell status at both sides can be restored to initial status. After PCU sends the message, if no response is received from BSC within 5 seconds, it will resend the Cell Reset message. If it resends the message three times and still receives no response, PCU will take it as cell reset failure and generate this alarm.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Event alarm

RLC/MAC RLC/MAC 1730 None


Frame No., Board No., Module No. (or Module Name) and Cell No.

20.2 Impact upon System Due to cell reset failure, the cell cannot provide GPRS services.

20.3 System Self-processing procedures If cell reset fails, PCU will attempt to reset the cell repeatedly until the fault is removed. During that course, alarms may be generated several times.

20 1730 Cell Resetting Failed M900/M1800 Packet Control Unit



20.4 Alarm Handling

Probable Cause Step 1 The configuration of the specified cell is not appropriate.

Step 2 The LAPD link of Pb interface is abnormal.

----End

Recommendation Step 1 Check whether the corresponding LAPD links of the cell work normally

1. Check whether the physical connection between PCU and BSC is normal.

View the ALM indicator (yellow) on the involved L2PU board. If the indicator flashes, it indicates physical connection fault, please check and remove the fault. For example, check and confirm the connection between E1 cable and L2PU board and the connection between E1 cable and PDF are normal, the trunk between PCU and BSC is normal.

2. Check whether PCU and BSC are consistent in LAPD data configuration, including LAPD Semi-permanent Connection Table, Pb Trunk Circuit Table in BSC and LAPD Link Table in PCU. In the case of inconsistency, please modify the configuration.

3. Check the management status of all the LAPD links connected to the BSC with the command mt lapd show state. Unblock the links if they are in block status.

4. Check whether the running status of BSC is normal. If abnormal, contact BSC maintenance engineer for handling.

Step 2 Check whether the configuration of the cell CGI parameters in PCU ATTR Table is consistent with that in the cell table of BSC. In case of inconsistency, deactivate the cell with the command mt gcell deactive, modify the ATTR Table with the command pcu set attr, and finally activate the cell with the command mt gcell active.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 21 1731 Cell Configuration Request Failed


21 1731 Cell Configuration Request Failed

21.1 Alarm Meaning

Description During the course of initialization, PCU sends a Cell Configuration Request message to BSC for the configuration data of the cell. If the PCU receives the negative response from the BSC, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm Event alarm RLC/MAC RLC/MAC 1731 None


Frame No., board No., module No. (or module name), cell ID and cause value.

21.2 Impact upon System Due to the cell configuration request failure, the cell cannot provide GPRS services.

21.3 System Self-processing procedures PCU will resend the request message for the configuration data of the cell.

21 1731 Cell Configuration Request Failed M900/M1800 Packet Control Unit



21.4 Alarm Handling

Probable Cause Step 1 If the cause value is 0, it means that there is no response from BSC.

Step 2 If the cause value is 1, it means that the cell does not support GPRS service.

Step 3 If the cause value is 2, it means that the cell does not exist.

Step 4 If the cause value is 3, it means that BSC is resetting the cell.

----End

Recommendation Because there are several possible causes for this alarm, the corresponding measures should be taken according to the various causes:

Step 1 If the cause value is 0, generally, such alarm is caused by LAPD link fault. Please follow the handling procedures below:



2. Check whether PCU and BSC are consistent in data configurations for LAPD.

Check and confirm LAPD Semi-permanent Connection Table, Pb Trunk Circuit Table of BSC and LAPD Link Table of PCU are consistent, or else modify them.

3. Check the management status of all the LAPD links connected to the BSC.

Check the link status with the command mt lapd show state. If they are blocked, unblock the links with the command mt lapd unblock.

4. Check whether BSC is normal.

If the status of BSC is abnormal, please contact BSC maintenance engineer for handling.

Step 2 If the cause value is 1, please check and confirm the cell is configured as "Support GPRS" in BSC Cell Table, or else ask BSC maintenance engineer to modify the configuration.

Step 3 If the cause value is 2, please check and confirm that the cell has been configured in BSC Cell Table, or else ask BSC maintenance engineer to add the configuration.

Step 4 If the cause value is 3, no handling is required. PCU will try sending the Cell Configuration Request message once again.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 22 1732 Cell Configuration Error


22 1732 Cell Configuration Error

22.1 Alarm Meaning

Description After successful acquisition of cell configuration data, PCU will check the validity of the configuration. If it finds any error, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Event alarm



Frame No., board No., module No. (or module name) and cell ID

22.2 Impact upon System Due to the cell configuration error, the cell cannot provide GPRS services.

22.3 System Self-processing procedures PCU records the cell status as data configuration error.

22 1732 Cell Configuration Error M900/M1800 Packet Control Unit



22.4 Alarm Handling

Probable Cause Step 1 Cell configuration is not appropriate in PCU.

Step 2 The PDCH of the cell has not been configured in BSC.

Step 3 The cell is configured as not support GPRS service in BSC.

Step 4 The PBCCH has been configured in BSC.

Step 5 The configuration of dual-timeslot is not consistent in BSC.

----End

Recommendation Step 1 Check whether the data configuration is complete.

Check and confirm that the data configuration of each cell is complete with the command pcu check cellconfig. Or else, please add or modify the related configuration.

Step 2 Check BSC Data Configuration Table.

If the cell has been configured with PBCCH in BSC, please check whether it meets the PCU License limitation. If not, please delete PBCCH configuration or purchase the relevant License. If it meets the limitation, please check whether the cell has been configured with more than one PBCCH. One cell can be configured with only one PBCCH.

Step 3 Check and confirm that the cell has been configured with PDCH in BSC. Or else, please add the configuration.

Step 4 Check and confirm that the cell is configured as supporting GPRS in BSC. Or else, please modify the configuraton.

Step 5 If the dual-timeslot function is adopted, please check and confirm the configuraton of cell attributes and carrier attributes are appropriate in BSC.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 23 1733 PDCH Configuration Invalid


23 1733 PDCH Configuration Invalid

23.1 Alarm Meaning

Description Due to system capacity limitation, each RPPU board can only be configured with 120 PDCHs (or 100 PDCHs for all-EDGE cell)at most. During the course of cell initialization, if PCU finds a RPPU board configured with over 120 PDCHs, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Event alarm



Frame No., board No. and module No. (or module name)

23.2 Impact upon System During system initialization, PDCHs after the 120th will not work normally.

23.3 System Self-processing procedures PCU discards the redundant channel configuration information and continuously generates alarms.

23 1733 PDCH Configuration Invalid M900/M1800 Packet Control Unit



23.4 Alarm Handling

Probable Cause The number of PDCHs configured in the RPPU board is more than 120.

Recommendation Step 1 Reduce the number of PDCHs configured in BSC.

Step 2 �Check the number of cells configured on the RPPU board.

Each RPPU board can only be configured with 120 PDCHs and 120 cells at most. If the number of PDCHs configured exceeds 120, please configure the cell with the redundant PDCHs to other RPPU boards. If the number of cells configured is less than 120, please reduce the number of PDCHs for each cell.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 24 1734 PDCH Request Failed


24 1734 PDCH Request Failed

24.1 Alarm Meaning

Description In the course of initialization and operation, PCU sends a PDCH Request message to BSC, requesting that part of the channels that previously supported circuit service be changed into supporting GPRS. After receipt of the request message, if BSC finds any abnormality, it will send a negative response to PCU. PCU will generate this alarm after it receives the negative response.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Event alarm



Frame No., board No., module No. (or module name), cell ID, TRX No., timeslot No. and cause value.

24.2 Impact upon System PDCH request fails after the alarm occurrence, and in a period of time, these PDCHs cannot be allocated to support GPRS.

24 1734 PDCH Request Failed M900/M1800 Packet Control Unit



24.3 System Self-processing procedures If the cause for alarm occurrence is "The channels have been networked", after it generates this alarm, PCU will check the channel status periodically with BSC. If it finds its channel status inconsistent with that of BSC, it will keep the consistency by means of maintenance messages.

If it is due to other causes, there is no further self-processing procedure after PCU generates this alarm.

24.4 Alarm Handling

Probable Cause Step 1 If the cause value is 0, it means that the channels have been networked.

Step 2 If the cause value is 1, it means that the PCIC is not available.

Step 3 If the cause value is 2, it means that the BSC internal networking has failed.

Step 4 If the cause value is 3, it means that BSC cannot find free timeslots at Abis interface.

Step 5 If the cause value is 4, it means that other causes make BSC abnormal.

----End

Recommendation Because there are several possible causes for this alarm, the corresponding measures should be taken according to the various causes:

Step 1 If the cause value is 0, please wait for the self-processing solution of the system.

Step 2 If the cause value is 1, please check whether PCU and BSC are consistent in PCIC data configuration and status.

Step 3 If the cause value is 2, please check whether BSC works normally.

Step 4 If the cause value is 3, please check the utilization status of the channel for the circuit switched service between BSC and BTS.

Step 5 If the cause value is 4, it indicates that PDCH request has failed due to other causes, such as the dynamic data configuration performed by BSC.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 25 1735 PDCH Relay Adjusting Failed


25 1735 PDCH Relay Adjusting Failed

25.1 Alarm Meaning

Description In the course of initialization and operation, if the number of PCIC that formed the channel switches from one to two or from two to one, PCU will send a Channel Coding Scheme Switch Request message to BSC. If the PCU cannot receive the acknowledge response after that, this alarm will be trigged.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor Alarm

Event alarm



Frame No., board No., module No. or module name, cell ID, TRX No., timeslot No. and cause value.

25.2 Impact upon System If this alarm occurs, indicating the switchover of coding schemes for a certain channel has failed, the channel will not support CS-3/CS-4 in a period of time.


25 1735 PDCH Relay Adjusting Failed M900/M1800 Packet Control Unit



25.4 Alarm Handling

Probable Cause Step 1 If the cause value is 0, it means that BSC sends channel configuration command to BTS, but

cannot receive the response or receives a negative answer within the designated time.

Step 2 �If the cause value is 2, it means that BSC atte mpts to find free timeslots at the Abis interface so as to exchange with the newly-added Pb interface E1 sub-timeslots, but fails.

----End

Recommendation As there are various possible causes for this alarm, the corresponding measures should be taken according to the cause values.

Step 1 If the cause value is 0, please check whether the connection between BSC and BTS is normal.

Step 2 If the cause value is 2, please check in BSC Radio Channel Configuration Table whether the BTS that the cell belongs to has been configured with free trunk or whether the configured free trunk can meet the requirement. or else, please add the configuration in the BTS or add a trunk.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 26 1738 Cell CCCH Overload


26 1738 Cell CCCH Overload

26.1 Alarm Meaning

Description If the PCU sends too many messages on CCCH, which makes the number of messages in the buffer memory of BTS exceeds the configured threshold, BTS will report the information to the PCU, and this alarm is triggered when this information is received by PCU.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor Alarm

Fault alarm

RLC/MAC RLC/MAC 1738 1739


Frame No., board No., module No. (or module name), cell ID.


26.3 System Self-processing procedures The PCU stop sending packet paging message or resending downlink assignment message to BSC.

26 1738 Cell CCCH Overload M900/M1800 Packet Control Unit



26.4 Alarm Handling

Probable Cause The number of message in the processing array of BTS DSP is overloaded.

Recommendation No manual processing is needed.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 27 1739 Cell CCCH Overload Recovered


27 1739 Cell CCCH Overload Recovered

27.1 Alarm Meaning

Description When the PCU reports the CCCH Overload alarm, it will start a timer. When the timer is timeout, this alarm is triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor Alarm

Fault alarm



Frame No., board No., module No. (or module name), cell ID.



27 1739 Cell CCCH Overload Recovered M900/M1800 Packet Control Unit



27.4 Alarm Handling

Probable Cause The number of message in the processing array of BTS DSP is below the threshold.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 28 1740 Cell Transmission Delay Abnormal


28 1740 Cell Transmission Delay Abnormal

28.1 Alarm Meaning

Description When the delay parameter is saved in cell record, PCU will compare the actual value with the configured one and the relationship between the delay value and the cell transmission attributes. This alarm is triggered when the cell transmission delay exceeds system capability or does not accord with cell transmission attribute.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor alarm

Fault alarm



Frame No., board No., module No. (or module name), cell ID and cause value.

28.2 Impact upon System The cell cannot support GPRS.


28 1740 Cell Transmission Delay Abnormal M900/M1800 Packet Control Unit



28.4 Alarm Handling

Probable Cause Step 1 If the alarm value is 0, it indicates that the cell is common transmission cell and the

transmission delay is greater than 240ms.

Step 2 If the alarm value is 1, it indicates that the cell is satellite transmission cell, and the transmission delay is less than 240ms.

Step 3 If the alarm value is 2, it indicates that the cell is satellite transmission cell, and the transmission delay is greater than 1000 ms.

----End

Recommendation Step 1 If the cause value is 0, please check and confirm the configuration on satellite transmission in

PCU with the command pcu show sattrans is consistent with cell transmission attributes configured in BSC, or else configure this cell as satellite transmission cell in PCU.

Step 2 If the cause value is 1, please check and confirm that this cell is configured as satellite transmission cell in BSC, or else, please delete the configuration as satellites transmission cell in PCU.

Step 3 If the cause value is 2, the quality of GPRS will be deteriorated. Please optimize the network to keep the delay of the transmission below 1000 ms.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 29 1760 LAPD Link Fault


29 1760 LAPD Link Fault

29.1 Alarm Meaning

Description When RPPU board detects that fault has occurred to a certain LAPD link configured on it and has led to the disconnection of the LAPD link, it will report this alarm to the alarm system.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Fault alarm



Frame No., Board No. and LAPD link No.

29.2 Impact upon System LAPD link is the internal signalling exchange link between PCU and BSC. All the LAPD links between PCU and a BSC work in the load-sharing mode. When fault occurs to a LAPD link, PCU can still implement signalling exchange through other LAPD links that are connected to the same BSC.

But when the traffic is quite large, signalling exchange congestion may occur due to inadequate LAPD links between PCU and the BSC.

29 1760 LAPD Link Fault M900/M1800 Packet Control Unit



29.3 System Self-processing procedures When fault occurs to one of the LAPD links between PCU and a BSC, PCU can automatically continue the signalling exchange through other normal LAPD links connected to this BSC, to ensure that the system can work normally.

29.4 Alarm Handling

Probable Cause Step 1 The connection between PCU and BSC or between BSC and BTS is broken.

Step 2 The configuration of LAPD link is appropriate.

Step 3 The LAPD link is blocked.

Step 4 The BSC is abnormal.

----End

Recommendation Step 1 Check whether the physical connection between PCU and BSC is normal.


Step 2 Check whether PCU and BSC are consistent in data configurations for LAPD.

Check and confirm that the LAPD parameters configured in PCU is consistent with that configured in LAPD Semi-permanent Connection Table and Pb Trunk Circuit Table of BSC, or else, please modify the configurations.

Step 3 Check the status of all the LAPD links connected to the BSC.

Check and confirm that the link is in unblock status with the command mt lapd show state, or else, please unblock the link in PCU or BSC.

Step 4 Check whether the running status of BSC is normal, or else, please contact BSC maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 30 1761 LAPD Link Fault Recovery


30 1761 LAPD Link Fault Recovery

30.1 Alarm Meaning

Description When RPPU board detects that the faulty LAPD link configured on it recovers to normal status, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Recovery alarm



Frame No., Board No. and LAPD link No.

30.2 Impact upon System The status of LAPD links recovers to normal.


30 1761 LAPD Link Fault Recovery M900/M1800 Packet Control Unit



30.4 Alarm Handling

Probable Cause The status of LAPD links recovers to be normal.


M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 31 1762 Communication Failed in BSC-PCU


31 1762 Communication Failed in BSC-PCU

31.1 Alarm Meaning

Description When all the LAPD links between PCU and a BSC are disconnected due to faults, namely, when the signalling channel between PCU and BSC is disconnected, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Critical alarm

Fault alarm

Communications system


1762 1763


Frame No., board No. and BSC No.

31.2 Impact upon System The communications interruption makes it impossible to implement signalling exchange between BSC and PCU. If the system is under initialization, it will lead to the initialization failure of the cells under the BSC. If the system is running, it may lead to service interruption (the system cannot continue to provide services), and may also lead to other abnormalities to BSC and PCU.

31 1762 Communication Failed in BSC-PCU M900/M1800 Packet Control Unit




31.4 Alarm Handling

Probable Cause Step 1 BSC is reset.

Step 2 All the LAPD links from PCU to a BSC is failed.

----End

Recommendation Step 1 Check whether the physical connection between PCU and BSC is normal.


Step 2 Check whether PCU and BSC are consistent in data configurations for LAPD.


Step 3 Check the status of all the LAPD links connected to the BSC.

Check and confirm that the link is in unblock status with the command mt lapd show state, or else, please unblock the link in PCU or BSC.

Step 4 Check whether the running status of BSC is normal, or else, please contact BSC maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling

32 1763 Communication Recovered in BSC-PCU


32 1763 Communication Recovered in BSC-PCU

32.1 Alarm Meaning

Description When the communication between BSC and PCU recovers, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Critical alarm

Recovery alarm



1763 None


Frame No., board No. and BSC No.

32.2 Impact upon System PCU system can provide GPRS services again.


32 1763 Communication Recovered in BSC-PCU M900/M1800 Packet Control Unit



32.4 Alarm Handling

Probable Cause At least one of the LAPD link to a BSC is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 33 1764 Cell BTS Does Not Support GPRS


33 1764 Cell BTS Does Not Support GPRS

33.1 Alarm Meaning

Description When PCU is initializing cells, it should issue a configuration message to the BTS that the cells belong to and wait for the response. If the BTS does not support GPRS services, it will send a relevant response message to PCU. Then this alarm will be triggered when PCU receives this information.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Event alarm

Miscellaneous Miscellaneous 1764 None


Frame No., board No. and Cell ID.

33.2 Impact upon System This alarm indicates that BTS does not support GPRS services, and the corresponding cells cannot provide GPRS services.

33 1764 Cell BTS Does Not Support GPRS M900/M1800 Packet Control Unit



33.3 System Self-processing procedures The corresponding cells cannot provide GPRS services normally, but this does not impact the services of other cells. When BSS is reset, the cells are reset by PCU or when the cells are under operation and maintenance, PCU will resend the configuration message to the BTS.

33.4 Alarm Handling

Probable Cause Step 1 The BSC is not configured to support GPRS.

Step 2 This version of BTS does not support GPRS.

----End

Recommendation Step 1 Check and confirm that this cell is configured as supporting GPRS in BSC, or else please

contact BTS maintenance engineer to modify the configuration.

Step 2 Check and confirm this version of BTS support GPRS, or else, please contact BTS maintenance engineer to update the BTS to support GPRS.

----End


34 1765 No Response When Sends SI13 to BSC


34 1765 No Response When Sends SI13 to BSC

34.1 Alarm Meaning

Description PCU sends the SI13 and relevant commands to BSC, and waits for the response information. If PCU cannot receive the response information, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Event alarm



Frame No., board No. and Cell ID.

34.2 Impact upon System This alarm indicates that BSC might not receive the SI13 and related information from PCU.

In the case that BSC has not received the SI13, the broadcasting of the system information in the related cell may be abnormal and the cells cannot provide GPRS services; in the case that the system information from PCU and BSC conflicts, the GPRS services provided by the cells become confused.

34 1765 No Response When Sends SI13 to BSC M900/M1800 Packet Control Unit



34.3 System Self-processing procedures The corresponding cells cannot provide GPRS services normally, but this does not impact the services of other cells. When the cells are reset by PCU or BSC, or when the cells are under operation and maintenance, PCU will resend the SI13 message and relevant commands to the BSC.

34.4 Alarm Handling

Probable Cause Step 1 The BSC is abnormal.

Step 2 The LAPD links between PCU and BSC are interrupted.

----End

Recommendation Step 1 Check the status of communication between PCU and BSC. If there is a "Communication

between BSC and PCU Interrupted" alarm, proceed to the following procedures:



2. Check whether PCU and BSC are consistent in data configurations for LAPD.


3. Check the management status of all the LAPD links between PCU and the BSC.

Check and confirm the LAPD link is unblocked with the command mt lapd show state, or else, please unblock the LAPD link manually.

Step 2 Check and confirm the BSC is normal, or else, please contact BSC maintenance engineer for handling..

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 35 1766 Pb E1 Local Port Out-of-syn.


35 1766 Pb E1 Local Port Out-of-syn.

35.1 Alarm Meaning

Description When Pb interface E1 port local end out-of-sync. Is detected, this alarm will be triggered.

Principle of local end out-of-sync. alarm and remote end out-of-sync. alarm is introduced in the following:

Rx

Tx Rx

Tx

Port A Port B


When port A cannot synchronize correct clock signals from its Rx line, it will report Pb interface E1 port Local End Out-of-sync. alarm. Causes for this alarm lies in disconnection of relay or the poor quality of signals. In the meantime, port A will send a special signal to port B through its Tx line, informing port B about the event. After reception of the signal, port B will report Pb interface E1 port Remote End Out-of-sync. alarm.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major alarm

Fault alarm



1766 1767


35 1766 Pb E1 Local Port Out-of-syn. M900/M1800 Packet Control Unit



Frame No., L2PU board No., module No. (or module name) and port No.

35.2 Impact upon System Because the data and signalling interaction between PCU and BSC is implemented via E1 trunk, if the E1 trunk at the local end is out of synchronization, it will have a severe impact on the communication between PCU and BSC, and hence packet service becomes impossible.


35.4 Alarm Handling

Probable Cause Step 1 Rx line of PCU to BSC is interrupted.


Step 3 The quality of signal transferred on the cable is poor.

----End

Recommendation Step 1 Check whether the physical connection between PCU and BTS is normal.


Step 2 Check whether the deviation of BSC E1 clock is less than 0.1 Hz.

Use a frequency meter to measure the output port of the 2MHz clock of TMU. The frequency deviation should be less than 0.1 Hz.

If the deviation is over 0.1 Hz, the problem possibly lies in the upper stratum clock. Contact the relevant maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 36 1767 Pb E1 Local Port Out-of-syn Removed


36 1767 Pb E1 Local Port Out-of-syn Removed

36.1 Alarm Meaning

Description After PCU system reports " Pb E1 Local Port Out-of-syn.” alarm, if it detects the synchronization signals of E1 port can be correctly extracted once again, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Recovery alarm



1767 None


Frame No., L2PU board No., module No.(or module name) and port No.

36.2 Impact upon System The communication between PCU and BSC is recovered.


36 1767 Pb E1 Local Port Out-of-syn Removed M900/M1800 Packet Control Unit



36.4 Alarm Handling

Probable Cause The Rx cable of E1 for PCU is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 37 1768 Pb E1 Peer Port Out-of-syn


37 1768 Pb E1 Peer Port Out-of-syn

37.1 Alarm Meaning

Description When Pb E1 peer port out-of-syn. is detected, this alarm will be triggered.

Principle of local end out-of-sync. alarm and peer end out-of-sync. alarm is introduced in the following:


Rx

Tx Rx

Tx

Port A Port B

When port A cannot synchronize correct clock signals from its Rx line, it will report Pb E1 port Local End Out-of-sync. alarm. Causes for this alarm lies in disconnection of relay or the poor quality of signals. In the meantime, port A will send a special signal to port B through its Tx line, informing port B about the event. After reception of the signal, port B will report Pb E1 port peer End Out-of-sync. alarm.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Fault alarm



1768 1769

37 1768 Pb E1 Peer Port Out-of-syn M900/M1800 Packet Control Unit




Frame No., L2PU board No., module No.(or module name) and port No.

37.2 Impact upon System Because the data and signalling interaction between PCU and BSC is implemented via E1 trunk, if the E1 trunk at the remote end is out of synchronization, it will have a severe impact on the communication between PCU and BSC, and hence packet service processing becomes impossible.


37.4 Alarm Handling

Probable Cause Step 1 Tx cable of E1 for PCU is interrupted.


Step 3 The quality of the transmission path is poor.

----End




Use a frequency meter to measure the output port of the 2MHz clock of TMU. The frequency deviation should be less than 0.1 Hz. If the deviation is over 0.1 Hz, the problem possibly lies in the upper stratum clock. Contact the relevant maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 38 1769 Pb E1 Peer Port Out-of-syn Removed


38 1769 Pb E1 Peer Port Out-of-syn Removed

38.1 Alarm Meaning

Description After PCU system reports "Pb E1 Port Peer End Out-of-Sync.” alarm, if it detects that the alarm signal of the peer end has disappeared, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Recovery alarm



1769 None


Frame No., L2PU board No., module No. (or module name) and port No.

38.2 Impact upon System Because the data and signalling interaction between PCU and the peer end is implemented via E1 trunk, if the remote end E1 trunk out-of-sync. is removed, the system will process packet service normally.


38 1769 Pb E1 Peer Port Out-of-syn Removed M900/M1800 Packet Control Unit



38.4 Alarm Handling

Probable Cause Step 1 The Tx cable of E1 for PCU is recovered.

Step 2 Since Pb E1 Local Port is Out-of-syn., it is impossible to detect whether the peer end is normal.

----End

Recommendation If the Tx cable of E1 for PCU is normal, no handling is needed. If the alarm Pb E1 port local Out-of-syn.is also reported, please take actions according to 1766 Pb E1 Local Port Out-of-syn.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 39 1771 Low Quality of TRAU Link


39 1771 Low Quality of TRAU Link

39.1 Alarm Meaning

Description When the ratio of CRC error frames of TRAU PCU receives from a certain TRAU link exceeds 0.5%, this alarm will be reported.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Event alarm



Frame No., L2PU board No., module No. (or module name), the port No. on L2PU board, 16k timeslot No. and erroneous block rate.

39.2 Impact upon System The poor quality of TRAU links may lead to TRAU link out-of-sync., thus impacting the transmission rate of packet service, or even making packet service processing impossible.


39 1771 Low Quality of TRAU Link M900/M1800 Packet Control Unit



39.4 Alarm Handling

Probable Cause Step 1 The clock is unstable.

Step 2 The quality of transmission path is poor.

----End


View the ALM indicator (yellow) on the involved L2PU board. If the indicator flashes, it indicates physical connection fault, please check and remove the fault. For example, check and confirm the connection between E1 cable and L2PU board and the connection between E1 cable and PDF are normal, the trunk between PCU and BSC or between BSC and BTS is normal.


Use a frequency meter to measure the output port of the 2MHz clock of TMU. The frequency deviation should be less than 0.1 Hz. If the deviation is over 0.1 Hz, the problem possibly lies in the upper stratum clock. Contact the relevant maintenance engineer for handling.

Step 3 Check the quality of line transmission path.

Poor quality of transmission path will trigger this alarm. If the bit error ratio is greater than 10-5, please contact transmission equipment maintenance engineer for handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 40 1775 Inconsistent BSC-PCU PCIC Config


40 1775 Inconsistent BSC-PCU PCIC Config

40.1 Alarm Meaning

Description The PCIC on the PCU side is different from that on the BSC side.

When the PCU finds the starting PCIC numbers on an E1 of both sides are different, it reports the alarm.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Minor alarm

Event alarm



1775 None


Frame No., Board No., Port No..

40.2 Impact upon System The inconsistent configuration can cause abnormal operation of the system.


40 1775 Inconsistent BSC-PCU PCIC Config M900/M1800 Packet Control Unit



40.4 Alarm Handling

Probable Cause The PCIC configuration is inconsistent between PCU and BSC.

Recommendation Please check the PCIC configuration of both PCU and BSC.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 41 1800 PCU-BTS TRAU Link Fault


41 1800 PCU-BTS TRAU Link Fault

41.1 Alarm Meaning

Description The bottom layer module of TRAU sends uplink data packets every 20ms. After receipt of the data packets, PCU checks whether they are valid or fault data. If PCU detects that the data sent from the bottom layer module of TRAU are all fault data for several successive times, PCU will report this alarm.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Fault alarm



Frame No., board No., module No. (or module name), cell No., TRX No. and timeslot No.

41.2 Impact upon System The links of the bottom layer module of TRAU are connected with PCU and BTS so that the data interaction between MS and GPRS network can be implemented. If any fault occurs to the links, the communication between BTS and PCU will be interrupted, and hence packet service processing becomes impossible.


41 1800 PCU-BTS TRAU Link Fault M900/M1800 Packet Control Unit



41.4 Alarm Handling

Probable Cause Step 1 The connection between BSC and BTS is interrupted.

Step 2 The related TRX is power off.

Step 3 The version of BTS does not match with that of BSC.

----End

Recommendation Step 1 Check and confirm the configuration of E1 timeslots in PCU is correspondent to the

configuration of PCIC in BSC, or else, please modify it.

Step 2 Check whether the physical connection between PCU and BSC is normal

View the ALM indicator (yellow) on the involved L2PU board. If the indicator flashes, it indicates physical connection fault, please check and remove the fault. For example, check and confirm the Tx and Rx ends have not been connected in reverse way, the connection between E1 cable and L2PU board and the connection between E1 cable and PDF are normal, the trunk between PCU and BSC or between BSC and BTS is normal.

Step 3 Check and confirm the channel of fault link is normal, or else, please contact BSC maintenance engineer for handling.

Step 4 Check and confirm the BTS and BSC is normal, and the version of BTS matches that of BSC, or else, please contact BSC maintenance engineer for further handling.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 42 1801 PCU-BTS TRAU Link Recovery


42 1801 PCU-BTS TRAU Link Recovery

42.1 Alarm Meaning

Description The bottom layer module of TRAU sends uplink data packets every 20ms. After receipt of the data packets, PCU checks whether they are valid or fault data. After PCU detects for a couple of successive times that the data sent from the bottom layer module of TRAU are fault data, if it goes on to receive normal and valid data, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Fault alarm



Frame No., board No., module No. (or module name), cell No., TRX No. and timeslot No.

42.2 Impact upon System After TRAU links recover to normally status, the packet service of PCU can be processed normally.


42 1801 PCU-BTS TRAU Link Recovery M900/M1800 Packet Control Unit



42.4 Alarm Handling

Probable Cause The transmission of TRAU frame is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 43 1802 TRX Type Configuration Error


43 1802 TRX Type Configuration Error

43.1 Alarm Meaning

Description PCU detects that the TRX type configured in BSC is incorrect.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Event alarm



Frame No., board No., module No. (or module name), cell No., and TRX No.

43.2 Impact upon System If a non-EGPRS TRX is configured as an EGPRS TRX at BSC, the packet channel configured on the TRX cannot be synchronized after being activated, and hence the TRX cannot provide GPRS services.

If an EGPRS TRX is configured as a common TRX, the packet channel configured on the TRX can be synchronized after being activated, and this alarm will not occur.


43 1802 TRX Type Configuration Error M900/M1800 Packet Control Unit



43.4 Alarm Handling

Probable Cause Normal TRX is configured as EGPRS TRX in BSC.

Recommendation Step 1 Please reconfigure the TRX type in BSC.

Step 2 Then check whether the status of PDCHs on it at PCU is “synchronized”.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 44 1824 CPU Overload


44 1824 CPU Overload

44.1 Alarm Meaning

Description When the system detects that the occupancy rate of CPU exceeds 86% during its real-time statistics, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Test alarm



Frame No., board No., statistic period, and CPU occupancy rate.

44.2 Impact upon System If alarms occur occasionally, indicating that the current traffic is quite heavy, the normal running of the system will not be affected.

But if the occurrence of the alarm is not due to heavy traffic, it may impact upon the provision of the GPRS.


44 1824 CPU Overload M900/M1800 Packet Control Unit



44.4 Alarm Handling

Probable Cause Step 1 The traffic is heavy.

Step 2 Some operation such as too much performance measurement may lead to the high occupancy rate.

----End

Recommendation Check whether the operations such as FTP, performance measurement task register and file operating are being implemented. If so, terminate the operations. or else, please make the performance measurement to check whether it is due to heavy traffic. If the traffic is too much heavy, system expansion is recommended.

If it is not due to heavy traffic, please write down the alarm occurrence frequency (occasional occurrence, frequent occurrence, and constant occurrence) and the alarm parameters (Frame No., board No., statistic period, and CPU occupancy rate) and contact Huawei technical support engineers for handling.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 45 1825 Clock Synchronization Alarm


45 1825 Clock Synchronization Alarm

45.1 Alarm Meaning

Description With the SNTP protocol, the system synchronizes clock with the clock server. If the system fails to get the clock from the server for continuous three times or the clock adjustment is beyond the threshold, this alarm is reported.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Event alarm



Frame No., board No., reason, old clock(UTC), adjustment

45.2 Impact upon System Clock synchronization fail indicates communication failure between the PCU and the server. Before communication recovers, the PCU uses the local clock.

If the clock adjustment is too large, that indicates the change of the PCU local clock is too large. This has great impact on alarms records and traffic statistics that are related to time.


45 1825 Clock Synchronization Alarm M900/M1800 Packet Control Unit



45.4 Alarm Handling

Probable Cause Step 1 Cause 0: failed to communicate with the server.

Step 2 Cause 1: the clock or time district configuration of the PCU or server have been adjusted.

----End

Recommendation Step 1 Check if the SNTP server is available and the clock is right.

Step 2 Execute "sntp disble" to shut the SNTP function or "sntp set server" to configure a new server.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 46 1850 Active POMU Fault


46 1850 Active POMU Fault

46.1 Alarm Meaning

Description The standby POMU board checks the status of hardware and software running in active POMU board periodically. When the standby POMU board finds the hardware or/and software in active POMU board is faulty, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Event alarm

Equipment alarm

Equipment alarm 1850 None


Frame No. and board No.

46.2 Impact upon System The PCU system will switch over the active/standby POMU boards, and all the boards in the Frame will be restarted, leading to temporary service interruption.

46.3 System Self-processing procedures When the standby POMU board detects that fault has occurred to the active POMU board, it initiates active/standby switchover. The previous standby POMU board will act as active board and will be in charge of the whole Frame.

46 1850 Active POMU Fault M900/M1800 Packet Control Unit



46.4 Alarm Handling

Probable Cause Step 1 The active POMU board is faulty or not plugged on the backboard.

Step 2 The communication between active and standby POMU board is abnormal.

----End

Recommendation Step 1 Check and confirm the cable connects LAN Switch and POMU board is normal.

Step 2 Check and confirm the LAN Switch is normal.

Connect a network port of LAN Switch to the PC. If the network card indicator is off, indicating LAN Switch fault, please reset the LAN Switch.

Step 3 Check the previous active POMU board (the standby POMU board after the switchover).

Reset the standby POMU board. If the fault cannot be removed, please replace the faulty board.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 47 1851 Standby POMU Fault


47 1851 Standby POMU Fault

47.1 Alarm Meaning

Description The active POMU board checks the status of hardware and software running in standby POMU board periodically. When the active POMU board finds the hardware or/and software in standby POMU board is faulty, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Fault alarm

Equipment alarm

Equipment alarm 1851 1852



47.2 Impact upon System The standby POMU board fault will not impact service. However, as there is no available standby POMU board in the system, if fault occurs to the active POMU board simultaneously, it will lead to long-time service interruption.

47.3 System Self-processing procedures The active POMU board will attempt to reset the standby POMU board after it detects the standby POMU board fault.

47 1851 Standby POMU Fault M900/M1800 Packet Control Unit



47.4 Alarm Handling

Probable Cause Step 1 There is no standby POMU board or the standby POMU board is faulty.

Step 2 The communication between active and standby POMU boards is interrupted.

----End

Recommendation Step 1 Check and confirm the cable connects LAN Switch and POMU board is normal.

Step 2 Check and confirm the LAN Switch is normal.

Connect a network port of LAN Switch to the PC. If the network card indicator is off, which indicates LAN Switch fault, please reset the LAN Switch.

Step 3 Reset the standby POMU board. If the fault cannot be removed, please replace the faulty board.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 48 1852 Standby POMU Recovered


48 1852 Standby POMU Recovered

48.1 Alarm Meaning

Description The active POMU board checks the status of hardware and software running in standby POMU board periodically. After the standby POMU board is faulty ,and the active POMU board finds the hardware and software in standby POMU board is recovered, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Recovery alarm

Equipment alarm




48.2 Impact upon System The standby POMU board go on to provide the backup function.


48 1852 Standby POMU Recovered M900/M1800 Packet Control Unit



48.4 Alarm Handling

Probable Cause The standby POMU board is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 49 1853 RPPU Hardware Fault


49 1853 RPPU Hardware Fault

49.1 Alarm Meaning

Description POMU board detects the status of RPPU board periodically. If it detects that RPPU board is abnormal, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Fault alarm

Equipment alarm




49.2 Impact upon System After fault occurs to RPPU board, the cells that configured on this board and also configured standby board will be migrated to the standby board, leading to temporary service interruption to the involved cells.

49.3 System Self-processing procedures Step 1 If the standby board has been configured for the cells, the system will automatically migrate

the cells from the faulty RPPU board to the standby board.

Step 2 POMU board attempts to reset the faulty RPPU board.

49 1853 RPPU Hardware Fault M900/M1800 Packet Control Unit



----End

49.4 Alarm Handling

Probable Cause Step 1 The hardware of the RPPU board is faulty.

Step 2 There is no such RPPU board.

----End

Recommendation Step 1 Check whether there are RPPU board recovery alarms.

After RPPU hardware fault alarm occurs, the system implements self-processing, such as resetting the faulty RPPU board. If the fault is removed, the system will report the corresponding recovery alarm.

Step 2 If there is no corresponding recovery alarm, please replace the faulty RPPU board.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 50 1854 RPPU Hardware Fault Recovered


50 1854 RPPU Hardware Fault Recovered

50.1 Alarm Meaning

Description POMU board detects the status of RPPU board periodically, and when the POMU board detects that the faulty RPPU board is recovered, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Recovery alarm

Equipment alarm




50.2 Impact upon System All the cells migrated to other RPPU boards will be remigrated to the recovered board. The relevant services will be temporarily interrupted.

50.3 System Self-processing procedures All the cells migrated to other RPPU boards will be remigrated to the recovered board.

50 1854 RPPU Hardware Fault Recovered M900/M1800 Packet Control Unit



50.4 Alarm Handling

Probable Cause The RPPU board is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 51 1855 RPPU Reset


51 1855 RPPU Reset

51.1 Alarm Meaning

Description When the POMU board detects that the RPPU board is reset, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Event alarm

Equipment alarm




51.2 Impact upon System RPPU board reset will lead to temporary interruption to all the services processing on this board. During the board reset, cells will not be migrated.


51 1855 RPPU Reset M900/M1800 Packet Control Unit



51.4 Alarm Handling

Probable Cause Step 1 The RPPU board is reset from PCU O&M console manually.

Step 2 The RPPU board is reset by the reset button on the panel of RPPU board.

Step 3 The running of software is abnormal and the board is reset by PCU automatically.

----End

Recommendation Step 1 Check whether there have been any RPPU board reset operations implemented by

maintenance engineer.

Use the command log browse to check the command log and see whether any maintenance engineer member ever used the command io reset to reset the RPPU board. Query whether any maintenance engineer member ever reset the RPPU board from OMC Shell/OMC at the Local WS.

Step 2 Check whether there are RPPU board fault alarms simultaneously.

If fault occurs to RPPU board, the system will automatically reset the board.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 52 1856 RPPU Software Fault


52 1856 RPPU Software Fault

52.1 Alarm Meaning

Description When the POMU board detects that RPPU board has failed to provide service after power-on for a period of time, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Fault alarm

Equipment alarm




52.2 Impact upon System The RPPU board cannot provide services.

52.3 System Self-processing procedures POMU board automatically resets the RPPU board.

52 1856 RPPU Software Fault M900/M1800 Packet Control Unit



52.4 Alarm Handling

Probable Cause Step 1 The version of software uploaded to RPPU board is not appropriate.

Step 2 The running of software is abnormal.

----End

Recommendation Step 1 Check and confirm that the RPPU board runs in MAX mode with the command io version

show, or else, please modify it with the command io version set, and then reset the RPPU board.

Step 2 Please contact the maintenance engineer to check and confirm the version of software is appropriate, or else, upload the software.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 53 1857 RPPU Software Fault Recovered


53 1857 RPPU Software Fault Recovered

53.1 Alarm Meaning

Description After POMU board detects a RPPU board software fault, if it detects that the faulty RPPU board goes on to provide service, this alarm will be generated.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Recovery alarm

Equipment alarm




53.2 Impact upon System RPPU board can provide the services normally.


53 1857 RPPU Software Fault Recovered M900/M1800 Packet Control Unit



53.4 Alarm Handling

Probable Cause The software of RPPU is running normally.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 54 1858 POMU Switchover


54 1858 POMU Switchover

54.1 Alarm Meaning

Description The standby POMU board will switch itself to be an active board and report this alarm to the alarm system when it detects that fault has occurred to the previous active POMU board or the active HSC board.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Fault alarm

Equipment alarm




54.2 Impact upon System After the switchover of the active/standby POMU boards, all the boards in the Frame will be restarted, leading to temporary service interruption.

54.3 System Self-processing procedures After the active/standby boards switchover, the previous standby POMU board will function as an active board and will be in charge of the whole Frame.

54 1858 POMU Switchover M900/M1800 Packet Control Unit



54.4 Alarm Handling

Probable Cause Step 1 The hardware and/or software of the active POMU board are abnormal.

Step 2 The hardware of the active HSC is abnormal.

Step 3 The communication between active and standby HSC is abnormal.

----End

Recommendation Check whether the system has generated "Active POMU Board Fault" alarm. The active/standby POMU boards will be automatically switched over after the PCU system reports this alarm.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 55 1859 POMU Switchover Failed


55 1859 POMU Switchover Failed

55.1 Alarm Meaning

Description When fault has occurred to the active POMU board or the active HSC board, the standby POMU board will automatically initiate the active/standby switchover. If the switchover fails, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Event alarm

Equipment alarm




55.2 Impact upon System The PCU equipment cannot provide the services.


55 1859 POMU Switchover Failed M900/M1800 Packet Control Unit



55.4 Alarm Handling

Probable Cause Internal software fault.

Recommendation Pull out the active POMU board, and power off the relevant PCU Frame, then power on again. After the system restarts to work, the previous standby board will function as an active board. In the meantime, contact Huawei technical support engineers of the local office for further handling.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 56 1860 Active HSC Fault


56 1860 Active HSC Fault

56.1 Alarm Meaning

Description The standby POMU board detects whether the active HSC board is plugged-in, and the active POMU board reports whether the active HSC board is normal to the standby POMU board. When the standby POMU board found that the active HSC was not plugged-in or received the fault information about the active HSC from active POMU board, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Fault alarm

Equipment alarm




56.2 Impact upon System After the active/standby switchover, all the boards in the Frame will be restarted, leading to temporary service interruption.

56.3 System Self-processing procedures When the standby POMU board detects that fault has occurred in the active HSC board, it initiates active/standby switchover. The previous standby POMU board will act as an active board and will be in charge of the whole Frame.

56 1860 Active HSC Fault M900/M1800 Packet Control Unit



56.4 Alarm Handling

Probable Cause Step 1 The active HSC is abnormal.

Step 2 The active HSC is plugged off.

----End

Recommendation If this alarm is triggered by the fault of the active HSC, please change the board.

If the active/standby POMU board is switched over since the active HSC is faulty, the primitive active HSC board will be the standby HSC board. There lies the correspondent relationship between the POMU boards and HSC boards, i.e., the HSC plugged in the 7th slot the correspond to the POMU plugged in the 8th slot, and the HSC plugged in the 9th slot correspond to the POMU plugged in the 6th slot. The HSC corresponds to the active POMU board is the active HSC.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 57 1861 Active HSC Fault Recovered


57 1861 Active HSC Fault Recovered

57.1 Alarm Meaning

Description The standby POMU board detects whether the active HSC board is plugged-in, and the active POMU board reports whether the active HSC board is normal to the standby POMU board. When the standby POMU board found that the active HSC was not plugged-in or received the fault information about the active HSC from the active POMU board, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Fault alarm

Equipment alarm




57.2 Impact on System None.

57.3 System Self-processing procedure None.

57 1861 Active HSC Fault Recovered M900/M1800 Packet Control Unit



57.4 Alarm Handling



! If the active POMU board and the standby POMU board are switched over because the

active HSC is faulty, the original active HSC board will be the standby HSC board. ! The active HSC corresponds to the active POMU and the standby HSC corresponds to the

standby POMU. The HSC in slot 7 corresponds to the POMU in slot 8, and the HSC in slot 9 corresponds to the POMU in slot 6.

! This alarm will not be reported due to the mapping mentioned above.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 58 1862 Standby HSC Fault


58 1862 Standby HSC Fault

58.1 Alarm Meaning

Description The active POMU board detects whether the standby HSC board is plugged-in, and the standby POMU board reports whether the standby HSC board is normal to the active POMU board. When the active POMU board found that the standby HSC was not plugged-in or received the fault information about the standby HSC from standby POMU board, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Fault alarm

Equipment alarm




58.2 Impact upon System The standby HSC board fault will not impact normal service. However, as there is no available standby HSC board in the system, if fault occurs to the active POMU board or the active HSC board simultaneously, it will lead to long-time service interruption.

58 1862 Standby HSC Fault M900/M1800 Packet Control Unit



58.3 System Self-processing procedures The active POMU board will attempt to reset the standby POMU board after it detects the standby HSC board fault.

58.4 Alarm Handling

Probable Cause Step 1 The hardware of the standby HSC board is fault.

Step 2 The standby HSC board is not plugged in the slot.

----End

Recommendation Step 1 If the standby HSC has not been configured, please add it.

Step 2 If the standby HSC board has been configured, please plug it off first, then plug it in. If the status of the HSC has not been recovered, please replace the faulty board.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 59 1863 Standby HSC Recovered


59 1863 Standby HSC Recovered

59.1 Alarm Meaning

Description After POMU board detects the standby HSC board fault, if it detects that the faulty RPPU board is in its slot, and receive the information from standby POMU board in which notify the status of standby HSC board is normal, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Recovery alarm

Equipment alarm






59 1863 Standby HSC Recovered M900/M1800 Packet Control Unit



59.4 Alarm Handling

Probable Cause The standby HSC board is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 60 1864 Harddisk Fault


60 1864 Harddisk Fault

60.1 Alarm Meaning

Description When the POMU board detects that the partitions of the harddisk cannot be accessed, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Fault alarm

Equipment alarm



Frame No., board No., module No. (or module name) and equipment name.

60.2 Impact upon System The active POMU board will be reset, and which will lead to the temporary interruption of the service.


60 1864 Harddisk Fault M900/M1800 Packet Control Unit



60.4 Alarm Handling

Probable Cause Step 1 No harddisk installed.

Step 2 Physical damage to harddisk.

----End

Recommendation Step 1 Check whether harddisk has been installed.

In the case of no harddisk installed, this alarm will be generated. Please install the harddisk.

Step 2 It takes 150s for the system to define a harddisk fault. If this alarm occurs, indicating unstable harddisk performance, replace the harddisk directly.

Step 3 Check and confirm the harddisk is normal with the command mt disk show, or else, please replace it with a sound harddisk.

Step 4 If further analysis is required, please dismantle the harddisk and check it with harddisk tools. If there is physical damage, the harddisk must be replaced.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 61 1865 Harddisk Recovered


61 1865 Harddisk Recovered

61.1 Alarm Meaning

Description After the alarm of harddisk fault is reported, when the POMU board found the partition can be access again, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Recovery alarm

Equipment alarm



Frame No., board No., module No. (or module name) and partition name.



61 1865 Harddisk Recovered M900/M1800 Packet Control Unit



61.4 Alarm Handling

Probable Cause The harddisk is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 62 1870 Alarm Box Fault


62 1870 Alarm Box Fault

62.1 Alarm Meaning

Description When the PCU cannot detect the alarm box, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Majorl alarm

Fault alarm

Equipment alarm



Frame No., board No. and error No.

62.2 Impact upon System Due to the alarm box fault, the maintenance engineer cannot get the audible and visual alarms, which reduces the availability of the system but has no impact on other services.


62 1870 Alarm Box Fault M900/M1800 Packet Control Unit



62.4 Alarm Handling

Probable Cause Step 1 No alarm box has been installed or the alarm box has not been installed correctly.

Step 2 The alarm box is not of GM12 or later version.

Step 3 Fault has occurred to the alarm box, or the cable between PCU and alarm box is abnormal.

----End

Recommendation Step 1 If no alarm box has been installed in the Host system, please install an alarm box or disregard

this alarm.

Step 2 If the error No. is 10, indicating inconsistency of the alarm box version, please replace it with GM12 or later version.

Step 3 If the error No is 11, please check and confirm that the alarm box has been correctly installed, the alarm box has been powered on and there is no fault in serial port cables, or else, please handle it according to the Alarm Box User Manual.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 63 1871 Alarm Box Fault Recovered


63 1871 Alarm Box Fault Recovered

63.1 Alarm Meaning

Description When the PCU detects the alarm box after it has sent the Alarm Box Fault, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Fault alarm

Equipment alarm




63.2 Impact upon System With the alarm box available, the audible and visual alarm can be generated.


63 1871 Alarm Box Fault Recovered M900/M1800 Packet Control Unit



63.4 Alarm Handling

Probable Cause PCU detects the alarm box is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 64 1872 L2PU Fault


64 1872 L2PU Fault

64.1 Alarm Meaning

Description When PCU detects that the L2PU board is abnormal, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Fault alarm

Equipment alarm



Frame No., and L2PU board No.

64.2 Impact upon System The Pb or Gb links on L2PU board are disconnected, thus impacting the normal processing of the services that utilize the links.


64 1872 L2PU Fault M900/M1800 Packet Control Unit



64.4 Alarm Handling

Probable Cause Step 1 The running of the software in the specified L2PU board is abnormal.

Step 2 The hardware of the specified L2PU board is fault.

----End

Recommendation Step 1 Check and confirm the software version of the L2PU board is appropriate, or else, please

upload the software.

Step 2 Reset the L2PU board and which may be recovered, or else, please replace it with sound board.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 65 1873 L2PU Fault Recovered


65 1873 L2PU Fault Recovered

65.1 Alarm Meaning

Description When the PCU detects the L2PU board is recovered after sending the L2PU Fault alarm, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Recovery alarm

Equipment alarm



Frame No., and L2PU board No.

65.2 Impact upon System The Pb or Gb links on the L2PU board become available.


65 1873 L2PU Fault Recovered M900/M1800 Packet Control Unit



65.4 Alarm Handling

Probable Cause The L2PU board is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 66 1874 Cells Successfully Migrated


66 1874 Cells Successfully Migrated

66.1 Alarm Meaning

Description When it detects that RPPU status becomes abnormal, the active POMU board will query the cell configuration status of RPPU board and the running status of each cell, and migrate all the cells running on this RPPU board to the configured standby RPPU board. After the cells are successfully migrated to the standby RPPU board, i.e., the cells are activated on the standby RPPU board, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Event alarm



Frame No., active RPPU board No. for the cells, standby RPPU board No. for the cells, and Cell ID.

66.2 Impact upon System Temporary interruption of the service in the involved cells will occur in course of migration.


66 1874 Cells Successfully Migrated M900/M1800 Packet Control Unit



66.4 Alarm Handling

Probable Cause The RPPU board is abnormal.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 67 1875 Cells Failed to Migrated


67 1875 Cells Failed to Migrated

67.1 Alarm Meaning

Description When the active POMU board detects the status of RPPU board transferred to be abnormal, it will intend to migrate all the cells configured in the abnormal RPPU board to the standby one, if the migration is failed, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Event alarm



Frame No., active RPPU No. for the cells, standby RPPU No. for the cells, and Cell ID.

67.2 Impact upon System All the cells involved cannot provide services.

67.3 System Self-processing procedures When the active RPPU board configured for the cells becomes faulty, and the cells fails to be migrated to the standby board, the system will monitor the status of the active/standby RPPU board and automatically reattempt to activate the cells.

67 1875 Cells Failed to Migrated M900/M1800 Packet Control Unit



67.4 Alarm Handling

Probable Cause Step 1 Both the active RPPU board and the standby one in which the cells are configured are

abnormal.

Step 2 The active RPPU board of the cells is abnormal, and more than 300 cells have already been activated in the standby board, or the activated cells in the standby RPPU board and the migrating cells belong to the different BSC.

Step 3 The running software is abnormal.

----End

Recommendation Step 1 Take actions to eliminate the failure according to the recommendation in 1853 RPPU

Hardware Fault

Step 2 Check whether the destination board is overloaded with cells.

The number of cells running on a RPPU board cannot exceed 300 and an RPPU board can only process the service with one BSC. Or else, it will lead to cell migration failure. First activate the cells with the command mt cell deactive, then modify the standby RPPU board No. configured for the cells with the command pcu set attr, and finally activate the cells with the command mt gcell active.

Step 3 Please activate the cells manually.

Please activate the cells with the command mt gcell active.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 68 1876 Cells Successfully Migrated Back


68 1876 Cells Successfully Migrated Back

68.1 Alarm Meaning

Description POMU board will attempt to migrate the cells back to the active RPPU board after it detects the active RPPU board recovers to normal status. If the remigration is successful, i.e., the cells can be activated and continue to provide services on the recovered RPPU board, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Event alarm




68.2 Impact upon System After the active RPPU board recovers and the cells are successfully remigrated back to this board, the cells will provide services on the active RPPU board, thus lessening the load of the standby RPPU board. In the course of migration, the services will be temporary interrupted.

68 1876 Cells Successfully Migrated Back M900/M1800 Packet Control Unit




68.4 Alarm Handling

Probable Cause The active RPPU board to the cells is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 69 1877 Cells Failed to Migrate Back


69 1877 Cells Failed to Migrate Back

69.1 Alarm Meaning

Description POMU board will attempt to migrate the cells back to the active RPPU board after it detects the active RPPU board recovers to normal status. If the remigration fails, i.e., the cells cannot be activated on the recovered active RPPU board, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Event alarm




69.2 Impact upon System If the remigration fails because no cell migration command has been received by the standby RPPU board, the cells will continue to provide services on the standby RPPU board .

But if the migration failure is due to a fault occurred after the cells have been migrated from the standby RPPU board, the cells cannot continue to provide services.

69 1877 Cells Failed to Migrate Back M900/M1800 Packet Control Unit



69.3 System Self-processing procedures POMU board will monitor the status of the active/standby RPPU board and automatically reattempt to activate the cells.

69.4 Alarm Handling

Probable Cause Step 1 The active RPPU board is normal, but the number of the activated cells is over 300.

Step 2 The deactivation of the cell on the standby RPPU board is failed, or the activation of the cells on the active RPPU board is failed.

----End

Recommendation At the PCU O&M terminal, activate the cells with the command mt gcell active. In the meantime, contact Huawei technical support engineers of the local office for further handling.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 70 1878 Cells Successfully Activated


70 1878 Cells Successfully Activated

70.1 Alarm Meaning

Description During the course of cell migration, if a cell fails to be migrated, the system will automatically monitor the status of the active/standby RPPU board and reattempt to activate the cell. If the cell is activated successfully, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Event alarm




70.2 Impact upon System After the system successfully activates the cell, the cell can continue to provide services.


70 1878 Cells Successfully Activated M900/M1800 Packet Control Unit



70.4 Alarm Handling

Probable Cause The cells are activated successfully.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 71 1879 Invalid SSN Alarm


71 1879 Invalid SSN Alarm

71.1 Alarm Meaning

Description POMU board will generate this alarm when it detects there is no valid PCU SSN (software serial No.) on POMU board.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Fault alarm

Miscellaneous Miscellaneous 1879 1880



71.2 Impact upon System After this alarm occurs, the system will work under default license. Some functions or the traffic may be restrained.


71 1879 Invalid SSN Alarm M900/M1800 Packet Control Unit



71.4 Alarm Handling

Probable Cause The SSN is invalid.

Recommendation Step 1 First, check whether the SSN has been purchased.

If not, purchase the license from Huawei.

Step 2 Check whether the SSN Hardware Fault alarm has simultaneously occurred. In case of occurrence, please replace the POMU board.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 72 1880 Invalid SSN Alarm Removed


72 1880 Invalid SSN Alarm Removed

72.1 Alarm Meaning

Description After the system generates an SSN Invalid alarm, if valid SSN is inputted, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Recovery alarm




72.2 Impact upon System PCU system will work under normal license.


72 1880 Invalid SSN Alarm Removed M900/M1800 Packet Control Unit



72.4 Alarm Handling

Probable Cause The valid SSN is inputted.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 73 1881 SSN Hardware Failure Alarm


73 1881 SSN Hardware Failure Alarm

73.1 Alarm Meaning

Description POMU board will generate this alarm when it detects a POMU hardware fault.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Fault alarm

Equipment alarm




73.2 Impact upon System After this alarm occurs, the system will work under default license. Some functions or the max, traffic will be restrained.


73 1881 SSN Hardware Failure Alarm M900/M1800 Packet Control Unit



73.4 Alarm Handling

Probable Cause POMU cannot get the valid SSN.

Recommendation Please replace the POMU board.

In order to keep on providing services, please switch over the active and standby POMU board with the command mt system forceswitch before the replacement of the faulty POMU board.


74 1882 SSN Hardware Failure Alarm Removed


74 1882 SSN Hardware Failure Alarm Removed

74.1 Alarm Meaning

Description When POMU board processes SSN and detects that the hardware fault has been removed, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Recovery alarm




74.2 Impact upon System The system will work normal again.


74 1882 SSN Hardware Failure Alarm Removed M900/M1800 Packet Control Unit



74.4 Alarm Handling

Probable Cause The POMU board is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 75 1883 Standby POMU SSN Alarm


75 1883 Standby POMU SSN Alarm

75.1 Alarm Meaning

Description When the standby POMU board is updating SSN, if an error occurs, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Fault alarm




75.2 Impact upon System This alarm has no impact on the current services, but will impact the system after the active/standby switchover. If no measures are taken, once the boards are switched over, the system will work under default license, and hence some functions or services will be possibly restrained.


75 1883 Standby POMU SSN Alarm M900/M1800 Packet Control Unit



75.4 Alarm Handling

Probable Cause The standby POMU board is abnormal.

Recommendation Replace the standby POMU board.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 76 1884 Standby POMU SSN Alarm Removed


76 1884 Standby POMU SSN Alarm Removed

76.1 Alarm Meaning

Description When the hardware fault of the standby POMU board is removed, or when it acquires a public key, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major alarm

Recovery alarm




76.2 Impact upon System After the active/standby switchover, the system will work normally.


76 1884 Standby POMU SSN Alarm Removed M900/M1800 Packet Control Unit



76.4 Alarm Handling

Probable Cause The SSN of the standby POMU board is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 77 1885 Lost Key Alarm


77 1885 Lost Key Alarm

77.1 Alarm Meaning

Description PCU system will generate this alarm when it detects there is no valid key configured.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Fault alarm




77.2 Impact upon System After this alarm occurs, the system will work under default license. Some functions or the traffic may be restrained.


77 1885 Lost Key Alarm M900/M1800 Packet Control Unit



77.4 Alarm Handling

Probable Cause No valid key is configured.

Recommendation Input the public key, or ask Huawei technical support engineers to replace the POMU board.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 78 1886 Lost Key Alarm Removed


78 1886 Lost Key Alarm Removed

78.1 Alarm Meaning

Description When PCU detects a valid key after it has reported " Lost Key Alarm ", this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Critical alarm

Recovery alarm




78.2 Impact upon System The system will be licensed to work normally.


78 1886 Lost Key Alarm Removed M900/M1800 Packet Control Unit



78.4 Alarm Handling

Probable Cause The SSN is recovered.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 79 1887 System Overload Alarm


79 1887 System Overload Alarm

79.1 Alarm Meaning

Description This alarm occurs when the user number or the traffic in the Gb interface of the PCU system exceeds the preset value for a long and consecutive time.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Major Alarm

Event alarm



Frame No. , board No., capacity expansion cause, port No., BCID,

79.2 Impact upon System If the activated user number or the traffic at the Gb interface of the PCU system exceeds 80% of the preset value, optimize the data at the Gb interface or the expand the capacity of the PCU.


79 1887 System Overload Alarm M900/M1800 Packet Control Unit



79.4 Alarm Handling

Probable Cause Cause value 0 : the activated user number exceeds 80% of the preset value.

Cause value 1/2/3: the traffic at the Gb interface exceeds 80% of the preset value.

Recommendation Take corresponding measures according to different causes:

! Cause value 0 : buy a new SSN from Huawei. ! Cause value 1/2/3: Configure more TS for the BC or adjust the cells of the GB. If the

total capacity of the BC arrives the preset value, contact Huawei to buy a new SSN. ! If the current hardware equipment already supports the max capacity, upgrade the

hardware.

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 80 1888 Cells Successfully Deactivated


80 1888 Cells Successfully Deactivated

80.1 Alarm Meaning

Description If cell deactivation fails, the system will automatically reattempt to deactivate the cells. If cell deactivation succeeds, this alarm will be triggered.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery Alarm ID

Warning alarm

Event alarm



Frame No., board No. and alarm module.



80 1888 Cells Successfully Deactivated M900/M1800 Packet Control Unit



80.4 Alarm Handling

Probable Cause The deactivation is successful after several times of failure.

Recommendation None

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 81 1889 SIG Successfully Migrated


81 1889 SIG Successfully Migrated

81.1 Alarm Meaning

Description In case of failure of RPPU board, if the SIG entity in the failed RPPU board is successfully migrated to its original configured standby RPPU, this alarm will be reported.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor Alarm

Event alarm

Gb Interface Gb Interface 1889 1890


Frame No., Original active RPPU board No., Original standby RPPU board No., Current active RPPU board No., Current standby RPPU board No., NSEI

81.2 Impact upon System The services will not be interrupted while the SIG entity migrating.


81 1889 SIG Successfully Migrated M900/M1800 Packet Control Unit



81.4 Alarm Handling



M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 82 1890 SIG Successfully Migrated Back


82 1890 SIG Successfully Migrated Back

82.1 Alarm Meaning

Description SIG entity is successfully migrated back to its original active RPPU when its original active RPPU recovers or reset.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Minor Alarm

Event alarm

Gb Interface Gb Interface 1890 None


Frame No., Original active RPPU board No., Original standby RPPU board No., Current active RPPU board No., Current standby RPPU board No., NSEI

82.2 Impact upon System The services will not be interrupted while the SIG entity migrating back.


82 1890 SIG Successfully Migrated Back M900/M1800 Packet Control Unit



82.4 Alarm Handling



M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 83 1895 POMUs IP Connection Failed


83 1895 POMUs IP Connection Failed

83.1 Alarm Meaning

Description This alarm is triggered when POMUs failed to shake hands through IP connection.

Alarm Information

Alarm level

Alarm type

NM alarm category


Alarm ID

Recovery alarm ID

Major Alarm

Fault alarm



Frame No.,BoardNo.

83.2 Impact upon System Interrupt the GPRS servers.


83 1895 POMUs IP Connection Failed M900/M1800 Packet Control Unit



83.4 Alarm Handling

Probable Cause This alarm is triggered when POMUs failed to shake hands through IP connection.

Recommendation Step 1 Check the cable connects LAN Switch and POMU board.

Step 2 Check and confirm the LAN Switch is normal, if not reset it.

Step 3 Check the arp-proxy function in local routers, if open, close it.

----End

M900/M1800 Packet Control Unit Maintenance Manual - Alarm Handling 84 1896 POMUs IP Connection Recovered


84 1896 POMUs IP Connection Recovered

84.1 Alarm Meaning

Description IP connection between two POMUs is recovered,this alarm will be triggered.

Alarm Information

Alarm level



Alarm ID

Recovery alarm ID

Major Alarm

Recoverery alarm



Frame No., BoardNo.

84.2 Impact upon System none.


84 1896 POMUs IP Connection Recovered M900/M1800 Packet Control Unit



84.4 Alarm Handling



PCU Alarm Guide

Documents

command e1t1

huawei technologies

command e1t1

command nsvc

problem possibly

maintenance

find free

command bc