The Rapid Ring Protection Protocol (RRPP) is a link layer protocol designed for Ethernet rings. RRPP can prevent broadcast storms caused by data loops when an Ethernet ring is healthy. RRPP can also rapidly restore the communication paths between the nodes when a link is disconnected on the ring.

Use this MIB to define management information for devices that support RRPP.

MIB file name

hh3c-rrpp.mib

Root object

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).huawei(2011).h3c(10).h3cCommon(2).h3cRrpp(45)

Scalar objects

hh3cRrppEnableStatus

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cRrppEnableStatus (1.3.6.1.4.1.25506.2.45.1.1)	read-write	INTEGER	enabled(1), disabled(2)	Whether RRPP is enabled on the device globally.	As per the MIB.

hh3cRrppPassword

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cRrppPassword (1.3.6.1.4.1.25506.2.45.1.2)	read-write	OCTET STRING	OCTET STRING(SIZE(1..16))	Password configured for RRPP.	Not supported

hh3cRrppPasswordType

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cRrppPasswordType (1.3.6.1.4.1.25506.2.45.1.3)	read-write	INTEGER	simple(1),cipher(2)	Password type.	Not supported

hh3cRrppProtectVlanConfigMode

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cRrppProtectVlanConfigMode (1.3.6.1.4.1.25506.2.45.1.4)	read-only	INTEGER	vlan(1), instance(2)	Mode in which the protected VLANs are configured for RPPP.	As per the MIB.

Tabular objects

hh3cRrppDomainTable

About this table

This table contains RRPP domain configuration information.

Support for operations

Create	Edit/Modify	Delete	Read
1. A maximum of 128 RRPP domains can be created. 2. When creating an RRPP domain, you must configure hh3cRrppDomainControlVlanID. 3. h3cRrppDomainID must be configured. 4. h3cRrppDomainHelloTime and h3cRrppDomainFailTime are optional. If configuration is required, they must be both configured. 5. By default, h3cRrppDomainHelloTime is 1 and h3cRrppDomainFailTime is 3. 6. The h3cRrppDomainFailTime value must be greater than or equal to three times the h3cRrppDomainHelloTime value. 7. h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh are optional. If configuration is required, they must be both configured. 8. h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh are optional. If configuration is required, they must be both configured. 9. If the value of h3cRrppProtectVlanConfigMode is vlan, you can only use h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh to configure protected VLANs. Configuration for the h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh nodes does not take effect. If the value of h3cRrppProtectVlanConfigMode is instance, you can only use h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh to configure VLANs mapped to the specified MSTIs as protected VLANs. Configuration for the h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh nodes does not take effect. 10. When configuring h3cRrppDomainControlVlanID, make sure the VLAN does not exist nor is a reserved VLAN.	1. h3cRrppDomainControlVlanID cannot be modified after being created. 2. To modify h3cRrppDomainHelloTime and h3cRrppDomainFailTime, configure the values for them at the same time. 3. The h3cRrppDomainFailTime value must be greater than or equal to three times the h3cRrppDomainHelloTime value. 4. To modify h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh, configure the values for them at the same time. 5. To modify h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh, configure the values for them at the same time. 6. If the value of h3cRrppProtectVlanConfigMode is vlan, you can only use h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHighto configure protected VLANs. Configuration for the h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh nodes does not take effect. If the value of h3cRrppProtectVlanConfigMode is instance, you can only use h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh to configure VLANs mapped to the specified MSTIs as protected VLANs. Configuration for the h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh nodes does not take effect.	An RRPP domain that has RRPP rings cannot be deleted.	Supported

Create

Edit/Modify

Delete

Read

1. A maximum of 128 RRPP domains can be created.

2. When creating an RRPP domain, you must configure hh3cRrppDomainControlVlanID.

3. h3cRrppDomainID must be configured.

4. h3cRrppDomainHelloTime and h3cRrppDomainFailTime are optional. If configuration is required, they must be both configured.

5. By default, h3cRrppDomainHelloTime is 1 and h3cRrppDomainFailTime is 3.

6. The h3cRrppDomainFailTime value must be greater than or equal to three times the h3cRrppDomainHelloTime value.

7. h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh are optional. If configuration is required, they must be both configured.

8. h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh are optional. If configuration is required, they must be both configured.

