RIPv2-MIB

All MIBs › RIPv2-MIB

Organization: IETF RIP-II Working Group

Last Updated: 1994-07-27

Category: Network Interfaces, Routing Protocols

Description: Defines managed objects for managing the Routing Information Protocol version 2 (RIPv2), including interface configuration and peer status information.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring RIPv2-MIB with a free 30-day trial of IPNetwork Monitor.

What Is RIPv2-MIB?

RIPv2-MIB is a vendor-neutral IETF standards-based MIB (in the RFC 1724 lineage) for managing the Routing Information Protocol version 2, a distance-vector IP routing protocol. It exposes routing-protocol configuration and status data: per-interface RIP configuration, protocol-wide globals, and peer/neighbor status information reflecting the health of RIP adjacencies. Rather than hardware environmental data, its monitoring value is protocol/software-level -- it lets an operator confirm RIP is running correctly on an interface and detect flapping or unreachable RIP peers, serving as a software/service-status analog to checking whether a routing process is healthy. It depends on the standard IF-MIB for interface indexing used to correlate RIP-enabled interfaces to their configuration and status entries. It is deployed on routers and Layer 3 switches from any vendor running RIPv2 for IP routing, typically in small-to-mid-sized or legacy enterprise networks, and reviewing the RIPv2-MIB OID list shows rip2Globals alongside the interface and peer tables under rip2Groups as the module's primary manageable objects.

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

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
IP routers and Layer 3 switches running RIPv2

Monitoring Examples

An operator would poll rip2Globals for protocol-wide counters and defaults, then walk the interface and peer tables defined under rip2Groups to check per-interface RIP configuration and peer state, catching a neighbor that has stopped sending updates, which indicates a routing adjacency failure. rip2Compliances and rip2Conformance describe which optional features and groups a given agent implements, useful when validating interoperability between different routers' RIP2 agents. A peer disappearing from the peer table would flag a link or routing-process failure needing investigation.

What Can Be Monitored

RIP protocol global counters/defaults
per-interface RIP configuration
RIP peer/neighbor status
routing adjacency health

Imported Objects

From RFC1213-MIB

mib-2

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using rip2PeerLastUpdate OID:

