Table of Contents
Chapter 1 Alarms.................................................................................................................. 1-1
1.1 Introduction................................................................................................................ 1-1
1.2 Alarm Message Content.............................................................................................. 1-1
1.2.1 Alarm Message Format..................................................................................... 1-1
1.2.2 Alarm Message Description............................................................................... 1-3
1.2.3 Alarm Level...................................................................................................... 1-3
1.2.4 Alarm Modules................................................................................................. 1-4
1.2.5 Alarm Parameters............................................................................................. 1-4
1.2.6 Function Types................................................................................................. 1-4
Chapter 2 Alarm Messages................................................................................................... 2-1
2.1 802.1x....................................................................................................................... 2-1
2.1.1 8021X/2/PRXYCHKED: 1.3.6.1.4.1.2011.5.22.1.0.1.............................................. 2-1
2.2 BGP.......................................................................................................................... 2-2
2.2.1 bgp/1/Trap4: 1.3.6.1.2.1.15.7.1.......................................................................... 2-2
2.2.2 bgp/1/Trap4: 1.3.6.1.2.1.15.7.2.......................................................................... 2-2
2.3 LDP.......................................................................................................................... 2-3
2.3.1 LDP/5/TRAP: 1.3.6.1.4.1.2011.5.12.2.2.0.15....................................................... 2-3
2.3.2 LDP/5/TRAP: 1.3.6.1.4.1.2011.5.12.2.2.0.16....................................................... 2-4
2.4 LSPM........................................................................................................................ 2-5
2.4.1 LSPM/5/TRAP: 1.3.6.1.2.1.10.166.2.0.1............................................................. 2-5
2.4.2 LSPM/5/TRAP: 1.3.6.1.2.1.10.166.2.0.2............................................................. 2-5
2.5 OSPF........................................................................................................................ 2-6
2.5.1 OSPF/1/ Trap1: 1.3.6.1.2.1.14.16.2.1................................................................. 2-6
2.5.2 OSPF/1/Trap2: 1.3.6.1.2.1.14.16.2.2.................................................................. 2-7
2.5.3 OSPF/1/ Trap3: 1.3.6.1.2.1.14.16.2.3................................................................. 2-8
2.5.4 OSPF/1/ Trap4: 1.3.6.1.2.1.14.16.2.4................................................................. 2-9
2.5.5 OSPF/1/ Trap5: 1.3.6.1.2.1.14.16.2.5............................................................... 2-10
2.5.6 OSPF/1/ Trap6: 1.3.6.1.2.1.14.16.2.6............................................................... 2-11
2.5.7 OSPF/1/ Trap7: 1.3.6.1.2.1.14.16.2.7............................................................... 2-11
2.5.8 OSPF/1/ Trap8: 1.3.6.1.2.1.14.16.2.8............................................................... 2-12
2.5.9 OSPF/1/ Trap9: 1.3.6.1.2.1.14.16.2.9............................................................... 2-13
2.5.10 OSPF/1/ Trap10: 1.3.6.1.2.1.14.16.2.10.......................................................... 2-14
2.5.11 OSPF/1/ Trap11: 1.3.6.1.2.1.14.16.2.11.......................................................... 2-15
2.5.12 OSPF/1/ Trap12: 1.3.6.1.2.1.14.16.2.12.......................................................... 2-16
2.5.13 OSPF/1/ Trap13: 1.3.6.1.2.1.14.16.2.13.......................................................... 2-17
2.5.14 OSPF/1/ Trap14: 1.3.6.1.2.1.14.16.2.14.......................................................... 2-18
2.5.15 OSPF/1/ Trap15: 1.3.6.1.2.1.14.16.2.15.......................................................... 2-19
2.5.16 OSPF/1/ Trap16: 1.3.6.1.2.1.14.16.2.16.......................................................... 2-19
2.6 MSTP...................................................................................................................... 2-20
2.6.1 MSTP/2/ ROOT: 1.3.6.1.4.1.2011.2.23.1.14.0.3................................................. 2-20
2.6.2 MSTP/2/ RGSUP: 1.3.6.1.4.1.2011.2.23.1.14.0.4.............................................. 2-21
2.6.3 MSTP/2/ IVBPDU: 1.3.6.1.4.1.2011.2.23.1.14.0.5.............................................. 2-22
2.6.4 MSTP/2/ LGEXP: 1.3.6.1.4.1.2011.2.23.1.14.0.6............................................... 2-23
2.7 POS........................................................................................................................ 2-23
2.7.1 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.5.................................................... 2-23
2.7.2 POS/2/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.2.................................................... 2-24
2.7.3 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.3.................................................... 2-24
2.7.4 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.6.................................................... 2-25
2.7.5 POS/2/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.1.................................................... 2-25
2.7.6 POS/2/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.8.................................................... 2-26
2.7.7 POS/2/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.4.................................................... 2-27
2.7.8 POS/2/ TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.7................................................... 2-27
2.7.9 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.9.................................................... 2-28
2.7.10 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.10................................................. 2-28
2.7.11 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.11................................................. 2-29
2.7.12 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.12................................................. 2-29
2.7.13 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.13................................................. 2-30
2.8 VRRP...................................................................................................................... 2-30
2.8.1 vrrp/5/TrapBecomeNewMaster: 1.3.6.1.2.1.68.0.1.............................................. 2-30
2.8.2 vrrp/4/ TrapAuthFailed: 1.3.6.1.2.1.68.0.2.......................................................... 2-31
2.9 DEV........................................................................................................................ 2-32
2.9.1 DEV/2/POWER STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.1... 2-32
2.9.2 DEV/2/POWER STATE CHANGE TO NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.2... 2-32
2.9.3 DEV/2/POWER REMOVED: 1.3.6.1.4.1.2011.2.23.1.12.1.5............................... 2-33
2.9.4 DEV/2/FAN STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.6......... 2-34
2.9.5 DEV/2/FAN STATE CHANGE TO NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.7......... 2-34
2.9.6 DEV/2/BOARD REMOVED: 1.3.6.1.4.1.2011.2.23.1.12.1.8................................ 2-35
2.9.7 DEV/2/BOARD INSERTED: 1.3.6.1.4.1.2011.2.23.1.12.1.9................................. 2-36
2.9.8 DEV/2/BOARD STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.10.. 2-36
2.9.9 DEV/2/BOARD STATE CHANGE TO NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.11.. 2-37
2.9.10 DEV/2/BOARD TEMPERATURE LOWER: 1.3.6.1.4.1.2011.2.23.1.12.1.14........ 2-38
2.9.11 DEV/2/BOARD TEMPERATURE NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.15...... 2-38
2.9.12 DEV/2/BOARD TEMPERATURE UPPER 1.3.6.1.4.1.2011.2.23.1.12.1.16.......... 2-39
2.9.13 DEV/2/BOARD TEMPERATURE NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.17...... 2-40
2.9.14 DEV/2/BOARD REQUEST LOADING: 1.3.6.1.4.1.2011.2.23.1.12.1.18.............. 2-40
2.9.15 DEV/2/LOAD FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.19.................................. 2-41
2.9.16 DEV/2/LOAD FINISHED: 1.3.6.1.4.1.2011.2.23.1.12.1.20................................. 2-42
2.9.17 DEV/2/POWER INSERT: 1.3.6.1.4.1.2011.2.23.1.12.1.23................................. 2-42
2.9.18 DEV/2/PORT POE POWER ON: 1.3.6.1.2.1.105.0.1........................................ 2-43
2.9.19 DEV/2/PSE POWER USAGE OVER THRESHOLD: 1.3.6.1.2.1.105.0.1............ 2-43
2.9.20 DEV/2/PSE POWER USAGE BELOW THRESHOLD: 1.3.6.1.2.1.105.0.3......... 2-44
2.9.21 DEV/2/PD PULL: 1.3.6.1.4.1.2011.10.2.14.6.1................................................. 2-45
2.9.22 DEV/2/PD PULL: 1.3.6.1.4.1.2011.10.2.14.6.1................................................. 2-45
2.10 ENTITY.................................................................................................................. 2-46
2.10.1 ENTITY/5/CONFIG CHANGE: 1.3.6.1.2.1.47.2.0.1........................................... 2-46
2.11 HWCM................................................................................................................... 2-47
2.11.1 HWCM/5/TRAP:1.3.6.1.4.1.2011.10.2.4.2.1..................................................... 2-47
2.11.2 HWCM/5/CFGCOPY: 1.3.6.1.4.1.2011.10.2.4.2.2............................................ 2-48
2.12 L2INF..................................................................................................................... 2-49
2.12.1 L2INF/2/ PORT LINK STATUS CHANGE: 1.3.6.1.6.3.1.1.5.4............................. 2-49
2.12.2 L2INF/2/PORT LINK STATUS CHANGE: 1.3.6.1.6.3.1.1.5.3.............................. 2-49
2.13 MIX........................................................................................................................ 2-50
2.13.1 MIX/2/SLAVE SWITCH OVER: 1.3.6.1.4.1.2011.2.23.1.17.10.1......................... 2-50
2.14 RMON................................................................................................................... 2-51
2.14.1 rmon/2/ ALARMUP: 1.3.6.1.2.1.16.0.1............................................................ 2-51
2.14.2 rmon/2/ ALARMFALL: 1.3.6.1.2.1.16.0.2......................................................... 2-51
2.14.3 rmon/2/ RISING: 1.3.6.1.4.1.2011.1.3.4.0.1..................................................... 2-52
2.14.4 rmon/2/FALLING: 1.3.6.1.4.1.2011.1.3.4.0.2.................................................... 2-53
2.15 VFS....................................................................................................................... 2-54
2.15.1 VFS/5/TRAP: 1.3.6.1.4.1.2011.10.2.5.1.3.1..................................................... 2-54
2.16 SNMP-V2............................................................................................................... 2-55
2.16.1 ColdStart: 1.3.6.1.6.3.1.1.5.1......................................................................... 2-55
2.16.2 WarmStart: 1.3.6.1.6.3.1.1.5.2....................................................................... 2-55
2.16.3 AuthenticationFailure: 1.3.6.1.6.3.1.1.5.5........................................................ 2-56
When a device fails or the system does not function somehow, the system generates an alarm based on the fault type and the faulty module, and saves the alarm in the alarm buffer of the device. At the same time, the system generates a log. You can determine the size of the alarm buffer as actually needed. If the Network Management System (NMS) is present, the alarm is sent to the NMS through the Simple Network Management Protocol (SNMP). The system can also sense the environment. When the device works beyond its limits, the system generates an alarm.
The equipment enables you to view alarm messages on the terminal. Alarm messages are displayed on the terminal interface, and saved in the buffer. You can also view all the alarms saved in the buffer using a command on the device.
Alarm messages fall into the following three categories in terms of nature:
l Failure alarms: Alarms generated due to the failure of hardware or some key functions;
l Recovery alarms: Alarms generated when the faulty device or abnormal functions are recovered;
l Event alarms: Warnings or alarms generated when the fault and the recovery messages do not match.
This section includes the following contents:
l Alarm Message Format
l Alarm Message Description
l Alarm Level
l Alarm Modules
l Alarm Parameters
An alarm starts with a “#” and takes the following format.
Figure 1-1 Alarm output format
The fields in the format are described as follows.
l TimeStamp
It specifies the time when the alarm is generated. It is in the format of “Mmm dd hh:mm:ss yyyy”.
“Mmm” stands for the month in English, that is, Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nove, and Dec.
“dd” is the date. If the value is smaller than 10, fill in as “space + date”, such as “ 7”.
“hh:mm:ss” is the local time. “hh” uses the 24-hour system, with a value ranging from 00 to 23. The values for both "mm" and “ss” range from 00 to 59.
“yyyy” specifies the year.
TimeStamp is separated from HostName by a space.
l HostName
It is the system name of the host, “H3C” by default.
HostName is separated from ModuleName by a space.
l ModuleName
It specifies the module that generates the alarm. ModuleName is separated from Alarm level by a slash (/).
l Alarm Level
Alarms fall into four Alarm level ranks, ranging from 1 to 4.
Alarm level is separated from Brief by a slash (/).
l Brief
It contains a short term to brief the alarm.
Brief is separated from Description by a colon (:).
l Description
It contains the character string sent by the module to the information center to detail the specific content of this alarm.
I. Basic information
See the following table.
Table 1-1 List of basic parameters in an alarm message
|
Item |
Description |
|
Alarm message |
Character string of alarm message displayed on the device. |
|
Alarm OID |
Object ID defined in the MIB file. |
|
Alarm meaning |
The meaning of the alarm message. |
|
Alarm type |
The nature of the alarm message. |
|
Alarm level |
Impacts of the failure upon the service. |
|
Alarm parameter |
Paramters contained in the alarm message used for alarm location and translation. |
|
Function type |
It specifies the function domain to which the fault belongs. |
II. Trigger action
It describes probable causes of the alarm message, and locates the exact reasons.
III. Recommended action
It provides the advice for further diagnosis and recovery based on the cause of the alarm message.
IV. Related alarm message
It describes the related alarm message to locate the root cause of the alarm message and reasons related alarm message occurs.
The alarm level identifies the severity of an alarm message. It has the following four ranks with severity in a descending sequence: Critical, Major, Minor, and Warning. For descriptions, see the following table.
Table 1-2 Alarm level description
|
Alarm level |
Definition |
Description |
|
1 |
Critical |
Such failure affects the services provided by the system and requires action at once. For example, when certain device or resource is completely unavailable, it requires recovery at once. Even if the failure occurs outside the working time, immediate actions are required. |
|
2 |
Major |
Such failure affects the quality of the service, and requires urgent recovery. For example, when the quality of certain device or resource declines, it must be restored so that the full capatility is recovered. In the case of occurrence in working hours, immediate actions are required. |
|
3 |
Minor |
Such failure does not affect the quality of the service at the moment. But to avoid more severe failures, processing at proper time or further observation is required. |
|
4 |
Warning |
Such failure indicates that there may be potential errors that affect the service. Related measures vary with the errors. |
The following table shows the abbreviations of alarm modules.
Table 1-3 Descriptions of alarm module abbreviations
|
Alarm Module |
Description |
|
802.1X |
802.1X protocol module |
|
BGP |
BGP module |
|
LDP |
Label Distribution Protocol module |
|
LSPM |
LSP Management module |
|
OSPF |
OSPF module |
|
MSTP |
MSTP module |
|
POS |
POS management module |
|
VRRP |
VRRP module |
|
DEV |
Device management module |
|
ENTITY |
Entity MIB module |
|
HWCM |
Configuration Management module |
|
L2INF |
Layer 2 Interface management module |
|
MIX |
Slave Swtichover management module |
|
RMON |
RMON module |
|
VFS |
File management module |
|
SNMP-V2 |
SNMP-V2 module |
The following table describes the variables in alarm parameters.
Table 1-4 Explanations of alarm parameters
|
Alarm parameter |
Description |
|
|
|
The following table describes the function types.
Table 1-5 Explanations of function types
|
Function type |
Description |
|
Communication alarm |
Such alarms are related to the handling process of message transmission, including alarms generated in communication failures between NEs, NE and OS, or OSs. |
|
Service quality alarm |
Such alarms result from reduction of the service quality, including alarms generated in congestion, performance reduction, high resource occupation rate, and bandwidth reduction. |
|
Alarm for error handling |
Such alarms result from software or handling process errors, including alarms generated in service processing such as software error, memory overflow, unmatched versions, and abnormal interruption of programs. |
|
Environmental alarm |
Such alarms result from problems related to the location of the device, including alarms generated when the temperature, humidity and ventilation in the environment are abnormal. |
|
Equipment alarm |
Such alarms result from faults of physical resources, including alarms generated by devices such as the power, fan, processor, clock, and input or output interface. |
I. Basic information
|
Item |
Description |
|
Alarm message |
The smart proxy-checker report! |
|
Alarm OID |
1.3.6.1.4.1.2011.5.22.1.0.1 |
|
Alarm name |
supplicantproxycheck |
|
Description |
None |
|
Meaning |
It is detected that the user connects to the Internet through an agent. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID
$2: VLAN ID
$3: Port Name
$4: MAC Address
$5: IP Address
$6: User Name |
|
Function type |
Communication alarm |
II. Trigger action
This alarm message has the following trigger actions:
l The user connects to the Internet through an Agent;
l There are multiple network cards on the device;
l The user connects to the Internet through the IE agent.
III. Recommended action
Based on the causes of the alarm message, the suggestions for recovery include:
l Notify the user to eliminate the agent
IV. Related alarm message
None
I. Basic information
|
Item |
Description |
|
Alarm message |
connection established
[oid] BgpPeerRemoteAddr = [ipaddr]
BgpPeerLastError = [octet]
BgpPeerState = [integer] |
|
Alarm OID |
1.3.6.1.2.1.15.7.1 |
|
Alarm name |
bgpEstablished |
|
Description |
The BGP Established event is generated when the BGP FSM enters the ESTABLISHED state. |
|
Meaning |
Establishment of adjacency with BGP |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID
$2: IP address of the peer neighbor
$3: Record of last break of adjacency
$4: Status of the current neighbor |
|
Function type |
Service quality alarm |
II. Trigger action
Adjacency with BGP is set up successfully.
III. Recommended action
This alarm informs the user of the successful setup of adjacency with BGP. The user does not need to clear the alarm.
IV. Related alarm message
2.2.2 bgp/1/Trap4: 1.3.6.1.2.1.15.7.2
I. Basic information
|
Item |
Description |
|
Alarm message |
BGP FSM moves from a higher numbered state to a lower numbered state [oid] BgpPeerRemoteAddr = [ipaddr]
BgpPeerLastError = [octet]
BgpPeerState = [integer] |
|
Alarm OID |
1.3.6.1.2.1.15.7.2 |
|
Alarm name |
bgpBackwardTransition |
|
Description |
The BGPBackwardTransition Event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. |
|
Meaning |
The BGP FSM moves from the higher numbered state to the lower numbered state. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID
$2: IP address of the peer neighbor
$3: Record of last break of adjacency
$4: State of the current neighbor |
|
Function type |
Service quality alarm |
II. Trigger action
This alarm message is sent when the BGP neighbor state changes from the higher numbered state to the lower numbered state.
State relationship:
IDLE(1)<CONNECT(2)<ACTIVE(3)<OPENSENT(4)<OPENCONFIRM(5)<ESTABLISHED(6)
III. Recommended action
This alarm message informs the user of the change to the BGP adjacency. If it is caused by the link state, check the links.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
bgpEstablished 1.3.6.1.2.1.15.7.1 |
|
Relationship |
bgpEstablished 1.3.6.1.2.1.15.7.1 |
|
Relation degree |
Prossible |
|
Cause |
After the BGP adjacency is set up, when BGP changes to the lower numbered state, “Related alarm messagebgpBackwardTransition: 1.3.6.1.2.1.15.7.2” appears. |
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LDP Session [integer] [integer] [integer] [integer] [octet] Changes to Up |
|
Alarm OID |
1.3.6.1.4.1.2011.5.12.2.2.0.15 |
|
Alarm name |
hwMplsLdpSessionUpEventFailure |
|
Description |
Generation of this trap occurs when the value of “hwMplsLdpSessionState” enters the “operational (5)” state. |
|
Meaning |
The LDP session is set up. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID
$2: LDP case ID, 0 at the moment
$3: Interface index, 0 at the moment
$4: Peer index, 0 at the moment
$5: Session index, 0 at the moment
$6: Session ID, LSR ID of the Peer |
|
Function type |
Communication alarm |
II. Trigger action
This alarm is triggered because:
l The LDP session is set up.
III. Recommended action
None
IV. Related alarm message
LDP/5/TRAP: 1.3.6.1.4.1.2011.5.12.2.2.0.16
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LDP Session [integer] [integer] [integer] [integer] [octet] Changes to Down |
|
Alarm OID |
1.3.6.1.4.1.2011.5.12.2.2.0.16 |
|
Alarm name |
hwMplsLdpSessionDownEventFailure |
|
Description |
Generation of this trap occurs when the value of “hwMplsLdpSessionState” leaves the “operational (5)” state. |
|
Meaning |
The LDP session is disconnected. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID
$2: LDP case ID, 0 at the moment
$3: Interface index, 0 at the moment
$4: Peer index, 0 at the moment
$5: Session index, 0 at the moment
$6: Session ID, LSR ID of the Peer |
|
Function type |
Communication alarm |
II. Trigger action
This alarm has the following trigger actions:
l The session setup interface fails;
l Related configurations have been deleted. For example, the LDP or MPLS is disabled.
III. Recommended action
Based on the cause, the recommended actions include:
l If the session setup interface fails, recover the session by finding and clearing the interface fault;
l If related configurations have been deleted, restore related configurations to re-set up the LSP.
IV. Related alarm message
LDP/5/TRAP: 1.3.6.1.4.1.2011.5.12.2.2.0.15
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LSP [integer] Changes to Up |
|
|