9. If the value of h3cRrppProtectVlanConfigMode is vlan, you can only use h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh to configure protected VLANs. Configuration for the h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh nodes does not take effect. If the value of h3cRrppProtectVlanConfigMode is instance, you can only use h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh to configure VLANs mapped to the specified MSTIs as protected VLANs. Configuration for the h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh nodes does not take effect.

10. When configuring h3cRrppDomainControlVlanID, make sure the VLAN does not exist nor is a reserved VLAN.

1. h3cRrppDomainControlVlanID cannot be modified after being created.

2. To modify h3cRrppDomainHelloTime and h3cRrppDomainFailTime, configure the values for them at the same time.

3. The h3cRrppDomainFailTime value must be greater than or equal to three times the h3cRrppDomainHelloTime value.

4. To modify h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh, configure the values for them at the same time.

5. To modify h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh, configure the values for them at the same time.

6. If the value of h3cRrppProtectVlanConfigMode is vlan, you can only use h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHighto configure protected VLANs. Configuration for the h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh nodes does not take effect. If the value of h3cRrppProtectVlanConfigMode is instance, you can only use h3cRrppDomainInstanceListLow and h3cRrppDomainInstanceListHigh to configure VLANs mapped to the specified MSTIs as protected VLANs. Configuration for the h3cRrppDomainProtectVlanListLow and h3cRrppDomainProtectVlanListHigh nodes does not take effect.

An RRPP domain that has RRPP rings cannot be deleted.

Supported

Columns

The table index is hh3cRrppDomainID.

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cRrppDomainID (1.3.6.1.4.1.25506.2.45.2.1.1.1)	accessible-for-notify	Integer32	1..128	RRPP domain ID	As per the MIB.
hh3cRrppDomainControlVlanID (1.3.6.1.4.1.25506.2.45.2.1.1.2)	read-create	Integer32	2..4094\|65535	Control VLAN ID	1. This object sets the primary control VLAN by its ID in the range of 2 to 4093. 1.The secondary control VLAN ID is automatically configured by using the primary control VLAN ID plus 1. 2. A control VLAN already configured for an RRPP domain cannot be modified or deleted. 3. Make sure the control VLAN for the RRPP domain has not been created nor reserved.
hh3cRrppDomainHelloTime (1.3.6.1.4.1.25506.2.45.2.1.1.3)	read-create	Integer32	1..10	Hello timer of the RRPP domain.	As per the MIB.
hh3cRrppDomainFailTime (1.3.6.1.4.1.25506.2.45.2.1.1.4)	read-create	Integer32	3..30	Fail timer of the RRPP domain.	As per the MIB.
hh3cRrppDomainRowStatus (1.3.6.1.4.1.25506.2.45.2.1.1.5)	read-create	RowStatus	SIZE(256)	Row status.	As per the MIB.
hh3cRrppDomainInstanceListLow (1.3.6.1.4.1.25506.2.45.2.1.1.6)	read-create	OCTET STRING	SIZE(256)	Low MSTI ID of the MSTI list mapped to protected VLANs.	As per the MIB.
hh3cRrppDomainInstanceListHigh (1.3.6.1.4.1.25506.2.45.2.1.1.7)	read-create	OCTET STRING	SIZE(256)	High MSTI ID of the MSTI list mapped to protected VLANs.	As per the MIB.

hh3cRrppRingTable

About this table

This table contains RRPP ring configuration information.

Support for operations

Create	Edit/Modify	Delete	Read
1. A maximum of 128 RRPP rings can be created for an RRPP domain. 2. h3cRrppDomainID must be configured. This index is provided by h3cRrppDomainID in h3cRrppDomainTable. 3. h3cRrppRingID must be configured. 4. The ring IDs in an RRPP domain must be different. The ring IDs in different RRPP domains can be the same. 5. You must configure h3cRrppRingNodeMode, h3cRrppRingPrimaryPort, h3cRrppRingSecondaryPort, and h3cRrppRingLevel. 6. h3cRrppRingEnableStatus is optional. The default value is disabled(2). 7. An RRPP ring cannot be created and enabled at the same time. You must create a ring and then enable it. 8. You must first create the primary ring and configure transit node for it before creating a subring and configure edge node and the assistant edge node for the subring. Make sure the two rings have only one common port.	1. Only the h3cRrppRingEnableStatus value can be modified. If an RRPP domain contains both a primary ring and subrings: a. To set the value from disabled to enabled, first enable the primary ring and then enable the subrings. b. To set the value from enabled to disabled, first disable all subrings and then disable the primary ring. 2. Other values cannot be modified. To modify a value, delete the row and then create it again.	1. An activated domain cannot be deleted. If h3cRrppRingActive is set to Active(1), the row cannot be deleted. 2. If subrings exist in an RRPP domain, the primary ring cannot be deleted.	Supported

