H3C-RRPP-MIB

All MIBs › H3C-RRPP-MIB

Organization: Huawei 3Com Technologies Co., Ltd.

Last Updated: 2004-12-02

Category: Technology: Switching/L2, Vendor: H3C/HH3C

Description: H3C MIB for Rapid Ring Protection Protocol (RRPP) managing Ethernet ring topology and fault recovery.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is H3C-RRPP-MIB?

H3C-RRPP-MIB is an H3C (Hangzhou Huawei-3Com/New H3C) proprietary MIB module that manages the Rapid Ring Protection Protocol, a Layer 2 mechanism for building self-healing Ethernet ring topologies on H3C switches. It exposes configuration data such as ring domain identifiers, control VLANs, hello and fail timers, protected VLAN lists, and ring node roles, alongside operational status of each ring instance. In terms of monitoring hardware and software status, it is primarily useful for tracking protocol operational health rather than physical hardware: administrators poll whether RRPP is enabled, whether a ring domain is in a normal or failed state, and receive traps when link breaks trigger protection switching, which indirectly signals physical link/port failures in the ring. The module depends conceptually on standard Ethernet/VLAN management (similar in spirit to Spanning Tree Protocol MIBs) but is not formally tied to a specific IETF MIB. It is typically deployed on H3C campus and metro Ethernet switches built into redundant ring topologies where sub-second failover is required for high availability. Engineers can download the H3C-RRPP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in H3C-RRPP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

H3C Layer 2/Layer 3 Ethernet switches

Monitoring Examples

An administrator would poll h3cRrppDomainTable/h3cRrppDomainEntry for each ring's h3cRrppDomainID, h3cRrppDomainControlVlanID, h3cRrppDomainHelloTime, and h3cRrppDomainFailTime to confirm the ring's timers match design intent. Checking h3cRrppEnableStatus and the per-domain h3cRrppDomainRowStatus reveals whether protection is actively armed on each switch in the ring. If a fiber link in the ring fails, h3cRrppNotifications traps fire, and a subsequent read of the domain state would show the ring has failed over to its backup path, letting the operator confirm the RRPP protocol reconverged within its configured hello/fail time budget.

What Can Be Monitored

RRPP enable status
ring domain state
control VLAN configuration
hello/fail timer values
protected VLAN list
ring protection switching events

Imported Objects

From HUAWEI-3COM-OID-MIB

h3cCommon

OBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using h3cRrppPortRXError OID:

