JACOBS-RPL-MIB

All MIBs › JACOBS-RPL-MIB

Organization: Jacobs University Bremen

Last Updated: 2012-10-19

Category: Technology: Routing, Vendor: Jacobs University

Description: Defines managed objects for the RPL (Routing Protocol for Low-Power and Lossy Networks) as implemented in research networks at Jacobs University Bremen.

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 JACOBS-RPL-MIB?

JACOBS-RPL-MIB is a research-oriented IETF-style MIB developed at Jacobs University Bremen for monitoring nodes running RPL (Routing Protocol for Low-Power and Lossy Networks), the IPv6 routing protocol used in low-power wireless mesh/IoT networks. It exposes configuration defaults for RPL behavior, such as DODAG Information Solicitation (DIS) timing, DAO delay/acknowledgement settings, route preference, hop-rank increase limits, mode of operation, and trickle-timer interval parameters. As a protocol-health MIB it is used mainly to verify that a low-power mesh node's routing configuration and operational parameters are correctly applied, functioning as a software/protocol-status check rather than a hardware sensor MIB. It is explicitly an IETF-derived module (published under IETF Trust copyright) intended to complement or extend other 6LoWPAN/IPv6 routing MIBs in constrained-network research. Typical deployment is academic or industrial research testbeds studying low-power and lossy networks (e.g., sensor mesh, IoT) rather than production enterprise gear. Engineers can download the JACOBS-RPL-MIB file directly to load it into their MIB browser.

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

low-power/lossy wireless mesh node (IoT/sensor device)
vendor-neutral, standards-based MIB, not tied to a specific manufacturer

Monitoring Examples

A researcher would inspect rplDefaultModeOfOperation and rplDefaultPreference to confirm a mesh node is configured with the intended RPL mode and DODAG rank preference, and would check rplDefaultDISTimeout and rplDefaultIntervalMin/rplDefaultIntervalDoublings to validate the trickle-timer schedule governing how often DIS/DAO messages are sent. rplDefaultDAOAckEnabled indicates whether the node expects acknowledged Destination Advertisement Object messages, which affects route reliability. rplNotifications would alert on RPL topology or configuration events, while rplConformance defines the compliance groups for implementations.

What Can Be Monitored

RPL mode of operation
DODAG rank preference
DIS/DAO timer settings
DAO acknowledgement configuration
hop-rank increase limits
trickle-timer interval parameters

Imported Objects

From IF-MIB

InterfaceIndex

From INET-ADDRESS-MIB

InetAddressIPv6

From JACOBS-SMI

cnds	OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32
mib-2

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using rplMemOverflows OID:

