HH3C-CFD-MIB

        Add hh3cCfdSlmStatisticClear trap info.
    
Source file
HH3C-CFD-MIB
Last revised
Identity
hh3cCfd
Base OID
1.3.6.1.4.1.25506.2.207
Imported Objects
HH3C-OID-MIB hh3cCommon
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
Net-SNMP examples using the hh3c MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'HH3C-CFD-MIB' -M '/opt/observium/mibs/hh3c:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'HH3C-CFD-MIB::hh3cCfd'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'HH3C-CFD-MIB' -M '/opt/observium/mibs/hh3c:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'HH3C-CFD-MIB::hh3cCfd'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (14)
.1.3.6.1.4.1.25506.2.207
.1.3.6.1.4.1.25506.2.207.1
.1.3.6.1.4.1.25506.2.207.1.0
.1.3.6.1.4.1.25506.2.207.1.1
Integer32
.1.3.6.1.4.1.25506.2.207.1.1.1
Unsigned32
.1.3.6.1.4.1.25506.2.207.1.1.10
Integer32
.1.3.6.1.4.1.25506.2.207.1.1.2
.1.3.6.1.4.1.25506.2.207.1.1.3
Enumeration
.1.3.6.1.4.1.25506.2.207.1.1.4
OctetString
.1.3.6.1.4.1.25506.2.207.1.1.5
Unsigned32
.1.3.6.1.4.1.25506.2.207.1.1.6
OctetString
.1.3.6.1.4.1.25506.2.207.1.1.7
Unsigned32
.1.3.6.1.4.1.25506.2.207.1.1.8
OctetString
.1.3.6.1.4.1.25506.2.207.1.1.9
Dependencies (3) 2 direct · 1 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. RFC1155-SMIrfc
  2. HH3C-OID-MIBhh3c
  3. SNMPv2-SMIrfc
  4. HH3C-CFD-MIBhh3cselected
Notifications / Traps (20)
NameOIDDescription
.1.3.6.1.4.1.25506.2.207.1.0.1
The result of two-way delay-measurement exceeded the threshold.
.1.3.6.1.4.1.25506.2.207.1.0.10
The MEP received a CCM with RDI flag set.
.1.3.6.1.4.1.25506.2.207.1.0.11
MEP enters AIS defect condition.
.1.3.6.1.4.1.25506.2.207.1.0.12
MEP exits AIS defect condition.
.1.3.6.1.4.1.25506.2.207.1.0.13
MEP did not receive any CCM with
unexpected MD level before timeout.
.1.3.6.1.4.1.25506.2.207.1.0.14
MEP did not receive any CCM with
unexpected MEG ID before timeout.
.1.3.6.1.4.1.25506.2.207.1.0.15
MEP did not receive any CCM
with unexpected MEP before timeout.
.1.3.6.1.4.1.25506.2.207.1.0.16
MEP did not receive any CCM with
unexpected period before timeout.
.1.3.6.1.4.1.25506.2.207.1.0.17
MEP is reconnected with the remote MEP.
.1.3.6.1.4.1.25506.2.207.1.0.18
MEP received a CCM with RDI flag cleared.
.1.3.6.1.4.1.25506.2.207.1.0.19
MEP received a CCM with the Port Status TLV or
Interface Status TLV reporting an error status cleared
.1.3.6.1.4.1.25506.2.207.1.0.2
The result of two-way delay-measurement is under the threshold.
.1.3.6.1.4.1.25506.2.207.1.0.20
The indexes in the one-way LM result fell blow the threshold.
.1.3.6.1.4.1.25506.2.207.1.0.3
The result of one-way LM is exceeded the threshold.
.1.3.6.1.4.1.25506.2.207.1.0.4
The MD level carried in a CCM sent by the RMEP
was different from that specified on the MEP.
.1.3.6.1.4.1.25506.2.207.1.0.5
An MD or MA name carried in a CCM sent by the
RMEP was different from that specified on the MEP.
.1.3.6.1.4.1.25506.2.207.1.0.6
The MEP received no CCM in an interval of 3.5
times the CCM sending interval.
.1.3.6.1.4.1.25506.2.207.1.0.7
The MEP received a CCM with unexpected MEP.
.1.3.6.1.4.1.25506.2.207.1.0.8
The MEP received a CCM with unexpected period.
.1.3.6.1.4.1.25506.2.207.1.0.9
The MEP received a CCM with the Port Status TLV or
Interface Status TLV reporting an error status.