No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Trap Overview

Trap Overview

Trap Implementation Principle

Overview

When faults occur or the system operates abnormally, alarms and events are triggered to help users detect and locate faults quickly.

  • Event

    Events are triggered by specific occurrences, and indicate anything that takes place on a managed object in the system. For example, an object is added, deleted, or modified.

    Events are recorded in logs. Certain events may trigger traps that are called event traps and shall be paid attention to or processed by users immediately. An event trap does not have a match trap.

  • Alarm

    Alarms are triggered when the device operation is abnormal, causing the service to be abnormal or disabling the device from properly working. Alarms require immediate attention or processing of users. They inform maintenance personnel of the device operating state and assist in fault location. For example, the change of the interface status may trigger an alarm.

    When a fault occurs, an alarm is triggered and the alarm trap is sent. After the fault is rectified, the alarm status changes from active to cleared and the clear alarm trap is sent. If an alarm trap is generated, a corresponding clear alarm trap will be generated after the fault is rectified. These two traps are a match and both called alarm traps.

NOTE:

Alarms and events may be defined differently on NMSs and can be re-defined.

Information Output

Information generated by the device can be output to the remote terminal, console, log buffer, log file, and SNMP agent. To output information in different directions, 10 information channels are defined for the information center. These channels work independently from one another. You can configure output rules so that information can be output from different objects to different objects based on types and severities, as shown in Figure 4-15.

Figure 4-15 Information center mechanism

NOTE:
  • For log information, an event trap is triggered only when an event that triggers trap sending generates a log.
  • For alarm information, an alarm trap is triggered as long as alarm information is generated.

Output directions

Output Directions

Description

Log file

Records all information generated by the device.

Saved as a .zip file on the hard disk or flash memory of a device.

Simple Network Management Protocol (SNMP) agent

If an NMS is configured, the system sends the traps to the NMS by the Simple Network Management Protocol (SNMP).

Log buffer

Records all log information generated by the device. For alarms, information recorded in the log buffer is the same as that recorded in the trap buffer.

Trap buffer

Records trap information after the trap function is enabled using the snmp-agent trap enable command.

Its size can be allocated as required.

Log host

Records all log information generated on the device. Information is saved in files on the log host and can be accessed as you want.

Remote terminal

Outputs all information to the VTY terminals for remote maintenance.

Console

Outputs all information to the local console.

Trap Generation Mechanism and Output Format
  • Alarm
Figure 4-16 Mechanism for the Input and output of the alarm information

Alarms are output in different forms, and their information formats also vary.

  • Alarm

    Alarms are output to a remote terminal or the console.

    #265/active/mplsLdpSessionDown/Critical/occurredTime:2015-08-07 12:44:01/-/-/alarmID:0x09020000/CID=0x801c043c: 
    The LDP session status is Down. (PeerLsrId=19.19.19.19:0, VrfName=_public_, SessionType=Local, IfName=10GE1/17/1, SubReason=0, 
    Reason=The LDP Keepalive timer expired.)
Figure 4-17 Alarm format

Alarm information is displayed on the terminal screen through the Monitor or Console channel. The format of alarm information displayed on the screen is different from that of the alarm log recorded in the log buffer and of the alarm trap recorded in the trap buffer. However, the information content is the same.

NOTE:

An alarm ID uniquely identifies an alarm. You are advised to locate the description and handling procedure of an alarm by searching for its ID in the manual.

  • Alarm trap

    Alarm traps are output to the trap buffer.

    Aug 17 2015 12:44:01 HUAWEI %%01LDP/1/Session-Down-MIB(t):CID=0x801c043c-OID=1.3.6.1.2.1.10.166.4.0.4; 
    The LDP session status is Down. (PeerLsrId=19.19.19.19:0, VrfName=_public_, SessionType=Local, IfName=10GE1/17/1, SubReason=0, 
    Reason=The LDP Keepalive timer expired.)
Figure 4-18 Alarm trap format

The alarm trap is also displayed on the terminal screen through the Monitor or Console channel. The format of the information displayed on the screen is the same as that of the alarm trap recorded in the trap buffer.

