- Table of Contents
-
- 18-Network Management and Monitoring
- 01-DISMAN-EVENT-MIB
- 02-DISMAN-PING-MIB
- 03-DISMAN-TRACEROUTE-MIB
- 04-HH3C-EMDI-MIB
- 05-HH3C-ESMC-MIB
- 06-HH3C-HTTP-MIB
- 07-HH3C-MIRRORGROUP-MIB
- 08-HH3C-NETCONF-MIB
- 09-HH3C-NQA-MIB
- 10-HH3C-NTP-MIB
- 11-HH3C-PTP-MIB
- 12-HH3C-RMON-EXT2-MIB
- 13-HH3C-SNMP-EXT-MIB
- 14-HH3C-TWAMP-MIB
- 15-RMON-MIB
- 16-RMON2-MIB
- 17-SFLOW-MIB
- 18-SNMP-FRAMEWORK-MIB
- 19-SNMP-MPD-MIB
- 20-SNMP-NOTIFICATION-MIB
- 21-SNMP-TARGET-MIB
- 22-SNMP-USER-BASED-SM-MIB
- 23-SNMP-VIEW-BASED-ACM-MIB
- 24-SNMPv2-MIB
- Related Documents
-
Title | Size | Download |
---|---|---|
04-HH3C-EMDI-MIB | 159.19 KB |
HH3C-EMDI-MIB
About this MIB
Use this MIB to implement the eMDI function.
MIB file name
hh3c-emdi.mib
Root object
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cEmdi(251)
Scalar objects
hh3cEmdiInstanceID
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiInstanceID (1.3.6.1.4.1.25506.2.251.1.1.1) |
accessible-for-notify |
Unsigned32 |
Unsigned32 (1.. 65535) |
Instance ID |
Not supported |
hh3cEmdiIndicatorType
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiIndicatorType (1.3.6.1.4.1.25506.2.251.1.1.2) |
accessible-for-notify |
INTEGER |
rtplr(1), rtpser (2) uplr(3), dplr(4), |
Monitored item type |
Not supported |
hh3cEmdiIndicatorValue
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiIndicatorValue (1.3.6.1.4.1.25506.2.251.1.1.3) |
accessible-for-notify |
Unsigned32 |
Standard MIB values. |
Monitored item value |
Not supported |
hh3cEmdiIndicatorThreshold
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiIndicatorThreshold (1.3.6.1.4.1.25506.2.251.1.1.4) |
accessible-for-notify |
Unsigned32 |
Standard MIB values. |
Threshold set for the monitored item |
Not supported |
hh3cEmdiSuppressTimes
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiSuppressTimes (1.3.6.1.4.1.25506.2.251.1.1.5) |
accessible-for-notify |
Unsigned32 |
Standard MIB values. |
Number of consecutive alarms to be suppressed before logging the event for a monitored item |
Not supported |
hh3cEmdiFlowSrcIPType
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiFlowSrcIPType (1.3.6.1.4.1.25506.2.251.1.1.6) |
accessible-for-notify |
InetAddressType |
Standard MIB values. |
Source IP address type of the target flow |
Not supported |
hh3cEmdiFlowSrcIP
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiFlowSrcIP (1.3.6.1.4.1.25506.2.251.1.1.7) |
accessible-for-notify |
InetAddress |
Standard MIB values. |
Source IP address of the target flow |
Not supported |
hh3cEmdiFlowDstIPType
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiFlowDstIPType (1.3.6.1.4.1.25506.2.251.1.1.8) |
accessible-for-notify |
InetAddressType |
Standard MIB values. |
Destination IP address type of the target flow |
Not supported |
hh3cEmdiFlowDstIP
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiFlowDstIP (1.3.6.1.4.1.25506.2.251.1.1.9) |
accessible-for-notify |
InetAddress |
Standard MIB values. |
Destination IP address of the target flow |
Not supported |
hh3cEmdiFlowSrcPort
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiFlowSrcPort (1.3.6.1.4.1.25506.2.251.1.1.10) |
accessible-for-notify |
Integer32 |
Integer32 (1..65535) |
Source port number of the target flow |
Not supported |
hh3cEmdiFlowDstPort
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiFlowDstPort (1.3.6.1.4.1.25506.2.251.1.1.11) |
accessible-for-notify |
Integer32 |
Integer32 (1..65535) |
Destination port number of the target flow |
Not supported |
hh3cEmdiFlowProtocol
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiFlowProtocol (1.3.6.1.4.1.25506.2.251.1.1.12) |
accessible-for-notify |
INTEGER |
tcp(1), udp(2) |
Protocol type of the target flow |
Not supported |
hh3cEmdiFlowVlanID
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiFlowVlanID (1.3.6.1.4.1.25506.2.251.1.1.13) |
accessible-for-notify |
Integer32 |
Integer32 (1..4094) |
VLAN ID of the target flow |
Not supported |
hh3cEmdiFlowVxlanID
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiFlowVxlanID (1.3.6.1.4.1.25506.2.251.1.1.14) |
accessible-for-notify |
Integer32 |
Integer32 (0..16777215) |
VXLAN ID of the target flow |
Not supported |
hh3cEmdiChassisID
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiChassisID (1.3.6.1.4.1.25506.2.251.1.1.15) |
accessible-for-notify |
Integer32 |
Integer32 (0..65535) |
Chassis number |
The value of 65565 indicates a non-IRF scenario. |
hh3cEmdiSlotID
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cEmdiSlotID (1.3.6.1.4.1.25506.2.251.1.1.16) |
accessible-for-notify |
Integer32 |
Integer32 (0..65535) |
Slot number |
Not supported |
Notifications
hh3cEmdiIndicatorOverThres
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.251.1.0.1 |
The value of the monitored item reaches the alarm threshold continuously for the specified times |
Error |
Warning |
1.3.6.1.4.1.25506.2.251.1.0.2 (hh3cEmdiIndicatorOverThresResume) |
OFF |
Notification triggers
The notification is generated when the value of the monitored item reaches the alarm threshold continuously for the specified times.
Monitored item types include:
· RTP-LR—RTP packet loss rate.
· RTP-SER—RTP packet sequence error rate.
· DPLR—Downstream TCP packet loss rate.
· UPLR—Upstream TCP packet loss rate.
System impact
If this alarm appears, the value of the monitored item reaches the alarm threshold continuously for the specified times. The network transmission quality is poor.
Status control
ON
CLI: snmp-agent trap enable emdi
OFF
CLI: undo snmp-agent trap enable emdi
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.251.1.1.1 (hh3cEmdiInstanceID) |
Instance ID |
None |
Unsigned32 |
Unsigned32 (1.. 65535) |
1.3.6.1.4.1.25506.2.251.1.1.2 (hh3cEmdiIndicatorType) |
Monitoring |
None |
INTEGER |
rtp-lr(1), rtp-ser (2) uplr(3), dplr(4), |
1.3.6.1.4.1.25506.2.251.1.1.3 (hh3cEmdiIndicatorValue) |
Monitored item value |
None |
Unsigned32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.251.1.1.4 (hh3cEmdiIndicatorThreshold) |
Threshold set for the monitored item |
None |
Unsigned32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.251.1.1.5 (hh3cEmdiSuppressTimes) |
Number of consecutive alarms to be suppressed before logging the event for a monitored item |
None |
Unsigned32 |
Standard MIB values. |
Recommended action
1. Locate the faulty device according to the eMDI statistics on the network.
2. Replace the transceiver module or optical fiber of the corresponding physical interface of the faulty device. Identify whether the alarm is cleared.
3. If the alarm is not cleared, collect alarm information and configuration data, and then contact H3C Support.
hh3cEmdiIndicatorOverThresResume
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.251.1.0.2 |
The value of the monitored item drops below the alarm threshold continuously for the specified times, and the monitored item is recovered |
Recovery |
Warning |
- |
OFF |
Notification triggers
The notification is generated when the value of the monitored item drops below the alarm threshold continuously for the specified times, and the monitored item is recovered.
System impact
The service is not impacted.
Status control
ON
CLI: snmp-agent trap enable emdi
OFF
CLI: undo snmp-agent trap enable emdi
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.251.1.1.1 (hh3cEmdiInstanceID) |
Instance ID |
None |
Unsigned32 |
Unsigned32 (1.. 65535) |
1.3.6.1.4.1.25506.2.251.1.1.2 (hh3cEmdiIndicatorType) |
Monitored item type |
None |
INTEGER |
rtp-lr(1), rtp-ser (2) uplr(3), dplr(4), |
1.3.6.1.4.1.25506.2.251.1.1.3 (hh3cEmdiIndicatorValue) |
Monitored item value |
None |
Unsigned32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.251.1.1.4 (hh3cEmdiIndicatorThreshold) |
Threshold set for the monitored item |
None |
Unsigned32 |
Standard MIB values. |
1.3.6.1.4.1.25506.2.251.1.1.5 (hh3cEmdiSuppressTimes) |
Number of consecutive alarms to be suppressed before logging the event for a monitored item |
None |
Unsigned32 |
Standard MIB values. |
Recommended action
No action is required.
hh3cEmdiFlowConflict
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.251.1.0.3 |
Destination flow conflict alarm between eMDI instances |
Informational |
Warning |
- |
OFF |
Notification triggers
This notification is generated when the target flow bound to a dynamic eMDI instance conflicts with the target flow of an existing instance.
Possible reasons are:
1. The target flow bound to a dynamic instance is the same as the target flow of an existing instance.
2. The target flow bound to a dynamic instance is a subset of the target flow of an existing instance.
System impact
The target flow cannot be bound to a dynamic instance.
Status control
ON
CLI: snmp-agent trap enable emdi
OFF
CLI: undo snmp-agent trap enable emdi
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.251.1.1.1 (hh3cEmdiInstanceID) |
Instance ID of the conflicting target flow. |
N/A |
Unsigned32 |
Unsigned32 (1.. 65535) |
1.3.6.1.4.1.25506.2.251.1.1.6 (hh3cEmdiFlowSrcIPType) |
Source IP address type of the target flow. |
N/A |
InetAddressType |
Standard MIB values. |
1.3.6.1.4.1.25506.2.251.1.1.7 (hh3cEmdiFlowSrcIP) |
Source IP address of the target flow. |
N/A |
InetAddress |
Standard MIB values. |
1.3.6.1.4.1.25506.2.251.1.1.8 (hh3cEmdiFlowDstIPType) |
Destination IP address type of the target flow. |
N/A |
InetAddressType |
Standard MIB values. |
1.3.6.1.4.1.25506.2.251.1.1.9 (hh3cEmdiFlowDstIP) |
Destination IP address of the target flow. |
N/A |
InetAddress |
Standard MIB values. |
1.3.6.1.4.1.25506.2.251.1.1.10 (hh3cEmdiFlowSrcPort) |
Source port number of the target flow. |
N/A |
Integer32 |
Integer32 (1..65535) |
1.3.6.1.4.1.25506.2.251.1.1.11 (hh3cEmdiFlowDstPort) |
Destination port number of the target flow. |
N/A |
Integer32 |
Integer32 (1..65535) |
1.3.6.1.4.1.25506.2.251.1.1.12 (hh3cEmdiFlowProtocol) |
Protocol type of the target flow. |
N/A |
INTEGER |
tcp(1), udp(2) |
1.3.6.1.4.1.25506.2.251.1.1.13 (hh3cEmdiFlowVlanID) |
VLAN ID of the target flow. |
N/A |
Integer32 |
Integer32 (1..4094) |
1.3.6.1.4.1.25506.2.251.1.1.14 (hh3cEmdiFlowVxlanID) |
VXLAN ID of the target flow. |
N/A |
Integer32 |
Integer32 (0..16777215) |
Recommended action
1. Execute the display emdi instance verbose command to view eMDI instance information to identify whether conflicts exist between target flows.
¡ If conflicts exist, configure the target flows properly.
¡ If no conflicts exist, go to step 2.
2. If the issue persists, collect alarm information and configuration data, and then contact H3C Support.
hh3cEmdiInstanceExceed
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.251.1.0.4 |
The number of eMDI instances exceeds the upper limit |
Informational |
Warning |
- |
OFF |
Notification triggers
This notification is generated when the number of eMDI instances exceeds the upper limit
System impact
You cannot create new instances after the number of instances exceeds the upper limit.
Status control
ON
CLI: snmp-agent trap enable emdi
OFF
CLI: undo snmp-agent trap enable emdi
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.251.1.1.15 (hh3cEmdiChassisID) |
Chassis number. |
N/A |
Integer32 |
Integer32 (0..65535) |
1.3.6.1.4.1.25506.2.251.1.1.16 (hh3cEmdiSlotID) |
Slot number. |
N/A |
Integer32 |
Integer32 (0..65535) |
Recommended action
1. Execute the display emdi resource command to view eMDI instance resource information to identify whether the number of instances exceeds the upper limit.
¡ If the upper limit is exceeded, plan and configure the instances properly.
¡ If the upper limit is not exceeded, go to step 2.
2. If the issue persists, collect alarm information and configuration data, and then contact H3C Support.