Select an H3C Layer 2/3 Ethernet switch (Rapid Ring Protection Protocol) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type h3cRrppPortRXError into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The statistics of illegal RRPP packets received from this port. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
h3cRrpp	1.3.6.1.4.1.2011.10.2.45			The RRPP (Rapid Ring Protection protocol) provides fast protection switching to layer 2 switches interconnected in an Ethernet ring topology. When a link in the ring breaks, the RRPP can recover the data path quickly. Its protection switching is similar to what can be achieved with the Spanning Tree Protocol (STP), but the converging time is less than a second after link failure. This MIB defines management information used on products which support RRPP.
h3cRrppScalarGroup	1.3.6.1.4.1.2011.10.2.45.1
ENA h3cRrppEnableStatus	1.3.6.1.4.1.2011.10.2.45.1.1	EnabledStatus	read-write	Indicating whether the RRPP is enabled on this switch.
OCT h3cRrppPassword	1.3.6.1.4.1.2011.10.2.45.1.2	OCTET STRING	read-write	Password configured for RRPP nodes to identify the validity of a link-down message. This value must be set together with h3cRrppPasswordType which indicates whether this value can be got. This value can not be set alone without configuring h3cRrppPasswordType.
INT h3cRrppPasswordType	1.3.6.1.4.1.2011.10.2.45.1.3	INTEGER	read-write	Indicating whether the h3cRrppPassword can be got. simple(1):h3cRrppPassword can be got. cipher(2):h3cRrppPassword can not be got. This value can not be set alone without configuring h3cRrppPassword.
INT h3cRrppProtectVlanConfigMode	1.3.6.1.4.1.2011.10.2.45.1.4	INTEGER	read-only	Indicating the mode in which the protected VLANs of an RRPP domain are configured. The value 'vlan' indicates that h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh can be used for setting protected VLANs, while h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh cannot. By contraries, the value 'instance' indicates that 3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh can be used for setting protected VLANs while the other two cannot.
h3cRrppTable	1.3.6.1.4.1.2011.10.2.45.2
h3cRrppDomainTable	1.3.6.1.4.1.2011.10.2.45.2.1		not-accessible	A table containing information about configurations and status of a RRPP domain.
h3cRrppDomainEntry	1.3.6.1.4.1.2011.10.2.45.2.1.1		not-accessible	Detailed information of a specified RRPP domain.
I32 h3cRrppDomainID	1.3.6.1.4.1.2011.10.2.45.2.1.1.1	Integer32	accessible-for-notify	An index uniquely identifies a RRPP domain, which ranges from 1~16. This value can't be modified after created.
I32 h3cRrppDomainControlVlanID	1.3.6.1.4.1.2011.10.2.45.2.1.1.2	Integer32	read-create	Index of the control VLAN specified to a domain. The value 65535 indicates the control VLAN has not been configured. The VLAN assigned to a RRPP Domain must not have been created. This value can't be modified after created.
I32 h3cRrppDomainHelloTime	1.3.6.1.4.1.2011.10.2.45.2.1.1.3	Integer32	read-create	The value indicates the interval between two hello packets sent by master-node, and its unit is second. The value ranges from 1s~10s.
I32 h3cRrppDomainFailTime	1.3.6.1.4.1.2011.10.2.45.2.1.1.4	Integer32	read-create	The expiration value of the fail-period timer and its unit is second. If not receiving hello packets before this expires, the master-node considers the ring is broken. The value of this node ranging from 3s~30s must not be less than triple h3cRrppDomainHelloTime's value.
ROW h3cRrppDomainRowStatus	1.3.6.1.4.1.2011.10.2.45.2.1.1.5	RowStatus	read-create	This object is responsible for managing the creation, deletion and modification of rows, which support active status and CreatAndGo, destroy operation.
OCT h3cRrppDomainInstanceListLow	1.3.6.1.4.1.2011.10.2.45.2.1.1.6	OCTET STRING	read-create	Each octet contained in this value specifies an eight-instance group, with the first octet specifying instances 0 through 7, the second octet specifying instances 8 through 15, and so on. Within each octet, the most significant bit represents the highest numbered instance, and the least significant bit represents the lowest numbered instance. Thus, each instance to which the protected VLANs of an RRPP domain are mapped corresponds to a bit within the value of this object. A bit with a value of '1' indicates that the VLANs mapped to the instance are protected VLANs of the RRPP domain. By contraries, the VLANs mapped to the instance are not protected VLANs if the corresponding bit has a value of '0'. The value of this object must be set with h3cRrppDomainInstanceListHigh at the same time when a SET operation is performed. This object is valid only when the value of h3cRrppProtectVlanConfigMode is 'instance'. If this object is invalid, it does not respond to SET operation, and it returns all '0' bits in response to GET operation.
OCT h3cRrppDomainInstanceListHigh	1.3.6.1.4.1.2011.10.2.45.2.1.1.7	OCTET STRING	read-create	Each octet contained in this value specifies an eight-instance group, with the first octet specifying instances 2048 through 2055, the second octet specifying instances 2056 through 2063, and so on. Within each octet, the most significant bit represents the highest numbered instance, and the least significant bit represents the lowest numbered instance. The most significant bit of the last octet is invalid. Thus, each instance to which the protected VLANs of an RRPP domain are mapped corresponds to a bit within the value of this object. A bit with a value of '1' indicates that the VLANs mapped to the instance are protected VLANs of the RRPP domain. By contraries, the VLANs mapped to the instance are not protected VLANs if the corresponding bit has a value of '0'. The value of this object must be set with h3cRrppDomainInstanceListLow at the same time when a SET operation is performed. This object is valid only when the value of h3cRrppProtectVlanConfigMode is 'instance'. If this object is invalid, it does not respond to SET operation, and it returns all '0' bits in response to GET operation.
OCT h3cRrppDomainProtectVlanListLow	1.3.6.1.4.1.2011.10.2.45.2.1.1.8	OCTET STRING	read-create	Each octet contained in this value specifies an eight-VLAN group, with the first octet specifying VLANs 1 through 7, the second octet specifying VLANs 8 through 15, and so on. Within each octet, the most significant bit represents the highest numbered VLAN, and the least significant bit represents the lowest numbered VLAN. The least significant bit of the first octet is invalid. Thus, each protected VLAN of an RRPP domain corresponds to a bit within the value of this object. A bit with a value of '1' indicates that the corresponding VLAN is a protected VLAN of the RRPP domain. By contraries, the VLAN is not a protected VLAN if the corresponding bit has a value of '0'. The value of this object must be set with h3cRrppDomainProtectVlanListHigh at the same time when a SET operation is performed. This object is valid only when the value of h3cRrppProtectVlanConfigMode is 'vlan'. If this object is invalid, it does not respond to SET operation, and it returns all '0' bits in response to GET operation.
OCT h3cRrppDomainProtectVlanListHigh	1.3.6.1.4.1.2011.10.2.45.2.1.1.9	OCTET STRING	read-create	Each octet contained in this value specifies an eight-VLAN group, with the first octet specifying VLANs 2048 through 2055, the second octet specifying VLANs 2056 through 2063, and so on. Within each octet, the most significant bit represents the highest numbered VLAN, and the least significant bit represents the lowest numbered VLAN. The most significant bit of the last octet is invalid. Thus, each protected VLAN of an RRPP domain corresponds to a bit within the value of this object. A bit with a value of '1' indicates that the corresponding VLAN is a protected VLAN of the RRPP domain. By contraries, the VLAN is not a protected VLAN if the corresponding bit has a value of '0'. The value of this object must be set with h3cRrppDomainProtectVlanListLow at the same time when a SET operation is performed. This object is valid only when the value of h3cRrppProtectVlanConfigMode is 'vlan'. If this object is invalid, it does not respond to SET operation, and it returns all '0' bits in response to GET operation.
h3cRrppRingTable	1.3.6.1.4.1.2011.10.2.45.2.2		not-accessible	A table containing information about configurations and status of a RRPP Ring.
h3cRrppRingEntry	1.3.6.1.4.1.2011.10.2.45.2.2.1		not-accessible	Detailed information of a specified RRPP Ring.
I32 h3cRrppRingID	1.3.6.1.4.1.2011.10.2.45.2.2.1.1	Integer32	accessible-for-notify	An index uniquely identifies a RRPP Ring, which ranges from 1~64. This value can't be modified after created.
ENA h3cRrppRingEnableStatus	1.3.6.1.4.1.2011.10.2.45.2.2.1.2	EnabledStatus	read-create	Indicating whether the RRPP is enabled on this Ring. NOTE: If major-ring and sub-ring(s) of a domain coexist on a switch, major-ring must be enabled before sub-ring is enabled. And sub-ring must be disabled before major-ring is disabled.
INT h3cRrppRingActive	1.3.6.1.4.1.2011.10.2.45.2.2.1.3	INTEGER	read-only	As both h3cRrppEnableStatus and h3cRrppRingEnableStatus are enabled, the ring is activated. Whereas either of the two items is disabled, the ring is inactive.
INT h3cRrppRingState	1.3.6.1.4.1.2011.10.2.45.2.2.1.4	INTEGER	read-only	The status (i.e. unknown, health or fault) of the Ethernet ring. This is valid only on the master-node.
INT h3cRrppRingNodeMode	1.3.6.1.4.1.2011.10.2.45.2.2.1.5	INTEGER	read-create	There are four RRPP node modes for the switch on a RRPP ring, such as master, transit, edge and assistant-edge. Each RRPP ring has a single designated master-node. All other nodes except edge-node and assistant-edge-node on that ring are referred to as transit-nodes. The node mode of edge and assistant-edge should be configured only on sub-ring. When there is a common link between a sub-ring and its major-ring, the node mode of the sub-ring must be edge or assistant-edge, and they must be configured in pairs. If node mode is designated as edge or assistant-edge, several points should be noticed: Major-ring must be created before a sub-ring is created; Major-ring can't be deleted unless all its sub-rings are deleted; The node mode of the switch on major-ring must be transit; Major-ring and sub-ring must have only a common port. This value can't be modified after created.
I32 h3cRrppRingPrimaryPort	1.3.6.1.4.1.2011.10.2.45.2.2.1.6	Integer32	read-create	If the switch is a master-node or transit-node, this value is the primary port ifIndex; otherwise, if the switch is a edge-node or assistant-edge-node, this value is the common port ifIndex. This value can't be modified after created.
I32 h3cRrppRingSecondaryPort	1.3.6.1.4.1.2011.10.2.45.2.2.1.7	Integer32	read-create	If the switch is a master-node or transit-node, this value is the secondary port ifIndex; otherwise, if the switch is an edge-node or assistant-edge-node, this value is the edge port ifIndex. This value can't be modified after created.
INT h3cRrppRingLevel	1.3.6.1.4.1.2011.10.2.45.2.2.1.8	INTEGER	read-create	Level of a ring. This field should be set 1 on major-ring and 2 on the sub-ring. This value can't be modified after created.
ROW h3cRrppRingRowStatus	1.3.6.1.4.1.2011.10.2.45.2.2.1.9	RowStatus	read-create	This object is responsible for managing the creation, deletion and modification of rows, which support active status and CreatAndGo, destroy operation. To create a new row, h3cRrppRingNodeMode, h3cRrppRingPrimaryPort, h3cRrppRingSecondaryPort and h3cRrppRingLevel must be specified.
h3cRrppPortTable	1.3.6.1.4.1.2011.10.2.45.2.3		not-accessible	A table containing information about configurations and status of a RRPP port.
h3cRrppPortEntry	1.3.6.1.4.1.2011.10.2.45.2.3.1		not-accessible	Detailed information of a specified RRPP port.
I32 h3cRrppPortID	1.3.6.1.4.1.2011.10.2.45.2.3.1.1	Integer32	not-accessible	ifIndex of the port.
INT h3cRrppPortRole	1.3.6.1.4.1.2011.10.2.45.2.3.1.2	INTEGER	read-only	The RRPP role of the port. (i.e. primary, secondary, common or edge port).
INT h3cRrppPortState	1.3.6.1.4.1.2011.10.2.45.2.3.1.3	INTEGER	read-only	State of RRPP port, including unknown, unblocked, blocked and down.
C32 h3cRrppPortRXErrorEx	1.3.6.1.4.1.2011.10.2.45.2.3.1.4	Counter32	read-only	The statistics of illegal RRPP packets received from this port.
C32 h3cRrppPortRXHello	1.3.6.1.4.1.2011.10.2.45.2.3.1.5	Counter32	read-only	The statistics of hello packets received from this port on specified ring.
C32 h3cRrppPortRXLinkUp	1.3.6.1.4.1.2011.10.2.45.2.3.1.6	Counter32	read-only	The statistics of link-up packets received from this port on specified ring.
C32 h3cRrppPortRXLinkDown	1.3.6.1.4.1.2011.10.2.45.2.3.1.7	Counter32	read-only	The statistics of link-down packets received from this port on specified ring.
C32 h3cRrppPortRXCommonFlush	1.3.6.1.4.1.2011.10.2.45.2.3.1.8	Counter32	read-only	The statistics of common-flush packets received from this port on specified ring. Instruction When master-node receives valid link-down packets or link-up packets, it will send common-flush packets, instructing the other nodes on the ring to flush their forwarding database. When the nodes except master-node receive common-flush, they will flush forwarding database. If there is any port blocked on that node, it won't be unblocked.
C32 h3cRrppPortRXCompleteFlush	1.3.6.1.4.1.2011.10.2.45.2.3.1.9	Counter32	read-only	The statistics of complete-flush packets received from this port on specified ring. Instruction When the ring recovers, master-node will receive its own hello packets. It will send complete-flush packets, instructing the other nodes on the ring to flush their forwarding database. When the nodes except master-node receive complete-flush, they will flush forwarding database. If there is any port blocked on that node, it will be unblocked.
C32 h3cRrppPortTXHello	1.3.6.1.4.1.2011.10.2.45.2.3.1.10	Counter32	read-only	The statistics of hello packets sent from this port on specified ring.
C32 h3cRrppPortTXLinkUp	1.3.6.1.4.1.2011.10.2.45.2.3.1.11	Counter32	read-only	The statistics of link-up packets sent from this port on specified ring.
C32 h3cRrppPortTXLinkDown	1.3.6.1.4.1.2011.10.2.45.2.3.1.12	Counter32	read-only	The statistics of link-down packets sent from this port on specified ring.
C32 h3cRrppPortTXCommonFlush	1.3.6.1.4.1.2011.10.2.45.2.3.1.13	Counter32	read-only	The statistics of common-flush packets sent from this port on specified ring.
C32 h3cRrppPortTXCompleteFlush	1.3.6.1.4.1.2011.10.2.45.2.3.1.14	Counter32	read-only	The statistics of complete-flush packets sent from this port on specified ring.
C32 h3cRrppPortRXEdgeHello	1.3.6.1.4.1.2011.10.2.45.2.3.1.15	Counter32	read-only	The statistics of edge-hello packets received from this port on specified ring. When edge-node sends edge-hello packets, assistantEdge-node will receive its own edge-hello packets from the common link and the master ring.
C32 h3cRrppPortRXMajorFault	1.3.6.1.4.1.2011.10.2.45.2.3.1.16	Counter32	read-only	The statistics of major-fault packets received from this port on specified ring. When assistantEdge can't receive edge-hello packets in the specified fault-time, assistantEdge-node will send its own major-fault packets from the edge port around the sub ring. Edge-node will receive the major-fault packets from its edge port. Then Edge-node will block its edge port.
C32 h3cRrppPortTXEdgeHello	1.3.6.1.4.1.2011.10.2.45.2.3.1.17	Counter32	read-only	The statistics of edge-hello packets sent from this port on specified ring.
C32 h3cRrppPortTXMajorFault	1.3.6.1.4.1.2011.10.2.45.2.3.1.18	Counter32	read-only	The statistics of major-fault packets sent from this port on specified ring.
h3cRrppNotifications	1.3.6.1.4.1.2011.10.2.45.3
NTF h3cRrppRingRecover	1.3.6.1.4.1.2011.10.2.45.3.1			Trap message is generated by master-node on the ring when the ring recovers from fault.
NTF h3cRrppRingFail	1.3.6.1.4.1.2011.10.2.45.3.2			Trap message is generated by master-node on the ring when the ring fails.
NTF h3cRrppMultiMaster	1.3.6.1.4.1.2011.10.2.45.3.3			Trap message is generated by master-node when it detects there are more than one master-node on the ring.
NTF h3cRrppMajorFault	1.3.6.1.4.1.2011.10.2.45.3.4			Trap message is generated by edge-node or assistant-edge-node when it detects major fault.

RFC description

Implements Rapid Ring Protection Protocol (RRPP) for fast recovery in Ethernet ring topologies on H3C switches.

Start monitoring H3C Layer 2/3 Ethernet switch (Rapid Ring Protection Protocol) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download H3C-RRPP-MIB