Alarm Reference (V900R007C02 02)

HUAWEI GGSN9811 Gateway GPRS Support Node
V900R007C02
Alarm Reference
Issue
02
Date
2009-06-30
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.


Alarm Reference
Contents
Contents
About This Document.....................................................................................................................1
1 ALM-0500 Physical entity is removed....................................................................................1-1
2 ALM-0501 Physical entity is unstable....................................................................................2-1
3 ALM-0502 Physical entity is restart........................................................................................3-1
4 ALM-0503 Communication channel is faulty.......................................................................4-1
5 ALM-0504 Physical entity failed.............................................................................................5-1
6 ALM-0505 Physical Entity changed to stand by...................................................................6-1
7 ALM-0506 Physical entity changed to the offline state......................................................7-1
8 ALM-0507 Physical entity temperature exceeded upper prealarm limit.........................8-1
9 ALM-0508 Physical entity temperature exceeded lower prealarm limit.........................9-1
10 ALM-0509 Physical entity humidity exceeded upper prealarm limit..........................10-1
11 ALM-0510 Physical entity humidity exceeded lower prealarm limit..........................11-1
12 ALM-0511 Physical entity voltage exceeded upper prealarm limit..............................12-1
13 ALM-0512 Physical entity voltage exceeded lower prealarm limit..............................13-1
14 ALM-0550 Physical line Down............................................................................................14-1
15 ALM-0601 License default config.......................................................................................15-1
16 ALM-0602 License overtime.................................................................................................16-1
17 ALM-0603 License will overtime.........................................................................................17-1
18 ALM-0604 License invalid....................................................................................................18-1
19 ALM-0605 License ESN invalid...........................................................................................19-1
20 ALM-0606 License config decrease.....................................................................................20-1
21 ALM-0610 Interface-Probe Fault Alarm.............................................................................21-1
22 ALM-0611 IP-Probe Fault Alarm.........................................................................................22-1
23 ALM-0618 None of the NTP servers replies......................................................................23-1
Issue 02 (2009-06-30)

Contents

Alarm Reference
24 ALM-0630 -48V input alarm.................................................................................................24-1

25 ALM-0631 External sensor alarm.........................................................................................25-1
26 ALM-0632 Insufficient Hard Disk Space..........................................................................26-1
27 ALM-0633 Hard Disk Error..................................................................................................27-1
28 ALM-0634 CPU Overload Alarm.........................................................................................28-1
29 ALM-0635 DPD detecting failed.........................................................................................29-1
30 ALM-0636 Recover Configuration Failure........................................................................30-1
31 ALM-0637 The master and slave SRU board's configure is different..........................31-1
32 ALM-0638 IKE negotiating tunnel abnormal...................................................................32-1
33 ALM-0639 Absence of physical entity................................................................................33-1
34 ALM-0650 The usage of Fragment Resource exceeds alarm threshold........................34-1
35 ALM-0701 Invalid operator login........................................................................................35-1
36 ALM-0702 Operator password is wrong............................................................................36-1
37 ALM-0703 Operator Account Change................................................................................37-1
38 ALM-0704 Operator Access To Log File.............................................................................38-1
39 ALM-0705 Operator Unauthorized Access Attempt........................................................39-1
40 ALM-0801 License is about to use up.................................................................................40-1
41 ALM-0802 License has been used up.................................................................................41-1
42 ALM-0803 Signalling path disconnected...........................................................................42-1
43 ALM-0804 Data path disconnected.....................................................................................43-1
44 ALM-0805 The usage of local address pool exceeds alarm threshold..........................44-1
45 ALM-0806 No response of the RADIUS authentication server.....................................45-1
46 ALM-0807 ARP threshold control of an APN...................................................................46-1
47 ALM-0808 ARP threshold control of the GGSN..............................................................47-1
48 ALM-0810 The GGSN and the BMSC are disconnected................................................48-1
49 ALM-0811 MBMS Service Flow Interruption...................................................................49-1
50 ALM-0812 RADIUS accounting server has no responding............................................50-1
51 ALM-0813 The usage of CDR POOL exceed alarm threshold.......................................51-1
52 ALM-0814 The communications path to CG is down alarm..........................................52-1
53 ALM-0815 The version of GTP' is not supported............................................................53-1
ii

Issue 02 (2009-06-30)

Alarm Reference
Contents
54 ALM-0816 CG redirection failed.........................................................................................54-1

55 ALM-0817 The GGSN and the OCS are disconnected...................................................55-1
56 ALM-0818 Disconnection Between the GGSN and FTP Server for CDR Audit.......56-1
57 ALM-0819 Insufficient Service Node Resources..............................................................57-1
58 ALM-0820 Redirection Server Unavailable.......................................................................58-1
59 ALM-0821 LNS Group has no responding........................................................................59-1
60 ALM-0822 IP spoofing has arisen.......................................................................................60-1
61 ALM-0826 The redirection server has no responding.....................................................61-1
62 ALM-0827 Disconnection Between GGSN and PCRF....................................................62-1
63 ALM-0828 Disconnection Between GGSN and Reporting Server...............................63-1
64 ALM-0829 Update the rule-library of SIG-CBB Failed...................................................64-1
65 ALM-0830 DPI service unavailable....................................................................................65-1
66 ALM-0835 Traffic control alarm..........................................................................................66-1
Issue 02 (2009-06-30)

iii

Alarm Reference
About This Document
About This Document

Purpose
This document describes the basic principle and operation of the alarm of the GGSN9811.
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
GGSN9811
V900R007C02
Intended Audience
The intended audiences of this document are:
l
Network monitoring engineer
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous issues.
Updates in 02 (2009-06-30)
The second commercial release has the following updates:
The mistakes are corrected.
Updates in Issue 01 (2009-05-26)
Initial commercial release.
Organization
1 ALM-0500 Physical entity is removed
2 ALM-0501 Physical entity is unstable
3 ALM-0502 Physical entity is restart
Issue 02 (2009-06-30)


Alarm Reference
About This Document
4 ALM-0503 Communication channel is faulty

5 ALM-0504 Physical entity failed
6 ALM-0505 Physical Entity changed to stand by
7 ALM-0506 Physical entity changed to the offline state
8 ALM-0507 Physical entity temperature exceeded upper prealarm limit
9 ALM-0508 Physical entity temperature exceeded lower prealarm limit
10 ALM-0509 Physical entity humidity exceeded upper prealarm limit
11 ALM-0510 Physical entity humidity exceeded lower prealarm limit
12 ALM-0511 Physical entity voltage exceeded upper prealarm limit
13 ALM-0512 Physical entity voltage exceeded lower prealarm limit
14 ALM-0550 Physical line Down
15 ALM-0601 License default config
16 ALM-0602 License overtime
17 ALM-0603 License will overtime
18 ALM-0604 License invalid
19 ALM-0605 License ESN invalid
20 ALM-0606 License config decrease
21 ALM-0610 Interface-Probe Fault Alarm
22 ALM-0611 IP-Probe Fault Alarm
23 ALM-0618 None of the NTP servers replies
24 ALM-0630 -48V input alarm
25 ALM-0631 External sensor alarm
26 ALM-0632 Insufficient Hard Disk Space
27 ALM-0633 Hard Disk Error
2

Issue 02 (2009-06-30)

Alarm Reference
About This Document
28 ALM-0634 CPU Overload Alarm

29 ALM-0635 DPD detecting failed
30 ALM-0636 Recover Configuration Failure
31 ALM-0637 The master and slave SRU board's configure is different
32 ALM-0638 IKE negotiating tunnel abnormal
33 ALM-0639 Absence of physical entity
34 ALM-0650 The usage of Fragment Resource exceeds alarm threshold
35 ALM-0701 Invalid operator login
36 ALM-0702 Operator password is wrong
37 ALM-0703 Operator Account Change
38 ALM-0704 Operator Access To Log File
39 ALM-0705 Operator Unauthorized Access Attempt
40 ALM-0801 License is about to use up
41 ALM-0802 License has been used up
42 ALM-0803 Signalling path disconnected
43 ALM-0804 Data path disconnected
44 ALM-0805 The usage of local address pool exceeds alarm threshold
45 ALM-0806 No response of the RADIUS authentication server
46 ALM-0807 ARP threshold control of an APN
47 ALM-0808 ARP threshold control of the GGSN
48 ALM-0810 The GGSN and the BMSC are disconnected
49 ALM-0811 MBMS Service Flow Interruption
50 ALM-0812 RADIUS accounting server has no responding
51 ALM-0813 The usage of CDR POOL exceed alarm threshold
Issue 02 (2009-06-30)


Alarm Reference
About This Document
52 ALM-0814 The communications path to CG is down alarm

53 ALM-0815 The version of GTP' is not supported
54 ALM-0816 CG redirection failed
55 ALM-0817 The GGSN and the OCS are disconnected
56 ALM-0818 Disconnection Between the GGSN and FTP Server for CDR Audit
57 ALM-0819 Insufficient Service Node Resources
58 ALM-0820 Redirection Server Unavailable
59 ALM-0821 LNS Group has no responding
60 ALM-0822 IP spoofing has arisen
61 ALM-0826 The redirection server has no responding
62 ALM-0827 Disconnection Between GGSN and PCRF
63 ALM-0828 Disconnection Between GGSN and Reporting Server
64 ALM-0829 Update the rule-library of SIG-CBB Failed
65 ALM-0830 DPI service unavailable
66 ALM-0835 Traffic control alarm
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level of risk, which if not
avoided,will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided,could result in equipment damage, data loss,
performance degradation, or unexpected results.

Issue 02 (2009-06-30)

Alarm Reference
Symbol
About This Document
Description
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
Issue 02 (2009-06-30)


Alarm Reference
About This Document
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder .
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action
Description
Click
Select and release the primary mouse button without moving

the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.

Issue 02 (2009-06-30)

Alarm Reference
ALM-0500 Physical entity is removed
Description
I. Description
This alarm occurs when the board or SPU subcard is manually removed or in poor contact with
the frame.
II. Attribute
Alarm ID
Severity level
Alarm type
0500
Critical
Fault
III. Parameters
Name
Meaning
Board type and slot No. or CPU No.
Specifies the type of the board and the No. of

the slot or the CPU where the alarm occurs.
Impact on System
l
If the active SRU is removed, the active and standby SRUs are switched over when the
standby SRU is available. During switchover, the interworking with the LMT is
diSRUpted. This alarm is not reported in real time; however, it can be displayed in the
alarm history record after the network element (NE) and the LMT can interwork.
The NE is unavailable if the active SRU is removed when the standby SRU is unavailable.
In addition, the alarm is not reported.
If the active SPU is removed, the active and standby SPUs are switched over when the
standby SPU is available. If the standby SPU has all information of the active SPU before
the switchover, the services of online users are not affected by the switchover; however,
users cannot be activated on this pair of SPUs during the interval of the switchover. If the
standby SPU does not have all information of the active SPU before the switchover, some
Issue 02 (2009-06-30)

1-1

Alarm Reference
users are offline due to the switchover. In addition, users cannot be activated on this pair
of SPUs during the interval of the switchover.
l
If the active SPU is removed and standby SPU is not exist, all services of the SPU is
interrupt.
If the LPU is removed, services on the active port of the LPU are switched over to the
standby port of another LPU when the reliable networking exists between the two LPUs.
If the LPU is removed, the communication between the devices connected to the removed
LPU and the NE is diSRUpted when the reliable networking does not exist between the
LPUs.
If the fault alarm occurs when the board is removed, after insert the same type board in the
slot. If you insert a new board to a slot without inserting any board, no alarm will occurs.
If you insert different type board (compare with the removed one), the "board type and slot
id" is not the same, the alarm cannot be cleared, it is need to cleared by the operator.
You can insert or remove the subcard of SPU when the mother board is normal.
Possible Causes
l
The physical entity is manually removed.
The physical entity is in poor contact with the frame.
Handling Procedure
Step 1 Check whether the physical entity is manually removed.
l
Yes ->(3)
No ->(2)
Step 2 Remove the physical entity, and then insert it into the slot. Check whether the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(4)
Step 3 Check the reason why the board is manually removed with the operator ->(5)
Step 4 Contact Huawei Technical Support.
Step 5 End.
----End
Related Information
None.
1-2

Issue 02 (2009-06-30)

Alarm Reference
ALM-0501 Physical entity is unstable
Description
I. Description
This alarm occurs when the board is not well inserted.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0501
Major
Fault
III. Parameters
Name
Meaning
Slot No.
Specifies the No. of the slot where the alarm

occurs.
Impact on System
l
The system service is disrupted.
The board does not work normally.
Possible Causes
The board is not well inserted.
Handling Procedure
Step 1 Remove the board, and then insert it into the slot. Check whether the alarm is cleared.
l
Cleared ->(3)
Not cleared ->(2)
Issue 02 (2009-06-30)

2-1

Alarm Reference

Step 3 End.
----End
Related Information
None.
2-2

Issue 02 (2009-06-30)

Alarm Reference
ALM-0502 Physical entity is restart
Description
This alarm is generated when a board is restart or the memory mode is configured in error.
This alarm is generated when the CPU on the SPU is restart.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0502
Critical
Fault
Parameters
Name
Meaning
Cause
Specifies the cause of board restart.
Board type and slot number or CPU number Specifies the type and slot number or CPU
number of the board generating the alarm.
Impact on System
l
If the active SPU is restart, the active and standby SPUs are switched over if the standby
SPU is available. If the standby SPU has all data on the active SPU before the switchover,
the ongoing services of users are not affected by the switchover; however, users cannot be
activated on this pair of SPUs during the switchover. If the standby SPU does not have all
data on the active SPU before the switchover, some users are offline due to the switchover.
In addition, users cannot be activated on this pair of SPUs during the switchover.
If the active SPU is restart, all users on the active SPU are offline if the standby SPU is
unavailable.
If the LPU is restart, services on the active port of this LPU are switched over to the standby
port of another LPU if the reliable networking is employed between these two LPUs.
If the LPU is restart, the communication between the NE and the devices connected to this
LPU is interrupted if the reliable networking is not employed between the LPUs.
If the CPU on the SPU is restart, the service processing capability is degraded.
Issue 02 (2009-06-30)

3-1

Alarm Reference
Possible Causes
l
A board is restart manually.
The memory mode is configured in error.
Software faults occur on a board.
Hardware faults occur on a board.
Handling Procedure
Step 1 Check whether a board is restart manually.
l
Yes => 2
No => 3
Step 2 Contact the operator to confirm the cause of board restart => End
Step 3 Check whether the memory mode of SPU is configured correctly.
l
Yes => Step 4
No, indicating that the alarm is caused by the fault of memory mode => Step 6
Step 4 Wait for the restart board to register again. Then, check whether the alarm is cleared after user
activation.
l
Cleared => End
Not cleared => Step 5
Step 5 Replace the faulty board. Then, check whether the alarm is cleared after user activation.
l
Cleared, indicating that the alarm is caused by board faults => End
Not cleared => Step 6
Step 6 Contact the technical support engineers of Huawei.

----End
Related Information
None
3-2

Issue 02 (2009-06-30)

Alarm Reference
ALM-0503 Communication channel is faulty
Description
I. Description
This alarm occurs when the communication channel between frames is faulty.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0503
Major
Fault
III. Parameters
Name
Meaning
Board type and slot No.
Specifies the type of the local board and the

No. of the local slot of the communication
channel.
The board can be LPU, SFU, MPU, or SPU.
NOTE
The SRU is composed of the main processing unit
(MPU) and SFU modules. The MPU is SRU board.
Specifies the type of the remote board of the

communication channel.
Board type

Signal number
Specifies the type of the faulty

communication channel.
The fault are communication failure of the
ARQ channel, the synchronous between the
entry interface of high speed network board
and interface board is failed.
Issue 02 (2009-06-30)

4-1

Alarm Reference
Impact on System
l
The system service is disrupted.
The board is reset.
Possible Causes
The communication of the ARQ channel is disrupted.
Handling Procedure
Step 1 Reset the faulty board manually. Then, check whether the alarm is cleared.
l
Cleared ->(4)
Not cleared ->(2)
Step 2 Replace the faulty board. Then, check whether the alarm is cleared.
l
Cleared ->(4)
Not cleared ->(3)

Step 4 End.
----End
Related Information
None.
4-2

Issue 02 (2009-06-30)

Alarm Reference
ALM-0504 Physical entity failed
Description
I. Description
This alarm occurs when the board is faulty.
II. Attribute
Alarm ID
Alarm Severity
Alarm Type
504
Critical
Fault
III. Parameters
Name
Meaning
Specifies the type of the board and the number

of the slot.
NOTE
The SRU is composed of the main processing unit
(MPU) and SFU modules. The MPU is SRU board.
Part
Specifies the faulty board.
Fault type
Specifies the type of the fault.
Impact on System
If Fault type is that the number of the SFU boards is less than 3, the packet forwarding function
of the GGSN9811 is affected. If Fault type is not less than 3, services are interrupted and the
boards may be reset.
If memory board faults that cannot be corrected are detected through the ECC function, the
impacts depend on position, meaning, and related impacts of the incorrect data.
Issue 02 (2009-06-30)

5-1

