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).
EFM

EFM

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.4 threshold

Description

Threshold event occured. (IfIndex=[INTEGER], EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK], EventLogOui=[OPAQUE], EventLogType=[GAUGE], EventLogLocation=[INTEGER], EventLogWindowHi=[GAUGE], EventLogWindowLo=[GAUGE], EventLogThresholdHi=[GAUGE], EventLogThresholdLo=[GAUGE], EventLogValue=[COUNTER64], EventLogRunningTotal=[COUNTER64], EventLogEventTotal=[GAUGE], IfName=[OCTET])

The number of errored frames, errored codes, or errored frame seconds exceeded the set threshold within the specified period.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Error

Mnemonic Code

threshold

Trap OID

1.3.6.1.4.1.2011.5.25.136.1.6.4

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

IfIndex

Interface index.

EventLogIndex

Index of ta printed log.

EventLogTimestamp

Timestamp that records when an event occurred.

EventLogOui

Name of an outbound interface of an event.

EventLogType

Type of an event.

EventLogLocation

Where the event occurs, on the local or remote end (1 indicates local end, 2 indicates peer end).

EventLogWindowHi

High-order value of a monitoring interval.

EventLogWindowLo

Low-order value of a monitoring interval.

EventLogThresholdHi

High-order value of the threshold of a monitoring interval.

EventLogThresholdLo

Low-order value of the threshold of a monitoring interval.

EventLogValue

Number of times that a threshold-crossing event occurs.

EventLogRunningTotal

Number of event occurrences.

EventLogEventTotal

Number of event notifications.

IfName

Interface name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.2

hwDot3ahEfmEventLogTimestamp

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.3

hwDot3ahEfmEventLogOui

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.4

hwDot3ahEfmEventLogType

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.5

hwDot3ahEfmEventLogLocation

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.6

hwDot3ahEfmEventLogWindowHi

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.7

hwDot3ahEfmEventLogWindowLo

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.8

hwDot3ahEfmEventLogThresholdHi

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.9

hwDot3ahEfmEventLogThresholdLo

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.10

hwDot3ahEfmEventLogValue

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.11

hwDot3ahEfmEventLogRunningTotal

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.12

hwDot3ahEfmEventLogEventTotal

ifIndex

hwDot3ahEfmEventLogIndex

Impact on the System

Services cannot be forwarded.

Possible Causes

Cause 1:

The user configured the efm error-code threshold 0, efm error-frame threshold 0 or efm error-frame-second threshold 0 command on the interface.

Cause 2:

The physical link became faulty, causing the error frame or error code.

Procedure
  1. Check the value of the EventLogType field in the trap:
  • 1: an errored code alarm. Then go to Step 2.
  • 2: an errored frame alarm. Then go to Step 3.
  • 4: an errored frame second alarm. Then go to Step 4.
  1. Run the display this command in the interface view. Check whether the efm error-code threshold 0 command is displayed in the command output.

    • If this command is displayed, go to Step 6.
    • If this command is not displayed, go to Step 5.

  2. Run the display this command in the interface view. Check whether the efm error-frame threshold 0 command is displayed in the command output.

    • If this command is displayed, go to Step 7.
    • If this command is not displayed, go to Step 5.

  3. Run the display this command in the interface view. Check whether the efm error-frame-second threshold 0 command is displayed in the command output.

    • If this command is displayed, go to Step 8.
    • If this command is not displayed, go to Step 5.

  4. Check whether a physical link fails.

    • If the physical link is working properly, go to Step 9.
    • If the physical link fails, go to Step 10.

  5. Run the efm error-code threshold threshold command in the interface view to set the EFM errored code detection threshold for the interface. Check whether a new event is continuously reported.

    • If a new event is continuously reported, go to Step 10.
    • If no new event is continuously reported, go to Step 11.

  6. Run the efm error-frame threshold threshold command in the interface view to set the EFM errored frame detection threshold for the interface. Check whether a new event is continuously reported.

    • If a new event is continuously reported, go to Step 10.
    • If no new event is continuously reported, go to Step 11.

  7. Run the efm error-frame-second threshold threshold command in the interface view to set the EFM errored frame seconds detection threshold for the interface. Check whether a new event is continuously reported.

    • If a new event is continuously reported, go to Step 10.
    • If no new event is continuously reported, go to Step 11.

  8. Rectify the physical link fault and check whether a new event is continuously reported.

    • If a new event is continuously reported, go to Step 10.
    • If no new event is continuously reported, go to Step 11.

  9. Collect the alarm, log, and configuration information, and then contact technical support personnel.
  10. End.

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.5 nonthreshold