Create

Edit/Modify

Delete

Read

1. A maximum of 128 RRPP rings can be created for an RRPP domain.

2. h3cRrppDomainID must be configured. This index is provided by h3cRrppDomainID in h3cRrppDomainTable.

3. h3cRrppRingID must be configured.

4. The ring IDs in an RRPP domain must be different. The ring IDs in different RRPP domains can be the same.

5. You must configure h3cRrppRingNodeMode, h3cRrppRingPrimaryPort, h3cRrppRingSecondaryPort, and h3cRrppRingLevel.

6. h3cRrppRingEnableStatus is optional. The default value is disabled(2).

7. An RRPP ring cannot be created and enabled at the same time. You must create a ring and then enable it.

8. You must first create the primary ring and configure transit node for it before creating a subring and configure edge node and the assistant edge node for the subring. Make sure the two rings have only one common port.

1. Only the h3cRrppRingEnableStatus value can be modified. If an RRPP domain contains both a primary ring and subrings:

a. To set the value from disabled to enabled, first enable the primary ring and then enable the subrings.

b. To set the value from enabled to disabled, first disable all subrings and then disable the primary ring.

2. Other values cannot be modified. To modify a value, delete the row and then create it again.

1. An activated domain cannot be deleted. If h3cRrppRingActive is set to Active(1), the row cannot be deleted.

2. If subrings exist in an RRPP domain, the primary ring cannot be deleted.

Supported

Columns

The table indexes are hh3cRrppDomainID and hh3cRrppRingID.

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cRrppRingID (1.3.6.1.4.1.25506.2.45.2.2.1.1)	accessible-for-notify	Integer32	1..64128	RRPP ring ID.	As per the MIB.
hh3cRrppRingEnableStatus (1.3.6.1.4.1.25506.2.45.2.2.1.2)	read-create	INTEGER	enabled(1), disabled(2)	Enabling status of the RRPP ring.	As per the MIB.
hh3cRrppRingActive (1.3.6.1.4.1.25506.2.45.2.2.1.3)	read-only	INTEGER	active(1),inactive(2)	Whether the RRPP ring is activated.	As per the MIB.
hh3cRrppRingState (1.3.6.1.4.1.25506.2.45.2.2.1.4)	read-only	INTEGER	unknown(1), health(2), fault(3)	RRPP ring state.	As per the MIB.
hh3cRrppRingNodeMode (1.3.6.1.4.1.25506.2.45.2.2.1.5)	read-create	INTEGER	master(1), transit(2), edge(3), assistantEdge(4)	Node mode of the device in the RRPP ring.	As per the MIB.
hh3cRrppRingPrimaryPort (1.3.6.1.4.1.25506.2.45.2.2.1.6)	read-create	Integer32	Standard MIB values.	Primary port of the device in the RRPP ring.	1. On a primary node or transit node, the value is the interface index of the primary port. If no primary port exists, the value is 0. 2. Common port on an edge node or the assistant edge node.
hh3cRrppRingSecondaryPort (1.3.6.1.4.1.25506.2.45.2.2.1.7)	read-create	Integer32	Standard MIB values.	Secondary port of the device in the RRPP ring.	If no secondary port or edge port exist, the value is 0.
hh3cRrppRingLevel (1.3.6.1.4.1.25506.2.45.2.2.1.8)	read-create	INTEGER	majorRing(1), subRing(2)	RRPP ring level.	As per the MIB.
hh3cRrppRingRowStatus (1.3.6.1.4.1.25506.2.45.2.2.1.9)	read-create	RowStatus	active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)	Row status.	As per the MIB.

hh3cRrppPortTable

About this table

This table contains RRPP port statistics information.

Support for operations

Create	Edit/Modify	Delete	Read
Supported	Supported	Supported	Supported

Columns

