HUAWEI-RIPV2-EXT-MIB

        The HUAWEI-RIPv2-EXT-MIB.mib contains objects to configure RIP
module, including query RIP process, RIP VPN-instance configuration
and status. This MIB module objects indicate hwRip2ProcInstTable.
                 
    RIP can support many processes, but mib can support only one of
them. To get more RIP configuration, it is required to locate one 
specified RIP process. 
    
Source file
HUAWEI-RIPV2-EXT-MIB
Last revised
Identity
hwRipv2Ext
Base OID
1.3.6.1.4.1.2011.5.25.120
Imported Objects
HUAWEI-MIB hwDatacomm
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter64 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString RowStatus
Net-SNMP examples using the huawei 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 'HUAWEI-RIPV2-EXT-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'HUAWEI-RIPV2-EXT-MIB::hwRipv2Ext'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'HUAWEI-RIPV2-EXT-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'HUAWEI-RIPV2-EXT-MIB::hwRipv2Ext'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (14)
.1.3.6.1.4.1.2011.5.25.120
.1.3.6.1.4.1.2011.5.25.120.1
.1.3.6.1.4.1.2011.5.25.120.1.1
Unsigned32
.1.3.6.1.4.1.2011.5.25.120.1.1.1
OctetString
.1.3.6.1.4.1.2011.5.25.120.1.1.2
Unsigned32
.1.3.6.1.4.1.2011.5.25.120.1.1.3
Unsigned32
.1.3.6.1.4.1.2011.5.25.120.1.1.4
OctetString
.1.3.6.1.4.1.2011.5.25.120.1.1.5
.1.3.6.1.4.1.2011.5.25.120.2
.1.3.6.1.4.1.2011.5.25.120.2.1
.1.3.6.1.4.1.2011.5.25.120.2.2
.1.3.6.1.4.1.2011.5.25.120.3
.1.3.6.1.4.1.2011.5.25.120.4
OctetString
.1.3.6.1.4.1.2011.5.25.120.4.1
Dependencies (4) 4 direct 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. SNMPv2-SMIrfc
  2. HUAWEI-MIBhuawei
  3. SNMPv2-CONFrfc
  4. SNMPv2-TCrfc
  5. HUAWEI-RIPV2-EXT-MIBhuaweiselected
Conformance Groups (2)
The HUAWEI RIPv2 extension Table.
.1.3.6.1.4.1.2011.5.25.120.2.1.2
This group is used for RIP notifications
.1.3.6.1.4.1.2011.5.25.120.2.1.3
Compliance Statements (1)

OID .1.3.6.1.4.1.2011.5.25.120.2.2.1
The compliance statement for SNMPv2 entities
which implement the HUAWEI RIP extension MIB.
Required groups
mandatory hwRip2ExtGroup
optional hwRip2NotificationsGroup This group is required for RIP systems that
support RIP notifications.
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.4.1.2011.5.25.120.3.1
A hwRip2DBOverFlow notification signifies that there
has been maximum number of routes added to RIP database for
the given process and no more routes can be added to RIP by
redistibution or by learning.

This notification should be generated when the number of routes
added to RIP database reaches maximum value. RIP process will be suspended at this state.
.1.3.6.1.4.1.2011.5.25.120.3.2
A hwRip2DBOverFlowResume notification signifies that the RIP database size has dropped to the
lower threshold. RIP process will resume it's normal operation.
.1.3.6.1.4.1.2011.5.25.120.3.3
This object indicates that an insecure authentication mode is configured for RIP.
.1.3.6.1.4.1.2011.5.25.120.3.4
This object indicates that the insecure authentication mode configured for RIP is deleted.