RIPSAP

All MIBs › RIPSAP

Category: Routing

Description: Manages RIP SAP (Service Advertising Protocol) entries for IPX network service routing.

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 RIPSAP?

RIPSAP is a vendor-specific (Novell-associated) MIB for managing RIP and SAP (Service Advertising Protocol) on IPX networks, the routing and service-discovery protocols historically used by Novell NetWare environments. It exposes per-system and per-circuit tables for both RIP (routing) and SAP (service advertisement), including protocol state and counts of malformed or incorrect packets received. Its monitoring focus is software/protocol health: watching ripSysState and sapSysState to confirm the protocols are actively running, and watching ripSysIncorrectPackets/sapSysIncorrectPackets to catch packet-format errors indicating a misbehaving neighbor or protocol version mismatch. It is tied specifically to the IPX protocol stack rather than TCP/IP, so it stands apart from standard IP-centric routing MIBs, though it follows the same general SMI table conventions. It would be deployed on routers or NetWare servers in legacy IPX/SPX networks needing SNMP visibility into RIP/SAP routing and service advertisement behavior. Engineers can download the RIPSAP file directly to load it into their MIB browser.

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

legacy Novell NetWare/IPX routers and servers

Monitoring Examples

An administrator would poll ripSysTable/ripSysEntry for ripSysState and ripSysIncorrectPackets per ripSysInstance, and similarly poll sapSysTable/sapSysEntry for sapSysState and sapSysIncorrectPackets, to confirm RIP and SAP are both operating cleanly on a given circuit. A rising ripCircTable circuit error count alongside increasing ripSysIncorrectPackets would point to a malfunctioning IPX router or a protocol version mismatch on that link.

What Can Be Monitored

RIP protocol state
SAP protocol state
incorrect/malformed packet counts
per-circuit RIP configuration
IPX routing and service advertisement health

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
enterprises

From RFC1213-MIB

PhysAddress

OIDs

OID symbolic	OID numeric	Type	Access	Description
novell	1.3.6.1.4.1.23
mibDoc	1.3.6.1.4.1.23.2
ripsap	1.3.6.1.4.1.23.2.20
ripsapSystem	1.3.6.1.4.1.23.2.20.1
ripSysTable	1.3.6.1.4.1.23.2.20.1.1		not-accessible	The RIP system table.
ripSysEntry	1.3.6.1.4.1.23.2.20.1.1.1		not-accessible	Each entry corresponds to one instance of RIP running on the system.
INT ripSysInstance	1.3.6.1.4.1.23.2.20.1.1.1.1	INTEGER	read-write	The unique identifier of the instance of RIP to which this row corresponds. This value links the instance of RIP to an instance of IPX running on the system (i.e. the value of ripSysInstance should be the same as a value of ipxSysInstance). This value may be written only when creating a new entry in the table.
INT ripSysState	1.3.6.1.4.1.23.2.20.1.1.1.2	INTEGER	read-write	Indicates the operational state of this instance of RIP.
CTR ripSysIncorrectPackets	1.3.6.1.4.1.23.2.20.1.1.1.3	Counter	read-only	The number of times that an incorrectly formatted RIP packet was received.
sapSysTable	1.3.6.1.4.1.23.2.20.1.2		not-accessible	The SAP system table.
sapSysEntry	1.3.6.1.4.1.23.2.20.1.2.1		not-accessible	Each entry corresponds to one instance of SAP running on the system.
INT sapSysInstance	1.3.6.1.4.1.23.2.20.1.2.1.1	INTEGER	read-write	The unique identifier of the instance of SAP to which this row corresponds. This value links the instance of SAP to an instance of IPX running on the system (i.e. the value of SApSysInstance should be the same as a value of ipxSysInstance). This value may be written only when creating a new entry in the table.
INT sapSysState	1.3.6.1.4.1.23.2.20.1.2.1.2	INTEGER	read-write	Indicates the operational state of this instance of SAP.
CTR sapSysIncorrectPackets	1.3.6.1.4.1.23.2.20.1.2.1.3	Counter	read-only	The number of times that an incorrectly formatted SAP packet was received.
ripsapCircuit	1.3.6.1.4.1.23.2.20.2
ripCircTable	1.3.6.1.4.1.23.2.20.2.1		not-accessible	The RIP Circuit table.
ripCircEntry	1.3.6.1.4.1.23.2.20.2.1.1		not-accessible	Each entry corresponds to one circuit known to the system.
INT ripCircSysInstance	1.3.6.1.4.1.23.2.20.2.1.1.1	INTEGER	read-write	The unique identifier of the instance of RIP and IPX (via ipxSysInstance) to which this entry corresponds. This value may be written only when creating a new entry in the table.
INT ripCircIndex	1.3.6.1.4.1.23.2.20.2.1.1.2	INTEGER	read-write	The identifier of this circuit, unique within the instance of RIP. This value corresponds to the circuit identifier found in ipxCircIndex. This value may be written only when creating a new entry in the table.
INT ripCircState	1.3.6.1.4.1.23.2.20.2.1.1.3	INTEGER	read-write	Indicates whether RIP information may be sent/received over this circuit.
INT ripCircPace	1.3.6.1.4.1.23.2.20.2.1.1.4	INTEGER	read-write	The maximum pace, in packets per second, at which RIP packets may be sent on this circuit.
INT ripCircUpdate	1.3.6.1.4.1.23.2.20.2.1.1.5	INTEGER	read-write	The RIP periodic update interval, in seconds.
INT ripCircAgeMultiplier	1.3.6.1.4.1.23.2.20.2.1.1.6	INTEGER	read-write	The holding multiplier for information received in RIP periodic updates.
INT ripCircPacketSize	1.3.6.1.4.1.23.2.20.2.1.1.7	INTEGER	read-write	The RIP packet size used on this circuit.
CTR ripCircOutPackets	1.3.6.1.4.1.23.2.20.2.1.1.8	Counter	read-only	The number of RIP packets sent on this circuit.
CTR ripCircInPackets	1.3.6.1.4.1.23.2.20.2.1.1.9	Counter	read-only	The number of RIP packets received on this circuit.
sapCircTable	1.3.6.1.4.1.23.2.20.2.2		not-accessible	The SAP Circuit table.
sapCircEntry	1.3.6.1.4.1.23.2.20.2.2.1		not-accessible	Each entry corresponds to one circuit known to the system.
INT sapCircSysInstance	1.3.6.1.4.1.23.2.20.2.2.1.1	INTEGER	read-write	The unique identifier of the instance of SAP and IPX (via ipxSysInstance) to which this entry corresponds. This value may be written only when creating a new entry in the table.
INT sapCircIndex	1.3.6.1.4.1.23.2.20.2.2.1.2	INTEGER	read-write	The identifier of this circuit, unique within the instance of SAP. This value corresponds to the circuit identifier found in ipxCircIndex. This value may be written only when creating a new entry in the table.
INT sapCircState	1.3.6.1.4.1.23.2.20.2.2.1.3	INTEGER	read-write	Indicates whether SAP information may be sent/received over this circuit.
INT sapCircPace	1.3.6.1.4.1.23.2.20.2.2.1.4	INTEGER	read-write	The maximum pace, in packets per second, at which SAP packets may be sent on this circuit.
INT sapCircUpdate	1.3.6.1.4.1.23.2.20.2.2.1.5	INTEGER	read-write	The SAP periodic update interval, in seconds.
INT sapCircAgeMultiplier	1.3.6.1.4.1.23.2.20.2.2.1.6	INTEGER	read-write	The holding multiplier for information received in SAP periodic updates.
INT sapCircPacketSize	1.3.6.1.4.1.23.2.20.2.2.1.7	INTEGER	read-write	The SAP packet size used on this circuit.
INT sapCircGetNearestServerReply	1.3.6.1.4.1.23.2.20.2.2.1.8	INTEGER	read-write	Indicates whether to respond to SAP get nearest server requests received on this circuit.
CTR sapCircOutPackets	1.3.6.1.4.1.23.2.20.2.2.1.9	Counter	read-only	The number of SAP packets sent on this circuit.
CTR sapCircInPackets	1.3.6.1.4.1.23.2.20.2.2.1.10	Counter	read-only	The number of SAP packets received on this circuit.

RFC description

Monitors RIP (Routing Information Protocol) and SAP (Service Advertising Protocol) activities in IPX environments, providing system and circuit-level statistics.

Start monitoring Novell NetWare/IPX routers and servers 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 RIPSAP

What Is RIPSAP?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description