- Table of Contents
-
- 13-Network Management and Monitoring
- 01-DISMAN-EVENT-MIB
- 02-DISMAN-PING-MIB
- 03-DISMAN-TRACEROUTE-MIB
- 04-HH3C-MIRRORGROUP-MIB
- 05-HH3C-NQA-MIB
- 06-HH3C-NTP-MIB
- 07-HH3C-RMON-EXT2-MIB
- 08-HH3C-SNMP-EXT-MIB
- 09-RMON-MIB
- 10-RMON2-MIB
- 11-SFLOW-MIB
- 12-SNMP-FRAMEWORK-MIB
- 13-SNMP-MPD-MIB
- 14-SNMP-NOTIFICATION-MIB
- 15-SNMP-TARGET-MIB
- 16-SNMP-USER-BASED-SM-MIB
- 17-SNMP-VIEW-BASED-ACM-MIB
- 18-SNMPv2-MIB
- Related Documents
-
Title | Size | Download |
---|---|---|
09-RMON-MIB | 92.98 KB |
Contents
RMON-MIB
About this MIB
Use this MIB to monitor data traffic on a network segment or the entire network.
MIB file name
rfc2819-rmon.mib
Root object
iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).rmon(16)
Tabular objects
eventTable
About this table
Use this table to configure event entries.
Support for operations
Create:Supported.
You must specify eventStatus when creating a row of instances. If the buildruns of the instances exceed the maximum specification, the creation fails.
Edit/Modify:Not supported
Delete:Supported
Read:Supported
Columns
The table index is eventIndex.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
eventLastTimeSent (1.3.6.1.2.1.16.9.1.1.5) |
read-only |
TimeTicks |
TimeTicks (0..4294967295) |
Time at which the most recent event occurs. |
As per the MIB. |
eventOwner (1.3.6.1.2.1.16.9.1.1.6) |
read-create |
OwnerString |
OCTET STRING (0..127) |
Event owner. |
Not-displayable characters or question marks are not allowed. Default value: Zero-length string. |
eventStatus (1.3.6.1.2.1.16.9.1.1.7) |
read-create |
EntryStatus |
valid(1), createRequest(2), underCreation(3), invalid(4) |
Event status. |
As per the MIB. |
logTable
About this table
Use this table to obtain event logs.
Support for operations
Create:Not supported
Edit/Modify:Not supported
Delete:Not supported
Read:Supported
Columns
The table indexes are logEventIndex and logIndex.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
logEventIndex (1.3.6.1.2.1.16.9.2.1.1) |
read-only |
Integer32 |
Integer32 (1..65535) |
Index of the event entry that generated this log entry. |
As per the MIB. |
logIndex (1.3.6.1.2.1.16.9.2.1.2) |
read-only |
Integer32 |
Integer32 (1..2147483647) |
Index of the log entry. |
As per the MIB. |
logTime (1.3.6.1.2.1.16.9.2.1.3) |
read-only |
TimeTicks |
Standard MIB values. |
Time when the log entry was created. |
As per the MIB. |
logDescription (1.3.6.1.2.1.16.9.2.1.4) |
read-only |
DisplayString |
OCTET STRING (0..255) |
Description of the event that activated this log entry. |
As per the MIB. |
Notifications
risingAlarm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.16.0.1 |
A variable of an alarm entry crossed its rising threshold. |
Informational |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when a variable of an alarm entry crosses its rising threshold and the triggered event is to send SNMP notifications.
System impact
No impact on services.
Status control
ON
CLI: Use the rmon event entry-number [ description string ] { log-trap security-string | trap security-string } [ owner text ] command.
OFF
CLI: Use the rmon event entry-number [ description string ] { log | none } [ owner text ] command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.16.3.1.1.1 (alarmIndex) |
Index of the alarm entry |
alarmIndex |
Integer32 |
1..65535 |
1.3.6.1.2.1.16.3.1.1.3 (alarmVariable) |
Variable to be sampled |
alarmIndex |
OBJECT IDENTIFIER |
Standard MIB values. |
1.3.6.1.2.1.16.3.1.1.4 (alarmSampleType) |
Sampling type |
alarmIndex |
INTEGER |
absoluteValue(1), deltaValue(2) |
1.3.6.1.2.1.16.3.1.1.5 (alarmValue) |
Sampled value |
alarmIndex |
Integer32 |
Standard MIB values. |
1.3.6.1.2.1.16.3.1.1.7 (alarmRisingThreshold) |
Rising threshold |
alarmIndex |
Integer32 |
Standard MIB values. |
Recommended action
To resolve the issue:
1.Execute the display rmon alarm command in any view to check information about the monitored variable and rising threshold. Locate and remove the reason causing the notification.
If the rising threshold is inappropriate, execute the rmon alarm command in system view to change the rising threshold.
2.If the issue persists, collect alarm information and configuration data and then contact H3C Support for help.
fallingAlarm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.2.1.16.0.2 |
A variable of an alarm entry fell to or below its falling threshold. |
Informational |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when a variable of an alarm entry falls to or below its falling threshold and the triggered event is to send SNMP notifications.
System impact
No impact on services.
Status control
ON
CLI: Use the rmon event entry-number [ description string ] { log-trap security-string | trap security-string } [ owner text ] command.
OFF
CLI: Use the rmon event entry-number [ description string ] { log | none } [ owner text ] command.
Object
OID (object name) |
Description |
Index |
Type |
Value range |
1.3.6.1.2.1.16.3.1.1.1 (alarmIndex) |
Index of the alarm entry |
alarmIndex |
Integer32 |
1..65535 |
1.3.6.1.2.1.16.3.1.1.3 (alarmVariable) |
Variable to be sampled |
alarmIndex |
OBJECT IDENTIFIER |
Standard MIB values. |
1.3.6.1.2.1.16.3.1.1.4 (alarmSampleType) |
Sampling type |
alarmIndex |
INTEGER |
absoluteValue(1), deltaValue(2) |
1.3.6.1.2.1.16.3.1.1.5 (alarmValue) |
Sampled value |
alarmIndex |
Integer32 |
Standard MIB values. |
1.3.6.1.2.1.16.3.1.1.8 (alarmFallingThreshold) |
Falling threshold |
alarmIndex |
Integer32 |
Standard MIB values. |
Recommended action
1.Execute the display rmon alarm command in any view to check information about the monitored variable and falling threshold. Locate and remove the reason causing the notification.
If the falling threshold is inappropriate, execute the rmon alarm command in system view to change the falling threshold.
2.If the issue persists, collect alarm information and configuration data and then contact H3C Support for help.