HUAWEI-RPR-MIB

        The HUAWEI-RPR-TRAP-MIB contains objects to
Monitor the RPR TRAPs.
        
*********************************
RPR TRAP
**********************************
 This RPR TRAP consists of the following TRAPs:
 1 :  hwRPRexcessReservedRateDefect
 2 :  hwRPRprotMisconfigDefect
 3 :  hwRPRtopoChange
 4 :  hwRPRtopoInvalidDefect
 5 :  hwRPRduplicateMacAddressDefect
 6 :  hwRPRtopoInstabilityDefect
 7 :  hwRPRtopoStabilityRestore
 8 :  hwRPRPhyIfEventTrap
 9 :  hwRPRLogicIfEventTrap
    
Source file
HUAWEI-RPR-MIB
Last revised
Identity
hwRPR
Base OID
1.3.6.1.4.1.2011.5.25.36
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-RPR-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'HUAWEI-RPR-MIB::hwRPR'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'HUAWEI-RPR-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'HUAWEI-RPR-MIB::hwRPR'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (16)
.1.3.6.1.4.1.2011.5.25.36
.1.3.6.1.4.1.2011.5.25.36.1
.1.3.6.1.4.1.2011.5.25.36.1.1
.1.3.6.1.4.1.2011.5.25.36.1.1.1
.1.3.6.1.4.1.2011.5.25.36.1.1.1.1
.1.3.6.1.4.1.2011.5.25.36.1.1.1.2
Enumeration
.1.3.6.1.4.1.2011.5.25.36.1.1.1.3
Enumeration
.1.3.6.1.4.1.2011.5.25.36.1.1.1.4
.1.3.6.1.4.1.2011.5.25.36.1.2
.1.3.6.1.4.1.2011.5.25.36.1.2.1
.1.3.6.1.4.1.2011.5.25.36.1.2.1.1
Enumeration
.1.3.6.1.4.1.2011.5.25.36.1.2.1.2
.1.3.6.1.4.1.2011.5.25.36.2
.1.3.6.1.4.1.2011.5.25.36.3
.1.3.6.1.4.1.2011.5.25.36.3.1
.1.3.6.1.4.1.2011.5.25.36.3.2
Dependencies (11) 5 direct · 6 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
Compliance Statements (1)

OID .1.3.6.1.4.1.2011.5.25.36.3.1.1
The compliance statement for entities that implement
RPRTRAP on a router.
Required groups
Notifications / Traps (17)
NameOIDDescription
.1.3.6.1.4.1.2011.5.25.36.2.1
This defect indicates that the amount of reserved
bandwidth on a ringlet exceeds the available LINK_RATE.
When an excess reserved rate defect is present,
a notification may be generated.
.1.3.6.1.4.1.2011.5.25.36.2.10
On RPR ring, to detect the connection, a kind of packet
is send between neighbor RPR nodes, This kind of packet
is SC(Single-Choke) packet, If a node cannot receive SC
packet from neighbor node in KEEPALIVE time, then there
is failure between the two nodes. When happened, auto protection
is executed by software.!
.1.3.6.1.4.1.2011.5.25.36.2.11
On RPR ring, to detect the connection, a kind of packet
is send between neighbor RPR nodes, This kind of packet
is SC(Single-Choke) packet, If a node cannot receive SC
packet from neighbor node in KEEPALIVE time, then there
is failure between the two nodes. When failure is resumed
, this notification is sent.!
.1.3.6.1.4.1.2011.5.25.36.2.12
Optical fiber is connected in error. i.e the east direction
of one node is connected with east direction of another node,
or the west direction of one node is connected with west direction
of another node!
.1.3.6.1.4.1.2011.5.25.36.2.13
when phenomena that Optical fiber is connected in error disappears,
this notification is sent!
.1.3.6.1.4.1.2011.5.25.36.2.14
In double RPR operating mode, east and west directions
of one rpr node lay on two RPR cards, These two cards are
internally conntected by Gigaibit-ethernet, which is called
MATE interface. The RPR nodes cannot work normaly under
condition of MATE error.!
.1.3.6.1.4.1.2011.5.25.36.2.15
In double RPR operating mode, east and west directions
of one rpr node lay on two RPR cards, These two cards are
internally conntected by Gigaibit-ethernet, which is called
MATE interface. The RPR nodes cannot work normaly under
condition of MATE error.when MATE error is resumed ,this
notification is sent!
.1.3.6.1.4.1.2011.5.25.36.2.16
On RPR physical layer, link connection is detected
through physical singal. When can't receive physical
singal, then local node from neighbor node, LOS(lost of signal)
alarm is report, auto protection is executed by software.!
.1.3.6.1.4.1.2011.5.25.36.2.17
On RPR physical layer, link connection is detected
through physical singal. When can't receive physical
singal, then local node from neighbor node, LOS(lost of signal)
alarm is report, auto protection is executed by software.when LOS
is resumed,this notification is sent
.1.3.6.1.4.1.2011.5.25.36.2.2
A critical severity defect that indicates the presence
of mismatched-protection-configuration stations, based
on the value returned by MismatchedProtection().
When a protection configuration defect is present
on the station, a notification may be generated.
.1.3.6.1.4.1.2011.5.25.36.2.3
When an topology change is present,
a notification may be generated..
.1.3.6.1.4.1.2011.5.25.36.2.4
A critical severity defect indicating that an
invalid entry has been found within the scope
of the topology,the stations on the ring excess
the MAX_STATIONS or the local station has one
or more duplicate secondary MAC addresses. When
a topology entry invalid defect ,exceeing MaxStations
or duplicate secondary MAC addresses is present,
a notification may be generated.
.1.3.6.1.4.1.2011.5.25.36.2.5
A critical severity defect indicating that a
duplicateMacAddress has been found on the ring.
When a duplicateMacAddress defect is present,
a notification may be generated.
.1.3.6.1.4.1.2011.5.25.36.2.6
The critical severity Instable topology defect.
When an Instable topology defect is present,
a notification may be generated.
.1.3.6.1.4.1.2011.5.25.36.2.7
The critical severity Instable topology restore.
When an stable topology is present,
a notification may be generated.
.1.3.6.1.4.1.2011.5.25.36.2.8
The critical severity physical interface defect.
When an physical interface defect is present,
a notification may be generated.
.1.3.6.1.4.1.2011.5.25.36.2.9
The critical severity Logic interface defect.
When an logic interface defect that caused
by physical interface event is present,
a notification may be generated.