Alarm Reference
Possible Causes
l
The hardware is faulty.
The board does not work normally.
Memory board faults that cannot be corrected are detected through the ECC function.
Handling Procedure
Step 1 If the alarm is caused by a board, perform the following steps:
(1) Manually reset the faulty board. Then, check whether this alarm is cleared.
l
Cleared -> Step 1.4
Not cleared -> Step 1.2
(2) Replace the faulty board. Then, check whether this alarm is cleared.
l
The board registers successfully and this alarm is cleared -> Step 1.4
The board fails to register and this alarm is not cleared -> Step 1.3
(3) Contact the technical support engineers of Huawei.

(4) End.
Step 2 If memory board faults that cannot be corrected are detected through the ECC function, perform
the following steps:
(1) Replace the faulty board or subcard. Then, check whether this alarm is cleared.
l
The board or subcard registers successfully and this alarm is cleared -> Step 2.3
The board or subcard fails to register and this alarm is not cleared -> Step 2.2
(2) Contact the technical support engineers of Huawei.

(3) End.
----End
Related Information
None.
5-2

Issue 02 (2009-06-30)

Alarm Reference
ALM-0505 Physical Entity changed to stand

by
Description
I. Description
This alarm is generated when the SRUs are switched with a command, the active SRU is faulty,
or the active SRU is reset abnormally. This alarm is cleared when the SRU is in the "Realtime
and routine backup" state.
II. Attribute
Alarm ID
Alarm level
Alarm type
0505
Major
Fault
III. Parameters
Name
Meaning
Board type and Slot No.
Specifies the type and slot number of the

board generating the alarm.
Reason
Specifies the reason why the active SRU exits

from the active state.
Impact on System
None
Possible Causes
The SRUs are switched with a command, the active SRU is faulty, or the active SRU is reset
abnormally.
Issue 02 (2009-06-30)

6-1

Alarm Reference
Handling Procedure
Step 1 Check whether the SRUs are reset with commands.
l
The active SRU is reset or switched with commands -> Step 3
The active SRU is faulty or reset abnormally -> Step 2

Step 3 End.
----End
Related Information
None
6-2

Issue 02 (2009-06-30)

Alarm Reference
ALM-0506 Physical entity changed to the

offline state
Description
I. Description
This alarm occurs when the number of reset times is greater than or equal to three due to
registration failure caused by network board faults. In addition, the network board is powered
off by the main control board.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0506
Major
Event
III. Parameters
Name
Meaning
Reason
Specifies the cause why the network board

exits from the active state.
Board type and Slot No.
Specifies the type of the board and the No. of

the slot.
Impact on System
The network board is faulty, and thus cannot register.
Possible Causes
The board cannot register because of board faults, which results in that the number of reset times
is greater than or equal to three.
Issue 02 (2009-06-30)

7-1

Alarm Reference
Handling Procedure
Step 1 Reset the faulty board manually. Then, check whether the alarm is cleared.
l
Cleared ->(4)
Not cleared ->(2)
l
Cleared ->(4)
Not cleared ->(3)

Step 4 End.
----End
Related Information
None.
7-2

Issue 02 (2009-06-30)

Alarm Reference
8 ALM-0507 Physical entity temperature exceeded upper

prealarm limit
ALM-0507 Physical entity temperature

exceeded upper prealarm limit
Description
I. Description
This alarm occurs when the temperature is higher than the preset upper limit. The temperature
sensor of the board detects the temperature of the key chips on the board.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0507
Critical
Fault
III. Parameters
Name
Meaning
Monitoring address
Specifies the point detected by the

temperature sensor.
Slot No.
Specifies the No. of the slot.
Threshold level
Specifies the level of the threshold. It can be

minor, major, or critical.
Impact on System
l
The hardware is damaged if the part works at a temperature over the upper limit for a long
time.
When two service boards are used, the active and standby switchover may occur if the
working temperature is higher than the upper limit.
When only one service board is used, the service may be disrupted.
Issue 02 (2009-06-30)

8-1
8 ALM-0507 Physical entity temperature exceeded upper

prealarm limit

Alarm Reference
Possible Causes
l
No filler panel is inserted in a vacant slot.
The fan is faulty.
The filtering net of the fan is jammed.
The ambient temperature is over high.
The temperature of the chip is over high.
Handling Procedure
Step 1 Check whether the temperature of the equipment room is within the normal range.
l
No ->Notify the manager of the equipment room to check the temperature controller ->(5)
Yes ->(2)
Step 2 Check whether the fan works normally.

l
Abnormally ->Replace the fan.
Normally ->(3)
Step 3 Run display temperature. The temperature of the processor and the power cannot be read. Then,
replace the faulty board. Check whether the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(4)

Step 5 End.
----End
Related Information
Board temperature: 0C to 80C
Ambient temperature: 5C to 40C for long-term running; 5C to 50C for short-term running
You can query current temperature by display temperature.
8-2

Issue 02 (2009-06-30)

Alarm Reference
9 ALM-0508 Physical entity temperature exceeded lower

prealarm limit
ALM-0508 Physical entity temperature

exceeded lower prealarm limit
Description
I. Description
This alarm occurs when the temperature is lower than the preset lower limit. The temperature
sensor of the board detects the temperature of the key chips on the board.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0508
Critical
Fault
III. Parameters
Name
Meaning
Monitoring address
Specifies the point detected by the

temperature sensor.
Slot No.
Threshold level

Impact on System
l
The hardware is damaged if the part works at a temperature below the lower limit for a
long time.
working temperature is lower than the lower limit.
Issue 02 (2009-06-30)

9-1
9 ALM-0508 Physical entity temperature exceeded lower

prealarm limit

Alarm Reference
Possible Causes
l
The indoor temperature is low.
There is cooling equipment near the GGSN9811.
Handling Procedure
Step 1 Check whether the temperature of the equipment room is within the normal range.
l
No ->Notify the manager of the equipment room to check the temperature controller ->(5)
Yes ->(2)
Step 2 Check whether the fan works normally.

l
Abnormally ->Replace the fan.
Normally ->(3)
Step 3 Run display temperature. The temperature of the processor and the power cannot be read. Then,
replace the faulty board. Check whether the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(4)

Step 5 End.
----End
Related Information
Board temperature: 0C to 80C
Ambient temperature: 5C to 40C for long-term running; 5C to 50C for short-term running
You can query current temperature by display temperature.
9-2

Issue 02 (2009-06-30)

Alarm Reference
10
10 ALM-0509 Physical entity humidity exceeded upper

prealarm limit
ALM-0509 Physical entity humidity

Description
I. Description
This alarm occurs when the humidity is higher than the preset upper limit. The humidity sensor
of the board detects the humidity of the key chips on the board.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0509
Critical
Fault
III. Parameters
Name
Meaning
Monitoring address
Specifies the point detected by the humidity

sensor.
Slot No.
Threshold level

Impact on System
l
When the device works for less than 48 hours, the device is not affected if the humidity is
beyond the long-term range but within the short-term range.
The faults such as system reset and packet loss may occur and the services are affected
when the humidity is beyond the long-term range for more than 48 hours or lower than the
short-term range.
Issue 02 (2009-06-30)

10-1
10 ALM-0509 Physical entity humidity exceeded upper

prealarm limit

Alarm Reference
Possible Causes
l
The ambient humidity is higher than the preset upper limit.
The humidity sensor of the board is faulty.
Handling Procedure
Step 1 Check whether the humidity of the equipment room is within the normal range.
l
No ->(2)
Yes ->(3)
Step 2 Notify the manager of the equipment room to check the humidity controller. Then, check whether
the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(3)
Step 3 Check on the LMT whether the alarm thresholds of ambient humidity are set correctly. The
upper limit of the ambient humidity ranges from 65 to 85. The lower limit of the ambient humidity
ranges from 5 to 30. Modify the thresholds that are set incorrectly, and then check whether the
alarm is cleared.
l
Cleared ->(5)
Not cleared ->(4)
l
Cleared ->(6)
Not cleared ->(5)

Step 6 End.
----End
Related Information
None
10-2

Issue 02 (2009-06-30)

Alarm Reference
11
11 ALM-0510 Physical entity humidity exceeded lower

prealarm limit
ALM-0510 Physical entity humidity

Description
I. Description
This alarm occurs when the humidity is lower than the preset lower limit. The humidity sensor
of the board detects the humidity of the key chips on the board.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0510
Critical
Fault
III. Parameters
Name
Meaning
Monitoring address
Specifies the point detected by the humidity

sensor.
Slot No.
Threshold level

Impact on System
l
When the device works for less than 48 hours, the device is not affected if the humidity is
beyond the long-term range but within the short-term range.
The faults such as system reset and packet loss may occur and the services are affected
when the humidity is beyond the long-term range for more than 48 hours or lower than the
short-term range.
Issue 02 (2009-06-30)

11-1
11 ALM-0510 Physical entity humidity exceeded lower

prealarm limit

Alarm Reference
Possible Causes
l
The ambient humidity is lower than the preset lower limit.
The humidity sensor of the board is faulty.
Handling Procedure
Step 1 Check whether the humidity of the equipment room is within the normal range.
l
No ->(2)
Yes ->(3)
Step 2 Notify the manager of the equipment room to check the humidity controller. Then, check whether
l
Cleared ->(5)
Not cleared ->(3)
Step 3 Check on the LMT whether the alarm threshold of ambient humidity is set correctly. The upper
limit of the ambient humidity ranges from 65 to 85. The lower limit of the ambient humidity
ranges from 5 to 30. Modify the thresholds that are set incorrectly, and then check whether the
alarm is cleared.
l
Cleared ->(5)
Not cleared ->(4)
l
Cleared ->(6)
Not cleared ->(5)

Step 6 End.
----End
Related Information
None
11-2

Issue 02 (2009-06-30)

Alarm Reference
12
12 ALM-0511 Physical entity voltage exceeded upper

prealarm limit
ALM-0511 Physical entity voltage

Description
I. Description
This alarm occurs when the voltage is higher than the preset upper limit. The voltage sensor of
the board detects the voltage of the key chips on the board.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0511
Critical
Fault
III. Parameters
Name
Meaning
Monitoring address
Specifies the point detected by the voltage

sensor.
Slot No.
Threshold level

Impact on System
l
The hardware is damaged if the board works at a voltage over the upper limit for a long
time.
voltage is higher than the upper limit.
Issue 02 (2009-06-30)

12-1
12 ALM-0511 Physical entity voltage exceeded upper

prealarm limit

Alarm Reference
Possible Causes
l
The ambient voltage is higher than the upper limit.
The voltage of the faulty board is higher than the upper limit.
Handling Procedure
Step 1 Reset the board where the alarm occurs. Check whether the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(2)
Step 2 Replace the board. Then, check whether the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(3)
Step 3 Replace the faulty power module. Then, check whether the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(4)

Step 5 End.
----End
Related Information
None
12-2

Issue 02 (2009-06-30)

Alarm Reference
13
13 ALM-0512 Physical entity voltage exceeded lower

prealarm limit
ALM-0512 Physical entity voltage

Description
I. Description
This alarm occurs when the voltage is lower than the preset lower limit. The voltage sensor of
the board detects the voltage of the key chips on the board.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0512
Critical
Fault
III. Parameters
Name
Meaning
Monitoring address
Specifies the point detected by the voltage

sensor.
Slot No.
Threshold level

Impact on System
l
The hardware is damaged if the part works at a voltage below the lower limit for a long
time.
voltage is lower than the lower limit.
Issue 02 (2009-06-30)

13-1
13 ALM-0512 Physical entity voltage exceeded lower

prealarm limit

Alarm Reference
Possible Causes
l
The ambient voltage is lower than the lower limit.
The voltage of the faulty board is lower than the lower limit.
Handling Procedure
Step 1 Reset the board where the alarm occurs. Check whether the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(2)
Step 2 Replace the board. Then, check whether the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(3)
Step 3 Replace the faulty power module. Then, check whether the alarm is cleared.
l
Cleared ->(5)
Not cleared ->(4)

Step 5 End.
----End
Related Information
None
13-2

Issue 02 (2009-06-30)

Alarm Reference
14
ALM-0550 Physical line Down
Description
This alarm occurs when the physical link connected to an interface on the LPU is broken.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0550
Critical
Fault
Parameters
Name
Meaning
Interface
Specifies the interface where the alarm occurs.
Impact on System
l
The services at the physical interface where the alarm occurs are interrupted.
Possible Causes
l
The cable or optical fiber connected to the interface where the alarm occurs is loose.
The cable or optical fiber is damaged.
The connected interface on the peer device is shut down.
Hardware faults occur on the LPU generating the alarm.
Handling Procedure
Step 1 Check whether alarms such as the board fault alarm is reported to the LMT.
l
Yes -> Clear the generated alarms by referring to the help specific to the alarms.
No -> Step 2
Check whether the interface is connected properly.

Issue 02 (2009-06-30)

14-1

Alarm Reference
Step 2 Check whether the cable or optical fiber connected to the interface where the alarm occurs is
connected properly (For example, check whether the cable or optical fiber is damaged and
whether the conversion module is loose).
l
Yes -> Step 4
No -> Step 3
Step 3 Reconnect the cable or optical fiber. Activate a user, and then check whether the alarm is cleared.
l
Cleared, indicating that the alarm is caused by the loose connection of the cable or optical
fiber -> End
Not cleared -> Step 4
Check whether the physical line is broken.

Step 4 Test the cable or optical fiber by using a test tool to check whether the line is normal.
l
Yes -> Step 6
No -> Step 5
Step 5 Replace the faulty cable or optical fiber. Activate a user, and then check whether the alarm is
cleared.
l
Cleared, indicating that the alarm is caused by the line break -> End
Check whether the operating mode and speed of the interface on the GGSN9811 are the
same as the operating mode and speed of the connected interface on the peer device.
Step 6 Run display interface [interface name] to check the status of the interface on the GGSN9811,
for example, check whether the interface is shut down, whether the duplex mode is correct, and
whether the operating mode and speed of the interface are the same as the operating mode and
speed of the connected interface on the peer device.
l
Yes -> Step 8
No -> Step 7
Step 7 Run duplex to set the operating mode of the interface. Run speed to set the speed of the interface.
If current state of the interface is Administratively down, run undo shutdown to enable the
interface. Then, check whether this alarm is cleared.
l
Cleared, indicating that the alarm is caused by the incorrect settings of the operating mode
and speed of the interface -> End
Contact the technical support engineers of related devices.

----End
Related Information
None
14-2

Issue 02 (2009-06-30)

Alarm Reference
15
ALM-0601 License default config
Description
I. Description
The alarm occurs when the available license file is not activated.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0601
Minor
Fault
III. Parameters
None
Impact on System
None
Possible Causes
The available license file is not activated.
Handling Procedure
Step 1 Apply for a valid license file.
Step 2 Download the valid license file to the GGSN.
Step 3 Activate the valid license file, and then check whether the alarm is cleared.
l
Cleared -> (5)
Not cleared -> (4)

Issue 02 (2009-06-30)

15-1

Alarm Reference
Step 5 End.
----End
Related Information
None.
15-2

Issue 02 (2009-06-30)

Alarm Reference
16
ALM-0602 License overtime
Description
I. Description
The alarm occurs when the license expires.
After the license file expires, the users are notified of the remaining trial days of the license file
by the alarm location message.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0602
Minor
Fault
III. Parameters
Name
Meaning
The days after that the evaluation period of

license will expire
Specifies the remaining trial days of the

license file.
Impact on System
When the alarm occurs, the GGSN can be used 30 days. After 30 days, the GGSN can only
support 10 users.
Possible Causes
The license file expires.
Handling Procedure
Step 1 Apply for a new license file.
Issue 02 (2009-06-30)

16-1

Alarm Reference
Step 2 Download the new license file to the GGSN.

Step 3 Activate the new license file, and then check whether the alarm is cleared.
l
Cleared -> (5)
Not cleared -> (4)

Step 5 End.
----End
Related Information
None
16-2

Issue 02 (2009-06-30)

Alarm Reference
17
ALM-0603 License will overtime
Description
I. Description
The alarm occurs when the license file is about to expire. The alarm is triggered one month
earlier than "AlM-0602 License overtime". This alarm rises once every day regularly after it is
first triggered until "AlM-0602 License overtime" is triggered.
Users are notified of the remaining days of the license file by the alarm location message.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0603
Minor
Event
III. Parameters
Name
Meaning
The days after that the valid period of license

will expire
Specifies the remaining days after which the

license file expires.
Impact on System
None
Possible Causes
The license file is about to expire.
Handling Procedure
Step 1 Apply for a new license file to be used when the current license file expires. Then, check whether
Issue 02 (2009-06-30)

17-1

Alarm Reference

l
Cleared -> (3)
Not cleared -> (2)

Step 3 End.
----End
Related Information
None
17-2

Issue 02 (2009-06-30)

Alarm Reference
18
ALM-0604 License invalid
Description
I. Description
The alarm occurs when the license file is illegally activated.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0604
Minor
Fault
III. Parameters
Name
Meaning
The days after that the evaluation period of

license will expire
Specifies the days after which the evaluation

