- Table of Contents
-
- 21-Network Management and Monitoring
- 01-DISMAN-EVENT-MIB
- 02-DISMAN-PING-MIB
- 03-DISMAN-TRACEROUTE-MIB
- 04-HH3C-NQA-MIB
- 05-HH3C-NTP-MIB
- 06-HH3C-RMON-EXT2-MIB
- 07-HH3C-SNMP-EXT-MIB
- 08-RMON-MIB
- 09-RMON2-MIB
- 10-SFLOW-MIB
- 11-SNMP-FRAMEWORK-MIB
- 12-SNMP-MPD-MIB
- 13-SNMP-NOTIFICATION-MIB
- 14-SNMP-TARGET-MIB
- 15-SNMP-USER-BASED-SM-MIB
- 16-SNMP-VIEW-BASED-ACM-MIB
- 17-SNMPv2-MIB
- Related Documents
-
Title | Size | Download |
---|---|---|
01-DISMAN-EVENT-MIB | 259.77 KB |
Contents
mteResourceSampleInstanceMaximum
mteResourceSampleInstancesHigh
mteResourceSampleInstanceLacks
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
Root object
iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).dismanEventMIB(88)
Scalar objects
mteResourceSampleMinimum
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteResourceSampleMinimum (1.3.6.1.2.1.88.1.1.1) |
read-write |
Integer32 |
Integer32 (1..2147483647) |
Minimum sampling interval allowed by the system. |
Default: 1. Each trigger sampling interval must be equal to or larger than the minimum sampling interval to lessen the impact of constant sampling. Modifying this node does not affect existing triggers. |
mteResourceSampleInstanceMaximum
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteResourceSampleInstanceMaximum (1.3.6.1.2.1.88.1.1.2) |
read-write |
Unsigned32 |
Standard MIB values. |
Maximum number of object instances that can be concurrently sampled. |
A value of 0 indicates that no manual limit is specified. The limit is dynamic based on system operations and resources. Changing the maximum number of object instances that can be concurrently sampled does not affect the existing instances. If the maximum number of object instances that can be concurrently sampled is changed to a value smaller than the number of existing instances, the existing instances will continue to be sampled. |
mteResourceSampleInstances
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteResourceSampleInstances (1.3.6.1.2.1.88.1.1.3) |
read-only |
Gauge32 |
Standard MIB values. |
Number of current sampled instances. |
As per the MIB. |
mteResourceSampleInstancesHigh
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteResourceSampleInstancesHigh (1.3.6.1.2.1.88.1.1.4) |
read-only |
Gauge32 |
Standard MIB values. |
Peak number of sampled instances. |
As per the MIB. |
mteResourceSampleInstanceLacks
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteResourceSampleInstanceLacks (1.3.6.1.2.1.88.1.1.5) |
read-only |
Counter32 |
Standard MIB values. |
Number of sampling failures after the maximum number of sampled instances is reached. |
As per the MIB. |
mteTriggerFailures
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteTriggerFailures (1.3.6.1.2.1.88.1.2.1) |
read-only |
Counter32 |
Standard MIB values. |
Number of trigger test failures. |
As per the MIB. |
mteEventFailures
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteEventFailures (1.3.6.1.2.1.88.1.4.1) |
read-only |
Counter32 |
Standard MIB values. |
As per the MIB. |
Tabular objects
mteTriggerTable
About this table
Use this table to configure or obtain information about triggers, including specifying monitored objects and setting the trigger test type, sampling interval, and sampling method.
Support for operations
Create |
Edit/Modify |
Delete |
Read |
Supported |
Supported |
Supported |
Supported |
Columns
The table indexes are mteOwner and mteTriggerName.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteOwner (1.3.6.1.2.1.88.1.2.2.1.1) |
not-accessible |
SnmpAdminString |
OCTET STRING (0..32) |
Level 1 index of the table. |
Supports only SNMPv3 users. You must configure the specified SNMPv3 user as the current operator. |
mteTriggerName (1.3.6.1.2.1.88.1.2.2.1.2) |
not-accessible |
SnmpAdminString |
OCTET STRING (1..32) |
Trigger name. Level 2 index of the table. |
As per the MIB. |
mteTriggerComment (1.3.6.1.2.1.88.1.2.2.1.3) |
read-create |
SnmpAdminString |
OCTET STRING (0..255) |
Trigger description. |
The first and last spaces in the string will be automatically removed. |
mteTriggerTest (1.3.6.1.2.1.88.1.2.2.1.4) |
read-create |
BITS |
BITS {existence(0), boolean(1), threshold(2)} |
As per the MIB. |
|
mteTriggerSampleType (1.3.6.1.2.1.88.1.2.2.1.5) |
read-create |
INTEGER |
absoluteValue(1), deltaValue(2) |
As per the MIB. |
|
mteTriggerValueID (1.3.6.1.2.1.88.1.2.2.1.6) |
read-create |
OBJECT IDENTIFIER |
OBJECT IDENTIFIER |
OID of the monitored object. |
Supports only table nodes, conceptual row nodes, table column nodes, simple leaf nodes, and parent nodes of leaf nodes. |
mteTriggerValueIDWildcard (1.3.6.1.2.1.88.1.2.2.1.7) |
read-create |
TruthValue |
true(1), false(2) |
Whether to enable wildcard search for objects. |
As per the MIB. |
mteTriggerTargetTag (1.3.6.1.2.1.88.1.2.2.1.8) |
read-create |
SnmpTagValue |
OCTET STRING (0..255) |
Remote tag for the monitored object. A length of 0 indicates the local system. This object supports only the local system. |
Supports only the read operation. |
mteTriggerContextName (1.3.6.1.2.1.88.1.2.2.1.9) |
read-create |
SnmpAdminString |
OCTET STRING (0..255) |
Name of the context for the OID of the monitored object. |
As per the MIB. |
mteTriggerContextNameWildcard (1.3.6.1.2.1.88.1.2.2.1.10) |
read-create |
TruthValue |
true(1), false(2) |
Whether to enable wildcard search for contexts. |
As per the MIB. |
mteTriggerObjectsOwner (1.3.6.1.2.1.88.1.2.2.1.12) |
read-create |
SnmpAdminString |
OCTET STRING (0..32) |
Owner of the objects bound to the trigger. |
As per the MIB. |
mteTriggerObjects (1.3.6.1.2.1.88.1.2.2.1.13) |
read-create |
SnmpAdminString |
OCTET STRING (0..32) |
Objects bound to the trigger. |
As per the MIB. |
mteTriggerEnabled (1.3.6.1.2.1.88.1.2.2.1.14) |
read-create |
TruthValue |
true(1), false(2) |
Whether to enable the trigger When the value is false, the trigger is not sampled. |
Supports only the read operation. The read value for this object is true(1) if the state of the mteTriggerEntryStatus row is active. |
mteTriggerEntryStatus (1.3.6.1.2.1.88.1.2.2.1.15) |
read-create |
RowStatus |
active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6) |
Row status. |
As per the MIB. |
mteTriggerBooleanTable
About this table
Use this table to configure or obtain information about Boolean trigger tests. It specifies the Boolean trigger test type and the reference value, configures whether to enable the event for the first sampling, and specifies the monitored objects and trigger event.
Support for operations
Create |
Edit/Modify |
Delete |
Read |
Not supported |
Supported |
Not supported |
Supported |
Columns
The table indexes are mteOwner and mteTriggerName.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteTriggerBooleanComparison (1.3.6.1.2.1.88.1.2.5.1.1) |
read-write |
INTEGER |
unequal(1), equal(2), less(3), lessOrEqual(4), greater(5), greaterOrEqual(6) |
Type of a Boolean trigger test. The comparison objects are mteTriggerValueID and mteTriggerBooleanValue. |
As per the MIB. |
mteTriggerBooleanValue (1.3.6.1.2.1.88.1.2.5.1.2) |
read-write |
Integer32 |
Integer32 (-2147483648..2147483647) |
Reference value for the Boolean trigger test. |
As per the MIB. |
mteTriggerBooleanStartup (1.3.6.1.2.1.88.1.2.5.1.3) |
read-write |
TruthValue |
true(1), false(2) |
Whether the event is enabled for the first sampling. |
As per the MIB. |
mteTriggerBooleanObjectsOwner (1.3.6.1.2.1.88.1.2.5.1.4) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Owner of the Boolean trigger test objects. |
Supports only SNMPv3 users. The configuration must be the same as that of the mteOwner object. |
mteTriggerBooleanObjects (1.3.6.1.2.1.88.1.2.5.1.5) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Name of the Boolean trigger test objects. |
As per the MIB. |
mteTriggerBooleanEventOwner (1.3.6.1.2.1.88.1.2.5.1.6) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Owner of the Boolean event. |
Supports only SNMPv3 users. The configuration must be the same as that of the mteOwner object. |
mteTriggerBooleanEvent (1.3.6.1.2.1.88.1.2.5.1.7) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Name of the Boolean event. |
As per the MIB. |
mteTriggerThresholdTable
About this table
Use this table to configure or obtain information about threshold trigger tests. It specifies the threshold trigger test type for the first sampling, sets the absolute or delta rising or falling threshold, and configures the monitored objects and the trigger event.
Support for operations
Create |
Edit/Modify |
Delete |
Read |
Not supported |
Supported |
Not supported |
Supported |
Columns
The table indexes are mteOwner and mteTriggerName.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteTriggerThresholdStartup (1.3.6.1.2.1.88.1.2.6.1.1) |
read-write |
INTEGER |
rising(1), falling(2), risingOrFalling(3) |
Threshold trigger test for the first sampling. |
As per the MIB. |
mteTriggerThresholdRising (1.3.6.1.2.1.88.1.2.6.1.2) |
read-write |
Integer32 |
Integer32 (-2147483648..2147483647) |
Absolute rising threshold. |
As per the MIB. |
mteTriggerThresholdFalling (1.3.6.1.2.1.88.1.2.6.1.3) |
read-write |
Integer32 |
Integer32 (-2147483648..2147483647) |
Absolute falling threshold. |
As per the MIB. |
mteTriggerThresholdDeltaRising (1.3.6.1.2.1.88.1.2.6.1.4) |
read-write |
Integer32 |
Integer32 (-2147483648..2147483647) |
Delta rising threshold. |
As per the MIB. |
mteTriggerThresholdDeltaFalling (1.3.6.1.2.1.88.1.2.6.1.5) |
read-write |
Integer32 |
Integer32 (-2147483648..2147483647) |
Delta falling threshold. |
As per the MIB. |
mteTriggerThresholdObjectsOwner (1.3.6.1.2.1.88.1.2.6.1.6) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Owner of the threshold test objects. |
Do not configure this object or configure the same settings for this object as the mteOwner object in the Trigger table. |
mteTriggerThresholdObjects (1.3.6.1.2.1.88.1.2.6.1.7) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Name of the threshold test objects. |
As per the MIB. |
mteTriggerThresholdRisingEventOwner (1.3.6.1.2.1.88.1.2.6.1.8) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Owner of the rising event. |
Do not configure this object or configure the same settings for this object as the mteOwner object in the Trigger table. |
mteTriggerThresholdRisingEvent (1.3.6.1.2.1.88.1.2.6.1.9) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Name of the rising event. |
As per the MIB. |
mteTriggerThresholdFallingEventOwner (1.3.6.1.2.1.88.1.2.6.1.10) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Owner of the falling event. |
Do not configure this object or configure the same settings for this object as the mteOwner object in the Trigger table. |
mteTriggerThresholdFallingEvent (1.3.6.1.2.1.88.1.2.6.1.11) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Name of the falling event. |
As per the MIB. |
mteTriggerThresholdDeltaRisingEventOwner (1.3.6.1.2.1.88.1.2.6.1.12) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Owner of the Delta rising event. |
Do not configure this object or configure the same settings for this object as the mteOwner object in the Trigger table. |
mteTriggerThresholdDeltaRisingEvent (1.3.6.1.2.1.88.1.2.6.1.13) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Name of the Delta rising event. |
As per the MIB. |
mteTriggerThresholdDeltaFallingEventOwner (1.3.6.1.2.1.88.1.2.6.1.14) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Owner of the Delta falling event. |
Do not configure this object or configure the same settings for this object as the mteOwner object in the Trigger table. |
mteTriggerThresholdDeltaFallingEvent (1.3.6.1.2.1.88.1.2.6.1.15) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Name of the Delta falling event. |
As per the MIB. |
mteObjectsTable
About this table
Use this table to configure or obtain monitored objects, including specifying the name of a monitored object and binding the OID of the object to a trigger.
Support for operations
Create |
Edit/Modify |
Delete |
Read |
Supported |
Not supported |
Supported |
Supported |
Columns
The table indexes are mteOwner, mteObjectsName, and mteObjectsIndex.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteObjectsName (1.3.6.1.2.1.88.1.3.1.1.1) |
not-accessible |
SnmpAdminString |
OCTET STRING (1..32) |
A locally-unique, administratively assigned name for a group of objects. Level 2 index. |
As per the MIB. |
mteObjectsIndex (1.3.6.1.2.1.88.1.3.1.1.2) |
not-accessible |
Unsigned32 |
Unsigned32 (1..2147483647) |
An arbitrary integer for the purpose of identifying individual objects within a mteObjectsName group. Level 3 index. |
As per the MIB. |
mteObjectsID (1.3.6.1.2.1.88.1.3.1.1.3) |
read-create |
OBJECT IDENTIFIER |
OBJECT IDENTIFIER |
OID of the objects. |
Supports one of the following node types: table, conceptual row, table column, simple leaf, and parent node of a leaf node. |
mteObjectsIDWildcard (1.3.6.1.2.1.88.1.3.1.1.4) |
read-create |
TruthValue |
true(1), false(2) |
Whether to enable wildcard matching. |
As per the MIB. |
mteObjectsEntryStatus (1.3.6.1.2.1.88.1.3.1.1.5) |
read-create |
RowStatus |
active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6) |
Row status. |
Supports only createAndGo, active, and destroy. |
mteEventTable
About this table
Use this table to configure or obtain information about events, including configuring the event name, event description, and event action type.
Support for operations
Create |
Edit/Modify |
Delete |
Read |
Supported |
Supported |
Supported |
Supported |
Columns
The table indexes are mteOwner and mteEventName.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteEventName (1.3.6.1.2.1.88.1.4.2.1.1) |
not-accessible |
SnmpAdminString |
OCTET STRING (1..32) |
Event name. |
As per the MIB. |
mteEventComment (1.3.6.1.2.1.88.1.4.2.1.2) |
read-create |
SnmpAdminString |
OCTET STRING (0..255) |
Event description. |
The first and last spaces will be deleted automatically. |
mteEventActions (1.3.6.1.2.1.88.1.4.2.1.3) |
read-create |
BITS |
BITS { notification(0), set(1)} |
Event action type. |
As per the MIB. |
mteEventEnabled (1.3.6.1.2.1.88.1.4.2.1.4) |
read-create |
TruthValue |
true(1), false(2) |
Enabling status of the event. |
Supports only the read operation. When the value of mteEventEntryStatus is active, the return value of this object for the read operation is true(1). |
mteEventEntryStatus (1.3.6.1.2.1.88.1.4.2.1.5) |
read-create |
RowStatus |
active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6) |
Row status. |
As per the MIB. |
mteEventNotificationTable
About this table
Use this table to configure or obtain information about notifications, including specifying the OID of a notification and binding objects to the notification.
Support for operations
Create |
Edit/Modify |
Delete |
Read |
Not supported |
Supported |
Not supported |
Supported |
Columns
The table indexes are mteOwner and mteEventName.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteEventNotification (1.3.6.1.2.1.88.1.4.3.1.1) |
read-write |
OBJECT IDENTIFIER |
Standard MIB values. |
Notification OID. |
As per the MIB. |
mteEventNotificationObjectsOwner (1.3.6.1.2.1.88.1.4.3.1.2) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Owner of the objects bound to the notification. |
Do not configure this object or configure the same settings as the mteOwner object in the Event table. |
mteEventNotificationObjects (1.3.6.1.2.1.88.1.4.3.1.3) |
read-write |
SnmpAdminString |
OCTET STRING (0..32) |
Name of the objects bound to the notification. |
As per the MIB. |
mteEventSetTable
About this table
Use this MIB to configure or obtain information about set objects, including specifying an event for set objects and setting a value for the objects.
Support for operations
Create |
Edit/Modify |
Delete |
Read |
Not supported |
Supported |
Not supported |
Supported |
Columns
The table indexes are mteOwner and mteEventName.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
mteEventSetObject (1.3.6.1.2.1.88.1.4.4.1.1) |
read-write |
OBJECT IDENTIFIER |
Standard MIB values. |
OID of a set-action object. |
Supports only the following types of nodes: table, conceptual row, table column, simple leaf, and parent node of a leaf node. |
mteEventSetObjectWildcard (1.3.6.1.2.1.88.1.4.4.1.2) |
read-write |
TruthValue |
true(1), false(2) |
Whether to enable wildcard matching. |
As per the MIB. |
mteEventSetValue (1.3.6.1.2.1.88.1.4.4.1.3) |
read-write |
Integer32 |
Integer32 (-2147483648..2147483647) |
Value of the set-action object. |
As per the MIB. |
mteEventSetTargetTag (1.3.6.1.2.1.88.1.4.4.1.4) |
read-write |
SnmpTagValue |
OCTET STRING (0..255) |
Remote tag for the set-action object. |
Supports only the read operation. This object does not support the edit/modify operation. |
mteEventSetContextName (1.3.6.1.2.1.88.1.4.4.1.5) |
read-write |
SnmpAdminString |
OCTET STRING (0..255) |
Context for the set-action object. |
OCTET STRING (0..32) |
mteEventSetContextNameWildcard (1.3.6.1.2.1.88.1.4.4.1.6) |
read-write |
TruthValue |
true(1), |
Whether to enable wildcard matching. |
As per the 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.