EFM/3/NONTHRESHOLDTRAP_active

Message

EFM/3/NONTHRESHOLDTRAP_active: Nonthreshold Event occured. (IfIndex=[IfIndex], EventLogIndex=[EventLogIndex], EventLogTimestamp=[EventLogTimestamp], EventLogOUI=[TrapLogOUI], EventLogType=[TrapLogType], EventLogLocation=[TrapLogLocation], IfName=[IfName])

Description

Event occurred, such as timeout, link fault, dying gasp, or critical event.

Parameters

Parameter Name	Parameter Meaning
IfIndex	Index of interface.
EventLogIndex	Log sequence.
EventLogTimestamp	Time stamp of the event log.
TrapLogOUI	OUI of the trap.
TrapLogType	The fault type: 254: Lost Link 256: Link Fault 257: Dying Gasp 258: Critiacl Event
TrapLogLocation	Indicates where the event occurs, on the local end or the remote end: 1: local 2: remote
IfName	The name of interface.

Possible Causes

Cause 1: The local end failed to receive EFM PDUs due to a timeout.
Cause 2: Receive link fault packet the remote carried.
Cause 3: Receive Dying Gasp packet the remote carried.
Cause 4: Receive critical event packet the remote carried.

Procedure

Cause 1: The local end failed to receive EFM PDUs due to a timeout.
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 to check whether EFM is enabled on the remote device.
- 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 normally, 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.
Cause 2: Receive link fault packet the remote carried.
The same as Cause 1.
Cause 3: Receive Dying Gasp packet the remote carried.
The same as Cause 1.
Cause 4: Receive critical event packet the remote carried.
The same as Cause 1.