period of the license file expires.
Impact on System
None
Possible Causes
The license file is illegally activated.
Handling Procedure
Step 1 Apply for a valid license file.
Step 2 Download the valid license file to the GGSN.
Step 3 Activate the valid license file, and then check whether the alarm is cleared.
Issue 02 (2009-06-30)

18-1

Alarm Reference

l
Cleared -> (5)
Not cleared -> (4)

Step 5 End.
----End
Related Information
None
18-2

Issue 02 (2009-06-30)

Alarm Reference
19
ALM-0605 License ESN invalid
Description
I. Description
The alarm occurs when the ESN of the license file is invalid.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0605
Minor
Fault
III. Parameters
None
Impact on System
None
Possible Causes
The ESN of the license file is invalid.
Handling Procedure
Step 1 Apply for a license file whose ESN is consistent with that of the GGSN.
Step 2 Download the new license file to the GGSN.
Step 3 Activate the new license file, and then check whether the alarm is cleared.
l
Cleared -> (5)
Not cleared -> (4)

Issue 02 (2009-06-30)

19-1

Alarm Reference
Step 5 End.
----End
Related Information
None
19-2

Issue 02 (2009-06-30)

Alarm Reference
20
ALM-0606 License config decrease
Description
I. Description
The alarm occurs when the configuration of the license file degrades.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0606
Minor
Event
III. Parameters
Name
Meaning
Newcfg
Specifies the new configurations.
Oldcfg
Specifies the original configurations.
Limit Item name
Specifies the configuration item.
Impact on System
None
Possible Causes
The configuration of the license file may degrade.
Handling Procedure
Step 1 Check whether the configuration degradation of the configuration items in the license file is
valid.
Issue 02 (2009-06-30)

20-1

l
Valid -> (3)
Invalid -> (2)

Alarm Reference

Step 3 End.
----End
Related Information
None
20-2

Issue 02 (2009-06-30)

Alarm Reference
21
ALM-0610 Interface-Probe Fault Alarm
Description
I. Description
If the Eth-trunk interfaces work in active/standby mode, the active Eth-trunk interface sends
ARP packets to probe the peer device. The alarm occurs if the number of probe failure times
reaches the configured threshold of link failure. In such a case, the active link is considered
faulty, and the active and standby Eth-trunk interfaces are switched.
After the active and standby Eth-trunk interfaces are switched, the fault alarm about the original
active Eth-trunk interface persists if the new active link works normally. This is because the
original Eth-trunk interface used for sending ARP packets becomes the standby Eth-trunk
interface. The original active Eth-trunk interface reverts to the active state only if the new active
link is faulty and the Eth-trunk interfaces are switched again. The alarm is cleared when the peer
device is probed with ARP packets.
After this alarm occurs, manually clear this alarm after the fault of the original active link is
rectified and it reverts to the normal state.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0610
Major
Fault
III. Parameters
Issue 02 (2009-06-30)
Name
Meaning
Name of physical interface
Specifies the name of the physical interface

through which the GGSN fails to probe the
peer end.
Peer IP address
Specifies the IP address of the peer end that

the GGSN probes.

21-1

Alarm Reference
Impact on System
When the alarm occurs, the link connection between faulty interface of the GGSN and the peer
end breaks down. If the communication can be realized through another interface, the GGSN
can maintain communication with the peer end. Otherwise, the communication fails.
Possible Causes
l
The interface of the GGSN is faulty.
The network cables of the GGSN that connect the LAN Switch are faulty.
The port of the LAN Switch that connects with the GGSN is faulty.
The LAN Switch is faulty.
The port of the LAN Switch that connects with the peer device is faulty.
The network cables of the peer device that connect with the LAN Switch are faulty.
The peer device is faulty.
Handling Procedure
Step 1 Probe a normal peer device through a port of the GGSN. Check whether the communication is
normal. If yes, it indicates that the GGSN is normal. Probe another peer device. If the peer device
is abnormal, clear the fault. If the peer device is normal, proceed with the following step.
Step 2 Check whether the network cables are normal. If not, replace the faulty network cables. If the
network cables are normal, proceed with the following step.
Step 3 Check whether the related ports of the LAN Switch and the LAN Switch are normal. If not,
replace the faulty ports or the LAN Switch. If yes, proceed with the following step.
Step 4 Check whether the ports of the GGSN are normal. If not, replace the faulty ports or the
corresponding LPU. If yes, proceed with the following step.
Step 6 End.
----End
Related Information
None
21-2

Issue 02 (2009-06-30)

Alarm Reference
22
ALM-0611 IP-Probe Fault Alarm
Description
I. Description
If the number of failure times reaches the configured threshold of link failure when the GGSN
probes the peer end with ARP through an eth-trunk interface, the corresponding link is
considered to be faulty. Then, the alarm occurs. The alarm is cleared when the active and standby
eth-trunk interfaces are switched over and the communication is restored.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0611
Major
Fault
III. Parameters
Name
Meaning
Local end IP address
Specifies the IP address of the GGSN that

probes the peer end.
Peer IP address
Specifies the IP address of the peer end that

the GGSN probes.
Impact on System
When the alarm occurs, the communication between the GGSN and the IP address of the peer
end fails.
Possible Causes
l
The interface of the GGSN is faulty.
The network cables of the GGSN that connect the LAN Switch are faulty.
Issue 02 (2009-06-30)

22-1

Alarm Reference

l
The port of the LAN Switch that connects with the GGSN is faulty.
The LAN Switch is faulty.
The port of the LAN Switch that connects with the peer device is faulty.
The network cables of the peer device that connect with the LAN Switch are faulty.
The peer device is faulty.
Handling Procedure
Step 1 Probe a normal peer device through a port of the GGSN. Check whether the communication is
normal. If yes, it indicates that the GGSN is normal. Probe another peer device. If the peer device
is abnormal, clear the fault. If the peer device is normal, proceed with the following step.
Step 2 Check whether the network cables are normal. If not, replace the faulty network cables. If the
network cables are normal, proceed with the following step.
Step 3 Check whether the related ports of the LAN Switch and the LAN Switch are normal. If not,
replace the ports or the LAN Switch. If yes, proceed with the following step.
Step 4 Check whether the ports of the GGSN are normal. If not, replace the faulty ports or the
corresponding LPU. If yes, proceed with the following step.
Step 6 End.
----End
Related Information
None
22-2

Issue 02 (2009-06-30)

Alarm Reference
23
ALM-0618 None of the NTP servers

replies
Description
I. Description
When the GGSN connects with all the configured NTP servers and requests network time
synchronization, it cannot receive any response from the NTP servers. Then, the alarm occurs.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0618
Minor
Fault
III. Parameters
None
Impact on System
When no NTP server responds, the system time of the GGSN cannot synchronize with the
network time of the NTP servers. Thus, the time precision of the GGSN cannot be guaranteed.
Possible Causes
l
The network fails.
The NTP server fails.
No NTP server is configured.
Handling Procedure
Step 1 Run display ntp-service sessions to check whether any NTP server is configured.
l
No -> (2)
Yes -> (3)
Issue 02 (2009-06-30)

23-1

Alarm Reference
Step 2 Run ntp-service unicast-server to configured an NTP server. Then, check whether the alarm
is cleared.
l
Cleared -> (10)
Not cleared -> (3)
Step 3 Run display ntp-service status to check the clock status of the NTP server.
l
Synchronized -> (8)
Unsynchronized -> (4)
Step 4 Ping the IP address of the configured NTP server on the GGSN.
Step 5 Check whether the configured NTP server is consistent with that actually used.
l
Consistent -> (5)
Inconsistent -> (7)
Step 6 Check whether another configurable NTP server is available for network time synchronization
of the GGSN.
l
Yes -> (2)
No -> (8)
Step 7 Run ntp-service unicast-server to modify the configurations of the NTP server. Then, check
whether the alarm is cleared.
l
Cleared -> (10)
Not cleared -> (9)
Step 8 Check whether the alarm is cleared.

l
Cleared -> (10)
Not cleared -> (9)

Step 10 End.
----End
Related Information
None
23-2

Issue 02 (2009-06-30)

Alarm Reference
24
ALM-0630 -48V input alarm
Description
I. Description
The input voltage of the rack is -48 V of two channels. The alarm occurs when the voltage of
one channel exceeds the preset upper limit or is lower than the preset lower limit. If the voltages
of two channels both exceed the range of the preset upper and lower limits, two alarms are
generated.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0630
Critical
Fault
III. Parameters
Name
Meaning
Slot No.
Specifies the number of the slot where the

faulty board is located.
Impact on System
l
The system adopts a two-channel power module. The subrack can continue working even
if one channel is faulty. In this case, the reliability of the system is affected but the services
are not.
If two alarms are generated at the same time for both channels, the GGSN may be restarted
and the services may thus be interrupted.
Possible Causes
l
Issue 02 (2009-06-30)
The -48V feeder cables of the path to the power distribution box are loose.
24-1

Alarm Reference

l
The voltage of the -48 V power circuit on the power distribution box is lower than the preset
lower limit.
The voltage of the -48 V power circuit on the power distribution box is higher than the
preset upper limit.
The monitoring board of the power distribution box is faulty.
Handling Procedure
Step 1 Check whether the connection of the -48 V feeder cables of the path to the power distribution
box is normal.
l
Normal -> (2)
Abnormal -> (4)
Step 2 Check whether the voltage of the power circuit on the power distribution box exceeds the range
of the preset lower and upper limits by using a voltmeter.
l
Yes -> (5)
No -> (3)
Step 3 Replace the monitoring board of the power distribution box. Then, check whether the alarm is
cleared.
l
Cleared -> (8)
Not cleared -> (7)
Step 4 Connect the -48 V feeder cables properly, and then check whether the alarm is cleared.
l
Cleared -> (8)
Not cleared -> (7)
Step 5 Contact the management personnel of the equipment room to clear the fault of the power supply
network. Then, check whether the alarm is cleared.
l
Cleared -> (8)
Not cleared -> (6)
Step 6 Query whether the threshold of the maximum input voltage is between 55 V and 59 V, and
whether the threshold of the minimum input voltage is between 41 V and 45 V. If not, adjust
the thresholds.
l
Cleared -> (8)
Not cleared -> (7)

Step 8 End.
----End
Related Information
None
24-2

Issue 02 (2009-06-30)

Alarm Reference
25
ALM-0631 External sensor alarm
Description
I. Description
The alarm occurs when any switch is off.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0631
Critical
Fault
III. Parameters
Name
Meaning
Slot No.

power distribution box is located.
Impact on System
Some devices cannot be powered on or the power supply status is abnormal. This may damage
the devices and affect the services.
Possible Causes
l
The switch status is abnormal.
The Boolean value output sensor of the power distribution box is faulty.
Handling Procedure
Step 1 According to the operation documents, check whether the switches of the power distribution
box are correctly set.
l
Issue 02 (2009-06-30)
Incorrect -> (2)

25-1

Alarm Reference

l
Correct -> (3)
Step 2 Set the switches correctly, and then check whether the alarm is cleared.
l
Cleared -> (5)
Not cleared -> (3)
Step 3 Replace the monitoring board of the power distribution box. Then, check whether the alarm is
cleared.
l
Cleared -> (5)
Not cleared -> (4)

Step 5 End.
----End
Related Information
None
25-2

Issue 02 (2009-06-30)

Alarm Reference
26
ALM-0632 Insufficient Hard Disk Space
Description
I. Description
This alarm is generated when the hard disk utilization reaches the threshold set with running the
alarm threshold hardware-alarm command in the operation and maintenance view.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0632
Major
Fault
III. Parameters
Name
Meaning
Slot No.

board generating the alarm is located.
Disk type
Specifies the hard disk type that can be the

OM hard disk or the CDR hard disk. This
parameter is of the enumeration type.
Alarm threshold
Specifies the alarm threshold.
Alarm recover threshold
Specifies the alarm stop threshold.
Impact on System
l
Issue 02 (2009-06-30)
Impact on the CDR hard disk:

1.
The available hard disk space is insufficient.
2.
The CDRs may not be normally stored, operation logs may be lost, or performance
statistics files may be lost.
26-1

Alarm Reference
Impact on the OM hard disk:
1.
The log files including performance result files may not be created.
2.
Software upgrade fails.
Possible Causes
For the CDR hard disk:
1.
The GGSN and the CG are disconnected, which causes that numerous CDR files are
stored on the hard disk.
2.
Excessive normal files are stored.
For the OM hard disk:
Excessive log files are stored.
Handling Procedure
Step 1 Run display cg to check whether the CG works normally.
l
Abnormal ->(6)
Normal ->(2)
Step 2 Run the ping command to check whether the connection between the GGSN and the CG is
normal.
l
Abnormal ->(3)
Normal ->(4)
Step 3 Check whether the physical link between the GGSN and the CG, firewall policy, and routing
configurations are normal.
l
Abnormal ->(2)
Normal ->(4)
Step 4 Contact technical support engineers of the CG.

Step 5 Clear faults related to the physical link between the GGSN and the CG, firewall policy, and
routing configurations, and then check whether the alarm is cleared.
l
Cleared ->(7)
Not cleared ->(6)

Step 7 End.
----End
Related Information
None
26-2

Issue 02 (2009-06-30)

Alarm Reference
27
ALM-0633 Hard Disk Error
Description
I. Description
This alarm is generated when the system detects hard disk errors.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0633
Critical
Fault
III. Parameters
Name
Meaning
Slot No.

Disk type
Specifies the hard disk type that can be the

OM hard disk or the CDR hard disk. This
parameter is of the enumeration type.
Impact on System
l
Data such as performance statistics and system logs may be lost when this alarm occurs.
After the system detects hard disk errors, if two SRUs are available and they work in active/
standby mode, active/standby switchover of SRUs is triggered when this alarm occurs on
the active SRU.
Possible Causes
The lifetime of the hard disk expires.
Issue 02 (2009-06-30)

27-1

Alarm Reference
Handling Procedure
Step 1 Replace the faulty SRU with a new SRU.
l
Cleared ->(3)
Not cleared ->(2)

Step 3 End.
----End
Related Information
None
27-2

Issue 02 (2009-06-30)

Alarm Reference
28
ALM-0634 CPU Overload Alarm
Description
I. Description
This alarm is generated when the CPU utilization is greater than the threshold for five consecutive
minutes.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0634
Major
Fault
III. Parameters
Name
Meaning
Slot No.

CPU No.
Specifies the number of the CPU of the board

generating the alarm.
Alarm threshold
Specifies the alarm stop threshold.
Impact on System
l
The device runs abnormally.
The service modules run abnormally. For example, user accesses are restricted.
When the CPU utilization of the SPU is equal to or greater than 80%, the system rejects
any new user access.
Issue 02 (2009-06-30)

28-1

Alarm Reference
When the CPU utilization of the SRU is equal to or greater than 80%, the link between the
GGSN and the maintenance console may be torn down.
Possible Causes
l
The GGSN is overloaded with excessive users.
The M2000 downloads data from the GGSN hard disk through the FTP server.
Handling Procedure
Step 1 Stop the FTP service to the M2000, and then check whether the alarm is cleared.
l
Cleared ->(4)
Not cleared ->(2)
Step 2 Set the CPU overload threshold to a higher value by running the alarm threshold cpu-alarm
command in the operation and maintenance view , and then check whether the alarm is cleared.
l
Cleared ->(4)
Not cleared ->(3)

Step 4 End.
----End
Related Information
None
28-2

Issue 02 (2009-06-30)

Alarm Reference
29
ALM-0635 DPD detecting failed
Description
I. Description
When the IPSec tunnel is used and the SA is generated through IKE negotiation, you can check
whether the peer device works normally through the IKE DPD function. After the number of
times that the peer device is not detected through IKE DPD reaches the alarm threshold, the peer
end of the IPSec tunnel is considered faulty. The DPD failure alarm is then generated. The alarm
is cleared after the faulty peer device recovers and IKE negotiation packets are received from
the peer device.
II. Attribute
Alarm ID
Alarm level
Alarm type
0635
Major
Fault
III. Parameters
Name
Meaning
IKE peer name
IKE peer name for identifying devices at the

peer end of the IPSec tunnel that are detected
as faulty devices through IKE DPD
Impact on System
When this alarm is generated, the communication link failure of the IPSec tunnel occurs between
the GGSN9811 and the devices at the peer end of the IPSec tunnel. If the peer end of the IPSec
tunnel is configured with only one device, data transmission through this tunnel is interrupted.
If the peer end of the IPSec tunnel is configured with more than one devices, data is automatically
switched over to another device.
Issue 02 (2009-06-30)

29-1

Alarm Reference
Possible Causes
l
Abnormal peer devices
Abnormal network links
Handling Procedure
Step 1 Check whether the network cables are normal.
l
Yes -> (3)
No -> (2)
Step 2 Replace the faulty network cables. Then, check whether the alarm is cleared.
l
Cleared -> (8)
Not cleared -> (3)
Step 3 Test whether relevant ports on the LAN Switch and the LAN Switch work normally.
l
Yes -> (5)
No -> (4)
Step 4 Replace the faulty port on the LAN Switch or replace the LAN Switch. Then, check whether
l
Cleared -> (8)
Not cleared -> (5)
Step 5 Check whether the peer device is normal.