The table indexes are hh3cRrppDomainID, hh3cRrppRingID, and hh3cRrppPortID.

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cRrppPortID (1.3.6.1.4.1.25506.2.45.2.3.1.1)	not-accessible	Integer32	Standard MIB values.	Port ID.	As per the MIB.
hh3cRrppPortRole (1.3.6.1.4.1.25506.2.45.2.3.1.2)	read-only	INTEGER	primary(1), secondary(2), common(3), edge(4)	Port role.	As per the MIB.
hh3cRrppPortState (1.3.6.1.4.1.25506.2.45.2.3.1.3)	read-only	INTEGER	unknown(1), unblocked(2), blocked(3), down(4)	Port state.	As per the MIB.
hh3cRrppPortRXError (1.3.6.1.4.1.25506.2.45.2.3.1.4)	read-only	Counter32	Standard MIB values.	Number of error packets received on the port.	As per the MIB.
hh3cRrppPortRXHello (1.3.6.1.4.1.25506.2.45.2.3.1.5)	read-only	Counter32	Standard MIB values.	Number of hello packets received on the port.	As per the MIB.
hh3cRrppPortRXLinkUp (1.3.6.1.4.1.25506.2.45.2.3.1.6)	read-only	Counter32	Standard MIB values.	Number of LinkUp packets received on the port.	As per the MIB.
hh3cRrppPortRXLinkDown (1.3.6.1.4.1.25506.2.45.2.3.1.7)	read-only	Counter32	Standard MIB values.	Number of LinkDown packets received on the port.	As per the MIB.
hh3cRrppPortRXCommonFlush (1.3.6.1.4.1.25506.2.45.2.3.1.8)	read-only	Counter32	Standard MIB values.	Number of CommonFlush packets received on the port.	As per the MIB.
hh3cRrppPortRXCompleteFlush (1.3.6.1.4.1.25506.2.45.2.3.1.9)	read-only	Counter32	Standard MIB values.	Number of CompleteFlush packets received on the port.	As per the MIB.
hh3cRrppPortTXHello (1.3.6.1.4.1.25506.2.45.2.3.1.10)	read-only	Counter32	Standard MIB values.	Number of hello packets sent on the port.	As per the MIB.
hh3cRrppPortTXLinkUp (1.3.6.1.4.1.25506.2.45.2.3.1.11)	read-only	Counter32	Standard MIB values.	Number of LinkUp packets sent on the port.	As per the MIB.
hh3cRrppPortTXLinkDown (1.3.6.1.4.1.25506.2.45.2.3.1.12)	read-only	Counter32	Standard MIB values.	Number of LinkDown packets sent on the port.	As per the MIB.
hh3cRrppPortTXCommonFlush (1.3.6.1.4.1.25506.2.45.2.3.1.13)	read-only	Counter32	Standard MIB values.	Number of CommonFlush packets sent on the port.	As per the MIB.
hh3cRrppPortTXCompleteFlush (1.3.6.1.4.1.25506.2.45.2.3.1.14)	read-only	Counter32	Standard MIB values.	Number of CompleteFlush packets sent on the port.	As per the MIB.
hh3cRrppPortRXEdgeHello (1.3.6.1.4.1.25506.2.45.2.3.1.15)	read-only	Counter32	Standard MIB values.	Number of EdgeHello packets received on the port.	As per the MIB.
hh3cRrppPortRXMajorFault (1.3.6.1.4.1.25506.2.45.2.3.1.16)	read-only	Counter32	Standard MIB values.	Number of MajorFault packets received on the port.	As per the MIB.
hh3cRrppPortTXEdgeHello (1.3.6.1.4.1.25506.2.45.2.3.1.17)	read-only	Counter32	Standard MIB values.	Number of EdgeHello packets sent on the port.	As per the MIB.
hh3cRrppPortTXMajorFault (1.3.6.1.4.1.25506.2.45.2.3.1.18)	read-only	Counter32	Standard MIB values.	Number of MajorFault packets sent on the port.	As per the MIB.

Notifications

hh3cRrppRingRecover

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.45.3.1	The RRPP ring state is restored from Disconnect to Health.	Informational	Warning	N/A	OFF

Notification triggers

A notification sent when the RRPP ring state is restored from Disconnect to Health. The notification is reported by the master node.

Possible reasons for generating this notification are as follows:

· The faults are recovered on other nodes in the network, and the master node receives the Health packet sent by itself through the secondary port.

· The port on the master node is recovered and comes up, and the master node receives the Health packet sent by itself through the secondary port.

System impact

No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable rrpp ring-recover command.

OFF

CLI: Use the undo snmp-agent trap enable rrpp ring-recover command.

