Login
| Title | Size | Downloads |
|---|---|---|
| 99-H3C S9500 Trap Message(V1.00, release 1250 or later versions)-20061011-E.pdf | 264 KB |
- Table of Contents
- Related Documents
-
- H3C S9500 Series Routing Switches SecBlade FW VPN Cards Operation Manual(V1.03)
- H3C S9500 SLM(V1.00release 1250 or later versions)
- H3C S9500 Series Routing Switches Compliance and Safety Manual(V1.04)
- H3C S9500 Series Routing Switches Installation Manual-(V1.01)
- H3C S9500 LSB1SRP1N4 Card Manual(V1.01)
- H3C PoE DIMM Module Installation Guide(V1.02)
Table of Contents
Chapter 1 Alarms.................................................................................................................. 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
Chapter 1 Alarms
1.1 Introduction
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.
1.2 Alarm Message Content
This section includes the following contents:
l Alarm Message Format
l Alarm Message Description
l Alarm Level
l Alarm Modules
l Alarm Parameters
1.2.1 Alarm Message Format
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.
1.2.2 Alarm Message Description
I. Basic information
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
1.2.3 Alarm Level
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. |
1.2.4 Alarm Modules
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 |
1.2.5 Alarm Parameters
The following table describes the variables in alarm parameters.
Table 1-4 Explanations of alarm parameters
|
Alarm parameter |
Description |
|
|
|
1.2.6 Function Types
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. |
Chapter 2 Alarm Messages
2.1 802.1x
2.1.1 8021X/2/PRXYCHKED: 1.3.6.1.4.1.2011.5.22.1.0.1
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
2.2 BGP
2.2.1 bgp/1/Trap4: 1.3.6.1.2.1.15.7.1
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
|
Item |
Description |
|
Related alarm |
|
|
Relationship |
|
|
Relation degree |
Prossible |
|
Cause |
After the BGP adjacency is set up, when the BGP status changes toward lower status, “Related alarm messagebgpBackwardTransition: 1.3.6.1.2.1.15.7.2” appears. |
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 |
|
|
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. |
2.3 LDP
2.3.1 LDP/5/TRAP: 1.3.6.1.4.1.2011.5.12.2.2.0.15
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
2.3.2 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
2.4 LSPM
2.4.1 LSPM/5/TRAP: 1.3.6.1.2.1.10.166.2.0.1
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LSP [integer] Changes to Up |
|
Alarm OID |
1.3.6.1.2.1.10.166.2.0.1 |
|
Alarm name |
mplsXCUp |
|
Description |
This notification is generated when a mplsXCOperStatus object for one of the configured cross-connect entries is about to leave the down state and transition into some other state (but not into the notPresent state). This other state is indicated by the included value of mplsXCOperStatus. |
|
Meaning |
The LSP is set up. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: LSP index |
|
Function type |
Communication alarm |
II. Trigger action
This alarm has the following trigger action:
l The LSP is set up.
III. Recommended action
None
IV. Related alarm message
LSPM/5/TRAP: 1.3.6.1.2.1.10.166.2.0.2
2.4.2 LSPM/5/TRAP: 1.3.6.1.2.1.10.166.2.0.2
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LSP [integer] Changes to Down |
|
Alarm OID |
1.3.6.1.2.1.10.166.2.0.2 |
|
Alarm name |
mplsXCDown |
|
Description |
This notification is generated when an mplsXCOperStatus object for one of the configured cross-connect entries is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of mplsXCOperStatus. |
|
Meaning |
The LSP is removed. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: LSP index |
|
Function type |
Communication alarm |
II. Trigger action
This alarm has the following trigger actions:
l The LDP session is disconnected;
l The LSP setup policy is changed;
l The route is changed. The route related to this LSP is removed or changed in the next jump;
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 LDP session is disconnected, locate the cause by viewing the link state and related configurations, and recover the session;
l If the LSP setup policy is changed, restore the policy by using the lsp-trigger command in the MPLS view;
l If the route is changed, restore the route to re-set up the LSP;
l If related configurations have been deleted, restore related configurations to re-set up the LSP.
IV. Related alarm message
LSPM/5/TRAP: 1.3.6.1.2.1.10.166.2.0.1
2.5 OSPF
2.5.1 OSPF/1/ Trap1: 1.3.6.1.2.1.14.16.2.1
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF virtual link state changed [oid] VirIfAreaId = [ipaddr] VirIfNbrId = [ipaddr] RouterId = [ipaddr] VirIfState = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.1 |
|
Alarm name |
ospfVirtIfStateChange |
|
Description |
An ospfIfStateChange trap signifies that there has been a change in the state of an OSPF virtual interface. This trap should be generated when the link state regresses (e.g., goes from Point-to-Point to Down) or progresses to a terminal state (i.e., Point-to-Point). |
|
Meaning |
The state of the link on an OSPF virtual interface changes. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1:Alarm OID $2: Area ID of the virtual interface $3: Neighbor router of the virtual interface $4: Local router $5: Virtual link state |
|
Function type |
Service quality alarm |
II. Trigger action
Possible causes of the state change of the link on an OSPF virtual interface include:
Normal state change. For example, the OSPF virtual interface serves as the Designated Router (DR);
The link state on an interface changes. For example, the link is set to Down.
III. Recommended action
If the alarm is caused by an link state change on the interface, find the cause of the change: if the link state is changed to Down through the command line, recover the state through the command Undo Shutdown on this interface; if the hardware on the interface fails, change the faulty hardware; if the peer interface fails, clear the fault.
IV. Related alarm message
None
2.5.2 OSPF/1/Trap2: 1.3.6.1.2.1.14.16.2.2
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF neighbour state changed [oid] NbrIpAddress = [ipaddr] NbrAddrLessIndex = [integer] RouterId = [ipaddr] NbrRouterId = [ipaddr] NbrState = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.2 |
|
Alarm name |
ospfNbrStateChange |
|
Description |
An ospfNbrStateChange trap signifies that there has been a change in the state of a non-virtual OSPF neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., 2-Way or Full). When a neighbor transitions from or to Full on non-broadcast multi-access and broadcast networks, the trap should be gen-erated by the designated router. A designated router transitioning to Down will be noted by ospfIfStateChange. |
|
Meaning |
The state of an OSPF neighbor changes. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: IP address of the neighbor $3: No address interface index in the neighbor $4: Local router $5: Neighbor router $6: Neighbor state |
|
Function type |
Service quality alarm |
II. Trigger action
Possible causes of the state change of an OSPF neighbor include:
The OSPF neighbor state changes from the lower numberd state to the higher numbered state, that is, normal setup of adjacency;
The OSPF neighbor state changes from the higher numbered state to the lower numbered state, that is, abnormal adjacency.
III. Recommended action
No alarm recovery is needed when the OSPF adjacency is set up normally;
When the OSPF neighbor changes from the higher numbered state to the lower numbered state, the user should check for abnormal link state. If there is no abnormal link state, check whether the peer neighbor normally sends the Hello packet.
IV. Related alarm message
None
2.5.3 OSPF/1/ Trap3: 1.3.6.1.2.1.14.16.2.3
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF virtual neighbour state changed [oid] VirNbrAreaId = [ipaddr] VirNbrRtrId = [ipaddr] RouterId = [ipaddr] VirNbrState = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.3 |
|
Alarm name |
ospfVirtNbrStateChange |
|
Description |
An ospfIfStateChange trap signifies that there has been a change in the state of an OSPF vir-tual neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., Full). |
|
Meaning |
The state of an OSPF virtual neighbor changes. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: Area ID of the virtual link $3: Neighbor router of the virtual link $4: Local router $5: Neighbor state of the virtual link |
|
Function type |
Service quality alarm |
II. Trigger action
Possible causes of the change to the state of an OSPF virtual neighbor include:
The OSPF neighbor state changes from the lower numbered state to the higher numbered state, that is, normal setup of adjacency;
The OSPF neighbor state changes from the higher numbered state to the lower numbered state, that is, abnormal setup of adjacency.
III. Recommended action
No alarm recovery is needed when the OSPF adjacency is set up normally;
When the OSPF neighbor changes from the higher numbered state to the lower numbered state, the user should check for abnormal link state. If there is no abnormal link state, check further whether the peer neighbor normally sends the report.
IV. Related alarm message
None
2.5.4 OSPF/1/ Trap4: 1.3.6.1.2.1.14.16.2.4
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF interface configuration error IfIpAddress = [ipaddr] IfAddrLessIndex = [integer] RouterId = [ipaddr] PacketSrc = [ipaddr] ErrorType = [integer] PacketType = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.4 |
|
Alarm name |
ospfIfConfigError |
|
Description |
An ospfIfConfigError trap signifies that a packet has been received on a non-virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event op-tionMismatch should cause a trap only if it prevents an adjacency from forming. |
|
Meaning |
OSPF interface configurations conflict. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: IP address of the interface $3: No address interface index $4: Local router $5: Packet source address $6: Error type $7: Packet type |
|
Function type |
Service quality alarm |
II. Trigger action
The local terminal is not a vlan interface. The parameter configurations on both interfaces are different. In this case, the adjacency cannot be normally set up.
The inconsistency of parameter configuration includes: OSPF version numbers, region configurations, network mask configurations, time settings of Hello packet timer, and time settings of the Dead timer.
III. Recommended action
Check whether the configurations mentioned earlier are the same.
IV. Related alarm message
None
2.5.5 OSPF/1/ Trap5: 1.3.6.1.2.1.14.16.2.5
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF virtual interface configuration error [oid] VirIfAreaId = [ipaddr] VirIfNbrId = [ipaddr] RouterId = [ipaddr] ErrorType = [integer] PacketType = [integer] \r\n |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.5 |
|
Alarm name |
ospfVirtIfConfigError |
|
Description |
An ospfConfigError trap signifies that a packet has been received on a virtual interface from a router whose configuration parameters conflict with this router’s configuration parameters. Note that the event optionMismatch should cause a trap only if it prevents an adjacency from forming. |
|
Meaning |
OSPF virtual link interface configurations conflict. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: Area ID of the virtual interface $3: Neighbor router of the virtual link $4: Local router $5: Error type $6: Packet type |
|
Function type |
Service quality alarm |
II. Trigger action
The local terminal is not a vlan interface. The parameter configurations on both interfaces are not the same.
The inconsistency of parameter configuration includes: OSPF version numbers, region configurations, network mask configurations, time settings of Hello packet timer, and time settings of the Dead timer.
III. Recommended action
Check whether the configurations mentioned earlier are the same.
IV. Related alarm message
None
2.5.6 OSPF/1/ Trap6: 1.3.6.1.2.1.14.16.2.6
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF interface authentication failure [oid] IfIpAddress = [ipaddr] IfAddrLessIndex = [integer] RouterId = [ipaddr] PacketSrc = [ipaddr] ErrorType = [integer] PacketType = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.6 |
|
Alarm name |
ospfIfAuthFailure |
|
Description |
An ospfIfAuthFailure trap signifies that a packet has been received on a non-virtual in-terface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type. |
|
Meaning |
The OSPF interface authentication fails. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: IP address of the interface $3: Local address interface index $4: Local router $5: Packet source address $6: Error type $7: Packet type |
|
Function type |
Service quality alarm |
II. Trigger action
Authentication configurations on both interfaces are not the same.
III. Recommended action
Check configurations of the authentication type and key on both interfaces. Set the types and keys to the same.
IV. Related alarm message
None
2.5.7 OSPF/1/ Trap7: 1.3.6.1.2.1.14.16.2.7
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF virtual interface authentication failure [oid] VirIfAreaId = [ipaddr] VirIfNbrId = [ipaddr] RouterId = [ipaddr] ErrorType = [integer] PacketType = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.7 |
|
Alarm name |
ospfVirtIfAuthFailure |
|
Description |
An ospfVirtIfAuthFailure trap signifies that a packet has been received on a virtual interface from a router whose authentication key or au-thentication type conflicts with this router's authentication key or authentication type. |
|
Meaning |
The OSPF virtual link interface authentication fails. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: Area ID of the virtual interface $3: Neighbor router of the virtual interface $4: Local router $5: Error type $6: Packet type |
|
Function type |
Service quality alarm |
II. Trigger action
Authentication keys on both interfaces are not the same.
III. Recommended action
Check the authentication types and keys on both interfaces. Set the types and keys to the same.
IV. Related alarm message
None
2.5.8 OSPF/1/ Trap8: 1.3.6.1.2.1.14.16.2.8
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF interface received wrong packet [oid] IfIpAddress = [ipaddr] IfAddrLessIndex = [integer] RouterId = [ipaddr] PacketSrc = [ipaddr] PacketType = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.8 |
|
Alarm name |
ospfIfRxBadPacket |
|
Description |
An ospfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed. |
|
Meaning |
The OSPF interface receives a wrong packet. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: IP address of the interface $3: No address interface index $4: Local router $5: Packet source address $6: Packet type |
|
Function type |
Service quality alarm |
II. Trigger action
The local termination is not a vlan interface. It receives a bad packet.
Bad packets include: packets with wrong types, IP addresses, or protocols, packets from an unknown neighbor, small bad packets, large bad packets, checksum error, Router ID conflict in Hello packets, Router ID conflict in DD packets, neighbor state errors in DD, LSA update, LSA request, or LSA confirmation packets, and empty LSA request packets.
III. Recommended action
Check whether the configuration on the related neighbor at this interface is correct, or whether there is an aggressive packet.
IV. Related alarm message
None
2.5.9 OSPF/1/ Trap9: 1.3.6.1.2.1.14.16.2.9
I. Basic information.
|
Item |
Description |
|
Alarm message |
OSPF virtual interface received wrong packet [oid] VirIfAreaId = [ipaddr] VirIfNbrId = [ipaddr] RouterId = [ipaddr] PacketType = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.9 |
|
Alarm name |
OspfVirtIfRxBadPacket |
|
Description |
An ospfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed. |
|
Meaning |
The OSPF virtual link interface receives a wrong packet. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: Area ID of the virtual interface $3: Neighbor router of the virtual interface $4: Local router $5: Local router |
|
Function type |
Service quality alarm |
II. Trigger action
The local termination is a vlan interface. It receives a bad packet.
Bad packets include: packets with wrong types, IP addresses, or protocols, packets from an unknown neighbor, small bad packets, large bad packets, checksum error, Router ID conflict in Hello packets, Router ID conflict in DD packets, neighbor state errors in DD, LSA update, LSA request, or LSA confirmation packets, and empty LSA request packets.
III. Recommended action
Check whether the configuration on the related neighbor at this interface is correct, or whether there is an aggressive packet.
IV. Related alarm message
None
2.5.10 OSPF/1/ Trap10: 1.3.6.1.2.1.14.16.2.10
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF interface retransmitted packet [oid] IfIpAddress = [ipaddr] IfAddrLessIndex = [integer] NbrIpAddress = [ipaddr] NbrAddrLessIndex = [integer] LsdbAreaId = [ipaddr] LsdbType = [integer] LsdbLsid = [ipaddr] LsdbRouterId = [ipaddr] RouterId = [ipaddr] NbrRouterId = [ipaddr] PacketType = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.10 |
|
Alarm name |
ospfTxRetransmit |
|
Description |
An ospfTxRetransmit trap signifies that an OSPF packet has been retransmitted on a non-virtual interface. All packets that may be re-transmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry. |
|
Meaning |
The OSPF interface retransmits a packet. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: IP address of the interface $3: No address interface index $4: IP address of the neighbor $5: No address interface index in the neighbor $6: LSA area ID $7: LSA type $8: LSA ID $9: LSA release router $10: Local router $11: Neighbor router $12: Packet type |
|
Function type |
Service quality alarm |
II. Trigger action
The local terminal is a non-virtual interface. When it does not receive the confirmation packet of a related LSA within the configured time, it retransmits the LSA.
III. Recommended action
None
IV. Related alarm message
None
2.5.11 OSPF/1/ Trap11: 1.3.6.1.2.1.14.16.2.11
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF virtual interface retransmitted packet [oid] VirIfAreaId = [ipaddr] VirIfNbrId = [ipaddr] LsdbAreaId = [ipaddr] LsdbType = [integer] LsdbLsid = [ipaddr] LsdbRouterId = [ipaddr] RouterId = [ipaddr] PacketType = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.11 |
|
Alarm name |
ospfVirtIfTxRetransmit |
|
Description |
An ospfTxRetransmit trap signifies than an OSPF packet has been retransmitted on a virtual interface. All packets that may be retransmit-ted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry. |
|
Meaning |
The link of the OSPF virtual interface retransmits a packet. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: Area ID of the virtual interface $3: Neighbor router of the virtual interface $4: LSA area ID $5: LSA type $6: LSA ID $7: LSA release router $8: Local router $9: Packet type |
|
Function type |
Service quality alarm |
II. Trigger action
The local terminal is a virtual interface. When it does not receive the confirmation packet of a related LSA within the configured time, it retransmits the LSA.
III. Recommended action
None
IV. Related alarm message
None
2.5.12 OSPF/1/ Trap12: 1.3.6.1.2.1.14.16.2.12
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF (re)originated LSA [oid] LsdbAreaId = [ipaddr] LsdbType = [integer] LsdbLsid = [ipaddr] LsdbRouterId = [ipaddr] RouterId = [ipaddr] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.12 |
|
Alarm name |
ospfOriginateLsa |
|
Description |
An ospfOriginateLsa trap signifies that a new LSA has been originated by this router. |
|
Meaning |
The OSPF (re-)generates an LSA. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: LSA area ID $3: LSA type $4: LSA ID $5: LSA release router $6: Local router |
|
Function type |
Service quality alarm |
II. Trigger action
When a new router is added in a network, a router LSA is generated in the area of the router;
When the DR in a network segment changes, or a new router is placed in the segment, the DR generates a network LSA;
When there is a change to the link state in the area where the Area Border Router (ABR) locates, a new network summary LSA is generated;
When there is a change to the Autonomous System Border Router (ASBR) in the area where the ABR locates, a new network summary LSA is generated;
When there is a change to the external route imported by the ASBR, a new ASE LSA is generated;
When there is a change to the external route brought to the NSSA area, the router that brings this external route generates a new NSSA LSA;
All situations stated above lead to this alarm message.
III. Recommended action
1) Check whether a cable was wrongly connected or disconnected before the alarm message;
2) Check whether there is a new router in the network;
3) Check whether there is a router removed from the network;
4) Check whether the interface of a router fails;
5) Check whether there is a change to the external route brought to the network.
IV. Related alarm message
None
2.5.13 OSPF/1/ Trap13: 1.3.6.1.2.1.14.16.2.13
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF LSA reached max-age [oid] LsdbAreaId = [ipaddr] LsdbType = [integer] LsdbLsid = [ipaddr] LsdbRouterId = [ipaddr] RouterId = [ipaddr] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.13 |
|
Alarm name |
ospfMaxAgeLsa |
|
Description |
An ospfMaxAgeLsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge. |
|
Meaning |
The OSPF LSA reaches the max age. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: LSA area ID $3: LSA type $4: LSA ID $5: LSA release router $6: Local router |
|
Function type |
Service quality alarm |
II. Trigger action
The neighbor state changes. The neighbor cannot send new packets.
The router that generated this LSA fails and cannot generate new LSAs.
There is a change to the router that generated this LSA. For example, the DR changes.
III. Recommended action
1) Check whether a wrong configuration existed or a cable was wrongly connected or disconnected before the alarm message is generated;
2) Check whether there is a change to the link state of the router that generated this LSA;
3) Check the ID of the router that generated this LSA. For example, if the category-3 LSA generates an alarm message, check whether the related router is still an ABR; if the category-2 LSA generates an alarm message, check whether the related router is still a DR;
4) Check whether there is a change to the neighbor state;
5) Check whether the link of a router fails.
IV. Related alarm message
None
2.5.14 OSPF/1/ Trap14: 1.3.6.1.2.1.14.16.2.14
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF number of LSAs exceeded ExtLsdbLimit [oid] RouterId = [ipaddr] ExtLsdbLimit = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.14 |
|
Alarm name |
ospfLsdbOverflow |
|
Description |
An ospfLsdbOverflow trap signifies that the number of LSAs in the router's link-state database has exceeded ospfExtLsdbLimit. |
|
Meaning |
The OSPF LSA number reaches ExtLsdbLimit. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: Local router $3: ExtLsdbLimit |
|
Function type |
Service quality alarm |
II. Trigger action
There are excessive routers, resulting in excessive router LSAs in the area;
Routes in category-3 LSAs that can be aggregated are not converged, resulting in excessive category-3 LSAs;
There are excessive external routes brought to the network, resulting in excessive category-5 LSAs.
III. Recommended action
This is the normal warning in the protocol, and requires no processing.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
|
|
Relationship |
ospfLsdbApproachingOverflow |
|
Relation degree |
Prossible |
|
Cause |
If the number of LSAs increases to ExtLsdbLimit after the ospfLsdbApproachingOverflow alarm, this alarm message appears. |
2.5.15 OSPF/1/ Trap15: 1.3.6.1.2.1.14.16.2.15
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF number of LSAs exceeded 90%% ExtLsdbLimit [oid] RouterId = [ipaddr] ExtLsdbLimit = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.15 |
|
Alarm name |
ospfLsdbApproachingOverflow |
|
Description |
An ospfLsdbApproachingOverflow trap signifies that the number of LSAs in the router's linkstate database has exceeded ninety percent of ospfExtLsdbLimit. |
|
Meaning |
The OSPF LSA number reaches 90% of ExtLsdbLimit. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: Local router $3: ExtLsdbLimit |
|
Function type |
Service quality alarm |
II. Trigger action
There are excessive routers, resulting in excessive router LSAs in the area;
Routes in category-3 LSAs that can be aggregated are not converged, resulting inexcessive category-3 LSAs;
There are excessive external routes brought to the network, resulting in excessive category-5 LSAs.
III. Recommended action
This is the normal prompt message in the protocol, and requires no processing.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
|
|
Relationship |
ospfLsdbApproachingOverflow |
|
Relation degree |
Prossible |
|
Cause |
If the number of LSAs continues to increase to ExtLsdbLimit after this alarm, the ospfLsdbApproachingOverflow alarm message appears. |
2.5.16 OSPF/1/ Trap16: 1.3.6.1.2.1.14.16.2.16
I. Basic information
|
Item |
Description |
|
Alarm message |
OSPF link state changed [oid] IfIpAddress = [ipaddr] IfAddrLessIndex = [integer] RouterId = [ipaddr] IfState = [integer] |
|
Alarm OID |
1.3.6.1.2.1.14.16.2.16 |
|
Alarm name |
ospfIfStateChange |
|
Description |
An ospfIfStateChange trap signifies that there has been a change in the state of a non-virtual OSPF interface. This trap should be generated when the link state regresses (e.g., goes from Dr to Down) or progresses to a terminal state (i.e., Point-to-Point, DR Other, Dr, or Backup). |
|
Meaning |
The OSPF link state changes. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1:Alarm OID $2: IP address of the interface $3: Router ID of the OSPF $4: Interface state |
|
Function type |
Service quality alarm |
II. Trigger action
Possible causes of the state change of an OSPF interface include:
Normal state change. For example, when the OSPF interface serves as the DR;
The link state changes. For example, the link state is set to Down.
III. Recommended action
Normal change to the OSPF link state does not require recovery.
If the alarm message is caused by a change of link state on the interface, find the cause of the change: If the link state is changed to Down through the command line, recover the state through the command Undo Shutdown on this interface; If the hardware on the interface fails, change the hardware; If the peer interface fails, clear the fault.
IV. Related alarm message
None
2.6 MSTP
2.6.1 MSTP/2/ ROOT: 1.3.6.1.4.1.2011.2.23.1.14.0.3
I. Basic information
|
Item |
Description |
|
Alarm message |
[OID]: We are not the root switch of the instance [INTEGER]! |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.14.0.3 |
|
Alarm name |
hwBridgeLostRootPrimary |
|
Description |
The SNMP trap that is generated when the bridge is no longer the root bridge of the instance. Another switch with higher priority has already been the root bridge of the instance. |
|
Meaning |
The switch that has been configured as the root bridge of an instance receives a superior packet and becomes no longer the root bridge of the instance. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
1: hwdot1sInstanceID instance ID |
|
Function type |
Environmental alarm |
II. Trigger action
The equipment that has been configured as the root bridge of an instance receives the superior packet of this instance.
If the local switch is configured as the root bridge of an instance, and another switch with a smaller MAC address is also configured as the root bridge of the instance, the second switch will preempt the root bridge of the local switch in the instance. In this case, the alarm is generated.
III. Recommended action
Check whether another switch is configured as the root bridge of the same instance. If so, change the configuration to ensure that only one switch is configured as the root bridge of one instance.
IV. Related alarm message
None
2.6.2 MSTP/2/ RGSUP: 1.3.6.1.4.1.2011.2.23.1.14.0.4
I. Basic information
|
Item |
Description |
|
Alarm message |
[OID]: Instance [INTEGER]'s ROOT-Protection port [INTEGER].[INTEGER] received superior message! |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.14.0.4 |
|
Alarm name |
hwPortMstiRootGuarded |
|
Description |
The SNMP trap that is generated when a root-guard port receives a superior message on the relevant instance. |
|
Meaning |
The root-guard port receives a superior message. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
1: hwdot1sInstanceID instance ID 2: hwdot1sMstiPortIndex port Index |
|
Function type |
Environmental alarm |
II. Trigger action
III. Recommended action
Check where the packet with higher priority comes from and whether the configuration is wrong.
IV. Related alarm message
None
2.6.3 MSTP/2/ IVBPDU: 1.3.6.1.4.1.2011.2.23.1.14.0.5
I. Basic information
|
Item |
Description |
|
Alarm message |
[OID]: BPDU-Protection port [INTEGER] received BPDU packet! |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.14.0.5 |
|
Alarm name |
hwPortMstiBpduGuarded |
|
Description |
The SNMP trap that is generated when an edged port of the BPDU-guard switch receives BPDU packets. |
|
Meaning |
A BPDU-protection edged port receives BPDU packets. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
1: dot1dStpPort port Index |
|
Function type |
Environmental alarm |
II. Trigger action
For the equipment at the access layer, the access ports are often directly connected to the user terminal (such as a PC) or file server. At this time, the access ports are set as an edged port to realize fast migration. When these ports receive a configuration message (BDPU packet), the system automatically sets these ports to non-edged ports, and re-calculates the Spanning Tree, leading to network topology storm. Under normal condition, these ports do not receive configuration messages of the Spanning Tree protocol. If a person forges configuration messages to attack the switch with malice, a network storm occurs.
MSTP uses BPDU-protection to prevent such attacks. The BPDU-protection is enabled in the switch. Once the edged ports receive configuration messages, the system generates this alarm message and closes these ports. The closed ports can only be resumed by network administrators.
III. Recommended action
Edged ports are generally connected to a PC or file server. Hence they do not receive BPDU packets under normal condition.Check the source of the BPDU this port receives. Check whether this port is wrongly connected to a switch. Recover the port connection first, and then undo shutdown the port.
IV. Related alarm message
None
2.6.4 MSTP/2/ LGEXP: 1.3.6.1.4.1.2011.2.23.1.14.0.6
I. Basic information
|
Item |
Description |
|
Alarm message |
[OID]: Instance [INTEGER]'s LOOP-Protection port [INTEGER].[INTEGER] did not receive message! |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.14.0.6 |
|
Alarm name |
hwPortMstiLoopGuarded |
|
Description |
The SNMP trap that is generated when an Alternate-Port or Root-Port is aged out. |
|
Meaning |
A root port or optional port times out when receiving a BPDU message. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
1: hwdot1sInstanceID instance ID 2: hwdot1sMstiPortIndex port Index |
|
Function type |
Environmental alarm |
II. Trigger action
The root port or optional port does not receive the BPDU packet from the upstream for a long time, leading to timeout of the port in receiving the BPDU message.
III. Recommended action
Check whether the upstream port normally sends a packet and whether the local port normally receives the packet.
IV. Related alarm message
None
2.7 POS
2.7.1 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.5
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LRDI Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.5 |
|
Alarm name |
h3cPosLRDIAlarm |
|
Description |
LRDI is used to return an indication to the transmit end that the received end has detected an incoming section defect or is receiving LAIS.LRDI is generated by inserting a “110” code in positions 6,7 and 8 of the K2 byte befor scrambing. |
|
Meaning |
LRDI is used to inform the transmission end of a serious link failure at the local end or of the event that the local end receives an LAIS. LRDI is generated by inserting “110” into bits 6, 7, and 8 in K2. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
The peer end has a serious link failure or receives an LAIS alarm message.
III. Recommended action
Check the links or peer configuration.
IV. Related alarm message
None
2.7.2 POS/2/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.2
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LOF Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.2 |
|
Alarm name |
h3cPosLOFAlarm |
|
Description |
This alarm message indicates loss of frame. |
|
Meaning |
Frame alignment loss |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
Bit errors occur in the links.
III. Recommended action
Check the links.
IV. Related alarm message
None
2.7.3 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.3
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] OOF Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.3 |
|
Alarm name |
h3cPosOOFAlarm |
|
Description |
Alarm indicates out of frame. |
|
Meaning |
Out of framed alignment. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
Bit errors occur in the links.
III. Recommended action
Check the link connection.
IV. Related alarm message
None
2.7.4 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.6
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] PRDI Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.6 |
|
Alarm name |
h3cPosPRDIAlarm |
|
Description |
PRDI is used to return an indication to the transmit STS PTE that the receiving STS PTE has detected an incoming STS Path defect.. |
|
Meaning |
PRDI is used to return an indication to the transmission STS PTE that the local STS PTE has detected a serious STS Path defect. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
An error occurs in the net load boren by the path layer or the path layers are not normally connected.
III. Recommended action
Check whether the path layers are configured in the same way at both ends, and whether the path layer connection is abnormal.
IV. Related alarm message
None
2.7.5 POS/2/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.1
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LOS Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.1 |
|
Alarm name |
h3cPosLOSAlarm |
|
Description |
Alarm indicates loss of signal. |
|
Meaning |
A signal is lost. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
The reception end cannot detect 01 transient within 20us.
III. Recommended action
1. Check the connection; 2. Check whether the scrambles at both ends are configured in the same way.
IV. Related alarm message
None
2.7.6 POS/2/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.8
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LOP Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.8 |
|
Alarm name |
h3cPosLOPAlarm |
|
Description |
Alarm indicates loss of pointer. |
|
Meaning |
A pointer is lost. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
An LOP alarm message appears when 8 consecutive frames receive an invalid pointer or NDF.
III. Recommended action
1. Check clock configuration; 2. Check frame format configurations at both ends.
IV. Related alarm message
None
2.7.7 POS/2/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.4
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LAIS Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.4 |
|
Alarm name |
h3cPosLAISAlarm |
|
Description |
LAIS is used to indicate that a signal defect has been detected at a section terminating equipment. LAIS is detected by a 111 code in bits 6,7 and 8 of the K2 byte after unsrambing. |
|
Meaning |
The local end receives an LOS or LOF alarm message. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
The local end receives an LOS or LOF alarm message.
III. Recommended action
Check whether links are normally connected.
IV. Related alarm message
None
2.7.8 POS/2/ TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.7
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] PAIS Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.7 |
|
Alarm name |
h3cPosPAISAlarm |
|
Description |
PAIS is generated by an LTE upon detection of an LOS, LOF, AIS-L, or LOP-P defect.. |
|
Meaning |
PAIS alarm message appears when the local end receives an LOS, LOF, AIS-L or LOP-P alarm message. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
The local end receives a serious alarm message such as LOS, LOF, AIS-L and LOP.
III. Recommended action
Check whether links are normally connected.
IV. Related alarm message
None
2.7.9 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.9
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] STIM Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.9 |
|
Alarm name |
h3cPosSTIMAlarm |
|
Description |
Alarm indicates inconsistency between sent and received J0 bytes. |
|
Meaning |
The received J0 bytes are different from the expected. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
The received J0 bytes are different from the expected.
III. Recommended action
Check whether J0 bytes are configured in the same way at both ends.
IV. Related alarm message
None
2.7.10 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.10
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] PTIM Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.10 |
|
Alarm name |
h3cPosPTIMAlarm |
|
Description |
Alarm indicates inconsistency between sent and received J1 bytes. |
|
Meaning |
The received J1 bytes are different from the expected. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
The received J1 bytes are different from the expected.
III. Recommended action
Check whether J1 bytes are configured in the same way at both ends.
IV. Related alarm message
None
2.7.11 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.11
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] PSLM Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.11 |
|
Alarm name |
h3cPosPSLMAlarm |
|
Description |
Alarm indicates a mismatched C2 byte. |
|
Meaning |
The received C2 bytes are different from the expected. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1:Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
The received C2 bytes are different from the expected.
III. Recommended action
Check whether C2 bytes are configured in the same way at both ends.
IV. Related alarm message
None
2.7.12 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.12
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LSD Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.12 |
|
Alarm name |
h3cPosLSDAlarm |
|
Description |
Alarm indicates that the B2 bit-error rate exceeds SD threshold. |
|
Meaning |
The bit-error rate exceeds the SD threshold. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
The bit-error rate exceeds the SD threshold.
III. Recommended action
Check whether errors occur in the optical fiber and optical module.
IV. Related alarm message
None
2.7.13 POS/3/TRAP: 1.3.6.1.4.1.2011.10.2.19.2.0.13
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] LSM Alarm on interface [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.19.2.0.13 |
|
Alarm name |
h3cPosLSFAlarm |
|
Description |
Alarm indicates that the B2 bit-error rate exceeds SF threshold. |
|
Meaning |
The bit-error rate exceeds the SF threshold. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Interface of the alarm |
|
Function type |
Equipment alarm |
II. Trigger action
The bit-error rate exceeds the SF threshold.
III. Recommended action
Check whether errors occur in the optical fiber and optical module.
IV. Related alarm message
None
2.8 VRRP
2.8.1 vrrp/5/TrapBecomeNewMaster: 1.3.6.1.2.1.68.0.1
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid]become new master |
|
Alarm OID |
1.3.6.1.2.1.68.0.1 |
|
Alarm name |
vrrpTrapNewMaster |
|
Description |
A device become new master |
|
Meaning |
The device becomes the master virtual switch. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
None |
|
Function type |
Communication alarm |
II. Trigger action
1) When a new group of VRRP backup switches are set up, one switch will be designated as the master;
2) When the priority of a switch that was not the master switch is elevated to a level higher than the former master, this switch becomes the new master;
3) When the master switch fails, the switch in the backup group that has the highest priority becomes the master.
III. Recommended action
None
IV. Related alarm message
None
2.8.2 vrrp/4/ TrapAuthFailed: 1.3.6.1.2.1.68.0.2
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid]failed to authenticate |
|
Alarm OID |
1.3.6.1.2.1.68.0.2 |
|
Alarm name |
vrrpTrapAuthFailure |
|
Description |
Virtual router anthtication failure,master and backup don not same |
|
Meaning |
The authentication passwords are different in the master and slave switches. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
None |
|
Function type |
Communication alarm |
II. Trigger action
The VRRP packet authentication passwords are different in the master and slave switches.
III. Recommended action
Set the authentication passwords in the master and slave switches to the same.
IV. Related alarm message
None
2.9 DEV
2.9.1 DEV/2/POWER STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.1
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: power ID is [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.1 |
|
Alarm name |
Powerfailure |
|
Description |
Equipment power failure. The alarm appears when the power is just inserted to the equipment or some power in the equipment fails. |
|
Meaning |
The power fails. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Power ID |
|
Function type |
Equipment alarm |
II. Trigger action
The power fails.
III. Recommended action
Replace the power.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/ POWER STATE CHANGE TO NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.2 |
|
Relationship |
DEV/2/ POWER STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.1 |
|
Relation degree |
Certain |
|
Cause |
The related alarm is the recovery alarm. If this fault is recovered, the related alarm appears. If the fault is not recovered, this related alarm does not appear. |
2.9.2 DEV/2/POWER STATE CHANGE TO NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.2
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: power ID is [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.2 |
|
Alarm name |
hwPowerNormal |
|
Description |
This alarm message appears when the power state turns normal. |
|
Meaning |
The power is normal. |
|
Alarm type |
Recovery alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Power ID |
|
Function type |
Equipment alarm |
II. Trigger action
The power recovers.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/ POWER STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.1 |
|
Relationship |
DEV/2/ POWER STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.1 |
|
Relation degree |
Certain |
|
Cause |
This alarm message may appear only after the related alarm is generated. |
2.9.3 DEV/2/POWER REMOVED: 1.3.6.1.4.1.2011.2.23.1.12.1.5
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: power ID is [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.5 |
|
Alarm name |
hwPowerRemoved |
|
Description |
This alarm message appears when the power is removed. |
|
Meaning |
The power is removed. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1:OID $2: Power ID |
|
Function type |
Equipment alarm |
II. Trigger action
The power is removed.
III. Recommended action
Insert the power.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
|
|
Relationship |
DEV/2/ POWER REMOVED: 1.3.6.1.4.1.2011.2.23.1.12.1.5 |
|
Relation degree |
Certain |
|
Cause |
The related alarm is the recovery alarm. |
2.9.4 DEV/2/FAN STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.6
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: fan ID is [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.6 |
|
Alarm name |
Fanfailure |
|
Description |
This alarm message appears when the fan fails. |
|
Meaning |
The fan fails. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Fan ID |
|
Function type |
Equipment alarm |
II. Trigger action
The fan fails.
III. Recommended action
Change the fan.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/ FAN STATE CHANGE TO NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.7 |
|
Relationship |
DEV/2/ FAN STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.6 is the root alarm. |
|
Relation degree |
Certain |
|
Cause |
The related alarm is the recovery alarm. |
2.9.5 DEV/2/FAN STATE CHANGE TO NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.7
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: fan ID is [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.7 |
|
Alarm name |
hwFanNormal |
|
Description |
This alarm message appears when the fan recovers from a failure. |
|
Meaning |
The fan recovers from a failure. |
|
Alarm type |
Recovery alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Fan ID |
|
Function type |
Equipment alarm |
II. Trigger action
The fan recovers from a failure.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/ FAN STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.6 |
|
Relationship |
DEV/2/ FAN STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.6 is the root alarm. |
|
Relation degree |
Certain |
|
Cause |
This alarm only appears when the fan recovers from a failure. |
2.9.6 DEV/2/BOARD REMOVED: 1.3.6.1.4.1.2011.2.23.1.12.1.8
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.8 |
|
Alarm name |
hwBoardRemoved |
|
Description |
This alarm message appears when a board is removed. |
|
Meaning |
A board is removed. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Equipment alarm |
II. Trigger action
A board is removed.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
|
|
Relationship |
DEV/2/ BOARD REMOVED: 1.3.6.1.4.1.2011.2.23.1.12.1.8 is the root alarm. |
|
Relation degree |
Certain |
|
Cause |
The related alarm is the recovery alarm. |
2.9.7 DEV/2/BOARD INSERTED: 1.3.6.1.4.1.2011.2.23.1.12.1.9
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.9 |
|
Alarm name |
hwBoardInserted |
|
Description |
This alarm message appears when a board is inserted. |
|
Meaning |
A board is inserted. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Equipment alarm |
II. Trigger action
A board is inserted.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
|
|
Relationship |
DEV/2/ BOARD REMOVED: 1.3.6.1.4.1.2011.2.23.1.12.1.8 is the root alarm. |
|
Relation degree |
Certain |
|
Cause |
This alarm may appear after the related alarm is generated. |
2.9.8 DEV/2/BOARD STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.10
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.10 |
|
Alarm name |
hwBoardFailure |
|
Description |
This alarm message appears when the board fails. |
|
Meaning |
The board fails. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Critical |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Equipment alarm |
II. Trigger action
1) The user reboots the system;
2) Abnormal boards are automatically rebooted.
III. Recommended action
Determine the reasons and whether the boards can be normally started.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/BOARD STATE CHANGE TO NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.11 |
|
Relationship |
DEV/2/ BOARD STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.10 is the root alarm. |
|
Relation degree |
Certain |
|
Cause |
The related alarm is the recovery alarm. |
2.9.9 DEV/2/BOARD STATE CHANGE TO NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.11
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.11 |
|
Alarm name |
hwBoardNormal |
|
Description |
This alarm message appears when the boards recovers from failure. |
|
Meaning |
The board recovers from failure. |
|
Alarm type |
Recovery alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Equipment alarm |
II. Trigger action
The board recovers from failure.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/ BOARD STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.10 |
|
Relationship |
DEV/2/ BOARD STATE CHANGE TO FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.10 is the root alarm. |
|
Relation degree |
Certain |
|
Cause |
This alarm message may appear only after the related alarm is generated. |
2.9.10 DEV/2/BOARD TEMPERATURE LOWER: 1.3.6.1.4.1.2011.2.23.1.12.1.14
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.14 |
|
Alarm name |
hwBoaardTemperatureLower |
|
Description |
This alarm message appears when the the board temperature is below the normal value. |
|
Meaning |
The board temperature is too low. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Environmental alarm |
II. Trigger action
The board temperature is too low.
III. Recommended action
Elevate the temperature.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/ BOARD TEMPERATURE NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.15 |
|
Relationship |
DEV/2/ BOARD TEMPERATURE LOWER: 1.3.6.1.4.1.2011.2.23.1.12.1.14 |
|
Relation degree |
Certain |
|
Cause |
The related alarm is the recovery alarm. |
2.9.11 DEV/2/BOARD TEMPERATURE NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.15
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.15 |
|
Alarm name |
hwBoaardTemperatureFromLowerToNormal |
|
Description |
This alarm message appears when the the board temperature turns to the normal value. |
|
Meaning |
The board temperature becomes normal. |
|
Alarm type |
Recovery alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Environmental alarm |
II. Trigger action
The board temperature turns normal from low.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/ BOARD TEMPERATURE LOWER: 1.3.6.1.4.1.2011.2.23.1.12.1.14 |
|
Relationship |
DEV/2/ BOARD TEMPERATURE LOWER: 1.3.6.1.4.1.2011.2.23.1.12.1.14 |
|
Relation degree |
Certain |
|
Cause |
This alarm message may appear only after the related alarm message is generated. |
2.9.12 DEV/2/BOARD TEMPERATURE UPPER 1.3.6.1.4.1.2011.2.23.1.12.1.16
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.16 |
|
Alarm name |
hwBoaardTemperatureHigher |
|
Description |
This alarm message appears when the the board temperature is above the normal value. |
|
Meaning |
The board temperature is too high. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Critical |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Environmental alarm |
II. Trigger action
The board temperature is too high.
III. Recommended action
Lower the temperature.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/ BOARD TEMPERATURE NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.17 |
|
Relationship |
DEV/2/ BOARD TEMPERATURE UPPER 1.3.6.1.4.1.2011.2.23.1.12.1.16 |
|
Relation degree |
Certain |
|
Cause |
The related alarm is the recovery alarm. |
2.9.13 DEV/2/BOARD TEMPERATURE NORMAL: 1.3.6.1.4.1.2011.2.23.1.12.1.17
I. Basic information
|
Item |
Description |
|
Alarm message |
[OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.17 |
|
Alarm name |
hwBoaardTemperatureFormHigherToNormal |
|
Description |
This alarm message appears when the the board temperature turns to the normal value. |
|
Meaning |
The board temperature turns normal from high. |
|
Alarm type |
Recovery alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Environmental alarm |
II. Trigger action
The board temperature turns normal from high.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
DEV/2/ BOARD TEMPERATURE UPPER 1.3.6.1.4.1.2011.2.23.1.12.1.16 |
|
Relationship |
DEV/2/ BOARD TEMPERATURE UPPER 1.3.6.1.4.1.2011.2.23.1.12.1.16 |
|
Relation degree |
Certain |
|
Cause |
This alarm may appear only after the related alarm is generated. |
2.9.14 DEV/2/BOARD REQUEST LOADING: 1.3.6.1.4.1.2011.2.23.1.12.1.18
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.18 |
|
Alarm name |
hwRequestLoading |
|
Description |
This alarm message appears when the linecard requests to load software. |
|
Meaning |
The board requests for loading. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Equipment alarm |
II. Trigger action
The board requests for loading.
III. Recommended action
None
IV. Related alarm message
None
2.9.15 DEV/2/LOAD FAILURE: 1.3.6.1.4.1.2011.2.23.1.12.1.19
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.19 |
|
Alarm name |
hwLoadFailure |
|
Description |
This alarm message appears when the linecard fails to load the software. |
|
Meaning |
The board fails to load the software. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Slot No. |
|
Function type |
Equipment alarm |
II. Trigger action
The board fails to load the software.
III. Recommended action
Re-insert the board or change other boards.
IV. Related alarm message
None
2.9.16 DEV/2/LOAD FINISHED: 1.3.6.1.4.1.2011.2.23.1.12.1.20
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: frameIndex is [INTEGER], slotIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.20 |
|
Alarm name |
hwLoadFinished |
|
Description |
This alarm message appears when the board loads the software successfully. |
|
Meaning |
The boards successfully loads the software. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: OID $2: Frame No. $3: Frame No. $4: Slot No. |
|
Function type |
Equipment alarm |
II. Trigger action
The board loads the software successfully.
III. Recommended action
None
IV. Related alarm message
None
2.9.17 DEV/2/POWER INSERT: 1.3.6.1.4.1.2011.2.23.1.12.1.23
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: power ID is [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.12.1.23 |
|
Alarm name |
hwPowerInserted |
|
Description |
This alarm message appears when the power is inserted. |
|
Meaning |
Insert the power. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: OID $2: Power ID |
|
Function type |
Equipment alarm |
II. Trigger action
Insert the power.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
|
|
Relationship |
DEV/2/ POWER REMOVED: 1.3.6.1.4.1.2011.2.23.1.12.1.5 |
|
Relation degree |
Certain |
|
Cause |
This alarm message may appear only after the related alarm is generated. |
2.9.18 DEV/2/PORT POE POWER ON: 1.3.6.1.2.1.105.0.1
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: slotIndex is [INTEGER], PortIndex [INTEGER].[INTEGER] |
|
Alarm OID |
1.3.6.1.2.1.105.0.1 |
|
Alarm name |
pethPsePortOnOffNotification |
|
Description |
The alarm appears when the PSE port is supplying power or does not supply power. The interval for two consecutive alarms is at least 500ms. |
|
Meaning |
This alarm indicates the status of the PSE port: open or closed. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
$1: Alarm OID $2: Slot No. $3: Slot No. $4: Interface No. |
|
Function type |
Equipment alarm |
II. Trigger action
The PSE port provides power for PD equipment.
III. Recommended action
If normal, no recovery is required.
IV. Related alarm message
None
2.9.19 DEV/2/PSE POWER USAGE OVER THRESHOLD: 1.3.6.1.2.1.105.0.1
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: slotIndex is [INTEGER] Power is [INTEGER] Watts |
|
Alarm OID |
1.3.6.1.2.1.105.0.2 |
|
Alarm name |
pethMainPowerUsageOnNotification |
|
Description |
This alarm message appears when the current power of the PSE port exceeds the upper threshold. The interval for two consecutive alarms is at least 500ms. |
|
Meaning |
The current power of the PSE port exceeds the upper threshold. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Slot No. $3: Current PSE power |
|
Function type |
Equipment alarm |
II. Trigger action
The current power of the PSE port exceeds the upper threshold.
III. Recommended action
Reduce the power of the PSE port.
IV. Related alarm message
None
2.9.20 DEV/2/PSE POWER USAGE BELOW THRESHOLD: 1.3.6.1.2.1.105.0.3
I. Basic information
|
Item |
Description |
|
Alarm message |
\r\n Trap [OID]: slotIndex is [INTEGER] Power is [INTEGER] Watts\r\n |
|
Alarm OID |
1.3.6.1.2.1.105.0.3 |
|
Alarm name |
pethMainPowerUsageOffNotification |
|
Description |
This alarm message appears when the current power of the PSE port is below the lower threshold. The interval for two consecutive alarms is at least 500ms. |
|
Meaning |
The current PSE power is below the lower threshold. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Slot No. $3: Current PSE power |
|
Function type |
Equipment alarm |
II. Trigger action
The current PSE power is below the lower threshold.
III. Recommended action
Increase the power of the PSE device.
IV. Related alarm message
None
2.9.21 DEV/2/PD PULL: 1.3.6.1.4.1.2011.10.2.14.6.1
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap[OID]:slotIndex is [INTEGER], PortIndex is [INTEGER],Port status is [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.14.6.1 |
|
Alarm name |
h3cpsePDChangeNotification |
|
Description |
This alarm message appears when the PD device is invalid or disconnected. |
|
Meaning |
The PD device is invalid or disconnected. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: Alarm OID $2: Slot No. $3: Port index $4: Port state |
|
Function type |
Equipment alarm |
II. Trigger action
The PD device is invalid or disconnected.
III. Recommended action
None
IV. Related alarm message
None
2.9.22 DEV/2/PD PULL: 1.3.6.1.4.1.2011.10.2.14.6.1
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap[OID]:slotIndex is [INTEGER], PortIndex is [INTEGER],Port status is [INTEGER] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.14.6.1 |
|
Alarm name |
h3cpsePDChangeNotification |
|
Description |
The power supply status of the PD device changes (normal or forbidden). |
|
Meaning |
The power suppy status of the PD device changes. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: Alarm OID $2: Slot No. $3: Port index $4: Port state |
|
Function type |
Equipment alarm |
II. Trigger action
The PD device normally provides power, or the power supply of the PD device is forbidden.
III. Recommended action
None
IV. Related alarm message
None
2.10 ENTITY
2.10.1 ENTITY/5/CONFIG CHANGE: 1.3.6.1.2.1.47.2.0.1
I. Basic information.
|
Item |
Description |
|
Alarm message |
Trap [OID]: Configuration has been changed |
|
Alarm OID |
1.3.6.1.2.1.47.2.0.1 |
|
Alarm name |
entConfigChange |
|
Description |
This alarm message appears when the entity MIB configuration is changed. |
|
Meaning |
The entity MIB configuration is changed. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: Alarm OID |
|
Function type |
Communication alarm |
II. Trigger action
1) This alarm will be sent when creating or deleting conception lines in the following MIB tables:
entPhysicalTable
entLogicalTable
entLPMappingTable
entAliasMappingTable
entPhysicalContainsTable
2) The alarm will also be sent when modifying the following MIB objective instances:
entPhysicalDescr
entPhysicalVendorType
entPhysicalContainedIn
entPhysicalClass
entPhysicalParentRelPos
entPhysicalName
entLogicalDescr
entLogicalType
entLogicalCommunity
entLogicalTAddress
entLogicalTDomain
entAliasMappingIdentifier
III. Recommended action
None
IV. Related alarm message
None
2.11 HWCM
2.11.1 HWCM/5/TRAP:1.3.6.1.4.1.2011.10.2.4.2.1
I. Basic information
|
Item |
Description |
|
Alarm message |
configure changed: EventIndex=[integer], ommandSource=[integer], onfigSource=[integer], onfigDestination=[integer] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.4.2.1 |
|
Alarm name |
h3cCfgManEventlog |
|
Description |
This alarm message appears when the current configuration is different from the saved. This alarm is detected every 10 minutes but is not sent repeatedly. |
|
Meaning |
Under the following situations, this alarm is generated to inform the user of a configuration change: SNMP SET operation; The initiation configuration file is changed; Enter into the system view; Check every 10 minutes whether the configuration is changed; |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
h3cCfgLogSrcCmd: Configure the command source of the change event; h3cCfgLogSrcData: Configure the data source of the change event; h3cCfgLogDesData: Configure the data’s destination of the change event. |
|
Function type |
Equipment alarm |
II. Trigger action
1) SNMP SET operation
This alarm message appears when the user uses SNMP to configure the equipment (SNMP SET operation).
2) Enter into the system view
This alarm is generated as a prompt for the user to configure the equipment when the user enters into the system view by typing the “system-view” command in the user view of the command line interface.
3) Check every 10 minutes whether the configuration is changed
The system checks every 10 minutes whether the configuration is changed. If so, the system sends this alarm message to inform the user.
4) Backup and recovery of CONFIGMAN MIB
When the user performs six types of operations in backup and recovery of CONFIGMAN MIB through NMS, the system generates this alarm message to inform the user.
III. Recommended action
This alarm is a warning and does not require alarm recovery.
IV. Related alarm message
None
2.11.2 HWCM/5/CFGCOPY: 1.3.6.1.4.1.2011.10.2.4.2.2
I. Basic information
|
Item |
Description |
|
Alarm message |
configuration copy: |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.4.2.2 |
|
Alarm name |
h3cCfgOperateCompletion |
|
Description |
This alarm message appears when h3cCfgOperateTable is successfully created. |
|
Meaning |
When the user performs six types of operations in backup and recovery of CONFIGMAN MIB through NMS, if the notice for complete operation is enabled, the system generates this alarm to note the user. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
h3cCfgOperateType: Operation type; h3cCfgOperateTime: Opeation start event; h3cCfgOperateState: Operation state (successful or not); h3cCfgOperateEndTime: Operation end time; |
|
Function type |
Equipment alarm |
II. Trigger action
When the user performs the six types of operations in backup and recovery of CONFIGMAN MIB through NMS: running2startup, startup2running, net2startup, startup2net, running2net, and net2running, this alarm message is generated to note the user of the operation result.
III. Recommended action
Pay special attention to the value of parameter h3cCfgOperateState (operation state) in the alarm message for the operation result. If the value of this parameter is not opSucess(2), consider the cause of the failed operation or re-execute the operation.
IV. Related alarm message
None
2.12 L2INF
2.12.1 L2INF/2/ PORT LINK STATUS CHANGE: 1.3.6.1.6.3.1.1.5.4
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: portIndex is [INTEGER], ifAdminStatus is [INTEGER], ifOperStatus is [INTEGER] |
|
Alarm OID |
1.3.6.1.6.3.1.1.5.4 |
|
Alarm name |
linkUp |
|
Description |
This alarm message appears when the port state turns UP. |
|
Meaning |
The port state turns UP. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: Alarm OID $2: Port index $3: Switch state of actual interface operation $4: Current state of the interface |
|
Function type |
Equipment alarm |
II. Trigger action
The port state turns UP.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
L2INF/2/ PORT LINK STATUS CHANGE: 1.3.6.1.6.3.1.1.5.3 |
|
Relationship |
L2INF/2/ PORT LINK STATUS CHANGE: 1.3.6.1.6.3.1.1.5.4 |
|
Relation degree |
Prossible |
|
Cause |
The port state changes (from UP to DOWN or from DOWN to UP). |
2.12.2 L2INF/2/PORT LINK STATUS CHANGE: 1.3.6.1.6.3.1.1.5.3
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: portIndex is [INTEGER], ifAdminStatus is [INTEGER], ifOperStatus is [INTEGER] |
|
Alarm OID |
1.3.6.1.6.3.1.1.5.3 |
|
Alarm name |
linkDown |
|
Description |
This alarm message appears when the port state turns DOWN. |
|
Meaning |
The port state turns DOWN. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: Alarm OID $2: Port index $3: Switch state of actual interface operation $4: Current state of the interface |
|
Function type |
Equipment alarm |
II. Trigger action
The port state turns DOWN.
III. Recommended action
None
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
L2INF/2/ PORT LINK STATUS CHANGE: 1.3.6.1.6.3.1.1.5.4 |
|
Relationship |
L2INF/2/ PORT LINK STATUS CHANGE: 1.3.6.1.6.3.1.1.5.3 |
|
Relation degree |
Prossible |
|
Cause |
The port state changes (from UP to DOWN or from DOWN to UP). |
2.13 MIX
2.13.1 MIX/2/SLAVE SWITCH OVER: 1.3.6.1.4.1.2011.2.23.1.17.10.1
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID]: Slave switch over. |
|
Alarm OID |
1.3.6.1.4.1.2011.2.23.1.17.10.1 |
|
Alarm name |
hwSlaveSwitchOver |
|
Description |
This alarm message appears in switchover between master and slave boards. |
|
Meaning |
The switchover between master and slave boards is complete. |
|
Alarm type |
Recovery alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID |
|
Function type |
Equipment alarm |
II. Trigger action
The master and slave boards are switched over.
III. Recommended action
This alarm is automatically recovered.
IV. Related alarm message
None
2.14 RMON
2.14.1 rmon/2/ ALARMUP: 1.3.6.1.2.1.16.0.1
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID] Alarm table [INTEGER] monitors [OID] with sample type [INTEGER],has sampled alarm value [LONG] uprise [INTEGER]. |
|
Alarm OID |
1.3.6.1.2.1.16.0.1 |
|
Alarm name |
risingAlarm |
|
Description |
This alarm message appears when the monitored value equals or exceeds the upper threshold. |
|
Meaning |
The monitored value equals or exceeds the upper threshold. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: Alarm OID $2: Row index $3: Alarm variable $4: Sample type $5: Sample value $6: Upper threshold |
|
Function type |
Service quality alarm |
II. Trigger action
This alarm is generated when the state of the alarm group is “valid”, and the sample value of the alarm variable (prialarmVariable) equals or exceeds the upper threshold (prialarmRisingThreshold).
III. Recommended action
Delete the rows corresponding to the row index, or increase the upper threshold, or change the states of the rows corresponding to the row index to “underCreation”.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
fallingAlarm |
|
Relationship |
None |
|
Relation degree |
Certain |
|
Cause |
These two alarm messages are sent in turns. |
2.14.2 rmon/2/ ALARMFALL: 1.3.6.1.2.1.16.0.2
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID] Alarm table [INTEGER] monitors [OID] with sample type [INTEGER], has sampled alarm value [LONG] less than (or =) [INTEGER]. |
|
Alarm OID |
1.3.6.1.2.1.16.0.2 |
|
Alarm name |
fallingAlarm |
|
Description |
This alarm message appears when the monitored value is equal to or below the lower threshold. |
|
Meaning |
The monitored value is equal to or below the lower threshold. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: Alarm OID $2: Row index $3: Alarm variable $4: Sample type $5: Sample value $6: Lower threshold |
|
Function type |
Service quality alarm |
II. Trigger action
This alarm is generated when the state of the alarm group is “valid”, and the sample value of the alarm variable (prialarmVariable) is equal to or below the lower threshold (prialarmRisingThreshold).
III. Recommended action
Delete the rows corresponding to the row index, or reduce the lower threshold, or change the states of the rows corresponding to the row index to “underCreation”.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
risingAlarm |
|
Relationship |
None |
|
Relation degree |
Certain |
|
Cause |
These two alarm messages are sent in turns. |
2.14.3 rmon/2/ RISING: 1.3.6.1.4.1.2011.1.3.4.0.1
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID] Private alarm table [INTEGER] monitors [OCTET] with sample type [INTEGER],has sampled alarm value [INTEGER] uprise [INTEGER]. |
|
Alarm OID |
1.3.6.1.4.1.2011.1.3.4.0.1 |
|
Alarm name |
pririsingAlarm |
|
Description |
This alarm message appears when the alarm variable equals or exceeds the upper threshold. |
|
Meaning |
The monitored value equals or exceeds the upper threshold. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: Alarm OID $2: Row index $3: Alarm variable $4: Sample type $5: Sample value $6: Upper threshold |
|
Function type |
Service quality alarm |
II. Trigger action
This alarm is generated when the state of the extended alarm group is “valid”, and the sample value of the alarm variable (prialarmVariable) equals or exceeds the upper threshold (prialarmRisingThreshold).
III. Recommended action
Delete the rows corresponding to the row index, or increase the upper threshold, or change the states of the rows corresponding to the row index to “underCreation”.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
prifallingAlarm |
|
Relationship |
None |
|
Relation degree |
Certain |
|
Cause |
These two alarm messages are sent in turns. |
2.14.4 rmon/2/FALLING: 1.3.6.1.4.1.2011.1.3.4.0.2
I. Basic information
|
Item |
Description |
|
Alarm message |
Trap [OID] Private alarm table [INTEGER] monitors [OCTET] with sample type [INTEGER],has sampled alarm value [INTEGER] less than(or =) [INTEGER]. |
|
Alarm OID |
1.3.6.1.4.1.2011.1.3.4.0.2 |
|
Alarm name |
prifallingAlarm |
|
Description |
This alarm message appears when the alarm variable is equal to or below the lower threshold. |
|
Meaning |
The monitored value is equal to or below the lower threshold. |
|
Alarm type |
Event alarm |
|
Alarm level |
Minor |
|
Alarm parameter |
$1: Alarm OID $2: Row index $3: Alarm variable $4: Sample type $5: Sample value $6: Lower threshold |
|
Function type |
Service quality alarm |
II. Trigger action
This alarm is generated when the state of the extended alarm group is “valid”, and the sample value of the alarm variable (prialarmVariable) is equal to or below the lower threshold (prialarmRisingThreshold).
III. Recommended action
Delete the rows corresponding to the row index, or reduce the lower threshold, or change the states of the rows corresponding to the row index to “underCreation”.
IV. Related alarm message
|
Item |
Description |
|
Related alarm message |
pririsingAlarm |
|
Relationship |
None |
|
Relation degree |
Certain |
|
Cause |
These two alarm messages are sent in turns. |
2.15 VFS
2.15.1 VFS/5/TRAP: 1.3.6.1.4.1.2011.10.2.5.1.3.1
I. Basic information
|
Item |
Description |
|
Alarm message |
[oid] Copy operation completed CopyIndex=[integer], CopyStatus =[integer] |
|
Alarm OID |
1.3.6.1.4.1.2011.10.2.5.1.3.1 |
|
Alarm name |
h3cFlhOperNotification |
|
Description |
When creating a row in the h3cFlhOpTable table, if the value of h3cFlhOperEndNotifications is set to true, this alarm message appears with the result of the operation. |
|
Meaning |
This alarm message displays the execution result of the flash operation. |
|
Alarm type |
Event alarm |
|
Alarm level |
Major |
|
Alarm parameter |
$1: Alarm OID $2: Current row index $3: Operation result |
|
Function type |
Service quality alarm |
II. Trigger action
When creating a row in the h3cFlhOpTable table, if the value of h3cFlhOperEndNotifications is set to true, this alarm is generated after the new row is successfully set up. The alarm displays the execution result of the operation designated by h3cFlhOperType.
III. Recommended action
The user can judge whether the returned result is “operation failed” based on the returned operation code.
IV. Related alarm message
None
2.16 SNMP-V2
2.16.1 ColdStart: 1.3.6.1.6.3.1.1.5.1
I. Basic information
|
Item |
Description |
|
Alarm message |
None |
|
Alarm OID |
1.3.6.1.6.3.1.1.5.1 |
|
Alarm name |
ColdStart |
|
Description |
A coldStart trap signifies that the SNMPv2 entity, acting in an agent role, is reinitializing itself and that its configuration may have been altered. |
|
Meaning |
The SNMP agent module in the equipment is re-initialized and its configuration may have changed. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
None |
|
Function type |
Communication alarm |
II. Trigger action
In the process of equipment startup, the initialization of the SNMP agent module is complete.
III. Recommended action
None
IV. Related alarm message
None
2.16.2 WarmStart: 1.3.6.1.6.3.1.1.5.2
I. Basic information
|
Item |
Description |
|
Alarm message |
None |
|
Alarm OID |
1.3.6.1.6.3.1.1.5.2 |
|
Alarm name |
WarmStart |
|
Description |
A warmStart trap signifies that the SNMPv2 entity, acting in an agent role, is reinitializing itself such that its configuration is unaltered. |
|
Meaning |
The SNMP agent module in the equipment is re-initialized and its configuration is not changed. |
|
Alarm type |
Event alarm |
|
Alarm level |
Warning |
|
Alarm parameter |
None |
|
Function type |
Communication alarm |
II. Trigger action
In the running process of the equipment, use “snmp-agent” in the command line to enable the SNMP agent.
III. Recommended action
None
IV. Related alarm message
None
2.16.3 AuthenticationFailure: 1.3.6.1.6.3.1.1.5.5
I. Basic information
|
Item |
Description |
|
Alarm message |
None |
|
Alarm OID |
1.3.6.1.6.3.1.1.5.5 |
|
Alarm name |
AuthenticationFailure |
|
Description |
An authenticationFailure trap signifies that the SNMPv2 entity, acting in an agent role, has received a protocol message that is not properly authenticated. While all implementations of the SNMPv2 must be capable of generating this trap, the snmpEnableAuthenTraps object indicates whether this trap will be generated. |
|
Meaning |
The received protocol message is not properly authenticated. |
|
Alarm type |
Failure alarm |
|
Alarm level |
Major |
|
Alarm parameter |
None |
|
Function type |
Communication alarm |
II. Trigger action
This alarm has the following trigger actions:
l For SNMPv1/v2c, the community used in the message does not exist;
l For SNMPv3, the authentication cipher key used for sending the message is wrong.
III. Recommended action
Based on the cause, the recommended actions include:
l For SNMPv1/v2c, use the correct community connection equipment;
l For SNMPv3, use the correct authentication cipher key.
IV. Related alarm message
None