l
Yes -> (7)
No -> (6)
Step 6 Clear faults of the peer device. Then, check whether the alarm is cleared.
l
Cleared -> (8)
Not cleared -> (7)
Step 7 Contact Huawei technical support.

Step 8 End
----End
Related Information
None.
29-2

Issue 02 (2009-06-30)

Alarm Reference
30
ALM-0636 Recover Configuration

Failure
Description
Description
The alarm occurs when configuration commands fail to be executed during the configuration
restoration process. The system fails to automatically re-run such commands that fail to be
executed. In such a case, you need to run them on the LMT and then clear the alarm.
Attribute
Alarm ID
Severity level
Alarm type
636
Major
Fault
Impact on System
Configurations fail to be restored, and services are interrupted.
Possible Causes
l
Configuration commands are entered incorrectly.
The SPU/LPU is faulty.
The system fails to issue configuration commands after the LPU is restarted or after the
SPU is restarted or switched.
Handling Procedure
Step 1 Check the log file, cfmresult.txt, that stores configurations.
Download the cfmresult.txt file in the /soft/temp directory, and then check whether some
configuration commands fail to be executed.
l
Yes => (2)
No=> (6)
Issue 02 (2009-06-30)

30-1

Alarm Reference
Step 2 Check the correctness of entered configuration commands.

l
Yes =>(3)
No =>(4)
Step 3 Check whether you can successfully run the configuration commands that fail to be executed.
l
Yes => (5)
No=> (6)
Step 4 Enter the configuration commands correctly, and then check whether they can be executed
successfully.
l
Yes => (5)
No=> (6)
Step 5 On the LMT, right-click an alarm and select Manually Recover Alarm. Then, check whether the
alarm is cleared.
l
Yes => (7)
No => (6)
NOTE
The alarm can not be cleared automatically and only can be cleared manually. If the alarm is not cleared
manually, it keeps existing and new alarm is not reported.

Step 7 End.
----End
Related Information
None
30-2

Issue 02 (2009-06-30)

Alarm Reference
31
31 ALM-0637 The master and slave SRU board's configure

is different
ALM-0637 The master and slave SRU

board's configure is different
Description
Description
The alarm occurs when the configurations on the active and standby SRUs are checked to be
inconsistent.
Attribute
Alarm ID
Severity level
Alarm type
0637
Major
Fault
Impact on System
When the active and standby SRUs are switched, the restored configurations are inconsistent,
thus resulting in configuration loss. The severity level of configuration loss depends on the
importance of lost configurations.
Possible Causes
During the batch backup process, abnormalities occur, which results in inconsistency of
configurations on the active and standby SRUs.
Handling Procedure
Step 1 On the LMT, run the command that is used to check the consistency of configurations on the
active and standby SRUs.
Run check master-slave-sru current-configuration to check whether the configurations on
the active and standby SRUs are consistent.
l
Yes, indicating that the alarm is cleared => End
No =>Step 2
Issue 02 (2009-06-30)

31-1
31 ALM-0637 The master and slave SRU board's configure

is different

Alarm Reference
Step 2 Run reset slot to restart the standby SRU.

Step 3 After standby SRU is running, run check master-slave-sru current-configuration to check
whether the configurations on the active and standby SRUs are consistent.
l
Yes, indicating that the alarm is cleared => End
No =>Step 4
Step 4 Contact Huawei technical support.

----End
Related Information
None
31-2

Issue 02 (2009-06-30)

Alarm Reference
32
ALM-0638 IKE negotiating tunnel

abnormal
Description
I. Description
This alarm is generated when the GGSN considers the negotiated tunnel abnormal. The
negotiated tunnel is abnormal if the IKE negotiation fails, if the renegotiation fails after SA
expiration, or if the detection of the IPSec tunnel through the KeepAlive packet fails. This alarm
is cleared after the fault in the tunnel is rectified, the GGSN receives the IKE negotiation packet
from the peer of the IPSec tunnel, and the IKE negotiation succeeds.
II. Attribute
Alarm ID
Severity Level
Alarm Type
638
Major
Fault
III. Parameters
Name
Meaning
IKE peer name
IKE peer name for identifying the device at

the peer end of the abnormal IPSec tunnel
Impact on System
If the alarm is generated, the communication link is broken between the GGSN and the peer of
the IPSec tunnel corresponding to the IKE peer generating the alarm. If only one peer is
configured for the IPSec tunnel, data transmission over the tunnel is interrupted. If multiple peers
are configured, the GGSN uses another peer for data transmission.
Issue 02 (2009-06-30)

32-1

Alarm Reference
Possible Causes
l
The peer device is abnormal.
The network link is abnormal.
Handling Procedure
Step 1 Check whether network cables are normal.
l
Yes -> Step 3
No -> Step 2
Step 2 Replace the network cables and then check whether the alarm is cleared.
l
Yes -> Step 8
No -> Step 3
Step 3 Check whether the interface connecting the LAN Switch to the GGSN is normal and whether
the LAN Switch is normal.
l
Yes -> Step 5
No -> Step 4
Step 4 Use another interface to connect the LAN Switch to the GGSN or replace the LAN Switch. Then,
check whether the alarm is cleared.
l
Yes -> Step 8
No -> Step 5
Step 5 Check whether the peer device is normal.

l
Yes -> Step 7
No -> Step 6
Step 6 Rectify the faults on the peer device and then check whether the alarm is cleared.
l
Yes -> Step 8
No -> Step 7
Step 7 Contact Huawei technical support engineers.

Step 8 End
----End
Related Information
None
32-2

Issue 02 (2009-06-30)

Alarm Reference
33
ALM-0639 Absence of physical entity
Description
I. Description
This alarm occurs when the subcard is configured in the configuration file, but not installed.
II. Attribute
Alarm ID
Alarm Severity
Alarm Type
639
Minor
Fault
III. Parameters
Name
Meaning
Specifies the type of the board and the number

of the slot.
Impact on System
Deep packet inspection (DPI) feature can not be realized. Layer 7 service, such as service
resolution and control and service report, can not be handled.
Possible Causes
The subcard is not installed.
Handling Procedure
Step 1 Manually insert the subbcard. Then, run display device and specify the slot number to check
whether the subcard registers successfully. Then, check whether this alarm is cleared.
l
Issue 02 (2009-06-30)
The subcard registers successfully and this alarm is cleared -> Step 3
33-1

Alarm Reference
The subcard registers successfully but this alarm is not cleared -> Step 2
The subcard fails to register and this alarm is not cleared -> Step 2
Step 2 Contact the technical support engineers of Huawei.

Step 3 End.
----End
Related Information
None.
33-2

Issue 02 (2009-06-30)

Alarm Reference
34
34 ALM-0650 The usage of Fragment Resource exceeds

alarm threshold
ALM-0650 The usage of Fragment

Resource exceeds alarm threshold
Description
I. Description
The alarm occurs when the usage of fragment resource exceeds alarm threshold.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
650
Major
Fault
III. Parameters
Name
Meaning
Slot.No
The Number of the Slot.
Infomaition
The infomation of the Alarm.
Impact on System
With the alarm ALM-0650,the GTP fragment may be blocked, and the user fragment may not
be charge.
Possible Causes
There are too many fragments.
Handling Procedure
Step 1 Operate the software parameter No.60, No.61.
Issue 02 (2009-06-30)

34-1
34 ALM-0650 The usage of Fragment Resource exceeds

alarm threshold

Alarm Reference
Step 2 Waiting for ten minutes, check whether the alarm restore.
l
yes => (3)
no => End.
NOTE
The alarm can not be restored in ten minute.

----End
Related Information
Software parameter operation reference: Software Parameter Operation Guide.chm
34-2

Issue 02 (2009-06-30)

Alarm Reference
35
ALM-0701 Invalid operator login
Description
I. Description
The alarm occurs when the invalid operator login on to the NE and the alarm security-alarm
command is enable.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
701
Minor
Fault
III. Parameters
Name
Meaning
Operator
Specifies name of the unauthorized operator
IP address
Specifies the IP address of the unauthorized

operator
Impact on System
None
Possible Causes
There is not the operator on the NE.
Handling Procedure
Step 1 Check whether the name of the operator is wrong.
l
Issue 02 (2009-06-30)
Yes => Enter the right name of operator => (3)

35-1

Alarm Reference
No => (2)
Step 2 Contact the manager, confirm whether need to add this operator.
Step 3 Clear the alarm manually and check whether the alarm occurs again.
l
Yes => (4)
No => End
NOTE
Step 4 Contact the HUAWEI Technical Support

----End
Related Information
alarm security-alarm
35-2

Issue 02 (2009-06-30)

Alarm Reference
36
ALM-0702 Operator password is wrong
Description
I. Description
This alarm occurs when the operator enter the wrong password for five times when the operator
logs on to the NE and the alarm security-alarm command is enable.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
702
Minor
Fault
III. Parameters
Name
Meaning
Operator
Specifies the name of the operator who

entered the wrong password.
Operator Domain Type
Specifies the domain type of the operator who

entered the wrong password. It can be local
or domain.
IP address
Specifies the IP address of the operator who

entered the wrong password.
Times of log on
Specifies the times the operator fail to log on

to the NE with the wrong password.
Impact on System
None
Issue 02 (2009-06-30)

36-1

Alarm Reference
Possible Causes
The password of the operator is wrong.
Handling Procedure
Step 1 Operator is locked currently. Wait until the locked time is over or contact administrator to unlock
the operator manually.
Step 2 Check whether the password of the operator is wrong.
l
Yes => Enter the right password.
No => Step 3
Step 3 Clear the alarm manually and check whether the alarm occurs again after the operator is
unlocked.
l
Yes => Step 4
No => End
NOTE

----End
Related Information
36-2

Issue 02 (2009-06-30)

Alarm Reference
37
ALM-0703 Operator Account Change
Description
I. Description
This alarm occurs when operator adds, modifies and deletes the account and the alarm securityalarm command is enable.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
703
Minor
Fault
III. Parameters
Issue 02 (2009-06-30)
Name
Meaning
Operator
Specifies name of the authorized operator
Specifies domain type of the operator that

executes the adding, modifying or deleting of
the operator. It can be local or domain.
IP Address
Specifies the IP address of the operator that

executes the adding, modifying or deleting of
the operator. It can be local or domain.
Change Type
Specifies the type the operator is changed to,

including the adding, modifying or deleting
of the operator.
Change Object
Specifies the operator added, modified or

deleted.

37-1

Alarm Reference
Impact on System
The operator is changed.
Possible Causes
l
Adding the operator.
Modifying the operator.
Deleting the operator.
Handling Procedure
Step 1 Check whether the specified operator's name that has been added, modified or deleted is right.
l
Yes => (2)
No => (3)
l
Yes => (4)
No => End
Step 3 Modify the name of the operator again. Clear the alarm manually and check whether the alarm
occurs again.
l
Yes => (4)
No => End
NOTE
If you want to clear the alarm after a long time when the alarm occurs, check the operation log and know
which operations has been done before. Ensure the clear of alarm influences nothing and then clear it.

Step 5 End
----End
Related Information
37-2

Issue 02 (2009-06-30)

Alarm Reference
38
ALM-0704 Operator Access To Log File
Description
I. Description
This alarm occurs when operator queries, upload or download the operation log and security log
and the alarm security-alarm command is enable.
II. Attribute
Alarm ID
Severity level
Alarm type
704
Minor
Fault
III. Parameters
Name
Meaning
Operator
Specifies the name of the operator who

queries, upload or download the operation log
and security log.
Specifies the domain type of operator who

and security log, including two types of local
and domain.
IP Address
Specifies the IP address of operator who

and security log.
Impact on System
None
Issue 02 (2009-06-30)

38-1

Alarm Reference
Possible Causes
Query, upload or download the operation log and security log.
Handling Procedure
Step 1 Check whether the operator do the operation of log correctly.
l
Yes => (2)
No => (3)
l
Yes => (4)
No => End
NOTE
Step 3 Do the operation of log again. Clear the alarm manually and check whether the alarm occurs
again.
l
Yes => (4)
No => End

Step 5 End
----End
Related Information
38-2

Issue 02 (2009-06-30)

Alarm Reference
39
ALM-0705 Operator Unauthorized

Access Attempt
Description
I. Description
This alarm occurs when operator executes commands exceeding his authority and the alarm
security-alarm command is enable.
II. Attribute
Alarm ID
Severity level
Alarm type
705
Minor
Fault
III. Parameters
Name
Meaning
Operator
Specifies the name of operator who executes

commands unauthorizedly.
Specifies the domain type of operator who

executes commands unauthorizedly,
including two types of local and domain.
IP Address
Specifies the IP address of operator who

executes commands unauthorizedly.
Impact on System
None
Issue 02 (2009-06-30)

39-1

Alarm Reference
Possible Causes
Executes commands exceeding authority.
Handling Procedure
Step 1 Check whether the operator executes the unauthorized commands by mistake.
l
Yes => (2)
No => (3)
l
Yes => (4)
No => End
NOTE
Step 3 Provide the operator with higher level of control authority. Clear the alarm manually and check
whether the alarm occurs again.
l
Yes => (4)
No => End
Step 4 Contact the HUAWEI Technical Support.

Step 5 End
----End
Related Information
39-2

Issue 02 (2009-06-30)

Alarm Reference
40
ALM-0801 License is about to use up
Description
The alarm occurs when the number of activated PDP contexts specific to a license resource
control item is equal to or greater than 90% of the number supported by the license resource
control item. The alarm is cleared when the number of activated PDP contexts decreases to 80%
of the number supported by the license resource control item.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0801
Major
Fault
Parameters
Name
Meaning
Feature name
Specifies the name of the feature generating the alarm.
Impact on System
l
If new license resources are unavailable, all new PDP context activation requests are
rejected after the number of activated PDP contexts specific to a license resource control
item increases to the number supported by the license resource control item.
Possible Causes
l
The number of activated PDP contexts specific to a license resource control item is about
to increase to the number supported by the license resource control item.
Handling Procedure
Step 1 Contact Huawei Technical Support to obtain a new license.
----End
Issue 02 (2009-06-30)

40-1

Alarm Reference
Related Information
None
40-2

Issue 02 (2009-06-30)

Alarm Reference
41
ALM-0802 License has been used up
Description
The alarm occurs when the number of activated PDP contexts specific to a license resource
control item increases to the number supported by the license resource control item. The alarm
is cleared when the number of activated PDP contexts decreases to 90% of the number supported
by the license resource control item.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0802
Critical
Fault
Parameters
Name
Meaning
Feature name
Specifies the name of the feature generating the alarm.
Impact on System
l
All new PDP context activation requests are rejected after the number of activated PDP
contexts specific to a license resource control item increases to the number supported by
the license resource control item.
Possible Causes
l
The number of activated PDP contexts specific to a license resource control item increases
to the number supported by the license resource control item.
Handling Procedure
Step 1 Contact Huawei Technical Support to obtain a new license.
----End
Issue 02 (2009-06-30)

41-1

Alarm Reference
Related Information
None
41-2

Issue 02 (2009-06-30)

Alarm Reference
42
ALM-0803 Signalling path disconnected
Description
The alarm occurs when the GTP-C path between the GGSN9811 and the SGSN is disconnected.
The GTP-C path is considered as disconnected if the following occurs: After sending or
resending an Echo Request message at a certain interval, the GGSN9811 does not receive an
Echo Response message or receives an incorrect Echo Response message from the SGSN within
the specific number of times. The interval and number of times for resending Echo Request
messages can be set.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0803
Critical
Fault
Name
Meaning
Slot No.
Specifies the number of the slot where the board generating the alarm
is located.
CPU No.
Specifies the number of the CPU where the disconnected GTP-C path
is processed.
Parameters
Signalling path local IP Specifies the local IP address of the faulty GTP-C path.
Signalling path peer IP Specifies the peer IP address of the faulty GTP-C path.
Protocol version
Specifies the protocol version that the faulty GTP-C path complies
with.
l
0: GTPv0
1: GTPv1
Impact on System
l
Issue 02 (2009-06-30)
The GGSN9811 cannot communicate with the SGSN.

42-1

l

Alarm Reference
If both the function of sending GTP-C Echo Request messages and the function of
deactivating contexts are enabled, contexts are deactivated after the duration for which the
GTP-C path is disconnected exceeds the set duration.
Possible Causes
l
The transmission line that connects the GGSN9811 and the SGSN is disconnected.
Faults occur on routes between the GGSN9811 and the SGSN.
After sending Echo Request messages, the GGSN9811 discards Echo Response messages
returned by the SGSN if they are incorrect.
After sending Echo Request messages, the SGSN fails to send Echo Response messages
to the GGSN9811.
Handling Procedure
Step 1 Check whether alarms such as the board fault alarm, physical line down alarm, CPU overload
alarm, interface-probe fault alarm, or IP-probe fault alarm are reported to the LMT.
l
No -> Step 2
Check whether the GGSN9811 communicates with the SGSN normally.
CAUTION
l
In the case that the GGSN9811 is connected with multiple SGSNs, proceed to the fault
location if only the GTP-C path under one APN is disconnected; go to Step 7 if more than
one GTP-C paths are disconnected.
Step 2 Run ping [-vpn-instance vpn-instance-name] [-a IP address of the Gn interface] host (IP
address of the SGSN). Check whether all response messages are received after ping request
messages are sent.
CAUTION
l
The source IP address is the IP address of the Gn interface.
The IP address of the SGSN can be obtained from the alarm information.
The entered VPN instance name must be correct.
If firewalls or routers are deployed between the GGSN9811 and the SGSN, check whether
the interworking between them is normal and whether the firewalls or routers function
properly.
No response messages are received -> Step 3
Not all response messages are received -> Step 13
Check whether the IP address of the Gn interface on the GGSN9811 is set correctly.
Step 3 Run display interface to check whether the IP address of Gn interface is set correctly.
42-2

