HH3C-RBM-MIB

        The MIB is designed to manage Rbm products.
    
Source file
HH3C-RBM-MIB
Last revised
Identity
hh3cRbm
Base OID
1.3.6.1.4.1.25506.2.187
Imported Objects
HH3C-OID-MIB hh3cCommon
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
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-RBM-MIB' -M '/opt/observium/mibs/hh3c:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'HH3C-RBM-MIB::hh3cRbm'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'HH3C-RBM-MIB' -M '/opt/observium/mibs/hh3c:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'HH3C-RBM-MIB::hh3cRbm'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (7)
.1.3.6.1.4.1.25506.2.187
.1.3.6.1.4.1.25506.2.187.1
.1.3.6.1.4.1.25506.2.187.1.1
Integer32
.1.3.6.1.4.1.25506.2.187.1.1.1
OctetString
.1.3.6.1.4.1.25506.2.187.1.1.2
.1.3.6.1.4.1.25506.2.187.1.2
.1.3.6.1.4.1.25506.2.187.1.2.0
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-RBM-MIBhh3cselected
Notifications / Traps (7)
NameOIDDescription
.1.3.6.1.4.1.25506.2.187.1.2.0.1
This notification is generated when RBM keepalive channel connected.
.1.3.6.1.4.1.25506.2.187.1.2.0.2
This notification is generated when RBM keepalive channel disconnected.
.1.3.6.1.4.1.25506.2.187.1.2.0.3
This notification is generated when RBM running status changes(0:new-state = Active,1:new-state = Standby).
.1.3.6.1.4.1.25506.2.187.1.2.0.4
When the result of RBM configuration consistency check is inconsistent, it checks the result of the last check.
If the result of the last check is also inconsistent, this notification is generated.
.1.3.6.1.4.1.25506.2.187.1.2.0.5
After the RBM is linked with the MAD,it responds to the MAD event.
When it receives a dual-primary conflict reported by the MAD,
it adds this notification to the original processing logic.
.1.3.6.1.4.1.25506.2.187.1.2.0.6
After the RBM is linked with the MAD,it responds to the MAD event.
When receiving the MAD report of dual-primary conflict recovery,
this notification is added to the original processing logic.
.1.3.6.1.4.1.25506.2.187.1.2.0.7
After the heartbeat cable is connected,
if the RBM configuration is a dual management master or dual management backup configuration or
is not configured with data-channel,this notification is sent every 30s.