RIPv2-MIB

MIB Reference — IPNetwork Monitor

All MIBsRIPv2-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.

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

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.

What Can Be Monitored

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

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.

OIDs
OID symbolicOID numericTypeAccessDescription
rip21.3.6.1.2.1.23The MIB module to describe the RIP2 Version 2 Protocol
rip2Globals1.3.6.1.2.1.23.1
C32 rip2GlobalRouteChanges1.3.6.1.2.1.23.1.1Counter32read-onlyThe number of route changes made to the IP Route Database by RIP. This does not include the refresh of a route's age.
C32 rip2GlobalQueries1.3.6.1.2.1.23.1.2Counter32read-onlyThe number of responses sent to RIP queries from other systems.
rip2IfStatTable1.3.6.1.2.1.23.2not-accessibleA list of subnets which require separate status monitoring in RIP.
rip2IfStatEntry1.3.6.1.2.1.23.2.1not-accessibleA Single Routing Domain in a single Subnet.
IP rip2IfStatAddress1.3.6.1.2.1.23.2.1.1IpAddressread-onlyThe 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.
C32 rip2IfStatRcvBadPackets1.3.6.1.2.1.23.2.1.2Counter32read-onlyThe 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 rip2IfStatRcvBadRoutes1.3.6.1.2.1.23.2.1.3Counter32read-onlyThe number of routes, in valid RIP packets, which were ignored for any reason (e.g. unknown address family, or invalid metric).
C32 rip2IfStatSentUpdates1.3.6.1.2.1.23.2.1.4Counter32read-onlyThe number of triggered RIP updates actually sent on this interface. This explicitly does NOT include full updates sent containing new information.
ROW rip2IfStatStatus1.3.6.1.2.1.23.2.1.5RowStatusread-createWriting invalid has the effect of deleting this interface.
rip2IfConfTable1.3.6.1.2.1.23.3not-accessibleA list of subnets which require separate configuration in RIP.
rip2IfConfEntry1.3.6.1.2.1.23.3.1not-accessibleA Single Routing Domain in a single Subnet.
IP rip2IfConfAddress1.3.6.1.2.1.23.3.1.1IpAddressread-onlyThe 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.
ROU rip2IfConfDomain1.3.6.1.2.1.23.3.1.2RouteTagread-createValue inserted into the Routing Domain field of all RIP packets sent on this interface.
INT rip2IfConfAuthType1.3.6.1.2.1.23.3.1.3INTEGERread-createThe type of Authentication used on this interface.
OCT rip2IfConfAuthKey1.3.6.1.2.1.23.3.1.4OCTET STRINGread-createThe 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 rip2IfConfSend1.3.6.1.2.1.23.3.1.5INTEGERread-createWhat 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.
INT rip2IfConfReceive1.3.6.1.2.1.23.3.1.6INTEGERread-createThis indicates which version of RIP updates are to be accepted. Note that rip2 and rip1OrRip2 implies reception of multicast packets.
INT rip2IfConfDefaultMetric1.3.6.1.2.1.23.3.1.7INTEGERread-createThis 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.
ROW rip2IfConfStatus1.3.6.1.2.1.23.3.1.8RowStatusread-createWriting invalid has the effect of deleting this interface.
IP rip2IfConfSrcAddress1.3.6.1.2.1.23.3.1.9IpAddressread-createThe 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.
rip2PeerTable1.3.6.1.2.1.23.4not-accessibleA list of RIP Peers.
rip2PeerEntry1.3.6.1.2.1.23.4.1not-accessibleInformation regarding a single routing peer.
IP rip2PeerAddress1.3.6.1.2.1.23.4.1.1IpAddressread-onlyThe 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 rip2PeerDomain1.3.6.1.2.1.23.4.1.2RouteTagread-onlyThe value in the Routing Domain field in RIP packets received from the peer. As domain suuport is deprecated, this must be zero.
TIK rip2PeerLastUpdate1.3.6.1.2.1.23.4.1.3TimeTicksread-onlyThe value of sysUpTime when the most recent RIP update was received from this system.
INT rip2PeerVersion1.3.6.1.2.1.23.4.1.4INTEGERread-onlyThe RIP version number in the header of the last RIP packet received.
C32 rip2PeerRcvBadPackets1.3.6.1.2.1.23.4.1.5Counter32read-onlyThe number of RIP response packets from this peer discarded as invalid.
C32 rip2PeerRcvBadRoutes1.3.6.1.2.1.23.4.1.6Counter32read-onlyThe number of routes from this peer that were ignored because the entry format was invalid.
rip2Conformance1.3.6.1.2.1.23.5
rip2Groups1.3.6.1.2.1.23.5.1
rip2GlobalGroup1.3.6.1.2.1.23.5.1.1This group defines global controls for RIP-II systems.
rip2IfStatGroup1.3.6.1.2.1.23.5.1.2This group defines interface statistics for RIP-II systems.
rip2IfConfGroup1.3.6.1.2.1.23.5.1.3This group defines interface configuration for RIP-II systems.
rip2PeerGroup1.3.6.1.2.1.23.5.1.4This group defines peer information for RIP-II systems.
rip2Compliances1.3.6.1.2.1.23.5.2
rip2Compliance1.3.6.1.2.1.23.5.2.1The compliance statement

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