Issue 02 (2009-06-30)

Alarm Reference
Yes -> Step 5
No -> Step 4
Step 4 Run interface gnif to set the IP address for the Gn interface. Activate a user, and then check
l
Cleared, indicating that the alarm is caused by the incorrect IP address setting for the Gn
interface on the GGSN9811 -> End
No -> Step 5
Check whether the routes to the SGSN are configured correctly on the GGSN9811.
Step 5 Run display ip routing-table [vpn-instance vpn-instance-name] to check whether the routes
to the SGSN are configured correctly on the GGSN9811. Ensure that the entered VPN instance
name is correct.
l
Yes -> Step 7
No -> Step 6
Step 6 Run undo ip route-static and ip route-static to modify the routing table on the GGSN9811.
Activate a user, and then check whether this alarm is cleared.
l
Cleared, indicating that the alarm is caused by the routes between the GGSN9811 and the
SGSN -> End
Check whether the operating mode and speed of the interface on the LPU of the GGSN9811
for interworking the SGSN are the same as the operating mode and speed of the connected
interface on the peer switch.
Step 7 Run display interface (physical interface on the LPU of the GGSN9811 for interworking the
SGSN) to check whether the operating mode and speed of the physical interface on the LPU of
the GGSN9811 are the same as the operating mode and speed of the connected interface on the
peer switch.
l
Yes -> Step 9
No -> Step 8
Step 8 Run duplex and speed on the GGSN9811 to set the operating mode and speed of the interface
on the LPU of the GGSN9811. Activate a user, and then check whether this alarm is cleared.
l
and speed for the physical interface -> End
Check whether the physical interface on the LPU of the GGSN9811 for interworking the
SGSN is normal.
SGSN) to check whether the interface is normal.
Check whether both current state and Line protocol current state of the interface are UP. If
yes, it indicates that the interface is normal. If either current state or Line protocol current
state of the interface is DOWN, it indicates that the interface is abnormal.
Issue 02 (2009-06-30)

42-3

Alarm Reference
CAUTION
interface.
l
Yes -> Step 12
No -> Step 10
Check whether the network cable or optical fiber is faulty.

Step 10 Remove and then insert the network cable or optical fiber again. Ensure that the network cable
or optical fiber is connected to the interface properly. Activate a user, and then check whether
this alarm is cleared.
l
Cleared, indicating that the alarm is caused by the loose connection of the network cable
or optical fiber -> End
Step 11 Replace the network cable or optical fiber. Activate a user, and then check whether the alarm is
cleared.
l
Cleared, indicating that the alarm is caused by network cable or optical fiber faults -> End
Check whether the transmission channel between the GGSN9811 and the SGSN is normal.
Step 12 Contact the technical support engineers of the SGSN to capture packets on the SGSN. Through
the captured packets, check whether the GTP-C Echo Request messages sent by the GGSN9811
can reach the SGSN.
l
Yes -> Step 13
No, indicating that the alarm is caused by the transmission failure between the GGSN9811
and the SGSN -> Step 18
the captured packets, check whether the SGSN replies with an Echo Response message each
time receiving a GTP-C Echo Request message from the GGSN9811.
l
Yes -> Step 14
No -> Step 15
Check whether the communication between the GGSN9811 and the SGSN is stable.
Step 14 On the LMT, capture packets transferred over the Gn interface to check whether an Echo
Response message is received each time a GTP-C Echo Request message is sent by the
GGSN9811.
l
Yes, indicating that the alarm is caused by packet loss due to network congestion between
the GGSN9811 and the SGSN -> Step 18
No, indicating that the alarm is caused by packet loss due to incorrect policy settings for
the firewalls or routers in the network between the GGSN9811 and the SGSN -> Step 18

Step 15 Contact the technical support engineers of the SGSN to check whether the parameters through
which the SGSN communicates with the GGSN9811 are set correctly and whether the
performance of the SGSN meets actual requirements.
l
42-4
Yes -> Step 16

Issue 02 (2009-06-30)

Alarm Reference
No, indicating that the alarm is caused by the SGSN -> Step 17

Step 17 Contact the technical support engineers of the SGSN.
Step 18 Contact the technical support engineers of the routers, switches, or any transmission devices
involved.
----End
Related Information
Run t3-timer to set the interval for and number of times for resending Echo Request messages.
The parameter t3-timer indicates the interval for resending Echo Request messages if the
GGSN9811 does not receive Echo Response messages from the SGSN. The value of this
parameter is expressed in seconds. The parameter n3-times indicates the maximum number of
times that the GGSN9811 resends Echo Request messages if the GGSN9811 does not receive
Echo Response messages from the SGSN.
Issue 02 (2009-06-30)

42-5

Alarm Reference
43
ALM-0804 Data path disconnected
Description
The alarm occurs when the GTP-U path between the GGSN9811 and the SGSN is disconnected.
The GTP-U path is considered as disconnected if the following occurs: After sending or
resending an Echo Request message at a certain interval, the GGSN9811 does not receive an
Echo Response message or receives an incorrect Echo Response message from the SGSN within
the specific number of times. The interval and number of times for resending Echo Request
messages can be set.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0804
Critical
Fault
Name
Meaning
Slot No.
Specifies the number of the slot where the board generating the alarm
is located.
CPU No.
Specifies the number of the CPU where the disconnected GTP-U is

processed.
Parameters
Data path local address Specifies the local IP address of the faulty GTP-U path.
Data path peer address Specifies the peer IP address of the faulty GTP-U path.
Protocol version
Specifies the protocol version that the faulty GTP-U path complies
with.
l
0: GTPv0
1: GTPv1
Impact on System
l
Issue 02 (2009-06-30)
The GGSN9811 cannot communicate with the SGSN.

43-1

l

Alarm Reference
If both the function of sending GTP-U Echo Request messages and the function of
deactivating contexts are enabled, contexts are deactivated after the duration for which the
GTP-U path is disconnected exceeds the set duration (30 minutes, by default).
Possible Causes
l
The transmission line that connects the GGSN9811 and the SGSN is disconnected.
Faults occur on routes between the GGSN9811 and the SGSN.
After sending Echo Request messages, the GGSN9811 discards Echo Response messages
returned by the SGSN if they are incorrect.
After sending Echo Request messages, the SGSN fails to send Echo Response messages
to the GGSN9811.
Handling Procedure
Step 1 Check whether alarm such as the board fault alarm, physical line down alarm, CPU overload
alarm, interface-probe fault alarm, and IP-probe fault alarm is generated on the LMT.
l
No -> Step 2
Check whether the GGSN9811 communicates with the SGSN normally.
CAUTION
l
In the case that the GGSN9811 is connected with multiple SGSNs, proceed to the fault
location if only the GTP-U path under one APN is disconnected; go to Step 7 if more than
one GTP-U paths are disconnected.
Step 2 Run ping [-vpn-instance vpn-instance-name] [-a IP address of the Gn interface] host (IP
address of the SGSN) . Check whether all response messages are received after ping request
messages are sent.
CAUTION
l
The source IP address is the IP address of the Gn interface.
The IP address of the SGSN can be obtained from the alarm information.
If firewalls or routers are deployed between the GGSN9811 and the SGSN, check whether
the interworking between them is normal and whether the firewalls or routers function
properly.
Check whether the IP address of the Gn interface on the GGSN9811 is set correctly.
Step 3 Run display interface gnif to check whether the IP address of Gn interface is set correctly.
43-2

Issue 02 (2009-06-30)

Alarm Reference
Yes -> Step 5
No -> Step 4
Step 4 Run interface gnif to set the IP address for the Gn interface. Activate a user, and then check
l
Cleared, indicating that the alarm is caused by the incorrect IP address setting for the Gn
interface on the GGSN9811 -> End
Check whether the routes to the SGSN are configured correctly on the GGSN9811.
Step 5 Run display ip routing-table [vpn-instance vpn-instance-name] to check whether the routes
to the SGSN are configured correctly on the GGSN9811. Ensure that the entered VPN instance
name is correct.
l
Yes -> Step 7
No -> Step 6
Activate a user, and then check whether the alarm is cleared.
l
SGSN -> End
for interworking the SGSN are the same as the operating mode and speed of the connected
SGSN) to check whether the operating mode and speed of the physical interface on the LPU of
the GGSN9811 are the same as the operating mode and speed of the connected interface on the
peer switch.
l
Yes -> Step 9
No -> Step 8
Step 8 Run duplex and speed on the GGSN9811 to set the operating mode and speed for the physical
interface on the LPU of the GGSN9811. Activate a user, and then check whether the alarm is
cleared.
l
SGSN is normal.
SGSN) to check whether the interface is normal.
Issue 02 (2009-06-30)

43-3

Alarm Reference
CAUTION
interface.
l
Yes -> Step 12
No -> Step 10

l
cleared.
l
Check whether the transmission channel between the GGSN9811 and the SGSN is normal.
the captured packets, check whether the GTP-U Echo Request messages sent by the GGSN9811
can reach the SGSN.
l
Yes -> Step 13
and the SGSN -> Step 18
the captured packets, check whether the SGSN replies with an Echo Response message each
time receiving a GTP-U Echo Request message from the GGSN9811.
l
Yes -> Step 14
No -> Step 15
Check whether the communication between the GGSN9811 and the SGSN is stable.
Step 14 On the LMT, capture packets transferred over the Gn interface to check whether an Echo
Response message is received each time a GTP-U Echo Request message is sent by the
GGSN9811.
l
the GGSN9811 and the SGSN -> Step 18
No, indicating that the alarm is caused by packet loss due to incorrect policy settings for
the firewalls or routers in the network between the GGSN9811 and the SGSN -> Step 18

Step 15 Contact the technical support engineers of the SGSN to check whether the parameters through
which the SGSN communicates with the GGSN9811 are set correctly and whether the
performance of the SGSN meets actual requirements.
l
43-4
Yes -> Step 16

Issue 02 (2009-06-30)

Alarm Reference
No, indicating that the alarm is caused by the SGSN -> Step 17

Step 17 Contact the technical support engineers of the SGSN.
involved.
----End
Related Information
Run t3-timer to set the interval for and number of times for resending Echo Request messages.
The parameter t3-timer indicates the interval for resending Echo Request messages if the
GGSN9811 does not receive Echo Response messages from the SGSN. The value of this
parameter is expressed in seconds. The parameter n3-times indicates the maximum number of
times that the GGSN9811 resends Echo Request messages if the GGSN9811 does not receive
Echo Response messages from the SGSN.
Issue 02 (2009-06-30)

43-5

Alarm Reference
44
44 ALM-0805 The usage of local address pool exceeds alarm

threshold
ALM-0805 The usage of local address

pool exceeds alarm threshold
Description
I. Description
The alarm occurs when the utilization of the local address pool bound to an APN exceeds the
specific threshold.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0805
Major
Fault
III. Parameters
Name
Meaning
The APN
Specifies the APN to which the utilization of

the address pool bound exceeds the specific
threshold.
Alarm threshold
Specifies the alarm clearance threshold.
Impact on System
When the utilization of the local address pool bound to an APN reaches 100%, new users under
this APN cannot be activated.
Possible Causes
l
Issue 02 (2009-06-30)
The number of addresses configured in the address pool bound to this APN is small.
44-1
44 ALM-0805 The usage of local address pool exceeds alarm

threshold

Alarm Reference
The number of users under the APN is large.
The alarm threshold is set to be lower than 80%.
Handling Procedure
Step 1 Run display alarm-threshold pool to check whether the alarm threshold is lower than 80%.
l
Yes -> (4)
No -> (2)
Step 2 Run display address-pool to check the usage of the address pool bound to the APN.
l
If the utilization of the address pool is higher than the alarm threshold -> (3)
Step 3 Run ip pool to configure the address pool, and then run address-pool under the APN to bind
this address pool to the APN.
l
The configuration fails and the address segments are exhausted -> (5)
Configuration succeeds -> (7)
Step 4 Run the set alarm pool command in the access viewto re-set the alarm threshold of the capacity
of the address pool.
l
Setting succeeds -> (7)
Step 5 Run display user-number to check whether users exist under some APNs.
l
Yes -> (7)
No -> (6)
Step 6 Run undo address-pool to release the binding relations between the APNs with no users and
the bound address pools. Check whether the operation succeeds.
l
Yes -> (3)
No -> (7)

l
Yes -> (9)
No -> (8)

Step 9 End.
----End
Related Information
None
44-2

Issue 02 (2009-06-30)

Alarm Reference
45
45 ALM-0806 No response of the RADIUS authentication

server
ALM-0806 No response of the RADIUS

authentication server
Description
The alarm occurs when the communication path between the GGSN9811 and the RADIUS
authentication server is disconnected. The communication path is considered as disconnected if
the following occurs: After sending or resending an authentication request message at a certain
interval, the GGSN9811 does not receive an authentication response message from the RADIUS
authentication server within the specific number of times. The interval and number of times for
resending authentication request messages can be set.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0806
Major
Fault
Parameters
Name
Meaning
Slot No.
Specifies the number of the slot where the board generating the alarm is
located.
CPU No.
Specifies the number of the CPU where authentication processing failure

occurs.
RADIUS Server IP Specifies the IP address of the RADIUS authentication server generating
the alarm.
VPN
Specifies the VPN to which the RADIUS authentication server generating

the alarm is bound.
Impact on System
l
Issue 02 (2009-06-30)
If a user is configured with only one RADIUS authentication server, the user cannot be
authenticated or access services when the alarm is generated.
45-1

server

Alarm Reference
Possible Causes
l
The parameters related to the RADIUS authentication server, such as the IP address, port
number, key, and bound VPN, are set incorrectly on the GGSN9811.
The parameters for interworking with the GGSN9811 are set incorrectly on the RADIUS
authentication server.
The RADIUS authentication server is faulty or the performance of the RADIUS

authentication server does not meet actual requirements.
The transmission between the GGSN9811 and the RADIUS authentication server is
interrupted.
Routes to the RADIUS authentication server are configured incorrectly on the GGSN9811.
The physical interface on the GGSN9811 is faulty.
Congestion occurs in the network between the GGSN9811 and the RADIUS authentication
server.
Handling Procedure
l
No -> Step 2
Check whether the GGSN9811 communicates with the RADIUS authentication server
normally.
CAUTION
l
In the case that the GGSN9811 is connected with multiple RADIUS authentication servers,
proceed to the fault location if only the RADIUS authentication server under one APN does
not respond; go to Step 7 if more than one RADIUS authentication servers do not respond.
Step 2 Run ping-vpn-instancevpn-instance-name-aIP address of the Gi interfacehostIP address

of the RADIUS authentication server. Check whether all response messages are received after
ping request messages are sent.
CAUTION
l
The source IP address is the IP address of the Gi interface.
The IP address of the RADIUS authentication server can be obtained from the alarm
information.
If firewalls or routers are deployed between the GGSN9811 and the RADIUS authentication
server, check whether the interworking between them is normal and whether the firewalls or
routers function properly.
l
45-2

Issue 02 (2009-06-30)

Alarm Reference

server
Check whether the parameters related to the RADIUS authentication server are set
correctly on the GGSN9811.
Step 3 Run display radius-server group to check whether the IP address, port number, key, and bound
VPN of the RADIUS authentication server are set correctly on the GGSN9811.
l
Yes -> Step 5
No -> Step 4
Step 4 Run radius-server authentication to set the IP address, port number, key, and bound VPN for
the RADIUS authentication server. Activate a user, and then check whether the alarm is cleared.
l
Cleared, indicating that the alarm is generated because the parameters related to the
RADIUS authentication server are set incorrectly on the GGSN9811 -> End
Check whether the routes to the RADIUS authentication server are configured correctly
on the GGSN9811.
Step 5 Run display ip routing-tablevpn-instancevpn-instance-name to check whether the routes to
the RADIUS authentication server are configured correctly on the GGSN9811. Ensure that the
entered VPN instance name is correct.
l
Yes -> Step 7
No -> Step 6
l
RADIUS authentication server -> End
for interworking with the RADIUS authentication server are the same as the operating
mode and speed of the connected interface on the peer switch.
Step 7 Run display interface to check whether the operating mode and speed of the physical interface
on the LPU of the GGSN9811 for interworking the RADIUS authentication server are the same
as the operating mode and speed of the connected interface on the peer switch.
l
Yes -> Step 9
No -> Step 8
on the LPU of the GGSN9811. Activate a user, and then check whether the alarm is cleared.
l
RADIUS authentication server is normal.
Step 9 Run display interfacephysical interface on the LPU of the GGSN9811 for interworking the
RADIUS authentication server to check whether the interface is normal.
Issue 02 (2009-06-30)

