All MIBs › NOVELL-RIPSAP-MIB
Category: Novell
Description: Manages Novell RIP and SAP routing protocol tables, timers, and broadcast interval parameters on NetWare routers.
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 NOVELL-RIPSAP-MIB?
This is a Novell private MIB for managing RIP (Routing Information Protocol) and SAP (Service Advertising Protocol), the two core routing/service-discovery protocols historically used on Novell NetWare-based IPX networks. It exposes configuration and operational-state tables for both protocols: per-instance system state, broadcast/update timers, error counters such as incorrect packets received, and per-circuit (interface) parameters governing how RIP routes and SAP service advertisements are exchanged. Its monitoring value is chiefly protocol/software health, checking whether the RIP and SAP processes are enabled and running correctly on each instance, and watching the incorrect-packet counters (ripSysIncorrectPackets, sapSysIncorrectPackets) as an early indicator of malformed traffic, misconfiguration, or a misbehaving neighbor router on the IPX network. It is tied to the legacy IPX/RIP/SAP protocol stack rather than modern IP routing standards, reflecting its NetWare-era origin. It is deployed on legacy Novell NetWare routers/servers and IPX-capable routing devices that still participate in RIP/SAP-based IPX networks. Engineers can download the NOVELL-RIPSAP-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in NOVELL-RIPSAP-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
- Novell NetWare router/server
- legacy IPX-routing network device
Monitoring Examples
An administrator would poll ripSysTable/ripSysEntry via ripSysInstance to check ripSysState and confirm RIP is actively running on each routing instance, then check ripSysIncorrectPackets for a rising count that would flag malformed or unexpected RIP packets arriving on the network. In parallel, sapSysTable/sapSysEntry's sapSysState and sapSysIncorrectPackets would be checked to make sure SAP service advertisements are being processed cleanly. The ripCircTable/ripCircEntry rows would then be used to drill into per-circuit (interface) RIP behavior when a specific link is suspected of causing the errors.
What Can Be Monitored
- RIP protocol instance state
- RIP incorrect/malformed packet count
- SAP protocol instance state
- SAP incorrect/malformed packet count
- per-circuit RIP configuration
Imported Objects
From NOVELL-IPX-MIB
| mibDoc | OBJECT-IDENTITY |
From RFC-1212
| OBJECT-TYPE |
From RFC1155-SMI
| Counter | |
| enterprises |
From RFC1213-MIB
| PhysAddress |
OIDs
RFC description
Novell vendor-private MIB for RIP and SAP (Service Advertising Protocol) routing and service advertising on NetWare systems.
Start monitoring Novell NetWare router/server (legacy IPX RIP/SAP) 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.