MSRIPSAP-MIB

All MIBs › MSRIPSAP-MIB

Category: IP Routing

Description: Manages Microsoft RIP SAP routing table and service advertisement protocol state.

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 MSRIPSAP-MIB?

MSRIPSAP-MIB is a Microsoft-specific MIB for the RIP (Routing Information Protocol) and SAP (Service Advertising Protocol, used with IPX) routing services on Windows Server. It exposes overall protocol operational state plus a per-interface configuration/status table covering administrative and operational state, update mode, update interval, and route aging. It is used to monitor the software status of the routing service — whether RIP and SAP are actually running (operational state) versus merely configured, and whether each interface is actively supplying and listening for routing updates. It is closely tied to the legacy IETF RIP-2 MIB conventions it mirrors for interface indexing and state semantics. It would typically be deployed in older enterprise networks where Windows servers acted as software routers using RIP for IP and SAP for IPX/Netware service advertisement. Engineers can download the MSRIPSAP-MIB file directly to load it into their MIB browser.

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

Windows Server (RIP/SAP routing service)
vendor-specific Microsoft MIB, not tied to network hardware

Monitoring Examples

An admin would check ripsapBaseRipOperState and ripsapBaseSapOperState to confirm the RIP and SAP services are operationally up, then walk ripIfTable/ripIfEntry keyed by ripIfIndex to see per-interface ripIfAdminState versus ripIfOperState. A mismatch — admin state enabled but operational state down on a given interface — flags a routing interface that failed to initialize; ripIfSupply and ripIfListen further show whether that interface is sending or accepting updates, and an unexpectedly long ripIfUpdateInterval could explain slow route convergence.

What Can Be Monitored

RIP protocol operational state
SAP protocol operational state
per-interface admin/operational state
route update interval and aging
interface supply/listen mode

Imported Objects

From MSFT-MIB

microsoft	OBJECT-IDENTITY
software	OBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

Counter
enterprises

OIDs

OID symbolic	OID numeric	Type	Access	Description
ripsap	1.3.6.1.4.1.311.1.9
ripsapBase	1.3.6.1.4.1.311.1.9.1
INT ripsapBaseRipOperState	1.3.6.1.4.1.311.1.9.1.1	INTEGER	read-only	Indicates the operational state of RIP.
INT ripsapBaseSapOperState	1.3.6.1.4.1.311.1.9.1.2	INTEGER	read-only	Indicates the operational state of SAP.
ripsapInterface	1.3.6.1.4.1.311.1.9.2
ripIfTable	1.3.6.1.4.1.311.1.9.2.1		not-accessible	The RIP interface table.
ripIfEntry	1.3.6.1.4.1.311.1.9.2.1.1		not-accessible	Each entry corresponds to one interface known to the system.
INT ripIfIndex	1.3.6.1.4.1.311.1.9.2.1.1.1	INTEGER	read-only	The identifier of this interface, unique within the instance of RIP. This value corresponds to the interface identifier found in ipxIfIndex.
INT ripIfAdminState	1.3.6.1.4.1.311.1.9.2.1.1.2	INTEGER	read-write	The desired state of the interface.
INT ripIfOperState	1.3.6.1.4.1.311.1.9.2.1.1.3	INTEGER	read-only	The current operational state of the interface. If ripIfAdminState is disabled(1) then ripIfOperState should be down(1). If ripIfAdminState is changed to enabled(2) then ripIfOperState should change to up(2) if the interface is ready to transmit and receive network traffic; it should change to sleeping(3) if the interface is waiting for external actions (such as a serial line waiting for an incomming connection); it should remain in the down(1) state if and only if there is a fault that prevents it from going to the up(2) state.
INT ripIfUpdateMode	1.3.6.1.4.1.311.1.9.2.1.1.4	INTEGER	read-write	The RIP update mechanism used on this interface. None(2) is used for static routes configurations. AutoStatic(3) means that the local router can issue an update request to the remote router and the response will be kept statically in the routing database as auto static routes. Standard(1) is the periodic broadcast RIP mechanism.
INT ripIfUpdateInterval	1.3.6.1.4.1.311.1.9.2.1.1.5	INTEGER	read-write	The RIP update interval, in sec. For Standard(1) ripIfUpdateMode, this is the interval with which periodic update broadcasts are sent, for AutoStatic(3) ripIfUpdateMode, this is the maximum interval for which router will listen for rip announcements, not used for None(2) ripIfUpdateMode
INT ripIfAgeMultiplier	1.3.6.1.4.1.311.1.9.2.1.1.6	INTEGER	read-write	The holding multiplier for routes received in RIP periodic updates (applies only if ripIfUpdateMode is Standard(1)).
INT ripIfSupply	1.3.6.1.4.1.311.1.9.2.1.1.7	INTEGER	read-write	Enable sending of RIP updates (change and periodic) on this interface.
INT ripIfListen	1.3.6.1.4.1.311.1.9.2.1.1.8	INTEGER	read-write	Enable listening to RIP updates on this interface.
CTR ripIfOutPackets	1.3.6.1.4.1.311.1.9.2.1.1.9	Counter	read-only	The number of RIP packets sent on this interface.
CTR ripIfInPackets	1.3.6.1.4.1.311.1.9.2.1.1.10	Counter	read-only	The number of RIP packets received on this interface.
sapIfTable	1.3.6.1.4.1.311.1.9.2.2		not-accessible	The SAP interface table.
sapIfEntry	1.3.6.1.4.1.311.1.9.2.2.1		not-accessible	Each entry corresponds to one interface known to the system.
INT sapIfIndex	1.3.6.1.4.1.311.1.9.2.2.1.1	INTEGER	read-only	The identifier of this interface, unique within the instance of SAP. This value corresponds to the interface identifier found in ipxIfIndex.
INT sapIfAdminState	1.3.6.1.4.1.311.1.9.2.2.1.2	INTEGER	read-write	The desired state of the interface.
INT sapIfOperState	1.3.6.1.4.1.311.1.9.2.2.1.3	INTEGER	read-only	The current operational state of the interface. If sapIfAdminState is disabled(1) then ripIfOperState should be down(1). If sapIfAdminState is changed to enabled(2) then sapIfOperState should change to up(2) if the interface is ready to transmit and receive network traffic; it should change to sleeping(3) if the interface is waiting for external actions (such as a serial line waiting for an incomming connection); it should remain in the down(1) state if and only if there is a fault that prevents it from going to the up(2) state.
INT sapIfUpdateMode	1.3.6.1.4.1.311.1.9.2.2.1.4	INTEGER	read-write	The SAP update mechanism used on this interface. None(2) is used for static routes configurations. AutoStatic(3) means that the local router can issue an update request to the remote router and the response will be kept statically in the routing database as auto static services. Standard(1) is the periodic broadcast SAP mechanism.
INT sapIfUpdateInterval	1.3.6.1.4.1.311.1.9.2.2.1.5	INTEGER	read-write	The SAP update interval, in sec. For Standard(1) ripIfUpdateMode, this is the interval with which periodic update broadcasts are sent, for AutoStatic(3) sapIfUpdateMode, this is the maximum interval for which router will listen for rip announcements. Not used for None (2) sapIfUpdateMode
INT sapIfAgeMultiplier	1.3.6.1.4.1.311.1.9.2.2.1.6	INTEGER	read-write	The holding multiplier for services received in SAP periodic updates (applies only if sapIfUpdateMode is Standard(1)).
INT sapIfSupply	1.3.6.1.4.1.311.1.9.2.2.1.7	INTEGER	read-write	Enable sending of SAP updates (change and periodic) on this interface.
INT sapIfListen	1.3.6.1.4.1.311.1.9.2.2.1.8	INTEGER	read-write	Enable listening to SAP updates on this interface.
INT sapIfGetNearestServerReply	1.3.6.1.4.1.311.1.9.2.2.1.9	INTEGER	read-write	Indicates whether to respond to SAP get nearest server requests received on this interface.
CTR sapIfOutPackets	1.3.6.1.4.1.311.1.9.2.2.1.10	Counter	read-only	The number of SAP packets sent on this interface.
CTR sapIfInPackets	1.3.6.1.4.1.311.1.9.2.2.1.11	Counter	read-only	The number of SAP packets received on this interface.

RFC description

Monitors RIP and SAP routing protocols running in IPX networks on Microsoft systems.

Start monitoring Windows Server (RIP/SAP routing service) 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 MSRIPSAP-MIB

What Is MSRIPSAP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description