45-3

server

Alarm Reference
CAUTION
interface.
l
Yes -> Step 12
No -> Step 10

l
cleared.
l
Check whether the transmission channel between the GGSN9811 and the RADIUS
authentication server is normal.
Step 12 Contact the technical support engineers of the RADIUS authentication server to capture packets
on the RADIUS authentication server. Through the captured packets, check whether the
RADIUS authentication request packets sent by the GGSN9811 can reach the RADIUS
authentication server.
l
Yes -> Step 13
and the RADIUS authentication server -> Step 18
Step 13 Contact the technical support engineers of the RADIUS authentication server to capture packets
on the RADIUS authentication server. Through the captured packets, check whether the
RADIUS authentication server replies with an authentication response message each time
receiving an authentication request message from the GGSN9811.
l
Yes -> Step 14
No -> Step 15
Check whether the communication between the GGSN9811 and the RADIUS
authentication server is stable.
Step 14 On the LMT, capture packets transferred over the Gi interface to check whether an authentication
response message is received each time an authentication request message is sent by the
GGSN9811.
l
the GGSN9811 and the RADIUS authentication server -> Step 18
No, indicating that the alarm is caused by packet loss due to incorrect policy setting for the
firewalls or routers between the GGSN9811 and the RADIUS authentication server -> Step
18

45-4

Issue 02 (2009-06-30)

Alarm Reference

server
Step 15 Contact the technical support engineers of the RADIUS authentication server to check whether
the parameters for interworking with the GGSN9811 are set correctly and whether the
performance of the RADIUS authentication server meets actual requirements.
l
Yes -> Step 16
No, indicating that the alarm is caused by the RADIUS authentication server -> Step 17

Step 17 Contact the technical support engineers of the RADIUS authentication server.
involved.
----End
Related Information
Run radius-server retransmit timeout to set the interval for and number of times for resending
authentication request messages. The parameter retransmit indicates the maximum number of
times that the GGSN9811 resends authentication request messages if the GGSN9811 does not
receive an authentication response message from the RADIUS authentication server. The
parameter timeout indicates the interval for resending authentication request messages if the
GGSN9811 does not receive an authentication response message from the RADIUS
authentication server. The value of this parameter is expressed in seconds.
Issue 02 (2009-06-30)

45-5

Alarm Reference
46
ALM-0807 ARP threshold control of an

APN
Description
I. Description
The alarm occurs in the following cases:
l
When the ratio of the number of PDP contexts under an APN to the total number of users
under this APN reaches the PDP access rejection threshold configured in the system, the
alarm occurs and users of a certain level or a certain service level cannot access the network.
The threshold is set through bandwidth-arp.
When the ratio of the bandwidth occupied by the users under an APN to the bandwidth of
this APN reaches the bandwidth rejection threshold configured in the system, users of a
certain level or a certain service level cannot access the network and the alarm occurs. The
threshold is set through pdpnumber-arp.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0807
Major
Fault
III. Parameters
Issue 02 (2009-06-30)
Name
Meaning
Threshold type
Specifies the threshold for generating the

alarm. It can be the PDP rejection threshold
or bandwidth threshold of the APN.
The APN
Specifies the APN where the alarm occurs.

46-1

Alarm Reference
Name
Meaning
User level
Specifies the user level to be restricted. It can

be set to the following:
l
High level users
Normal users
Low level users
Specifies the service level to be restricted. It

can be set to the following:
Service level
Conversation
Streaming service whose downlink

guarantee bandwidth is not less than 25
kbit/s

guarantee bandwidth is less than 25 kbit/s
Interactive service whose transmitting

control level is 1

control level is 2

control level is 3
Background service
Impact on System
The differentiated service function is not enabled, the PDP rejection threshold or bandwidth
rejection threshold is configured under the APN, and the ratio of the PDP number or occupied
bandwidth of an APN reaches the configured threshold. Then, the alarm occurs, it indicates that
the users of a certain level or a certain service level are rejected to access the network because
of the following reasons. Thus, resources are reserved for high level users. There is no other
impact on the system.
Possible Causes
l
The ratio of the number of PDP contexts under an APN to that of the maximum number of
PDP contexts under the APN is equal to or more than the PDP rejection threshold configured
based on the APN.
The ratio of the occupied bandwidth of an APN to the maximum bandwidth of the APN is
equal to or more than the bandwidth rejection threshold configured based on the APN.
Handling Procedure
Step 1 Run display gtp-support to check whether the differentiated service function is enabled.
46-2
If yes, and you need to use this function -> (2)
If yes, but you do not use this function -> (3)

Issue 02 (2009-06-30)

Alarm Reference
Step 2 Run display bandwidth-arp and display pdpnumber-arp to check the rejection thresholds
configured in the system.
l
If the thresholds are configured based on an APN -> (4)
Step 3 If the differentiated service function is not used, run gtp-support to disable this function. No
new alarm occurs. The alarm can be automatically cleared based on the service process.
Step 4 If the thresholds are configured based on an APN, run display max-bandwidth and display
max-pdpnumber to check the maximum bandwidth and maximum number of PDP contexts of
the APN.
Step 5 If the configured thresholds are unreasonable,
l
To increase the number used for threshold computing based on an APN -> (6)
To increase the rejection threshold based on an APN -> (7)
Step 6 Run max-bandwidth and max-pdpnumber to check the maximum bandwidth and maximum
number of PDP contexts of the APN respectively. If the modified value is smaller than the
threshold, check whether the alarm is cleared.
l
Cleared -> (10)
Not cleared -> (9)
Step 7 Run bandwidth-arp and pdpnumber-arp to increase the rejection thresholds, and then check
l
Cleared -> (10)
Not cleared -> (9)
Step 8 Generation of the alarm is a normal condition. You do not need to clear the alarm. When the
number of PDP contexts or occupied bandwidth of the APN decreases to the clearance threshold,
users can normally access the network and the alarm is cleared.
Step 10 End.
----End
Related Information
None
Issue 02 (2009-06-30)

46-3

Alarm Reference
47
ALM-0808 ARP threshold control of the

GGSN
Description
I. Description
The alarm occurs in the following cases:
l
The alarm occurs when the threshold set for the differentiated services is reached.
When the ratio of the number of PDP contexts to the total number of users in the system
reaches the PDP access rejection threshold configured, users of a certain level or a certain
service level cannot access the network. The threshold is set through pdpnumber-arp.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0808
Major
Fault
III. Parameters
Issue 02 (2009-06-30)
Name
Meaning
User level
Specifies the user level to be restricted. It can

be set to the following:
l
High level users
Normal users
Low level users

47-1

Alarm Reference
Name
Meaning
Service level
Specifies the service level to be restricted. It

can be set to the following:
l
Conversation

guarantee bandwidth is not less than 25
kbit/s

guarantee bandwidth is less than 25 kbit/s

control level is 1

control level is 2

control level is 3
Background service
Impact on System
l
The differentiated service function configured in the system is enabled.
The PDP rejection threshold is configured on the GGSN.
The ratio of the number of PDP contexts to the total number of users reaches the configured
threshold.
The users of a certain level or a certain service level are rejected to access the network.
Thus, resources are reserved for high level users.
Possible Causes
When the alarm is generated, users of the specific levels may not be able to access the network.
When the ratio of the PDP contexts decreases to the clearance threshold, users can normally
access the network.
Handling Procedure
Step 1 Run display gtp-support to check whether the differentiated service function is enabled.
l
If yes, and you need to use this function -> (2)
Step 2 Run display pdpnumber-arp to check the rejection threshold configured in the system.
l
If only the threshold based on the user level or service level is configured on the GGSN ->
(3)
Step 3 Run display license config to check the number of PDP contexts that can be supported by the
basic functions.
Step 4 Generation of the alarm is a normal condition. You do not need to clear the alarm. When the
ratio of the number of PDP contexts decreases to the clearance threshold, users can normally
access the network and the alarm is cleared.
47-2

Issue 02 (2009-06-30)

Alarm Reference

Step 6 End.
----End
Related Information
None
Issue 02 (2009-06-30)

47-3

Alarm Reference
48
ALM-0810 The GGSN and the BMSC are

disconnected
Description
I. Description
The alarm occurs when the GGSN is disconnected from the BMSC due to communication failure.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0810
Major
Fault
III. Parameters
Name
Meaning
Slot No.

CPU No.
Specifies the ID of the CPU where the alarm

occurs.
Host name
Specifies the host name of the BMSC.
BMSC IP
Specifies the IP address of the BMSC.
Impact on System
When the GGSN and the BMSC are disconnected, the MBMS service cannot proceed. The alarm
is not reported when the BMSC initiates the disconnection.
Possible Causes
The connection between the GGSN and the BMSC fails.
Issue 02 (2009-06-30)

48-1

Alarm Reference
Handling Procedure
Step 1 Check whether the communication cables between the BMSC and the GGSN are normally
connected.
l
Normally -> (3)
Abnormally -> (2)
Step 2 Connect the cables properly or replace the faulty cables, and then check whether the alarm is
cleared.
l
Cleared -> (4)
Not cleared -> (3)

Step 4 End.
----End
Related Information
None
48-2

Issue 02 (2009-06-30)

Alarm Reference
49
ALM-0811 MBMS Service Flow

Interruption
Description
I. Description
This alarm is generated when no downlink data flow of a multicast MBMS session is reported
for a certain consecutive period.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0811
Major
Fault
III. Parameters
Name
Meaning
Slot No.

CPU No.
Specifies the number of the CPU of the board

generating the alarm.
TMGI
Specifies the TMGI of an MBMS session that

does not have multicast MBMS data flows.
BMSC IP
Specifies the IP address of the peer BM-SC.
Group
Specifies the multicast group to which an

MBMS session belongs.
Impact on System
Multicast data flows are interrupted, and broadcast services stop.
Issue 02 (2009-06-30)

49-1

Alarm Reference
Possible Causes
l
The BM-SC stops sending downlink multicast data.
Abnormalities occur on the link of the BM-SC, for example, the link is torn down or a large
number of packets are lost.
The interfaces of the GGSN are abnormal, which causes receipt failure of downlink
multicast data packets.
Handling Procedure
Step 1 Observe the alarm subsystem to check whether alarms related to the Gi interface are generated.
l
No ->(2)
Yes ->(4)
Step 2 Run the display ip interface command to check the status of the outbound Gi interface.
l
Unavailable ->(3)
Available ->(4)
Step 3 Check whether the network cables are connected to the physical interfaces properly, and check
whether the other ends of the network cables are properly connected to the available NEs such
as routers, switches, and BM-SCs.
Step 4 Run the ping command to check whether the peer BM-SC can be pinged through.
l
No ->(5)
Yes ->(6)
Step 5 If the peer BM-SC cannot be pinged through, perform the following operations:
l
Check whether the intermediate physical links are connected properly.
Check whether the BM-SC is configured not to return ping packets.
If firewalls are used between the GGSN and the BM-SC, check whether the firewalls are
configured to intercept packets.
Capture packets on each interface on the entire link, and then run the ping command to specify
the NEs that lose packets.
Step 6 Check whether the BM-SC already stops forwarding MBMS multicast data.
l
No ->(8)
Yes ->(7)
Step 7 Consult the personnel from the office or personnel of the BM-SC.
Step 8 Capture packets on the Gi interfaces of the GGSN and BM-SC, as well as on the interfaces of
the intermediate NEs. Specify the NEs that lose packets. Then, consult technical support
personnel of related NEs.
Step 10 End.
----End
49-2

Issue 02 (2009-06-30)

Alarm Reference
Related Information
None
Issue 02 (2009-06-30)

49-3

Alarm Reference
50
ALM-0812 RADIUS accounting server

has no responding
Description
The alarm occurs when the communication path between the GGSN9811 and the RADIUS
accounting server is disconnected. The communication path is considered as disconnected if the
following occurs: After sending or resending an accounting request message at a certain interval,
the GGSN9811 does not receive an accounting response message from the RADIUS accounting
server within the specific number of times. The interval and number of times for resending
accounting request messages can be set.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0812
Major
Fault
Parameters
Name
Meaning
Slot No.
Specifies the number of the slot where the board generating the alarm is
located.
CPU No.
Specifies the number of the CPU where accounting processing failure

occurs.
RADIUS server IP Specifies the IP address of the RADIUS accounting server.

VPN
Specifies the VPN to which the RADIUS accounting server generating

the alarm is bound.
Impact on System
l
Issue 02 (2009-06-30)
After the communication path to the RADIUS accounting server is disconnected, the
GGSN9811 cannot send CDRs to the RADIUS accounting server, but the GGSN9811 can
send the CDRs to an available CG.
50-1

l

Alarm Reference
For new access users, the GGSN9811 cannot receive an Accounting Start Response
message after sending an Accounting Start message so that the GGSN9811 deactivates the
contexts of users under the APN by default. To modify the action of the GGSN9811, run
radius acctctrl to set response-timeout to continue. Then, the GGSN9811 does not
deactivate the contexts of the users even if Accounting Start Response messages are not
received.
Possible Causes
l
The RADIUS accounting server is faulty or the performance of the RADIUS accounting
server does not meet actual requirements.
The parameters related to the RADIUS accounting server, such as the IP address, port
number, key, and bound VPN, are set incorrectly on the GGSN9811.
The parameters for interworking with the GGSN9811 are set incorrectly on the RADIUS
accounting server.
The transmission between the GGSN9811 and the RADIUS accounting server is
interrupted.
Congestion occurs in the network between the GGSN9811 and the RADIUS accounting
server.
Routes to the RADIUS accounting server are configured incorrectly on the GGSN9811.
The physical interface on the GGSN9811 is faulty.
Handling Procedure
l
No -> Step 2
Check whether the GGSN9811 communicates with the RADIUS accounting server
normally.
CAUTION
l
In the case that the GGSN9811 is connected with multiple RADIUS accounting servers,
proceed to the fault location if only the RADIUS accounting server under one APN does not
respond; go to Step 7 if more than one RADIUS accounting servers do not respond.
Step 2 Run ping-vpn-instancevpn-instance-name-aIP address of the Gi interfacehostIP address

of the RADIUS accounting server. Check whether all response messages are received after
ping request messages are sent.
50-2

Issue 02 (2009-06-30)

Alarm Reference
CAUTION
l
The source IP address is the IP address of the Gi interface.
The IP address of the RADIUS accounting server can be obtained from the alarm information.
If firewalls or routers are deployed between the GGSN9811 and the RADIUS accounting
server, check whether the interworking between them is normal and whether the firewalls or
routers function properly.
Check whether the parameters related to the RADIUS accounting server are set correctly
on the GGSN9811.
Step 3 Run display radius-server group to check whether the IP address, port number, key, and bound
VPN of the RADIUS accounting server are set correctly on the GGSN9811.
l
Yes -> Step 5
No -> Step 4
Step 4 Run radius-server accounting to set the IP address, port number, key, and bound VPN for the
RADIUS accounting server. Activate a user, and then check whether the alarm is cleared.
l
Cleared, indicating that the alarm is generated because the parameters related to the
RADIUS accounting server are set incorrectly on the GGSN9811 -> End
Check whether the routes to the RADIUS accounting server are configured correctly on
the GGSN9811.
the RADIUS accounting server are configured correctly on the GGSN9811. Ensure that the
entered VPN instance name is correct.
l
Yes -> Step 7
No -> Step 6
Step 6 Run undo ip route-static and ip route-staticto modify the routing table on the GGSN9811.
l
RADIUS accounting server -> End
for interworking the RADIUS accounting server are the same as the operating mode and
speed of the connected interface on the peer switch.
Step 7 Run display interface to check whether the operating mode and speed of the physical interface
on the LPU of the GGSN9811 for interworking the RADIUS accounting server are the same as
the operating mode and speed of the connected interface on the peer switch.
l
Yes -> Step 9
No -> Step 8
Issue 02 (2009-06-30)

50-3

Alarm Reference
on the LPU of the GGSN9811. Activate a user, and then check whether the alarm is cleared.
l
Check whether the physical interface on LPU of the GGSN9811 for interworking the
RADIUS accounting server is normal.
RADIUS accounting server to check whether the interface is normal.
CAUTION
interface.
l
Yes -> Step 12
No -> Step 10

l
cleared.
l
Check whether the transmission channel between the GGSN9811 and the RADIUS
accounting server is normal.
Step 12 Contact the technical support engineers of the RADIUS accounting server to capture packets on
the RADIUS accounting server. Through the captured packets, check whether the RADIUS
accounting request packets sent by the GGSN9811 can reach the RADIUS accounting server.
l
Yes -> Step 13
and the RADIUS accounting server -> Step 18
Step 13 Contact the technical support engineers of the RADIUS accounting server to capture packets on
the RADIUS accounting server. Through the captured packets, check whether the RADIUS
accounting server replies with an accounting response message each time receiving an
accounting request message from the GGSN9811.
50-4

Issue 02 (2009-06-30)

