HPN-ICF-RRPP-MIB

All MIBs › HPN-ICF-RRPP-MIB

Last Updated: 2004-12-02

Category: Technology: High Availability, Technology: Switching/L2, Vendor: H3C/HH3C, Vendor: HP/HPE

Description: Manages Rapid Ring Protection Protocol (RRPP) ring topology and failover state on HP/Comware switches.

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 HPN-ICF-RRPP-MIB?

HPN-ICF-RRPP-MIB is an HP/Comware ICF MIB managing Rapid Ring Protection Protocol (RRPP), a fast Layer 2 ring-topology failover mechanism used as an alternative to Spanning Tree on Ethernet rings, recovering from a link break in under a second. It exposes global RRPP enable state, authentication (password/type), and per-domain configuration including control VLAN, hello/fail timers, and instance assignment, plus fault notifications. Its monitoring role is ring-topology health: administrators track domain state and timer configuration to confirm the ring is intact and protection switching parameters are set correctly, and watch RRPP notifications to detect ring breaks or unexpected topology changes in near-real time. It is conceptually related to but distinct from the IEEE 802.1 Spanning Tree family, explicitly designed as a faster-converging alternative per its own description. It is deployed on HP/H3C Comware switches interconnected in Ethernet ring topologies, typically in metro or campus ring networks. Engineers can download the HPN-ICF-RRPP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HPN-ICF-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

HP/H3C Comware switch in Ethernet ring topology

Monitoring Examples

An administrator polls hpnicfRrppDomainTable/hpnicfRrppDomainEntry to check hpnicfRrppDomainHelloTime and hpnicfRrppDomainFailTime configuration against the ring's actual failover behavior, and hpnicfRrppDomainControlVlanID to confirm the correct control VLAN is in use. hpnicfRrppEnableStatus confirms RRPP is actually active globally, and hpnicfRrppNotifications would fire when a ring link break is detected, letting the admin correlate a reported outage with automatic ring protection switching. hpnicfRrppDomainRowStatus shows whether a given ring domain is properly provisioned (active) or left incomplete.

What Can Be Monitored

RRPP global enable state
per-domain hello/fail timers
control VLAN configuration
ring domain provisioning status
ring break/topology-change notifications

Imported Objects

From HPN-ICF-OID-MIB

hpnicfCommon

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 hpnicfRrppPortRXError OID:

