NLSP

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NLSP

Description: MIB for NetWare Link Services Protocol routing, adjacency, LSP, and circuit management in Novell IPX network environments

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

NLSP is a private MIB (enterprise OID 23) implementing NLSP (NetWare Link Services Protocol), Novell's link-state routing protocol for IPX networks, analogous to OSPF/IS-IS. Its system table, keyed by instance, records protocol state, system ID, minimum non-broadcast/broadcast LSP transmission intervals, minimum/maximum LSP generation intervals, and maximum LSP age. As a configuration/protocol-status MIB it lets an administrator confirm NLSP timer settings are consistent across routers when diagnosing slow convergence in a legacy IPX/NetWare network. It is deployed on routers running NLSP in legacy Novell NetWare environments. Engineers can download the NLSP file directly to load it into their MIB browser.

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

  • Routers running NLSP (legacy Novell NetWare/IPX environments)

Monitoring Examples

An administrator compares nlspSysMinLSPGenInt and nlspSysMaxLSPAge across NLSP routers to confirm consistent timer settings when diagnosing unusually slow route convergence in a legacy IPX network.

What Can Be Monitored

  • NLSP protocol state and LSP timing parameters
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
enterprises

From RFC1213-MIB

PhysAddress

From SNMPv2-TC

TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using nlspSysL1DbaseOloads OID:

Select a Router running NLSP (legacy Novell NetWare/IPX environment) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type nlspSysL1DbaseOloads into the Find box to locate it in the OID tree, then select it and click OK. The number of times the NLSP Level 1 LSP database has become overloaded. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

NetWare Link Services Protocol MIB for IPX environments, providing NLSP system, circuit, forwarding, neighbor, and LSP management information.

Start monitoring Router running NLSP (legacy Novell NetWare/IPX environment) 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 NLSP