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

Parent Topic: EFM
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >