All MIBs › RFC1389-MIB
Category: IETF Standards
Description:
Defines RIP version 2 routing protocol management objects for neighbor and route monitoring per RFC 1389.
Imported Objects
From RFC-1212
| OBJECT-TYPE |
From RFC1155-SMI
| Counter | |
| IpAddress | |
| TimeTicks |
What Is RFC1389-MIB?
RFC1389-MIB is an IETF standards-track MIB (RFC 1389) that defines managed objects for monitoring and managing RIP Version 2 (RIPv2), the classless distance-vector IP routing protocol, on any device running it. It is registered under the standard mib-2 tree (rip2) and covers RIP-specific data such as neighbor/peer routing information and per-interface RIP configuration and route counters. In monitoring terms it is used to check the software-level health of the RIP routing process on a router - verifying which neighbors are exchanging routes, catching route-count anomalies, and confirming the protocol is actively running on expected interfaces - rather than reporting physical hardware status. Since the module is small and its identifiers are easy to overlook, network engineers frequently consult an RFC1389-MIB OID list to map each managed object to its numeric OID before configuring polling. As a standards MIB it is used alongside the base IP-MIB and IF-MIB for interface context, and was effectively superseded by RFC 1724's RIPv2-MIB. It is deployed on any RIPv2-capable router or Layer 3 switch, typically in small-to-mid-sized enterprise networks still using RIP for interior routing.
IPNetwork Monitor allows you to monitor SNMP objects defined in RFC1389-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
- RIPv2 neighbor/peer status
- per-interface RIP configuration
- route counts
- RIP protocol operational status
Supported Devices
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer
- any router or Layer 3 switch running RIP version 2
Monitoring Examples
The sample objects available (mgmt, mib-2, rip2) are top-level tree nodes rather than specific data tables; in practice an admin would poll the RIP neighbor and interface tables under the rip2 subtree to confirm active RIPv2 peers and per-interface route counts, watching for a neighbor dropping out as a sign of a routing adjacency failure.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| mgmt | 1.3.6.1.2 | |||
| mib_2 | 1.3.6.1.2.1 | |||
| rip2 | 1.3.6.1.2.1.23 | |||
| rip2GlobalGroup | 1.3.6.1.2.1.23.1 | |||
| CTR rip2GlobalRouteChanges | 1.3.6.1.2.1.23.1.1 | Counter | 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. |
| CTR rip2GlobalQueries | 1.3.6.1.2.1.23.1.2 | Counter | read-only | The number of responses sent to RIP queries from other systems. |
| rip2IfStatTable | 1.3.6.1.2.1.23.2 | not-accessible | A list of subnets which require separate status monitoring in RIP. | |
| rip2IfStatEntry | 1.3.6.1.2.1.23.2.1 | not-accessible | A Single Routing Domain in a single Subnet. | |
| 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. |
| CTR rip2IfStatRcvBadPackets | 1.3.6.1.2.1.23.2.1.2 | Counter | 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). |
| CTR rip2IfStatRcvBadRoutes | 1.3.6.1.2.1.23.2.1.3 | Counter | read-only | The number of routes, in valid RIP packets, which were ignored for any reason (e.g. unknown address family, or invalid metric). |
| CTR rip2IfStatSentUpdates | 1.3.6.1.2.1.23.2.1.4 | Counter | read-only | The number of triggered RIP updates actually sent on this interface. This explicitly does NOT include full updates sent containing new information. |
| INT rip2IfStatStatus | 1.3.6.1.2.1.23.2.1.5 | INTEGER | read-write | 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. | |
| rip2IfConfEntry | 1.3.6.1.2.1.23.3.1 | not-accessible | A Single Routing Domain in a single Subnet. | |
| 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. |
| ROU rip2IfConfDomain | 1.3.6.1.2.1.23.3.1.2 | RouteTag | read-write | Value inserted into the Routing Domain field of all RIP packets sent on this interface. |
| INT rip2IfConfAuthType | 1.3.6.1.2.1.23.3.1.3 | INTEGER | read-write | The type of Authentication used on this interface. |
| OCT rip2IfConfAuthKey | 1.3.6.1.2.1.23.3.1.4 | OCTET STRING | read-write | The value to be used as the Authentication Key whenever the corresponding instance of rip2IfConfAuthType has the value simplePassword word. 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 rip2IfConfSend | 1.3.6.1.2.1.23.3.1.5 | INTEGER | read-write | 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. |
| INT rip2IfConfReceive | 1.3.6.1.2.1.23.3.1.6 | INTEGER | read-write | This indicates which version of RIP updates are to be accepted. Note that rip2 and rip1OrRip2 implies reception of multicast packets. |
| INT rip2IfConfDefaultMetric | 1.3.6.1.2.1.23.3.1.7 | INTEGER | read-write | 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. |
| INT rip2IfConfStatus | 1.3.6.1.2.1.23.3.1.8 | INTEGER | read-write | Writing invalid has the effect of deleting this interface. |
| IP rip2IfConfSrcAddress | 1.3.6.1.2.1.23.3.1.9 | IpAddress | read-write | 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. |
| rip2PeerTable | 1.3.6.1.2.1.23.4 | not-accessible | A list of RIP Peers. | |
| rip2PeerEntry | 1.3.6.1.2.1.23.4.1 | not-accessible | Information regarding a single routing peer. | |
| 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. |
| TIK rip2PeerLastUpdate | 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. |
| 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. |
| CTR rip2PeerRcvBadPackets | 1.3.6.1.2.1.23.4.1.5 | Counter | read-only | The number of RIP response packets from this peer discarded as invalid. |
| CTR rip2PeerRcvBadRoutes | 1.3.6.1.2.1.23.4.1.6 | Counter | read-only | The number of routes from this peer that were ignored because the entry format was invalid. |
RFC description
RIP Version 2 MIB extensions (RFC 1389) for managing RIP-2 routing protocol objects, statistics, and neighbor relationships.
Start monitoring vendor-neutral, standards-based MIB, any router or Layer 3 switch running RIP version 2 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.