HUAWEI-RANAPS-MIB

        Added trap node hwRanApsK1K2MisResume which corresponds to hwRanApsK1K2Mismatch.
    
Source file
HUAWEI-RANAPS-MIB
Last revised
Identity
hwRanApsMIB
Base OID
1.3.6.1.4.1.2011.5.25.200
Imported Objects
HUAWEI-MIB hwDatacomm
IF-MIB ifIndex ifName InterfaceIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC PhysAddress 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-RANAPS-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'HUAWEI-RANAPS-MIB::hwRanApsMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'HUAWEI-RANAPS-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'HUAWEI-RANAPS-MIB::hwRanApsMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (43)
.1.3.6.1.4.1.2011.5.25.200
.1.3.6.1.4.1.2011.5.25.200.1
.1.3.6.1.4.1.2011.5.25.200.1.1
.1.3.6.1.4.1.2011.5.25.200.1.1.1
Unsigned32
.1.3.6.1.4.1.2011.5.25.200.1.1.1.1
.1.3.6.1.4.1.2011.5.25.200.1.1.1.10
.1.3.6.1.4.1.2011.5.25.200.1.1.1.11
Integer32
.1.3.6.1.4.1.2011.5.25.200.1.1.1.12
Integer32
.1.3.6.1.4.1.2011.5.25.200.1.1.1.13
OctetString
.1.3.6.1.4.1.2011.5.25.200.1.1.1.14
.1.3.6.1.4.1.2011.5.25.200.1.1.1.15
.1.3.6.1.4.1.2011.5.25.200.1.1.1.16
OctetString
.1.3.6.1.4.1.2011.5.25.200.1.1.1.17
OctetString
.1.3.6.1.4.1.2011.5.25.200.1.1.1.18
Enumeration
.1.3.6.1.4.1.2011.5.25.200.1.1.1.19
.1.3.6.1.4.1.2011.5.25.200.1.1.1.2
Enumeration
.1.3.6.1.4.1.2011.5.25.200.1.1.1.20
Enumeration
.1.3.6.1.4.1.2011.5.25.200.1.1.1.21
Unsigned32
.1.3.6.1.4.1.2011.5.25.200.1.1.1.3
.1.3.6.1.4.1.2011.5.25.200.1.1.1.4
Enumeration
.1.3.6.1.4.1.2011.5.25.200.1.1.1.5
Integer32
.1.3.6.1.4.1.2011.5.25.200.1.1.1.6
Enumeration
.1.3.6.1.4.1.2011.5.25.200.1.1.1.7
Enumeration
.1.3.6.1.4.1.2011.5.25.200.1.1.1.8
Enumeration
.1.3.6.1.4.1.2011.5.25.200.1.1.1.9
.1.3.6.1.4.1.2011.5.25.200.1.2
.1.3.6.1.4.1.2011.5.25.200.1.2.1
Unsigned32
.1.3.6.1.4.1.2011.5.25.200.1.2.1.1
.1.3.6.1.4.1.2011.5.25.200.1.2.1.2
.1.3.6.1.4.1.2011.5.25.200.1.3
.1.3.6.1.4.1.2011.5.25.200.1.3.1
Unsigned32
.1.3.6.1.4.1.2011.5.25.200.1.3.1.1
Enumeration
.1.3.6.1.4.1.2011.5.25.200.1.3.1.2
Enumeration
.1.3.6.1.4.1.2011.5.25.200.1.3.1.3
.1.3.6.1.4.1.2011.5.25.200.1.3.1.4
.1.3.6.1.4.1.2011.5.25.200.1.4
.1.3.6.1.4.1.2011.5.25.200.1.4.1
.1.3.6.1.4.1.2011.5.25.200.1.4.1.1
Unsigned32
.1.3.6.1.4.1.2011.5.25.200.1.4.1.2
.1.3.6.1.4.1.2011.5.25.200.2
.1.3.6.1.4.1.2011.5.25.200.3
.1.3.6.1.4.1.2011.5.25.200.3.1
.1.3.6.1.4.1.2011.5.25.200.3.2
Dependencies (7) 5 direct · 2 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. SNMPv2-SMIrfc
  2. HUAWEI-MIBhuawei
  3. SNMPv2-TCrfc
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. HUAWEI-RANAPS-MIBhuaweiselected
Compliance Statements (1)

OID .1.3.6.1.4.1.2011.5.25.200.3.1.1
The compliance statement for entities that implement
extend APS on a router.
Required groups
Notifications / Traps (14)
NameOIDDescription
.1.3.6.1.4.1.2011.5.25.200.2.1
This object indicates that an alarm is generated when the LMSP state machine processing fails.
.1.3.6.1.4.1.2011.5.25.200.2.10
This object indicates that the LMSP working modes between two NEs are the same.
.1.3.6.1.4.1.2011.5.25.200.2.11
This object indicates that the peer protection mode represented by the K2 byte (the fifth byte in descending order) in the received packet is the same as the local protection mode.
.1.3.6.1.4.1.2011.5.25.200.2.12
This object indicates that the alarm generated when PGP Keepalive packets timed out is cleared.
.1.3.6.1.4.1.2011.5.25.200.2.13
This object indicates that the LMSP switchback modes configured between two devices are inconsistent.
.1.3.6.1.4.1.2011.5.25.200.2.14
This object indicates that the received K1 and K2 bytes match the transmitted K1 and K2 bytes.
.1.3.6.1.4.1.2011.5.25.200.2.2
This object indicates the PGP packet error.
.1.3.6.1.4.1.2011.5.25.200.2.3
This object indicates that an alarm is generated when PGP Keepalive packets time out.
.1.3.6.1.4.1.2011.5.25.200.2.4
This object indicates that the APS modes configured between two NEs are inconsistent.
.1.3.6.1.4.1.2011.5.25.200.2.5
This object indicates that the received K1 and K2 bytes do not match the transmitted K1 and K2 bytes.
.1.3.6.1.4.1.2011.5.25.200.2.6
This object indicates that an alarm is generated when the peer protection mode represented
by the K2 byte (the fifth byte in descending order) in the received packet is different from the local.
.1.3.6.1.4.1.2011.5.25.200.2.7
This object indicates that an LMSP protection switchover succeeds.
.1.3.6.1.4.1.2011.5.25.200.2.8
This object indicates that an LMSP protection switchback succeeds.
.1.3.6.1.4.1.2011.5.25.200.2.9
This object indicates that an interface in an LMSP group becomes Up and begins to work as a protection interface.