Description

Nonthreshold Event occured. (IfIndex=[INTEGER], EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK], EventLogOUI=[OPAQUE], EventLogType=[GAUGE], EventLogLocation=[INTEGER], IfName=[OCTET])

None-threshold-crossing events occur on the link, including LinkLost, LinkFault and DyingGasp.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Error

Mnemonic Code

nonthreshold

Trap OID

1.3.6.1.4.1.2011.5.25.136.1.6.5

Alarm ID

0x00f10002

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.17 nonthredholdrecovery

Parameters

Parameter

Description

IfIndex

Indicates the interface index.

EventLogIndex

Indicates the index of the printed log.

EventLogTimestamp

Indicates the time stamp that records when the event occurs.

EventLogOUI

Indicates the OUI of an event.

EventLogType

Indicates the type of an event.

EventLogLocation

Indicates where the event occurs, on the local end or the remote end.

IfName

Indicates the interface name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.2

hwDot3ahEfmEventLogTimestamp

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.3

hwDot3ahEfmEventLogOui

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.4

hwDot3ahEfmEventLogType

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.5

hwDot3ahEfmEventLogLocation

ifIndex

hwDot3ahEfmEventLogIndex

Impact on the System

Services will be interrupted.

Possible Causes

Cause 1:

The remote interface was not enabled with EFM.

Cause 2:

The interface was shut down; or the physical link went Down.

Cause 3:

The local or remote device was restarted.

Procedure
  1. Check the value of the EventLogType field in the trap:
  • 254: indicates the timeout. Then, go to Step 2.
  • 256: indicates that the local interface is shut down. Then, go to Step 3.
  • 257: indicates the DyingGasp event. Then, go to Step 4.
  1. Run the display this command in the interface view to check whether EFM is enabled on the remote device.

    • If so, go to Step 5.
    • If not, go to Step 6.

  2. Run the display this command in the interface view to check whether the local interface is shut down.

    • If so, go to Step 7.
    • If not, go to Step 5.

  3. Check whether the remote device is being restarted.

    • If so, go to Step 8.
    • If not, go to Step 10.

  4. Check whether the physical link is faulty.

    • If so, go to Step 9.
    • If not, go to Step 10.

  5. Run the efm enable command in the interface view of the remote device to enable EFM. Then, check whether the alarm is cleared.

    • If so, go to Step 11.
    • If not, go to Step 10.

  6. Run the undo shutdown command in the interface view to check whether the alarm is cleared.

    • If so, go to Step 11.
    • If not, go to Step 5.

  7. After the remote device works normally, check whether the alarm is cleared.

    • If so, go to Step 11.
    • If not, go to Step 10.

  8. Replace the physical link and then check whether the alarm is cleared.

    • If so, go to Step 11.
    • If not, go to Step 10.

  9. Collect trap messages, log messages, and configurations, and then contact the technical support personnel.
  10. End.

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.8 dyinggasp

Description

Remote DyingGasp Event occurred. (IfIndex=[INTEGER], RemoteMacAddress=[OCTET], IfName=[OCTET])

An unrecoverable event occurs, for example, the system or a board restarts, or the device is powered off.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Error

Mnemonic Code

dyinggasp

Trap OID

1.3.6.1.4.1.2011.5.25.136.1.6.8

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

IfIndex

Interface index of the peer device received by the local device

