- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
01-DISMAN-EVENT-MIB | 101.11 KB |
Contents
DISMAN-EVENT-MIB
About this MIB
This MIB provides an automatic and distributed monitoring and management mechanism for MIB objects. By periodically monitoring MIB objects., the system automatically triggers the predefined notifications or set operations when the monitored objects meet the trigger conditions.
MIB file name
rfc2981-disman-event.mib
Notifications
mteTriggerFired
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.88.2.0.1 |
A notification was triggered by a trigger test. |
Informational |
Warning |
N/A |
ON |
Notification triggers
If an existence trigger test is configured, this notification is generated when the state of the monitored object changes from absent to present or from present to absent, or the value of the object changes.
If a Boolean trigger test is configured, this notification is generated if the comparison result for the value of the monitored object and the value of mteTriggerBooleanValue meets the trigger condition. If the comparison result changes from meeting the trigger condition to not meeting the trigger condition and then changing back to meeting the trigger condition, this notification is generated again. In other situations, this notification is not generated.
System impact
No impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable event-mib command.
OFF
CLI: Use the undo snmp-agent trap enable event-mib command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.88.2.1.1 (mteHotTrigger) |
Trigger name |
N/A |
SnmpAdminString |
OCTET STRING (1..32) |
1.3.6.1.2.1.88.2.1.2 (mteHotTargetName) |
Target host name. |
N/A |
SnmpAdminString |
OCTET STRING (0..255) |
1.3.6.1.2.1.88.2.1.3(mteHotContextName) |
Context name. |
N/A |
SnmpAdminString |
OCTET STRING (0..32) |
1.3.6.1.2.1.88.2.1.4(mteHotOID) |
Monitored object OID. |
N/A |
OBJECT IDENTIFIER |
Standard MIB values. |
1.3.6.1.2.1.88.2.1.5(mteHotValue) |
Value of the monitored object. |
N/A |
Integer32 |
Standard MIB values. |
Recommended action
When an Event MIB monitor event is triggered, determine whether to process the event and take the corresponding action according to the OIDs and values of variables carried in the trap.
mteTriggerRising
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.88.2.0.2 |
A rising alarm event was triggered. |
Informational |
Warning |
N/A |
ON |
Notification triggers
If a threshold trigger test is configured and the value of mteTriggerThresholdStartup is rising or risingOrFaling, this notification is generated when the monitored object meets the trigger condition.
· The value of the monitored object is greater than or equal to the rising threshold, this notification is generated.
· The difference between the current sampled value and the previous sampled value is greater than or equal to the delta rising threshold, this notification is generated.
If the value of the monitored object crosses a threshold multiple times in succession, the managed device triggers an alarm event only for the first crossing. For example, if the value of a sampled object crosses the rising threshold multiple times before it crosses the falling threshold, only the first crossing triggers a rising alarm event.
System impact
No impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable event-mib command.
OFF
CLI: Use the undo snmp-agent trap enable event-mib command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.88.2.1.1 (mteHotTrigger) |
Trigger name. |
N/A |
SnmpAdminString |
OCTET STRING (1..32) |
1.3.6.1.2.1.88.2.1.2 (mteHotTargetName) |
Target host name. |
N/A |
SnmpAdminString |
OCTET STRING (0..255) |
1.3.6.1.2.1.88.2.1.3(mteHotContextName) |
Context name. |
N/A |
SnmpAdminString |
OCTET STRING (0..32) |
1.3.6.1.2.1.88.2.1.4(mteHotOID) |
Monitored object OID. |
N/A |
OBJECT IDENTIFIER |
Standard MIB values. |
1.3.6.1.2.1.88.2.1.5(mteHotValue) |
Value of the monitored object. |
N/A |
Integer32 |
Standard MIB values. |
Recommended action
When an Event MIB monitored object triggers a rising alarm event, determine whether to process the event and take the corresponding action according to the OIDs and values of variables carried in the trap.
mteTriggerFalling
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.88.2.0.3 |
A falling alarm event was triggered |
Informational |
Warning |
N/A |
ON |
Notification triggers
If the value of mteTriggerThresholdStartup is falling or risingOrFaling, this notification is generated when the monitored object meets the trigger condition.
· If the value of the monitored object is smaller than or equal to the falling threshold, this notification is generated.
· If the difference between the current sampled value and the previous sampled value is smaller than or equal to the delta falling threshold, this notification is generated.
If the value of the monitored object crosses a threshold multiple times in succession, the managed device triggers an alarm event only for the first crossing. For example, if the value of a sampled object crosses the falling threshold multiple times before it crosses the rising threshold, only the first crossing triggers a falling alarm event.
System impact
No impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable event-mib command.
OFF
CLI: Use the undo snmp-agent trap enable event-mib command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.88.2.1.1 (mteHotTrigger) |
Trigger name. |
N/A |
SnmpAdminString |
OCTET STRING (1..32) |
1.3.6.1.2.1.88.2.1.2 (mteHotTargetName) |
Target host name. |
N/A |
SnmpAdminString |
OCTET STRING (0..255) |
1.3.6.1.2.1.88.2.1.3(mteHotContextName) |
Context name. |
N/A |
SnmpAdminString |
OCTET STRING (0..32) |
1.3.6.1.2.1.88.2.1.4(mteHotOID) |
Monitored object OID. |
N/A |
OBJECT IDENTIFIER |
Standard MIB values. |
1.3.6.1.2.1.88.2.1.5(mteHotValue) |
Value of the monitored object. |
N/A |
Integer32 |
Standard MIB values. |
Recommended action
When an Event MIB monitored object triggers a failing alarm event, determine whether to process the event and take the corresponding action according to the OIDs and values of variables carried in the trap.
mteTriggerFailure
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.88.2.0.4 |
Trigger test failure notification. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the Event MIB fails to obtain values for monitored objects.
System impact
No impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable event-mib command.
OFF
CLI: Use the undo snmp-agent trap enable event-mib command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.88.2.1.1(mteHotTrigger) |
Trigger name. |
N/A |
SnmpAdminString |
OCTET STRING (1..32) |
1.3.6.1.2.1.88.2.1.2(mteHotTargetName) |
Target host name. |
N/A |
SnmpAdminString |
OCTET STRING (0..255) |
1.3.6.1.2.1.88.2.1.3(mteHotContextName) |
Context name. |
N/A |
SnmpAdminString |
OCTET STRING (0..32) |
1.3.6.1.2.1.88.2.1.4(mteHotOID) |
Monitored object OID. |
N/A |
OBJECT IDENTIFIER |
Standard MIB values. |
1.3.6.1.2.1.88.2.1.6(mteFailedReason) |
Failure reason |
N |
INTEGER |
localResourceLack(-1),, badDestination(-2),, destinationUnreachable(-3),, noResponse(-4),, badType(-5),, sampleOverrun(-6),, noError(0),, tooBig(1),, noSuchName(2),, badValue(3),, readOnly(4),, genErr(5),, noAccess(6),, wrongType(7),, wrongLength(8),, wrongEncoding(9),, wrongValue(10),, noCreation(11),, inconsistentValue(12),, resourceUnavailable(13),, commitFailed(14),, undoFailed(15),, authorizationError(16),, notWritable(17),, inconsistentName(18) |
Recommended action
Take actions according to failure cause and destination variable OID, for example:
1. Identify whether the destination variable OID exists from the MIB tree. If the destination variable OID does not exist or the object to be monitored is the instance for this variable, change the destination variable OID.
2. Verify that the attribute of the destination variable OID node complies with trigger settings. For more information about how to configure trigger settings, see the Event MIB configuration guide.
3. Verify that the RBAC permission of the login user allows the user to configure and manage MIB objects.
4. If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
mteEventSetFailure
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.88.2.0.5 |
Event set-action failure notification. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the set action is specified and the system fails to perform a set operation in response to an event.
System impact
No impact on the system.
Status control
ON
CLI: Use the snmp-agent trap enable event-mib command.
OFF
CLI: Use the undo snmp-agent trap enable event-mib command.
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.88.2.1.1(mteHotTrigger) |
Trigger name. |
N/A |
SnmpAdminString |
OCTET STRING (1..32) |
1.3.6.1.2.1.88.2.1.2(mteHotTargetName) |
Target host name. |
N/A |
SnmpAdminString |
OCTET STRING (0..255) |
1.3.6.1.2.1.88.2.1.3(mteHotContextName) |
Context name. |
N/A |
SnmpAdminString |
OCTET STRING (0..32) |
1.3.6.1.2.1.88.2.1.4(mteHotOID) |
Monitored object OID. |
N/A |
OBJECT IDENTIFIER |
Standard MIB values. |
1.3.6.1.2.1.88.2.1.6(mteFailedReason) |
Failure reason |
N/A |
INTEGER |
localResourceLack(-1),, badDestination(-2),, destinationUnreachable(-3),, noResponse(-4),, badType(-5),, sampleOverrun(-6),, noError(0),, tooBig(1),, noSuchName(2),, badValue(3),, readOnly(4),, genErr(5),, noAccess(6),, wrongType(7),, wrongLength(8),, wrongEncoding(9),, wrongValue(10),, noCreation(11),, inconsistentValue(12),, resourceUnavailable(13),, commitFailed(14),, undoFailed(15),, authorizationError(16),, notWritable(17),, inconsistentName(18) |
Recommended action
Deploy the configuration as needed according to the set failure cause in the trap.