Select a Low-power/lossy wireless mesh node (IoT/sensor device, RPL routing) 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 rplMemOverflows into the Find box to locate it in the OID tree, then select it and click OK. The number of memory allocation failures (e.g., routing table overflows). 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
rplActive	1.3.6.1.4.1.30982.1.2.1.2
ADR rplActiveDodag	1.3.6.1.4.1.30982.1.2.1.2.2	InetAddressIPv6	read-write	The currently active RPL DODAG in the active RPL Instance. Changes to this value may not persist across restarts.
U32 rplActiveDodagTriggerSequence	1.3.6.1.4.1.30982.1.2.1.2.3	Unsigned32	read-write	The DAO Trigger Sequence Number (DTSN) of the active DODAG as defined in Section 6.3.1 of RFC 6550. Changes to this value may not persist across restarts.
RPL rplActiveInstance	1.3.6.1.4.1.30982.1.2.1.2.1	RplInstanceID	read-write	The currently active RPL Instance. Changes to this value may not persist across restarts.
C32 rplActiveNoParentSecs	1.3.6.1.4.1.30982.1.2.1.8.12	Counter32	read-only	The number of seconds with packets to forward without a next hop (DODAG parent).
rplCompliances	1.3.6.1.4.1.30982.1.2.2.2
rplConformance	1.3.6.1.4.1.30982.1.2.2
T/F rplDefaultDAOAckEnabled	1.3.6.1.4.1.30982.1.2.1.1.5	TruthValue	read-write	Indicates whether DAO Acknowledgements are sent on this RPL instance. Changes to this value may not persist across restarts.
RPL rplDefaultDAODelay	1.3.6.1.4.1.30982.1.2.1.1.4	RplDAODelay	read-write	The default delay for aggregations before a DAO is send. Changes to this value may not persist across restarts.
U32 rplDefaultDISMessages	1.3.6.1.4.1.30982.1.2.1.1.2	Unsigned32	read-write	The number of DIS messages that are sent as an initial probe for nearby DODAGs if the DIS mode is 'send'. The value of this object is ignored if the DIS mode is 'silent'. Changes to this value may not persist across restarts.
RPL rplDefaultDISMode	1.3.6.1.4.1.30982.1.2.1.1.1	RplDISMode	read-write	Determines whether a DIS message is send upon boot-up. Changes to this value may not persist across restarts.
U32 rplDefaultDISTimeout	1.3.6.1.4.1.30982.1.2.1.1.3	Unsigned32	read-write	The number of seconds after which a node in DIS mode 'send' in the absence of DIO messages may decide to root a floating DODAG. Changes to this value may not persist across restarts.
U32 rplDefaultIntervalDoublings	1.3.6.1.4.1.30982.1.2.1.1.10	Unsigned32	read-write	The default Imax parameter of the DIO trickle timer. Changes to this value may not persist across restarts.
U32 rplDefaultIntervalMin	1.3.6.1.4.1.30982.1.2.1.1.11	Unsigned32	read-write	The default Imin parameter of the DIO trickle timer. Changes to this value may not persist across restarts.
U32 rplDefaultMaxRankIncrease	1.3.6.1.4.1.30982.1.2.1.1.8	Unsigned32	read-write	The default maximum allowable increase in rank in support of local repair. If DAGMaxRankIncrease is 0 then this mechanism is disabled. Changes to this value may not persist across restarts.
RPL rplDefaultMinHopRankIncrease	1.3.6.1.4.1.30982.1.2.1.1.7	RplMinHopRankIncrease	read-write	The default minimum increase of the rank in a single hop. Changes to this value may not persist across restarts.
RPL rplDefaultModeOfOperation	1.3.6.1.4.1.30982.1.2.1.1.9	RplModeOfOperation	read-write	The mode of operation of the RPL instance. Changes to this value may not persist across restarts.
RPL rplDefaultPreference	1.3.6.1.4.1.30982.1.2.1.1.6	RplDodagPreference	read-write	The default preference of this DODAG compared to other DODAGs within the same instance. Changes to this value may not persist across restarts.
U32 rplDefaultRedundancyConstant	1.3.6.1.4.1.30982.1.2.1.1.12	Unsigned32	read-write	The default k parameter of the DIO trickle timer. Changes to this value may not persist across restarts.
rplDefaults	1.3.6.1.4.1.30982.1.2.1.1
rplDodagChildEntry	1.3.6.1.4.1.30982.1.2.1.7.1		not-accessible	Information about a known DODAG child.
ADR rplDodagChildID	1.3.6.1.4.1.30982.1.2.1.7.1.1	InetAddressIPv6	not-accessible	An RPL child associated with this DODAG.
NUM rplDodagChildIf	1.3.6.1.4.1.30982.1.2.1.7.1.2	InterfaceIndex	read-only	The interface over which the child can be reached.
rplDodagChildTable	1.3.6.1.4.1.30982.1.2.1.7		not-accessible	The list of children for a DODAG.
T/F rplDodagDAOAckEnabled	1.3.6.1.4.1.30982.1.2.1.5.1.8	TruthValue	read-only	Indicates whether DAO Acknowledgements are sent on this DODAG.
RPL rplDodagDAODelay	1.3.6.1.4.1.30982.1.2.1.5.1.7	RplDAODelay	read-only	The delay for aggregations before a DAO is send.
rplDodagEntry	1.3.6.1.4.1.30982.1.2.1.5.1		not-accessible	An entry representing information about a DODAG.
ADR rplDodagID	1.3.6.1.4.1.30982.1.2.1.5.1.2	InetAddressIPv6	read-only	The identifier of a DODAG root (DODAGID) of this RPL instance. The root of the DODAG reports its own IPv6 address as the DODAG root. This is uniquely identifying a DODAG within an RPL instance.
U32 rplDodagIndex	1.3.6.1.4.1.30982.1.2.1.5.1.1	Unsigned32	not-accessible	The index identifying a DODAG within an RPL instance. This index is used to keep the table indexes short. The RPL protocol identifies a DODAG within an RPL instance by the DODAGID.
U32 rplDodagIntervalDoublings	1.3.6.1.4.1.30982.1.2.1.5.1.12	Unsigned32	read-only	The Imax parameter of the DIO trickle timer.
U32 rplDodagIntervalMin	1.3.6.1.4.1.30982.1.2.1.5.1.13	Unsigned32	read-only	The Imin parameter of the DIO trickle timer.
U32 rplDodagMaxRankIncrease	1.3.6.1.4.1.30982.1.2.1.5.1.11	Unsigned32	read-only	The maximum allowable increase in rank in support of local repair. If DAGMaxRankIncrease is 0 then this mechanism is disabled.
RPL rplDodagMinHopRankIncrease	1.3.6.1.4.1.30982.1.2.1.5.1.10	RplMinHopRankIncrease	read-only	The minimum increase of the rank in a single hop.
NUM rplDodagOCP	1.3.6.1.4.1.30982.1.2.1.5.1.6	RplObjectiveCodePoint	read-only	The Objective Code Point of this DODAG.
rplDodagParentEntry	1.3.6.1.4.1.30982.1.2.1.6.1		not-accessible	Information about a known DODAG parent.
ADR rplDodagParentID	1.3.6.1.4.1.30982.1.2.1.6.1.1	InetAddressIPv6	not-accessible	An RPL parent associated with this DODAG.
NUM rplDodagParentIf	1.3.6.1.4.1.30982.1.2.1.6.1.2	InterfaceIndex	read-only	The interface over which the parent can be reached.
rplDodagParentTable	1.3.6.1.4.1.30982.1.2.1.6		not-accessible	The list of parents for a DODAG.
RPL rplDodagPathControlSize	1.3.6.1.4.1.30982.1.2.1.5.1.15	RplPathControlSize	read-only	The Path Control Size of this DODAG.
RPL rplDodagPreference	1.3.6.1.4.1.30982.1.2.1.5.1.9	RplDodagPreference	read-only	How preferred this DODAG is compared to other DODAGs within the same instance.
RPL rplDodagRank	1.3.6.1.4.1.30982.1.2.1.5.1.4	RplRank	read-only	The rank of the node within the DODAG.
U32 rplDodagRedundancyConstant	1.3.6.1.4.1.30982.1.2.1.5.1.14	Unsigned32	read-only	The k parameter of the DIO trickle timer.
INT rplDodagState	1.3.6.1.4.1.30982.1.2.1.5.1.5	INTEGER	read-only	The status of the DODAG: other(0) An unknown state. grounded(1) The DODAG is grounded. floating(2) The DODAG is floating (not grounded).
rplDodagTable	1.3.6.1.4.1.30982.1.2.1.5		not-accessible	The table represents information about all locally known DODAGs.
RPL rplDodagVersion	1.3.6.1.4.1.30982.1.2.1.5.1.3	RplDodagVersionNumber	read-only	The version of the DODAG in this RPL instance.
C32 rplFBitSet	1.3.6.1.4.1.30982.1.2.1.8.15	Counter32	read-only	Number of packets received with the 'F' bit set as defined in Section 18.3.2 of RFC 6550.
rplFullCompliance	1.3.6.1.4.1.30982.1.2.2.2.1			Compliance statement for implementations supporting read/write access, according to the object definitions.
rplGeneralGroup	1.3.6.1.4.1.30982.1.2.2.1.1			A collection of objects providing general information about the RPL implementation.
rplGroups	1.3.6.1.4.1.30982.1.2.2.1
U32 rplInstanceDISMessages	1.3.6.1.4.1.30982.1.2.1.4.1.3	Unsigned32	read-only	The number of DIS messages that are sent as an initial probe for nearby DODAGs if the DIS mode is 'send'.
RPL rplInstanceDISMode	1.3.6.1.4.1.30982.1.2.1.4.1.2	RplDISMode	read-only	Reports whether a DIS message is send for this instance upon boot-up.
U32 rplInstanceDISTimeout	1.3.6.1.4.1.30982.1.2.1.4.1.4	Unsigned32	read-only	The number of seconds after which a node in DIS mode 'send' in the absence of DIO messages may decide to root a floating DODAG.
rplInstanceEntry	1.3.6.1.4.1.30982.1.2.1.4.1		not-accessible	An entry representing information about a RPL Instance.
rplInstanceGroup	1.3.6.1.4.1.30982.1.2.2.1.2			A collection of objects providing insight into RPL Instances and RPL DODAGs.
RPL rplInstanceID	1.3.6.1.4.1.30982.1.2.1.4.1.1	RplInstanceID	not-accessible	The InstanceID of this RPL Instance.
RPL rplInstanceModeOfOperation	1.3.6.1.4.1.30982.1.2.1.4.1.5	RplModeOfOperation	read-only	The mode of operation of the RPL instance.
rplInstanceTable	1.3.6.1.4.1.30982.1.2.1.4		not-accessible	The table represents information about all known RPL Instances.
C32 rplIntegrityCheckFailures	1.3.6.1.4.1.30982.1.2.1.8.5	Counter32	read-only	The number of messages discarded because the integrity check failed against the received message authentication code (MAC) as defined in Section 10.7. of RFC 6550.
C32 rplMemOverflowsEx	1.3.6.1.4.1.30982.1.2.1.8.1	Counter32	read-only	The number of memory allocation failures (e.g., routing table overflows).
rplMib	1.3.6.1.4.1.30982.1.2			The MIB module for monitoring nodes implementing the IPv6 routing protocol for low power and lossy networks (RPL). Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
rplMsgStatsEntry	1.3.6.1.4.1.30982.1.2.1.9.1		not-accessible	Statistics for a specific RPL message type.
C32 rplMsgStatsInMsgs	1.3.6.1.4.1.30982.1.2.1.9.1.2	Counter32	read-only	The number of RPL messages received of this type.
C32 rplMsgStatsOutMsgs	1.3.6.1.4.1.30982.1.2.1.9.1.3	Counter32	read-only	The number of RPL messages sent of this type.
rplMsgStatsTable	1.3.6.1.4.1.30982.1.2.1.9		not-accessible	Basic RPL message statistics by message type.
RPL rplMsgStatsType	1.3.6.1.4.1.30982.1.2.1.9.1.1	RplMessageType	not-accessible	The RPL message type being counted by this row.
C32 rplNoInstanceIDs	1.3.6.1.4.1.30982.1.2.1.8.8	Counter32	read-only	The number of times a packet could not be sent because of a missing RPLInstanceID.
C32 rplNoParentSecs	1.3.6.1.4.1.30982.1.2.1.8.11	Counter32	read-only	The number of seconds without a next hop (DODAG parent).
rplNotifications	1.3.6.1.4.1.30982.1.2.0
C32 rplOBitClearedUpwards	1.3.6.1.4.1.30982.1.2.1.8.14	Counter32	read-only	Number of packets received with the 'O' bit cleared from a node with a lower rank as defined in Section 18.3.2 of RFC 6550.
C32 rplOBitSetDownwards	1.3.6.1.4.1.30982.1.2.1.8.13	Counter32	read-only	Number of packets received with the 'O' bit set from a node with a higher rank as defined in Section 18.3.2 of RFC 6550.
rplObjects	1.3.6.1.4.1.30982.1.2.1
NUM rplOCPCodepoint	1.3.6.1.4.1.30982.1.2.1.3.1.1	RplObjectiveCodePoint	not-accessible	A supported Objective Code Point.
T/F rplOCPEnabled	1.3.6.1.4.1.30982.1.2.1.3.1.2	TruthValue	read-write	Enables the usage of this Objective Code Point. Changes to this value may not persist across restarts.
rplOCPEntry	1.3.6.1.4.1.30982.1.2.1.3.1		not-accessible	An entry representing a supported Objective Code Point.
rplOCPTable	1.3.6.1.4.1.30982.1.2.1.3		not-accessible	The table of all supported Objective Code Points (OCPs).
C32 rplParseErrors	1.3.6.1.4.1.30982.1.2.1.8.2	Counter32	read-only	The number of received malformed messages.
C32 rplRBitSet	1.3.6.1.4.1.30982.1.2.1.8.16	Counter32	read-only	Number of packets received with the 'R' bit set as defined in Section 18.3.2 of RFC 6550.
rplReadOnlyCompliance	1.3.6.1.4.1.30982.1.2.2.2.2			Compliance statement for implementations supporting only readonly access.
C32 rplReplayProtectionFailures	1.3.6.1.4.1.30982.1.2.1.8.6	Counter32	read-only	The number of messages discarded because the received message Counter value is non-zero and less than the maintained incoming Counter watermark or because the received Timestamp Counter value indicates a message transmission time that is earlier than the Current time less the acceptable packet delay as defined in Section 10.7. of RFC 6550. This counter is also incremented if the temporal consistency check of the message fails as defined in Section 10.7.1.
C32 rplSecurityPolicyViolations	1.3.6.1.4.1.30982.1.2.1.8.4	Counter32	read-only	The number of messages discarded because the described level of security for the message type and originator is unknown or does not meet locally maintained security policies as defined in Section 10.7. of RFC 6550.
rplStats	1.3.6.1.4.1.30982.1.2.1.8
rplStatsGroup	1.3.6.1.4.1.30982.1.2.2.1.3			A collection of objects providing statistics about the RPL implementation.
C32 rplTrickleTimerResets	1.3.6.1.4.1.30982.1.2.1.8.17	Counter32	read-only	The number of trickle timer resets.
C32 rplTriggeredGlobalRepairs	1.3.6.1.4.1.30982.1.2.1.8.10	Counter32	read-only	The number of times a global repair procedure was triggered.
C32 rplTriggeredLocalRepairs	1.3.6.1.4.1.30982.1.2.1.8.9	Counter32	read-only	The number of times a local repair procedure was triggered.
C32 rplUnknownMsgTypes	1.3.6.1.4.1.30982.1.2.1.8.3	Counter32	read-only	The number of received RPL messages that we dropped because the message type is not recognized by the implementation.
C32 rplValidParentFailures	1.3.6.1.4.1.30982.1.2.1.8.7	Counter32	read-only	The number of times a packet could not be sent to a DODAG parent flagged as valid.

RFC description

Monitors IPv6 RPL (Routing Protocol for Low-power and Lossy Networks) on resource-constrained devices.

Start monitoring Low-power/lossy wireless mesh node (IoT/sensor device, RPL routing) 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 JACOBS-RPL-MIB