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

Alarm Handling

S9300, S9300E, and S9300X V200R013C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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 hwDot3ahEfmThresholdEvent

Description

EFM/3/THRESHOLDTRAP:OID [oid] 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])

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

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.4 Minor communicationsAlarm(2)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
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 (1 indicates local end, 2 indicates peer end).
EventLogWindowHi Indicates the high-order value of the monitoring interval.
EventLogWindowLo Indicates the low-order value of the monitoring interval.
EventLogThresholdHi Indicates the high-order value of the threshold of the monitoring interval.
EventLogThresholdLo Indicates the low-order value of the threshold of the monitoring interval.
EventLogValue Indicates the number of times that the threshold-crossing event occurs.
EventLogRunningTotal Indicates the number of event occurrences.
EventLogEventTotal Indicates the number of event notifications.

Impact on the System

Services cannot be forwarded.

Possible Causes

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.

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: indicates a trap about error codes. Then, go to Step 2.

    • 2: indicates a trap about error frames. Then, go to Step 3.

    • 4: indicates a trap about error frame seconds. Then, go to Step 4.

  2. Run the display this command in the interface view to check whether the efm error-code threshold 0 command is configured.

    • If so, go to Step 6.

    • If not, go to Step 5.

  3. Run the display this command in the interface view to check whether the efm error-frame threshold 0 command is configured.

    • If so, go to Step 7.

    • If not, go to Step 5.

  4. Run the display this command in the interface view to check whether the efm error-frame-second threshold 0 command is configured.

    • If so, go to Step 8.

    • If not, go to Step 5.

  5. Check whether the physical link is faulty.

    • If so, go to Step 9.

    • If not, go to Step 10.

  6. Run the efm error-code threshold threshold command in the interface view to reconfigure the threshold for detecting error frames on the current interface as required. Then, check whether the alarm is cleared.

    • If so, go to Step 11.

    • If not, go to Step 5.

  7. Run the efm error-frame threshold threshold command in the interface view to reconfigure the threshold for detecting error frames on the current interface as required. Then, check whether the alarm is cleared.

    • If so, go to Step 11.

    • If not, go to Step 5.

  8. Run the efm error-frame-second threshold threshold command in the interface view to reconfigure the threshold for detecting error frame seconds on the current interface as required. Then, check whether the alarm is cleared.

    • If so, go to Step 11.

    • If not, go to Step 5.

  9. Change the physical link and then check whether the alarm is cleared.

    • If so, go to Step 11.

    • If not, go to Step 10.

  10. Collect alarm information and configuration information, and then contact technical support personnel.
  11. End.

Related Information

None

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.5 hwDot3ahEfmNonThresholdEvent

Description

EFM/3/NONTHRESHOLDTRAP:OID [oid] Nonthreshold Event occurred. (IfIndex=[INTEGER], EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK], EventLogOUI=[OPAQUE], EventLogType=[GAUGE], EventLogLocation=[INTEGER])

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

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.5 Minor communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

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 (1 indicates local end, 2 indicates peer end).

Impact on the System

Services will be interrupted.

Possible Causes

1. The remote interface was not enabled with EFM.

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

3. The local or remote device was restarted.

4. Faults occurred at the public network side.

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.

    • 258: indicates the CriticalLink event. Then, go to Step 5.

  2. Run the display this command in the interface view of the remote device to check whether EFM is enabled.

    • If so, go to Step 6.

    • If not, go to Step 8.

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

    • If so, go to Step 9.

    • If not, go to Step 6.

  4. Check whether the remote device is being restarted.

    • If so, go to Step 10.

    • If not, go to Step 12.

  5. Check whether a fault occurs on the module associated with EFM.

    • If so, go to Step 7.

    • If not, go to Step 12.

  6. Check whether the physical link is faulty.

    • If so, go to Step 11.

    • If not, go to Step 12.

  7. Restore the module associated with EFM, and then check whether the alarm is cleared.

    • If so, go to Step 13.

    • If not, go to Step 12.

  8. 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 13.

    • If not, go to Step 12.

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

    • If so, go to Step 13.

    • If not, go to Step 6.

  10. After the remote device works properly, check whether the alarm is cleared.

    • If so, go to Step 13.

    • If not, go to Step 12.

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

    • If so, go to Step 13.

    • If not, go to Step 12.

  12. Collect alarm information and configuration information, and then contact technical support personnel.
  13. End.

Related Information

None

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.8 hwDot3ahEfmRemoteDyingGaspEvent

Description

EFM/3/DYINGGASP: OID [oid] Remote DyingGasp Event occurred. (IfIndex=[INTEGER], RemoteMacAddress=[OCTET], IfName=[OCTET])

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

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.8 Minor processingErrorAlarm (4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

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

Impact on the System

Services on the remote device are unavailable.

Possible Causes

Cause 1:

The remote device restarts.

Cause 2:

The remote device is powered off.

Procedure

  1. After the remote device restarts, run the display efm session command to check whether EFM State is Detect or Discovery.

    • If EFM State is Detect, go to Step 3.
    • If EFM State is Discovery, go to Step 2.

  2. Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

Related Information

None.

EFM_1.3.6.1.4.1.2011.5.25.136.1.6.17 hwDot3ahEfmNonThresholdRecovery

Description

EFM/3/NONTHRDRECV:OID [OID] Nonthreshold trap recovered.(IfIndex=[INTEGER], EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK], TrapLogOUI=[OPAQUE], TrapLogType=[GAUGE], TrapLogLocation=[INTEGER])

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

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.17 Minor communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

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.

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 hwDot3ahEfmLoopbackFailed

Description

EFM/5/LOOPBACKFAIL:OID [OID] 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.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.136.1.6.29 Indeterminate qualityOfServiceAlarm (3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Interface index

IfName

Interface name

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.

  2. Then check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 6.

    • If the alarm is not cleared, go to Step 3.

  3. 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.

  4. Check whether the physical link is working properly.

    • If the physical link is working properly, go to Step 5.
    • If the physical link is not working properly, troubleshoot the link fault (for details, see "Physical Interconnection Troubleshooting").

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 5061

Downloads: 6

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