This manual mainly describes traps recorded in the trap buffer. For details, see Descriptions of Traps in the Trap Buffer.

  • Alarm log

    Alarm logs are output to the log buffer.

    Aug 17 2015 12:44:01 HUAWEI %%01LDP/1/mplsLdpSessionDown_active(l):CID=0x801c043c-alarmID=0x09020000; 
    The LDP session status is Down. (PeerLsrId=19.19.19.19:0, VrfName=_public_, SessionType=Local, IfName=10GE1/17/1, SubReason=0, 
    Reason=The LDP Keepalive timer expired.)
Figure 4-19 Alarm log format

The alarm log is also displayed on the terminal screen through the Monitor or Console channel. The format of the information displayed on the screen is the same as that of the alarm log recorded in the log buffer.

Logs recorded in the log buffer can be located in the log reference through the information digest.

  • Event
NOTE:

All events are recorded in logs, and only events that trigger trap sending trigger event traps.

  • Event that triggers trap sending
Figure 4-20 Input and output mechanism for an event that triggers trap sending

Events that trigger trap sending are saved as event traps and output through different information channels but in the same information format (except for the SNMP agent). Figure 4-21 shows the information format.

Figure 4-21 Event trap format

For example, an event trap displayed on the screen is as follows:

Aug 17 2015 21:27:58 HUAWEI %%01MSTP/4/hwMstpProRootChanged(t):CID=0x8054042c-OID=1.3.6.1.4.1.2011.5.25.42.4.2.17; 
The root bridge of MSTP process changed. (ProcessID=0,InstanceID=0, PortID=2)

This manual mainly describes traps recorded in the trap buffer. For details, see Descriptions of Traps in the Trap Buffer.

  • Event that does not trigger trap sending
Figure 4-22 Input and output mechanism for an event that does not trigger trap sending

Events that do not trigger trap sending are saved in event logs. Figure 4-15 shows the information format.

Figure 4-23 Event log format

The formats of the logs that the terminal screen, log host, log file, and log buffer display are the same. For example, an event log displayed on the terminal screen is as follows:

Aug 17 2015 21:16:38 HUAWEI %%01OSPF/3/NBR_DOWN_REASON(l):CID=0x80830436;Neighbor state left full or changed to Down. 
 (ProcessId=65534, NeighborRouterId=128.254.255.252, NeighborIp=128.254.255.252, NeighborAreaId=0.0.0.0,NeighborInterface=-,NeighborDownImmediate  
reason=Neighbor Down Due to Kill Neighbor, NeighborDownPrimeReason=Link Fault or Interface Configuration Change,CpuUsage=0%)

Logs recorded in the log buffer can be located in the log reference through the information digest.

Descriptions of Traps in the Trap Buffer

The output format of a trap on a CLI terminal is as follows:

Aug 17 2015 12:44:01 HUAWEI %%01LDP/1/Session-Down-MIB(t):CID=0x801c043c-OID=1.3.6.1.2.1.10.166.4.0.4; 
The LDP session status is Down. (PeerLsrId=19.19.19.19:0, VrfName=_public_, SessionType=Local, IfName=10GE1/17/1, SubReason=0, 
Reason=The LDP Keepalive timer expired.)

Figure 4-24 shows the output format of a trap.

Figure 4-24 Output format of traps

Field

Meaning

Description

Time

Timestamp, that is, time to output log information

Five timestamp formats are available:

  • boot: indicates that the timestamp is expressed in the format of relative time, a period of time since the start of the system. The format is xxxxxx.yyyyyy. xxxxxx is the higher order 32 bits of the milliseconds elapsed since the start of the system; yyyyyy is the lower order 32 bits of the milliseconds elapsed since the start of the system.
  • data: indicates that the timestamp employs the current data and time of the system and is expressed in the format of "mm dd yyyy hh:mm:ss".
  • short-date: indicates that the timestamp employs the short date. The timestamp of this type is almost the same as that of the data type, with the only difference lying in that the short-date type cancels the display of the year.
  • format-date: indicates that the timestamp is expressed in YYYY-MM-DD hh:mm:ss format.

A timestamp and a host name are separated by a space. The format of the trap timestamp is configurable.

Host

Host name

The default name is HUAWEI.

%%

Huawei identifier

Indicates that the trap is output by a Huawei device.

dd

Version number

Indicates the version of the trap format.

Module

Module name