Select an HP/H3C Comware switch in Ethernet ring topology (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 hpnicfRrppPortRXError 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
hpnicfRrpp	1.3.6.1.4.1.11.2.14.11.15.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.
hpnicfRrppScalarGroup	1.3.6.1.4.1.11.2.14.11.15.2.45.1
ENA hpnicfRrppEnableStatus	1.3.6.1.4.1.11.2.14.11.15.2.45.1.1	EnabledStatus	read-write	Indicating whether the RRPP is enabled on this switch.
OCT hpnicfRrppPassword	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppPasswordType which indicates whether this value can be got. This value can not be set alone without configuring hpnicfRrppPasswordType.
INT hpnicfRrppPasswordType	1.3.6.1.4.1.11.2.14.11.15.2.45.1.3	INTEGER	read-write	Indicating whether the hpnicfRrppPassword can be got. simple(1):hpnicfRrppPassword can be got. cipher(2):hpnicfRrppPassword can not be got. This value can not be set alone without configuring hpnicfRrppPassword.
INT hpnicfRrppProtectVlanConfigMode	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainProtectVlanListLow and hpnicfRrppDomainProtectVlanListHigh can be used for setting protected VLANs, while hpnicfRrppDomainInstanceListLow and hpnicfRrppDomainInstanceListHigh cannot. By contraries, the value 'instance' indicates that 3cRrppDomainInstanceListLow and hpnicfRrppDomainInstanceListHigh can be used for setting protected VLANs while the other two cannot.
hpnicfRrppTable	1.3.6.1.4.1.11.2.14.11.15.2.45.2
hpnicfRrppDomainTable	1.3.6.1.4.1.11.2.14.11.15.2.45.2.1		not-accessible	A table containing information about configurations and status of a RRPP domain.
hpnicfRrppDomainEntry	1.3.6.1.4.1.11.2.14.11.15.2.45.2.1.1		not-accessible	Detailed information of a specified RRPP domain.
I32 hpnicfRrppDomainID	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainControlVlanID	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainHelloTime	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainFailTime	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainHelloTime's value.
ROW hpnicfRrppDomainRowStatus	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainInstanceListLow	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainInstanceListHigh at the same time when a SET operation is performed. This object is valid only when the value of hpnicfRrppProtectVlanConfigMode 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 hpnicfRrppDomainInstanceListHigh	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainInstanceListLow at the same time when a SET operation is performed. This object is valid only when the value of hpnicfRrppProtectVlanConfigMode 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 hpnicfRrppDomainProtectVlanListLow	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainProtectVlanListHigh at the same time when a SET operation is performed. This object is valid only when the value of hpnicfRrppProtectVlanConfigMode 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 hpnicfRrppDomainProtectVlanListHigh	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppDomainProtectVlanListLow at the same time when a SET operation is performed. This object is valid only when the value of hpnicfRrppProtectVlanConfigMode 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.
hpnicfRrppRingTable	1.3.6.1.4.1.11.2.14.11.15.2.45.2.2		not-accessible	A table containing information about configurations and status of a RRPP Ring.
hpnicfRrppRingEntry	1.3.6.1.4.1.11.2.14.11.15.2.45.2.2.1		not-accessible	Detailed information of a specified RRPP Ring.
I32 hpnicfRrppRingID	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppRingEnableStatus	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppRingActive	1.3.6.1.4.1.11.2.14.11.15.2.45.2.2.1.3	INTEGER	read-only	As both hpnicfRrppEnableStatus and hpnicfRrppRingEnableStatus are enabled, the ring is activated. Whereas either of the two items is disabled, the ring is inactive.
INT hpnicfRrppRingState	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppRingNodeMode	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppRingPrimaryPort	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppRingSecondaryPort	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppRingLevel	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppRingRowStatus	1.3.6.1.4.1.11.2.14.11.15.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, hpnicfRrppRingNodeMode, hpnicfRrppRingPrimaryPort, hpnicfRrppRingSecondaryPort and hpnicfRrppRingLevel must be specified.
hpnicfRrppPortTable	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3		not-accessible	A table containing information about configurations and status of a RRPP port.
hpnicfRrppPortEntry	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1		not-accessible	Detailed information of a specified RRPP port.
I32 hpnicfRrppPortID	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.1	Integer32	not-accessible	ifIndex of the port.
INT hpnicfRrppPortRole	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.2	INTEGER	read-only	The RRPP role of the port. (i.e. primary, secondary, common or edge port).
INT hpnicfRrppPortState	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.3	INTEGER	read-only	State of RRPP port, including unknown, unblocked, blocked and down.
C32 hpnicfRrppPortRXErrorEx	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.4	Counter32	read-only	The statistics of illegal RRPP packets received from this port.
C32 hpnicfRrppPortRXHello	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.5	Counter32	read-only	The statistics of hello packets received from this port on specified ring.
C32 hpnicfRrppPortRXLinkUp	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.6	Counter32	read-only	The statistics of link-up packets received from this port on specified ring.
C32 hpnicfRrppPortRXLinkDown	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.7	Counter32	read-only	The statistics of link-down packets received from this port on specified ring.
C32 hpnicfRrppPortRXCommonFlush	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppPortRXCompleteFlush	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppPortTXHello	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.10	Counter32	read-only	The statistics of hello packets sent from this port on specified ring.
C32 hpnicfRrppPortTXLinkUp	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.11	Counter32	read-only	The statistics of link-up packets sent from this port on specified ring.
C32 hpnicfRrppPortTXLinkDown	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.12	Counter32	read-only	The statistics of link-down packets sent from this port on specified ring.
C32 hpnicfRrppPortTXCommonFlush	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.13	Counter32	read-only	The statistics of common-flush packets sent from this port on specified ring.
C32 hpnicfRrppPortTXCompleteFlush	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.14	Counter32	read-only	The statistics of complete-flush packets sent from this port on specified ring.
C32 hpnicfRrppPortRXEdgeHello	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppPortRXMajorFault	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppPortTXEdgeHello	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.17	Counter32	read-only	The statistics of edge-hello packets sent from this port on specified ring.
C32 hpnicfRrppPortTXMajorFault	1.3.6.1.4.1.11.2.14.11.15.2.45.2.3.1.18	Counter32	read-only	The statistics of major-fault packets sent from this port on specified ring.
hpnicfRrppNotifications	1.3.6.1.4.1.11.2.14.11.15.2.45.3
NTF hpnicfRrppRingRecover	1.3.6.1.4.1.11.2.14.11.15.2.45.3.1			Trap message is generated by master-node on the ring when the ring recovers from fault.
NTF hpnicfRrppRingFail	1.3.6.1.4.1.11.2.14.11.15.2.45.3.2			Trap message is generated by master-node on the ring when the ring fails.
NTF hpnicfRrppMultiMaster	1.3.6.1.4.1.11.2.14.11.15.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 hpnicfRrppMajorFault	1.3.6.1.4.1.11.2.14.11.15.2.45.3.4			Trap message is generated by edge-node or assistant-edge-node when it detects major fault.

RFC description

Manages the H3C/HP Rapid Ring Protection Protocol (RRPP), providing ring topology protection and fast recovery for Ethernet networks.

Start monitoring HP/H3C Comware switch in Ethernet ring topology (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 HPN-ICF-RRPP-MIB