Select a device implementing RIPv2-MIB 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 rip2PeerLastUpdate 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. It records sysUpTime at the moment the most recent RIP update was received from this peer — comparing it against the device's current sysUpTime tells you how long it's been since that peer last sent an update. 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 TimeTicks-type OID, Value bounds is the most useful condition here — trigger an alert if the time since the last update from this peer exceeds a few RIP update intervals (e.g. 3x the normal ~30-second interval), which indicates the peer has likely gone silent or down. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
rip2	1.3.6.1.2.1.23			The MIB module to describe the RIP2 Version 2 Protocol
rip2Compliance	1.3.6.1.2.1.23.5.2.1			The compliance statement
rip2Compliances	1.3.6.1.2.1.23.5.2
rip2Conformance	1.3.6.1.2.1.23.5
rip2GlobalGroup	1.3.6.1.2.1.23.5.1.1			This group defines global controls for RIP-II systems.
C32 rip2GlobalQueries	1.3.6.1.2.1.23.1.2	Counter32	read-only	The number of responses sent to RIP queries from other systems.
C32 rip2GlobalRouteChanges	1.3.6.1.2.1.23.1.1	Counter32	read-only	The number of route changes made to the IP Route Database by RIP. This does not include the refresh of a route's age.
rip2Globals	1.3.6.1.2.1.23.1
rip2Groups	1.3.6.1.2.1.23.5.1
IP rip2IfConfAddress	1.3.6.1.2.1.23.3.1.1	IpAddress	read-only	The IP Address of this system on the indicated subnet. For unnumbered interfaces, the value 0.0.0.N, where the least significant 24 bits (N) is the ifIndex for the IP Interface in network byte order.
OCT rip2IfConfAuthKey	1.3.6.1.2.1.23.3.1.4	OCTET STRING	read-create	The value to be used as the Authentication Key whenever the corresponding instance of rip2IfConfAuthType has a value other than noAuthentication. A modification of the corresponding instance of rip2IfConfAuthType does not modify the rip2IfConfAuthKey value. If a string shorter than 16 octets is supplied, it will be left- justified and padded to 16 octets, on the right, with nulls (0x00). Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
INT rip2IfConfAuthType	1.3.6.1.2.1.23.3.1.3	INTEGER	read-create	The type of Authentication used on this interface.
INT rip2IfConfDefaultMetric	1.3.6.1.2.1.23.3.1.7	INTEGER	read-create	This variable indicates the metric that is to be used for the default route entry in RIP updates originated on this interface. A value of zero indicates that no default route should be originated; in this case, a default route via another router may be propagated.
ROU rip2IfConfDomain	1.3.6.1.2.1.23.3.1.2	RouteTag	read-create	Value inserted into the Routing Domain field of all RIP packets sent on this interface.
rip2IfConfEntry	1.3.6.1.2.1.23.3.1		not-accessible	A Single Routing Domain in a single Subnet.
rip2IfConfGroup	1.3.6.1.2.1.23.5.1.3			This group defines interface configuration for RIP-II systems.
INT rip2IfConfReceive	1.3.6.1.2.1.23.3.1.6	INTEGER	read-create	This indicates which version of RIP updates are to be accepted. Note that rip2 and rip1OrRip2 implies reception of multicast packets.
INT rip2IfConfSend	1.3.6.1.2.1.23.3.1.5	INTEGER	read-create	What the router sends on this interface. ripVersion1 implies sending RIP updates compliant with RFC 1058. rip1Compatible implies broadcasting RIP-2 updates using RFC 1058 route subsumption rules. ripVersion2 implies multicasting RIP-2 updates. ripV1Demand indicates the use of Demand RIP on a WAN interface under RIP Version 1 rules. ripV2Demand indicates the use of Demand RIP on a WAN interface under Version 2 rules.
IP rip2IfConfSrcAddress	1.3.6.1.2.1.23.3.1.9	IpAddress	read-create	The IP Address this system will use as a source address on this interface. If it is a numbered interface, this MUST be the same value as rip2IfConfAddress. On unnumbered interfaces, it must be the value of rip2IfConfAddress for some interface on the system.
ROW rip2IfConfStatus	1.3.6.1.2.1.23.3.1.8	RowStatus	read-create	Writing invalid has the effect of deleting this interface.
rip2IfConfTable	1.3.6.1.2.1.23.3		not-accessible	A list of subnets which require separate configuration in RIP.
IP rip2IfStatAddress	1.3.6.1.2.1.23.2.1.1	IpAddress	read-only	The IP Address of this system on the indicated subnet. For unnumbered interfaces, the value 0.0.0.N, where the least significant 24 bits (N) is the ifIndex for the IP Interface in network byte order.
rip2IfStatEntry	1.3.6.1.2.1.23.2.1		not-accessible	A Single Routing Domain in a single Subnet.
rip2IfStatGroup	1.3.6.1.2.1.23.5.1.2			This group defines interface statistics for RIP-II systems.
C32 rip2IfStatRcvBadPackets	1.3.6.1.2.1.23.2.1.2	Counter32	read-only	The number of RIP response packets received by the RIP process which were subsequently discarded for any reason (e.g. a version 0 packet, or an unknown command type).
C32 rip2IfStatRcvBadRoutes	1.3.6.1.2.1.23.2.1.3	Counter32	read-only	The number of routes, in valid RIP packets, which were ignored for any reason (e.g. unknown address family, or invalid metric).
C32 rip2IfStatSentUpdates	1.3.6.1.2.1.23.2.1.4	Counter32	read-only	The number of triggered RIP updates actually sent on this interface. This explicitly does NOT include full updates sent containing new information.
ROW rip2IfStatStatus	1.3.6.1.2.1.23.2.1.5	RowStatus	read-create	Writing invalid has the effect of deleting this interface.
rip2IfStatTable	1.3.6.1.2.1.23.2		not-accessible	A list of subnets which require separate status monitoring in RIP.
IP rip2PeerAddress	1.3.6.1.2.1.23.4.1.1	IpAddress	read-only	The IP Address that the peer is using as its source address. Note that on an unnumbered link, this may not be a member of any subnet on the system.
ROU rip2PeerDomain	1.3.6.1.2.1.23.4.1.2	RouteTag	read-only	The value in the Routing Domain field in RIP packets received from the peer. As domain suuport is deprecated, this must be zero.
rip2PeerEntry	1.3.6.1.2.1.23.4.1		not-accessible	Information regarding a single routing peer.
rip2PeerGroup	1.3.6.1.2.1.23.5.1.4			This group defines peer information for RIP-II systems.
TIK rip2PeerLastUpdateEx	1.3.6.1.2.1.23.4.1.3	TimeTicks	read-only	The value of sysUpTime when the most recent RIP update was received from this system.
C32 rip2PeerRcvBadPackets	1.3.6.1.2.1.23.4.1.5	Counter32	read-only	The number of RIP response packets from this peer discarded as invalid.
C32 rip2PeerRcvBadRoutes	1.3.6.1.2.1.23.4.1.6	Counter32	read-only	The number of routes from this peer that were ignored because the entry format was invalid.
rip2PeerTable	1.3.6.1.2.1.23.4		not-accessible	A list of RIP Peers.
INT rip2PeerVersion	1.3.6.1.2.1.23.4.1.4	INTEGER	read-only	The RIP version number in the header of the last RIP packet received.

RFC description

Manages Routing Information Protocol version 2 parameters, routes, and statistics per RFC 1723.

Start monitoring vendor-neutral, standards-based MIB, IP routers and Layer 3 switches running RIPv2 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 RIPv2-MIB