Indicates the name of the module by which traps are output.

Severity

Trap level

Indicates the severity of a trap.

Trap levels are classified into eight levels. The lower the value of the trap level, the higher the severity is.

  • 0: emergency

    A fatal fault, such as a abnormal program or a memory error, occurs on the device. The system must restart.

  • 1: alert

    A major fault occurs, such as the device memory threshold reaches the upper limit. The fault needs to be rectified immediately.

  • 2: critical

    A critical fault occurs, such as the device memory threshold reaches the lower limit, the temperature reaches the lower limit, the BFD device is unreachable, or an internal fault generated by the device itself. The fault needs to be analyzed and rectified.

  • 3: error

    A fault caused by an incorrect operation or wrong process occurs, such as an incorrect user password or a wrong protocol packet is received from another device. The fault needs to be addressed.

  • 4: warning

    An abnormal situation occurs, such as the user disables the routing process, BFD detects the packet loss, or a wrong protocol packet is received. The fault needs to be addressed.

  • 5: notice

    Indicates the key operations that are used to keep the device functioning properly, such as the shutdown command, neighbor discovery, or the state machine.

  • 6: informational

    Indicates the common operations that are used to keep the device functioning properly, such as the display command.

  • 7: debugging

    Indicates that a routine operation is performed, and no action is required.

Brief

Description

Indicates the information type.

(t)

Information type

Indicates the trap information.

CID=Z

System component ID

Indicates the system component ID.

OID=F

Trap OID

Indicates the trap OID, which is an object identifier defined in a MIB file.

Des

Information about details

Indicates the detail information about the system component output. Each time before the trap is output, the module fills up its contents.

Trap Information Description

Trap Buffer Description

Two parts are included:

  • Trap message: indicates the character string that describes the trap. It is displayed on a device.
  • Trap meaning: indicates the meaning of the trap.
Trap Attributes

Table 4-18 describes trap attributes.

Table 4-18 Trap Attribute

Attribute

Description

Alarm or Event

Indicates the trap type, which can be:

  • Alarm
  • Event

Trap Severity

Indicates to what extent the fault affects the performance of the device.

Mnemonic Code

Indicates the digest of trap content for the ease of memorization.

Trap OID

Indicates the object ID defined in the MIB.

Alarm ID

Indicates the alarm ID defined by the network management system (NMS).

Alarm Type

Indicates the type that the fault is related to.

  • communicationsAlarm

    Indicates that a fault occurs in the process associated with the data transfer. For example, an alarm is generated due to the communication failure between the NEs, between the NE and the OS, or between the OSs.

  • qualityOfServiceAlarm

    Indicates that the QoS decreases. For example, an alarm is generated due to congestion, performance decrease, high resource occupancy, or bandwidth shortage.

  • processingErrorAlarm

    Indicates that an error occurs when the software or process handles data. For example, an alarm is generated due to the software error, memory overflow, version mismatch, or abortion of the program.

  • equipmentAlarm

    Indicates that a fault occurs in physical resources, including power supply, fan, processor, clock, and I/O interfaces.

  • environmentalAlarm

    Indicates that the environment cannot meet the requirements for the equipment to operate normally. For example, an alarm is generated due to improper temperature, humidity, or ventilation.

NOTE:

The alarm type is valid only for alarm traps but not event traps.

Raise or Clear

Indicates whether a fault occurs or is rectified:

  • Raise: A fault occurs.
  • Clear: A fault is rectified.
  • None: A fault may occur or be rectified.
NOTE:

Raise or Clear is valid only for alarm traps but not event traps.

Match trap

Indicates the match trap for a generated or cleared alarm.

NOTE:

The match trap is valid only for alarm traps but not event traps.

Trap Buffer Parameters

Indicates the parameters included in the trap. Parameters in a trap help in locating the fault and analyzing the trap.

VB Information Parameter

The variable binding (VB) information parameter applies to alarm location and connection to a third-party NMS. The VB information parameter includes:

  • VB OID
  • VB Name
  • VB Index
Impact on the System

Analyzes the impact of this trap on system.

Possible Causes

This part describes the causes for a trap generated by the system.

Procedure

This part describes associated traps to help in finding out the root cause for the trap and the causes for the associated traps.

Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 194704

Downloads: 1569

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next