RemoteMacAddress

MAC address of the remote device

IfName

Interface name of the peer device received by the local device

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.136.1.2.2.3.1.1

hwDot3ahEfmPeerMacAddress

ifIndex

1.3.6.1.2.1.2.2.1.2

None

ifDescr

Impact on the System

Services on the remote device are unavailable.

Possible Causes

Cause 1:

The remote device restarts.

Cause 2:

The board on the remote device restarts.

Cause 3:

The remote device is powered off.

Procedure
  1. After the remote device or the board on the remote device restarts, run the display efm session command to check the EFM status.
  • If yes, go to Step 3.
  • If no, go to Step 2.
  1. Collect configuration, trap messages, and log messages, and then contact technical personnel.
  2. End.

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.17 nonthredholdrecovery

Description

Nonthreshold trap recovered. (IfIndex=[INTEGER], EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK], TrapLogOUI=[OPAQUE], TrapLogType=[GAUGE], TrapLogLocation=[INTEGER], IfName=[OCTET])

The trap about handshake timeout or a link event was cleared.

The trap about handshake timeout, a link event, or DyingGasp was cleared.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Error

Mnemonic Code

nonthredholdrecovery

Trap OID

1.3.6.1.4.1.2011.5.25.136.1.6.17

Alarm ID

0x00f10002

Alarm Type

communicationsAlarm

Raise or Clear

Clear

Match trap

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.5 nonthreshold

Parameters

Parameter

Description

IfIndex

Indicates the interface index.

EventLogIndex

Indicates the index of the printed log.

EventLogTimestamp

Indicates the time stamp that records when the event occurs.

TrapLogOUI

Indicates the OUI of an event.

TrapLogType

Indicates the type of an event.

TrapLogLocation

Indicates where the event occurs, on the local end or the remote end.

IfName

Indicates the interface name.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.2

hwDot3ahEfmEventLogTimestamp

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.3

hwDot3ahEfmEventLogOui

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.4

hwDot3ahEfmEventLogType

ifIndex

hwDot3ahEfmEventLogIndex

1.3.6.1.4.1.2011.5.25.136.1.2.2.7.1.5

hwDot3ahEfmEventLogLocation

ifIndex

hwDot3ahEfmEventLogIndex

Impact on the System

The system performance is not affected.

Possible Causes

The trap about handshake timeout, a link event, an urgent event, or a remote fault was cleared.

Procedure
  • This trap message is informational only, and no action is required.

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.29 loopbackfailed

Description

Interface starts loopback failed. (IfIndex=[INTEGER],IfName=[STRING])

802.3ah loopback failed after no response to an 802.3ah loopback request was received within a specified period of time.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Notice

Mnemonic Code

loopbackfailed

Trap OID

1.3.6.1.4.1.2011.5.25.136.1.6.29

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

IfIndex

Interface index

IfName

Interface name

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.2.2.1.2

ifDescr

ifIndex;

Impact on the System

EFM OAM loopback cannot be initiated.

Possible Causes

802.3ah loopback failed after no response to an 802.3ah loopback request was received within a specified period of time.

Procedure
  1. Check whether the remote interface denies the remote loopback request from the local end.

Run the display current-configuration command. Check whether the efm loopback ignore-request command is used.

  • If this command is used, the remote interface denies the request. Run the undo efm loopback ignore-request command to enable the remote interface to receive the remote loopback request. Then go to Step 2.
  • If this command is not used, the remote interface is able to receive the request. Then go to Step 3.
  1. Then check whether the alarm is cleared.

    If the alarm persists, go to Step 3.

  2. Check the EFM status.

    Run the display efm session all command. Check whether the value of the EFM State field is detect.

    • If the value of the EFM State field is detect, go to Step 5.
    • If the value of the EFM State field is not detect, go to Step 4.

  3. Check the physical link. If the physical link is faulty, see "Physical Interconnection Troubleshooting" for details about how to troubleshoot the link fault.
  4. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 192126

Downloads: 1565

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