Alarm Reference
Yes -> Step 14
No -> Step 15
Check whether the communication between the GGSN9811 and the RADIUS accounting
server is stable.
Step 14 On the LMT, capture packets transferred over the Gi interface to check whether an accounting
response message is received each time an accounting request message is sent by the GGSN9811.
l
the GGSN9811 and the RADIUS accounting server -> Step 18
firewalls or routers between the GGSN9811 and the RADIUS accounting server -> Step
18

Step 15 Contact the technical support engineers of the RADIUS accounting server to check whether the
parameters for interworking with the GGSN9811 are set correctly and whether the performance
of the RADIUS accounting server meets actual requirements.
l
Yes -> Step 16
No, indicating that the alarm is caused by the RADIUS accounting server -> Step 17

Step 17 Contact the technical support engineers of the RADIUS accounting server.
involved.
----End
Related Information
Run radius-server retransmit timeout to set the interval for and number of times for resending
accounting request messages. The parameter retransmit indicates the maximum number of
times that the GGSN9811 resends accounting request messages if the GGSN9811 does not
receive an accounting response message from the RADIUS accounting server. The parameter
timeout indicates the interval for resending accounting request messages if the GGSN9811 does
not receive an accounting response message response from the RADIUS accounting server. The
value of this parameter is expressed in seconds.
Issue 02 (2009-06-30)

50-5

Alarm Reference
51
51 ALM-0813 The usage of CDR POOL exceed alarm

threshold
ALM-0813 The usage of CDR POOL

exceed alarm threshold
Description
I. Description
The alarm occurs when the capacity of the CDR pool exceeds the configured alarm threshold.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0813
Major
Fault
III. Parameters
Name
Meaning
Slot No.

CPU No.
Specifies the ID of the CPU where the alarm

occurs.
Alarm threshold
Specifies the configured alarm threshold.
Alarm Recover threshold
Specifies the configured alarm clearance

threshold.
Impact on System
l
CDRs is saved in the hard disk on the GGSN.
When a large number of users are actthresholdd, if the threshold for CDR generation is
low, the CDRs generated cannot be reported to the CG in time.
Issue 02 (2009-06-30)

51-1

threshold

Alarm Reference
Possible Causes
l
The connection between the GGSN and the CG is broken.
The threshold for CDR generation is low.
The configured alarm threshold for the capacity of the CDR pool is low.
Handling Procedure
Step 1 Check whether the CG is normal.
l
Abnormal -> (12)
Normal -> (2)
Step 2 Check whether the physical links between the GGSN and the CG are normal.
l
Normal -> (13)
Abnormal -> (3)
Step 3 Recover the physical links. Run display cg-status to check whether the working status of the
CG is normal.
l
Abnormally -> (5)
Normal -> (4)

l
Cleared -> (14)
Not cleared -> (5)
Step 5 Run display ip routing-table to check whether the route of the GGSN to the CG is correct.
l
Incorrect -> (6)
Correct -> (7)
Step 6 Run ip route-static to configure a correct route, and then check whether the alarm is cleared.
l
Cleared -> (14)
Not cleared -> (7)
Step 7 Check whether the route of the CG to the GGSN is configured.

l
Configured -> (8)
Not configured -> (7)
Step 8 Configure the correct route on the CG to the GGSN, and then check whether the alarm is cleared.
l
Cleared -> (14)
Not cleared -> (9)
Step 9 Run display charge-general-property to check the threshold for CDR generation.
Step 10 Run charge-general-property to increase the threshold for CDR generation, and then check
l
Cleared -> (14)
Not cleared -> (13)

51-2

Issue 02 (2009-06-30)

Alarm Reference
l
Cleared -> (14)
Not cleared -> (13)

threshold
Step 12 Contact CG Technical Support.

Step 14 End.
----End
Related Information
None
Issue 02 (2009-06-30)

51-3

Alarm Reference
52
52 ALM-0814 The communications path to CG is down

alarm
ALM-0814 The communications path to

CG is down alarm
Description
The alarm occurs when the communication path between the GGSN9811 and the CG is
disconnected. The communication path is considered as disconnected if the following occurs:
After sending or resending an Echo Request message at a certain interval, the GGSN9811 does
not receive an Echo Response message from the CG within the specific number of times. The
interval and number of times for resending Echo Request messages can be set.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0814
Minor
Fault
Parameters
Name
Meaning
Slot No. Specifies the number of the slot where the board generating the alarm is located.
CPU ID Specifies the number of the CPU where the failure of CG charging processing occurs.
CG
Specifies the IP address of the CG generating the alarm.
Port
Specifies the port number of the CG generating the alarm.
Impact on System
l
If another CG of the same type as the faulty CG is available and its communication with
the GGSN9811 is normal, the GGSN9811 redirects CDRs to the CG when the alarm is
generated.
If a CG is normal, the CG sends redirection request messages to the GGSN9811. If a CG

is abnormal, or the type of the CG is not the same as the type of the faulty CG, the
GGSN9811 fails to redirect CDRs to the CG and generates 54 ALM-0816 CG redirection
failed.
Issue 02 (2009-06-30)

52-1

alarm
l

Alarm Reference
If the communication paths between the GGSN9811 and all CGs of the same type as the
faulty CG are disconnected, the GGSN9811 cannot send CDRs to a CG in time; instead
the GGSN9811 stores the CDRs in the hard disk of the GGSN9811. If the available capacity
of the hard disk is insufficient, the GGSN9811 discards new CDRs and generates 26
ALM-0632 Insufficient Hard Disk Space.
Possible Causes
l
Routes to the CG are configured incorrectly on the GGSN9811.
The CG fails to reply with Echo Response messages within the specific number of resending
times due to fault or performance degradation of the CG.
The communication path between the GGSN9811 and the CG is faulty.
Congestion occurs in the network between the GGSN9811 and the CG.
Handling Procedure
l
No -> Step 2
Check whether the GGSN9811 communicates with the CG normally.
CAUTION
l
In the case that the GGSN9811 is connected with multiple CGs, proceed to the fault location
if only one CG does not respond; go to Step 7 if more than one CGs do not respond.
Step 2 Run ping-vpn-instancevpn-instance-name-aIP address of the Ga interfacehostIP address

of the CG. Check whether all response messages are received after ping request messages are
sent.
CAUTION
l
The source IP address is the IP address of the Ga interface.
The IP address of the CG can be obtained from the alarm information.
If firewalls or routers are deployed between the GGSN9811 and the CG, check whether the
interworking between them is normal and whether the firewalls or routers function properly.
Check whether the parameters related to the CG are set correctly on the GGSN9811.
Step 3 Run display cg to check whether the IP address, priority, CG type, and port number of the CG
are set correctly on the GGSN9811.
52-2

Issue 02 (2009-06-30)

Alarm Reference
Yes -> Step 5
No -> Step 4

alarm
Step 4 Run cg to set the IP address, priority, CG type, and port number for the CG. Activate a user, and
then check whether the alarm is cleared.
l
Cleared, indicating that the alarm is generated because the parameters related to the CG
are set incorrectly on the GGSN9811 -> End
Check whether the routes to the CG are configured correctly on the GGSN9811.
the CG are configured correctly on the GGSN9811. Ensure that the entered VPN instance name
is correct.
l
Yes -> Step 7
No -> Step 6
Activate a user, and then check whether this alarm is cleared.
l
CG -> End
for interworking the CG are the same as the operating mode and speed of the connected
CG to check whether the operating mode and speed of the physical interface on the LPU of the
GGSN9811 for interworking the CG are the same as the operating mode and speed of the
connected interface on the peer switch.
l
Yes -> Step 9
No -> Step 8
on the LPU of the GGSN9811. Activate a user, and then check whether this alarm is cleared.
l
Check whether the physical interface on the GGSN9811 for interworking the CG is normal.
CG to check whether the interface is normal.
CAUTION
interface.
Issue 02 (2009-06-30)

52-3

alarm
Yes -> Step 12
No -> Step 10

Alarm Reference

this alarm is cleared.
l
cleared.
l
Check whether the transmission channel between the GGSN9811 and the CG is normal.
Step 12 Contact the technical support engineers of the CG to capture packets on the CG. Through the
captured packets, check whether the Echo Request messages sent by the GGSN9811 every
minute can reach the CG.
NOTE
If services are being processed, contact the technical support engineers of the CG to capture packets on the
CG. Through the captured packets, check whether accounting request messages can reach the CG.
Yes -> Step 13
and the CG -> Step 18
Step 13 Contact the technical support engineers of the CG to capture packets on the CG. Through the
captured packets, check whether the CG replies with an Echo Response message each time
receiving an Echo Request message from the GGSN9811.
NOTE
The CG may not respond to all accounting request messages.
Yes -> Step 14
No -> Step 15
Check whether the communication between the GGSN9811 and the CG is stable.
Step 14 On the LMT, capture packets transferred over the Ga interface to check whether an Echo
Response message is received each time an Echo Request message is sent by the GGSN9811.
Note that the CG may not respond to all accounting request messages.
l
the GGSN9811 and the CG -> Step 18
firewalls or routers between the GGSN9811 and the CG -> Step 18

Step 15 Contact the technical support engineers of the CG to check whether the parameters through
which the CG communicates with the GGSN9811 are set correctly and whether the performance
of the CG meets actual requirements.
l
52-4
Yes -> Step 16

Issue 02 (2009-06-30)

Alarm Reference

alarm
No, indicating that the alarm is caused by the CG -> Step 17

Step 17 Contact the technical support engineers of the CG.
involved.
----End
Related Information
Run cg-resend-times to set the number of times for resending GTP' Echo Request messages
and accounting request messages and set the interval for resending accounting request messages.
Set the interval for sending Echo Request messages to 1 minute.
The parameter retransmit indicates the number of times that the GGSN9811 resends GTP' Echo
Request messages and accounting request messages.
NOTE
For Echo Request messages, the parameter retransmit indicates the number of times that the
GGSN9811 resends the GTP' Echo Request message. If the CG does not respond within the set value
of retransmit, the CG is considered as abnormal.
For accounting request messages, the parameter retransmit indicates the maximum number of times
that the GGSN9811 resends the accounting request message to the CG if the CG does not respond.
The parameter timeout indicates the interval for resending accounting request messages if the
GGSN9811 does not receive an accounting response message. The value of this parameter is
expressed in seconds.
Issue 02 (2009-06-30)

52-5

Alarm Reference
53
ALM-0815 The version of GTP' is not

supported
Description
I. Description
The alarm occurs when the GGSN receives the GTP' signaling of an incorrect version. The alarm
does not occur again when the interconnection between the GGSN and the CG succeeds.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0815
Minor
Event
III. Parameters
Name
Meaning
Slot No.

CPU No.
Specifies the number of the CPU where the

alarm occurs.
CG IP
Specifies the IP address of the CG.
CG Port
Specifies the port number of the CG.
Impact on System
The GGSN does not process the GTP' signaling of an incorrect version.
Issue 02 (2009-06-30)

53-1

Alarm Reference
Possible Causes
The GGSN receives a GTP' signaling message and the protocol version in the GTP' header is
not V0, V1, or V2.
Handling Procedure
Step 1 Check whether the protocol version of GTP' used by the CG that is connected with the GGSN
is V0, V1, or V2.
l
Yes -> (3)
No -> (2)
Step 2 Run the proper configuration commands on the CG to change the version of GTP' to V0, V1, or
V2. Then, check whether the alarm is cleared.
l
Cleared -> (4)
Not cleared -> (3)

Step 4 End.
----End
Related Information
None
53-2

Issue 02 (2009-06-30)

Alarm Reference
54
ALM-0816 CG redirection failed
Description
I. Description
The alarm occurs when the GGSN receives the redirection request sent by the source CG and
the redirection fails. The source CG refers to the CG that sends redirection requests to the GGSN.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0816
Minor
Event
III. Parameters
Name
Meaning
Slot No.

CPU No.

alarm occurs.
CG IP
Specifies the IP address of the CG.
CG Port
Specifies the port number of the CG.
Impact on System
l
When the CG redirection fails, if no CG whose type is the same as that of the source CG
exists among the CGs that are normally connected with the GGSN, the GGSN stores the
CDRs that are to be directed to such CGs to the hard disk. If the number of stored CDRs
reaches the maximum value, the GGSN discards the CDRs that are newly generated.
When CG redirection fails, the GGSN searches for the CG whose type is the same as that
of the source CG among the CGs that are normally connected with the GGSN. If such a
CG is found, the GGSN redirects the CDRs to the CG. If the GGSN cannot find this CG,
Issue 02 (2009-06-30)

54-1

Alarm Reference
the GGSN stores the CDRs in the hard disk. If the number of the stored CDRs reaches the
maximum value, the GGSN discards the CDRs that are newly generated.
l
If the communication between the GGSN and the source CG fails, "ALM-0814 The
communications path to CG is down alarm" is generated.
Possible Causes
l
The communication link between the GGSN and the redirection CG is faulty.
The redirection CG runs abnormally.
The data configuration on the source CG and the corresponding configuration on the GGSN
are not consistent and the AAA authentication server is faulty.
Handling Procedure
Step 1 Run display cg to check whether the redirection CG is configured on the GGSN and the type
of the CG.
l
If the redirection CG is configured and the type of the CG is the same as that of the source
CG -> (2)
If the redirection CG is not configured or if the type of the CG is different from that of the
source CG -> (6)
Step 2 Run display cg-status to check whether the communication between the redirection CG and the
GGSN is normal.
l
Normal -> (8)
Abnormal -> (3)
Step 3 Check whether the communication cables between the redirection CG and the GGSN are
normally connected.
l
Normally -> (5)
Abnormally -> (4)
cleared.
l
Cleared -> (9)
Not cleared -> (5)
Step 5 Check whether the redirection CG runs normally.

l
Normally -> (8)
Abnormally -> clear the fault of the redirection CG -> (7)
Step 6 Run cg to configure a redirection CG on the GGSN. The type of the CG must be the same as
that of the source CG. Then, based on the networking condition, determine whether a route to
the redirection CG needs to be configured through ip route-static.
l
Configuration succeeds -> (7)
Configuration fails and the CGs are fully configured -> Locate the CGs that can be deleted,
and then run undo cg to delete the CGs -> (6)

l
54-2
Cleared -> (9)

Issue 02 (2009-06-30)

Alarm Reference
l
Not cleared -> (8)

Step 9 End.
----End
Related Information
None
Issue 02 (2009-06-30)

54-3

Alarm Reference
55
ALM-0817 The GGSN and the OCS are

disconnected
Description
I. Description
The alarm occurs when the GGSN is disconnected from the OCS, the alarm reason is Connection
lay failure and is cleared when the connection is restored.
The alarm also occurs when the GGSN waiting for CCA from the OCS time out and the amount
of CCA time out has reached the threshold.The alarm reason is Application lay failure. If the
amount of continuously received CCA afterward reaches the threshold, the alarm is cleared.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0817
Critical
Fault
III. Parameters
Issue 02 (2009-06-30)
Name
Meaning
Slot No.

CPU No.

alarm occurs.
OCS Name
Specifies the Name of the OCS.
Alarm Reason
Specifies the reason of the alarm.

55-1

Alarm Reference
Impact on System
l
The links between the GGSN and the OCSs of the same type are all disconnected.
Connection lay alarm of the OCS will occur and the alarm reason is Connection lay
failure.When the link between the OCS and the GGSN is restored, the alarm is cleared.
When the GGSN waiting for CCA from the OCS time out and the amount of CCA time
out has reached the threshold. Application lay alarm of the OCS will occur and the alarm
reason is Application lay failure. If the amount of continuously received CCA afterward
reaches the threshold, the alarm is cleared.
Possible Causes
l
The communication link between the GGSN and the OCS is faulty. For example, the
interface connection is loose or the cables are damaged.
The peer OCS is faulty.
The link status between the GGSN and the OCS is normal, but the capability of process
the CCR messages is not enough
Handling Procedure
Step 1 Check whether the GGSN and the OCS are normally connected.
l
Normally -> (3)
Abnormally -> (2)
cleared.
l
Cleared -> (6)
Not cleared -> (3)
Step 3 Check whether the peer OCS runs normally.

l
Normally -> (5)
Abnormally -> Clear the fault of the OCS -> (4)

l
Cleared -> (6)
Not cleared -> (5)

Step 6 End.
----End
Related Information
None
55-2

Issue 02 (2009-06-30)

Alarm Reference
56
56 ALM-0818 Disconnection Between the GGSN and FTP

Server for CDR Audit
ALM-0818 Disconnection Between the

GGSN and FTP Server for CDR Audit
Description
I. Description
This alarm is generated when the GGSN and the FTP server for CDR audit are disconnected.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0818
Major
Fault
III. Parameters
Name
Meaning
FTP address
Specifies the IP address of the FTP server.
Impact on System
The CDR audit files cannot be uploaded to the FTP server.
Possible Causes
l
Routes between the GGSN and the FTP server are unavailable.
The FTP server is not started.
The user name and password configured on the GGSN for logging in to the FTP server are
wrong.
Issue 02 (2009-06-30)

56-1
56 ALM-0818 Disconnection Between the GGSN and FTP

Server for CDR Audit

