RIP Version 2 MIB Extensions
obsoleted by
- rfc-1724 — RIP Version 2 MIB Extension
Extracted elements (25)
Global counters (rip2GlobalRouteChanges, rip2GlobalQueries) are intended to facilitate rapid debugging of quickly changing routes or failing neighbors, not just long-term statistics.
rip2IfConfDomain inserts a value into the Routing Domain field of all RIP packets sent on the interface, defaulting to 0x0000, enabling routing domain separation where needed.
Textual conventions Validation and RouteTag have no effect on syntax or semantics of managed objects; they are adopted solely to improve readability and ease comparison with other specifications.
The MIB explicitly preserves compatibility with RIP-1 systems by providing per-interface controls to monitor and govern version interactions, since the two protocol versions coexist on the same network.
Because RIP versions 1 and 2 do not handle addressless links, the MIB assumes RIP interfaces correspond to subnets within a routing domain, not unnumbered point-to-point links.
Receive modes rip2 and rip1OrRip2 both imply reception of multicast packets; deployments must ensure the interface can receive RIP-2 multicast when either value is configured.
rip1Compatible send mode broadcasts RIP-2 updates using RFC 1058 route subsumption rules, enabling interoperability with RIP-1 routers that do not understand RIP-2 multicast.
Implementation of the RIP Interface Groups (rip2IfStatTable and rip2IfConfTable) is mandatory for all systems that implement RIP-2.
Implementation of the rip2GlobalGroup (global counters) is mandatory for all systems that implement RIP-2.
Implementation of the rip2PeerTable is optional; it is intended to assist in debugging active peer relationships.
rip2GlobalQueries is a read-only Counter tracking the number of responses sent to RIP queries from other systems.
rip2GlobalRouteChanges is a read-only Counter under rip2GlobalGroup tracking the number of changes made to the IP Route Database by RIP.
rip2IfConfAuthType is a read-write INTEGER with values noAuthentication(1) and simplePassword(2), defaulting to noAuthentication.
rip2IfConfDefaultMetric is an INTEGER in range 0..15 controlling the metric advertised as a default route; a value of zero means no default route should be originated.
rip2IfConfReceive controls accepted RIP versions per interface: rip1(1), rip2(2), or rip1OrRip2(3); defaults to rip1OrRip2.
rip2IfConfSend controls what RIP version is sent per interface: doNotSend(1), ripVersion1(2), rip1Compatible(3), or ripVersion2(4); defaults to rip1Compatible.
rip2IfConfTable is a per-subnet configuration table with fields for routing domain tag, authentication type and key, send/receive version control, and default metric.
rip2IfStatSentUpdates counts only triggered RIP updates sent on an interface; it explicitly does not include full updates sent containing new information.
rip2IfStatTable is an interface status table indexed by IP address, containing per-subnet counters: rip2IfStatRcvBadPackets, rip2IfStatRcvBadRoutes, and rip2IfStatSentUpdates, plus a Validation status object.
rip2PeerTable is an optional read-only table indexed by (rip2PeerAddress, rip2PeerDomain), recording the last update time, RIP version, and per-peer bad packet/route counters for debugging.
rip2PeerVersion records the RIP version number from the header of the last RIP packet received from a peer, as an INTEGER in range 0..255.
Reading rip2IfConfAuthKey always returns an OCTET STRING of length zero regardless of the configured value, preventing authentication keys from being retrieved via SNMP GET operations.
The Security Considerations section states that security issues are not discussed in this memo; the only authentication mechanism exposed is simple password via rip2IfConfAuthType.
rip2IfConfAuthKey is an OCTET STRING of SIZE(0..16); if a string shorter than 16 octets is supplied, it is left-justified and padded on the right with null bytes (0x00) to form a 16-octet key.
RouteTag is a textual convention defined as OCTET STRING SIZE(2), representing the 2-octet Route Tag field present in RIP-2 packet headers and route entries.