Objects

OID (object name)

Description

Index nodes

Type

Value range

1.3.6.1.4.1.25506.2.45.2.1.1.1 (hh3cRrppDomainID)

RRPP domain ID.

hh3cRrppDomainID

Integer32

As per the MIB.

1.3.6.1.4.1.25506.2.45.2.2.1.1 (hh3cRrppRingID)

RRPP ring ID.

hh3cRrppDomainID

hh3cRrppRingID

Integer32

As per the MIB.

Recommended action

No action is required.

hh3cRrppRingFail

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.45.3.2	The RRPP ring state transitions from Health to Disconnect.	Informational	Warning	1.3.6.1.4.1.25506.2.45.3.1 (hh3cRrrpRingRecover)	OFF

Notification triggers

A notification sent when the RRPP ring state transitions from Health to Disconnect. The notification is reported by the master node.

Possible reasons for generating this notification are as follows:

· A physical link is disconnected in the ring network.

· The link quality is poor in the ring network, and packet loss occurs.

System impact

The RRPP ring is in Disconnect state, and a link switchover might occur.

Status control

ON

CLI: Use the snmp-agent trap enable rrpp ring-fail command.

OFF

CLI: Use the undo snmp-agent trap enable rrpp ring-fail command.

Objects

OID (object name)

Description

Index nodes

Type

Value range

1.3.6.1.4.1.25506.2.45.2.1.1.1

(hh3cRrppDomainID)

RRPP domain ID.

hh3cRrppDomainID

Integer32

As per the MIB.

1.3.6.1.4.1.25506.2.45.2.2.1.1 (hh3cRrppRingID)

RRPP ring ID.

hh3cRrppDomainID

hh3cRrppRingID

Integer32

As per the MIB.

Recommended action

To resolve this issue:

1. Execute the display rrpp verbose on each node on the ring to identify the faulty node.

2. Troubleshoot the node interface and configuration.

3. If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

hh3cRrppMultiMaster

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.45.3.3	Multiple master nodes are configured for the RRPP ring.	Informational	Warning	N/A	OFF

Notification triggers

Device configuration error. Multiple master nodes are configured for the same RRPP ring.

System impact

The RRPP ring cannot be created.

Status control

ON

CLI: Use the snmp-agent trap enable rrpp multi-master command.

OFF

CLI: Use the undo snmp-agent trap enable rrpp multi-master command.

Objects

OID (object name)

Description

Index nodes

Type

Value range

1.3.6.1.4.1.25506.2.45.2.1.1.1 (hh3cRrppDomainID)

RRPP domain ID.

hh3cRrppDomainID

Integer32

As per the MIB.

1.3.6.1.4.1.25506.2.45.2.2.1.1 (hh3cRrppRingID)

RRPP ring ID.

hh3cRrppDomainID

hh3cRrppRingID

Integer32

As per the MIB.

Recommended action

Check the configuration on each node, and make sure the RRPP ring has only one master node.

hh3cRrppMajorFault

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.45.3.4	The SRPTs between the edge node and the assistant edge node are disconnected.	Informational	Warning	N/A	OFF

Notification triggers

A notification sent when the SRPTs between the edge node and the assistant edge node are disconnected.

System impact

The SRPTs become faulty.

Status control

ON

CLI: Use the snmp-agent trap enable rrpp major-fault command.

OFF

CLI: Use the undo snmp-agent trap enable rrpp major-fault command.

Objects

OID (object name)

Description

Index nodes

Type

Value range

1.3.6.1.4.1.25506.2.45.2.1.1.1 (hh3cRrppDomainID)

RRPP domain ID.

hh3cRrppDomainID

Integer32

As per the MIB.

1.3.6.1.4.1.25506.2.45.2.2.1.1 (hh3cRrppRingID)

RRPP ring ID.

hh3cRrppDomainID

hh3cRrppRingID

Integer32

As per the MIB.

Recommended action

Check the fault status on the primary ring and restore the fault.

17-High Availability

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

Basic information

Notification triggers

System impact

Status control

ON

OFF

Objects

Recommended action

Basic information

Notification triggers

System impact

Status control

ON

OFF

Objects

Recommended action

Basic information

Notification triggers

System impact

Status control

ON

OFF

Objects

Recommended action

Basic information

Notification triggers

System impact

Status control

ON

OFF

Objects

Recommended action

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us