Alarm Reference
Handling Procedure
Step 1 Run the ping command to check whether the FTP server can be pinged through.
l
No ->(2)
Yes ->(3)
Step 2 Check the routes between the GGSN and the FTP server.
Step 3 Run the ftp command to check whether you can log in to the FTP server.
l
The "user name okay, need password" message is displayed by the GGSN ->(4)
You can log in to the FTP server normally ->(5)
Step 4 Check whether the user name and password configured on the GGSN are the same as those
configured on the FTP server. If different, modify the user name and password configured on
the GGSN. Check whether the alarm is cleared.
l
Cleared ->(6)
Not cleared ->(5)

Step 6 End.
----End
Related Information
None
56-2

Issue 02 (2009-06-30)

Alarm Reference
57
ALM-0819 Insufficient Service Node

Resources
Description
I. Description
This alarm is generated when the utilization of the local service node resources exceeds the alarm
threshold. The resources consist of fiveitem nodes and tariff nodes corresponding to service
flows.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0819
Major
Fault
III. Parameters
Name
Meaning
Slot No.

service node generating this alarm is located.
CPU No.
Specifies the number of the CPU of the

service node generating this alarm.
Resource type
Specifies the resource type, which can be

fiveitem nodes and tariff nodes
Impact on System
l
When service node resources are insufficient, activation requests of new users are rejected
because their services and charging cannot be controlled.
When this alarm is generated, the currently activated users can continue to apply for service
node resources. If activated users fail to apply for node resources due to exhaustion of
service node resources, based on the configuration of the software parameter No. 57, the
Issue 02 (2009-06-30)

57-1

Alarm Reference
GGSN9811 determines to block services or allow services passing through without

charging.
l
After this alarm is generated, the system continues to check the unitization of service node
resources. When the utilization of service node resources is lower than the threshold, this
alarm is cleared.
Possible Causes
l
Excessive services are accessed by users.
The utilization of service node resources exceeds the alarm threshold
The alarm threshold is set to a too low value.
Handling Procedure
Step 1 Check the performance statistics item of service node resources to obtain the overall utilization
of service node resources and utilizations of different protocol types of service node resources.
Step 2 Check the aging times of different protocol types of service node resources.
Step 3 Shorten the aging times of service node resources.
Step 4 It is recommended to cut over partial user services to another CPU of the SPU.
Step 6 End.
----End
Related Information
None
57-2

Issue 02 (2009-06-30)

Alarm Reference
58
ALM-0820 Redirection Server

Unavailable
Description
I. Description
This alarm is generated when no server for the redirection IP farm (hereinafter referred to as
farm) configured on the GGSN is available.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0820
Critical
Fault
III. Parameters
Name
Meaning
Farm name
Specifies the farm name. This parameter

indicates whether the farm is normal. If the
farm is abnormal, it indicates that no server is
available.
Impact on System
All redirection services bound to this farm cannot be processed normally, and user packets to
be redirected are blocked.
Possible Causes
l
Issue 02 (2009-06-30)
The server-farm that corresponds to the virtual IP address configured in the captivation/
web-proxy action is not in the same VPN with the user.
58-1

Alarm Reference
No server is configured for the server-farm that corresponds to the virtual IP address
configured in the captivation/web-proxy action.
All the servers configured for the server-farm that corresponds to the virtual IP address
configured in the captivation/web-proxy action are down.
No heartbeat detection interface is configured and the interface attributes are modified for
the server-farm that corresponds to the virtual IP address configured in the captivation/webproxy action.
This alarm is cleared when the redirection rule is removed or an available server can be obtained
based on the virtual IP address in the rule.
Handling Procedure
Step 2 End.
----End
Related Information
None
58-2

Issue 02 (2009-06-30)

Alarm Reference
59
ALM-0821 LNS Group has no responding
Description
I. Description
This alarm occurs when the GGSN and the LNS are disconnected due to communication failure.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0821
Major
Fault
III. Parameters
Name
Meaning
Slot No.
No. of the slot where the alarm occurs.
CPU No.
No. of the CPU where the alarm occurs.
LNS1 address
IP address of LNS 1
LNS2 address
IP address of LNS 2
VPN
VPN instance name
Impact on System
The L2TP service cannot be performed after the GGSN and the LNS are disconnected.
Possible Causes
The communication link between the GGSN and the LNS is broken.
This alarm can be cleared if the redirection rule is deleted or a server is available based on the
virtual IP address in the rule.
Issue 02 (2009-06-30)

59-1

Alarm Reference
Handling Procedure
Step 1 Run display ip routing-table to check whether the route from the GGSN to the LNS is normal.
Check whether the router from the LNS to the GGSN is normal on the LNS.
l
Yes -> (2)
No -> (3)
Step 2 Check whether the LNS is normal.

l
Yes -> (5)
No -> (4)
Step 3 Run undo ip route-static and ip_route-static to modify the routing table on the GGSN. Modify
the routing table on the LNS by following the help of the LNS. Then, check whether the alarm
is cleared.
l
Cleared -> (6)
Not cleared -> (4)
Step 4 Contact the technical support personnel of the LNS.

Step 6 End.
----End
Related Information
None.
59-2

Issue 02 (2009-06-30)

Alarm Reference
60
ALM-0822 IP spoofing has arisen
Description
I. Description
This alarm occurs, when the number of the PDP contexts under IP spoofing attacks reaches a
predefined threshold.
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0822
Major
Fault
III. Parameters
Name
Meaning
Slot No.
No. of the slot where the alarm occurs.
CPU No.
Number of the CPU where the alarm occurs.
Impact on System
The IP spoofing packets are discarded.
Possible Causes
The PDP contexts of the GGSN are under IP spoofing attacks.
Handling Procedure
Step 2 End.
----End
Issue 02 (2009-06-30)

60-1

Alarm Reference
Related Information
None.
60-2

Issue 02 (2009-06-30)

Alarm Reference
61
ALM-0826 The redirection server has no

responding
Description
I. Description
The alarm occurs when the correct health checking and the redirection server, but there is no
response when checking the redirection server
II. Attribute
Alarm ID
Alarm Severity
Alarm type
0826
Major
Fault
III. Parameters
Name
Meaning
Ip-Farm name
Specifies the name of IP-farm.
Server IP
Specifies the IP address of the redirection

server.
Impact on System
The web proxy or captive portal service is disrupted.
Possible Causes
l
The routes between the GGSN and the redirection server are incorrect.
The redirection server fails.
Health check interface fails, the interface is not used to send or receive health check
messages.
Issue 02 (2009-06-30)

61-1

Alarm Reference
Handling Procedure
Step 1 Enter system-view, run ping -i interface to check the status of the redirection server. The interface
means health check interface.
l
Normal =>(9)
Abnormal =>(2)
Step 2 Enter system-view, run display interface to check the status of the health check interface.
l
UP =>(4)
DOWN =>(3)
Step 3 Check the status of physical link between the GGSN and the redirection server.
l
Normal =>(4)
Abnormal =>(6)
Step 4 Enter system-view, run display ip routing-table to check whether the route of the GGSN to the
redirection server is correct. On the redirection server, check whether the route of the redirection
server to the GGSN is correct
l
Correct =>(5)
Incorrect =>(7)
Step 5 Check whether the redirection server is normal.

l
Normal =>(9)
Abnormal =>(8)
Step 6 Replace the faulty network cable, and then check whether the alarm is cleared.
l
Cleared =>(10)
Not cleared =>(1)
Step 7 Clear the fault of route configurations. Run ip route-static andundo ip route-static to modify
the routing table of the GGSN. Modify the routing table of the redirection server according to
the online help of the redirection server. Then, check whether the alarm is cleared.
l
Cleared =>(10)
Not cleared =>(1)
Step 8 Contact Redirection Server Technical Support.

Step 10 End.
----End
Related Information
None
61-2

Issue 02 (2009-06-30)

Alarm Reference
62
ALM-0827 Disconnection Between

GGSN and PCRF
Description
The alarm occurs when the path between GGSN and PCRF is disconnected, it is cleared after
the path between GGSN and PCRF is connected.
Parameters
Name
Meaning
Slot No.
Specifies the slot number of the SPU.
CPU No.
Specifies the number of the CPU where the alarm occurs.
IP
Specifies the IP address of the PCRF
Impact on System
l
There is not effective on the IP-CAN session of the PCRF related, but the authentication
request will be failed,
If there is any other valid PCRF in this PCRF group, the created IP-CAN session can access
normally; Or the accessing of the IP-CAN will be denied.
Possible Causes
l
The configuration of the PCRF is wrong;
The CPU of the configured Gx interface on the SPU is faulty.
The path between the GGSN and the PCRF is disconnected.
The PCRF is faulty.
Handling Procedure
Step 1 Check whether the PCRF is normal.
l
Issue 02 (2009-06-30)
Yes -> (9)

62-1

l

Alarm Reference
No -> (2)
Step 2 Check whether the path between the GGSN and PCRF is connected.
l
Yes -> (5)
No -> (3)
Step 3 Check whether the configuration of the PCRF is right using the display pcrf command.
l
Yes -> (5)
No -> (4)
Step 4 Delete the PCRF using the undo pcrf command, configure the PCRF using the pcrf, then check
whether the alarm is recovered.
l
Yes -> (9)
No -> (6)
Step 5 Check whether the path between the GGNS and the PCRF is disconnected after replacing the
network cable.
l
Yes -> (5)
No -> (3)
Step 6 Check whether the CPU of the SPU is normal.

l
Yes -> (8)
NO -> (3)
Step 7 check whether the alarm is recovered.

l
Yes -> (10)
No -> (8)

Step 9 Contact technical support engineer of the PCRF.
Step 10 End.
----End
Related Information
None
62-2

Issue 02 (2009-06-30)

Alarm Reference
63
63 ALM-0828 Disconnection Between GGSN and Reporting

Server
ALM-0828 Disconnection Between

GGSN and Reporting Server
Description
The alarm occurs when the path between the one of the CPUs on the GGSN and reporting server
is disconnected.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0828
Major
Fault
Parameters
Name
Meaning
Subrack No. Specifies the number of the subrack where the board generating the alarm is
located.
Slot No.
Specifies the number of the slot where the board generating the alarm is located.
CPU No.
Specifies the number of the CPU that manages the reporting server.
Impact on System
l
This alarm is stand for that the reporting server is disconnected with the GGSN, the GGSN
can not reporting and lose the report.
There is not effect on the user service.
Possible Causes
l
The IP address of the reporting server configured on the GGSN is error.
The path between the Gi interface on the GGSN and the reporting server is disconnected.
The reporting server is disable.
Issue 02 (2009-06-30)

63-1
63 ALM-0828 Disconnection Between GGSN and Reporting

Server

Alarm Reference
Handling Procedure
Step 1 Check whether the IP address of the reporting server configured on the GGSN is right.
l
Yes -> (3)
No -> (3)
Step 2 Check whether the alarm is recovered after configuring the IP address of the reporting server on
the GGSN.
l
Yes -> (8)
No -> (3)
Step 3 Check whether the path between the Gi interface on the GGSN and the reporting server is
connected using the ping command.
l
Yes -> (5)
No -> (2)
Step 4 Check whether the alarm is recovered after configuring the routing from Gi interface to the
reporting server.
l
Yes -> (8)
No -> (3)
Step 5 Check whether the reporting server is enable.

l
Yes -> (7)
No -> (6)
Step 6 Check whether the alarm is recovered after enable the reporting server.
l
Yes -> (8)
No -> (7)

Step 8 End.
----End
Related Information
None
63-2

Issue 02 (2009-06-30)

Alarm Reference
64
ALM-0829 Update the rule-library of

SIG-CBB Failed
Description
The alarm occurs when the updating the rule-library of SIG-CBB is failed.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0829
Major
Event
Parameters
Name
Meaning
Slot No.
Specifies the number of the slot where the DMPU card is located.
CPU No.
Specifies the number of the CPU where the SIG-CBB is located.
Abnormal Type
Specifies the type of the alarm occurred in the SIG-CBB.
Impact on System
l
After the updating the rule-library of SIG-CBB is failed, the GGSN will run the lasted
version succeed upload. It is not effective on the identifying of the GGSN.
The protocol and the matching rule defined in the new rule-library are invalid.
If the updating is failed result on the engine of the SIG is failed to upload, the identifying
function of the SIG-CBB is invalid.
Possible Causes
l
The file name of the rule-library or the format is error.
The rule-library is not existed.
The version remarked on the file is not consistent with the version in the file.
The license updating is expires.
Issue 02 (2009-06-30)

64-1

Alarm Reference
The engine of the SIG is failed to upload when the board is restarted.
Handling Procedure
Step 1 Check whether both the "Sam-1.0.0.***.rul" and the "Sam-1.0.0.***.xml" files is existed in the
path:hd1:/service/ (*** is the version number of the rule-library need to update)
l
Yes -> (4)
No -> (2)
Step 2 Upload the "Sam-1.0.0.***.rul" and the "Sam-1.0.0.***.xml" files in the path: hd1:/service/ on
the GGSN -> (3)
Step 3 Check whether the alarm is recovered using the update_signature-database command.
l
Yes -> (5)
No -> (4)
Step 4 Query the current version information using the display signature-database command, and
Contact Huawei Technical Support
Step 5 End.
Step 7 End.
----End
Related Information
None
64-2

Issue 02 (2009-06-30)

Alarm Reference
65
ALM-0830 DPI service unavailable
Description
The alarm occurs when all the L7 parse is failed because on the DMPU cards configured on the
SPU are invalid.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0830
Critical
Fault
Parameters
Name
Meaning
Slot No.
Specifies the number of the slot where the board generating the alarm is located.
CPU No. Specifies the number of the CPU where the charging is abnormal.
Impact on System
l
L7 parse is failed, the matching rules are is disable. All the service controlling and the
charging is based on the L3/L4 layer, the content-based charging on the l7 is error.
It is effect on that the reporting server can not report the protocol information.
Possible Causes
l
The DMPU card is configured, but it is not inserted.
The DMPU card is not in its position.
The hardware of the DMPU card is faulty.
The GGSN processing is abnormal.
Handling Procedure
Step 1 Check whether the work mode is subboard mode using the display subboard command.
Issue 02 (2009-06-30)

65-1

l
Yes -> (2)
No -> (7)

Alarm Reference
Step 2 Check whether the subboard mode is configured on the SPU using the display subboard
command.
l
Yes -> (3)
No -> Delete the subboard mode using the undo subboard command, and then restart the
SPU where the alarm occurred.
Step 3 Check whether the CPU2 and the CPU3 are present using the display device slotnum command.
l
Yes -> (4)
No -> The subboard is not in its position. Insert the subboard again to keep the connection
is normal.
Step 4 Check whether the status of the CPU2 and CPU3 is Registered using the display device slotnum
command.
l
Yes -> (5)
No -> Wait for 5 minutes.
Step 5 Check whether the alarm is recovered.

l
Yes -> (8)
No -> (6)
Step 6 Check whether there is any valid subboard on the SPU using the display device slotnum
command.
l
Yes -> Switch over the active/standby SPU to ensure the L7 parse is enable.
No -> (7)

Step 8 End.
----End
Related Information
None
65-2

Issue 02 (2009-06-30)

Alarm Reference
66
ALM-0835 Traffic control alarm
Description
The alarm occurs when system reaches volume threshold.
Attribute
Alarm ID
Alarm Severity
Alarm Type
0835
Major
Fault
Parameters
Name
Meaning
Slot No. Specifies the number of the slot where the board generating the alarm is located.
Impact on System
l
The SPU is abnormal.
When the SPU reaches volume threshold, the system will discards the data packets in some
probability
Possible Causes
l
There are a lot of users accessed, the system is busy.
The M2000 downloads data from GGSN hard disk by FTP server.
Handling Procedure
Step 1 Check whether the alarm is cleared after stopping the FTP service for M2000.
l
Yes=>(4)
No=>(2)
Step 2 Check whether the alarm is cleared using the alarm threshold command to enhance the alarm
threshold of the CPU over load.
Issue 02 (2009-06-30)

66-1

Alarm Reference

l
Yes=>(4)
No=>(3)

Step 4 End.
----End
Related Information
None
66-2

Issue 02 (2009-06-30)

Alarm Reference (V900R007C02 02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alarm Reference (V900R007C02 02)

Uploaded by

Copyright:

Available Formats

HUAWEI GGSN9811 Gateway GPRS Support Node

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

24 ALM-0630 -48V input alarm.................................................................................................24-1

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

54 ALM-0816 CG redirection failed.........................................................................................54-1

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

About This Document

About This Document

Network monitoring engineer

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

About This Document

4 ALM-0503 Communication channel is faulty

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

About This Document

28 ALM-0634 CPU Overload Alarm

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

About This Document

52 ALM-0814 The communications path to CG is down alarm

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

Items (keywords or arguments) in brackets [ ] are optional.

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

About This Document

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

HUAWEI GGSN9811 Gateway GPRS Support Node

1 ALM-0500 Physical entity is removed

ALM-0500 Physical entity is removed

Board type and slot No. or CPU No.

Specifies the type of the board and the No. of

Huawei Proprietary and Confidential

1 ALM-0500 Physical entity is removed