MSIPX-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › MSIPX-MIB

Category: IP Routing

Description: Manages Microsoft IPX routing protocol configuration and network binding 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 MSIPX-MIB?

MSIPX-MIB is a Microsoft-specific MIB for monitoring and configuring the IPX (Internetwork Packet Exchange) routing protocol stack on Microsoft Windows NT/Server systems that ran Novell IPX network binding and routing services. It exposes base protocol operational state (network number, node address, system name), path/routing limits, and per-interface configuration in an IPX interface table. In terms of software status monitoring, ipxBaseOperState reports whether the IPX protocol stack is currently up or down on the host, while ipxBaseDestCount and ipxBaseServCount give a sense of routing/service-table size, and ipxIfAdminState reports per-interface administrative status. This MIB is a legacy, vendor-specific (Microsoft) implementation modeled after the standard IPX MIB conventions from the IETF/Novell era rather than reusing a shared standards module directly. Typical deployment context is a legacy Windows NT/2000 server acting as an IPX router or gateway in an older Novell NetWare-integrated enterprise network, now largely obsolete. Engineers can download the MSIPX-MIB file directly to load it into their MIB browser.

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

  • Microsoft Windows NT/Server hosts running IPX routing services (legacy)

Monitoring Examples

An administrator would poll ipxBaseOperState to confirm the IPX stack is operational on the server, then check ipxIfTable/ipxIfEntry (via ipxIfIndex) and ipxIfAdminState to verify each bound network interface is administratively up and correctly running IPX. ipxBaseDestCount and ipxBaseServCount would be tracked over time to spot an unexpectedly empty or shrinking routing/SAP table, indicating a loss of IPX connectivity to the rest of the Novell network. ipxBasePrimaryNetNumber and ipxBaseNode confirm the host's IPX network/node addressing is as expected after a configuration change.

What Can Be Monitored

  • IPX protocol operational state
  • per-interface administrative state
  • destination (routing) table count
  • IPX service (SAP) table count
  • primary network number and node address
Imported Objects

From MSFT-MIB

microsoftOBJECT-IDENTITY
softwareOBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

Counter
enterprises
OIDs

RFC description

Management Information Base for multiprotocol IPX (Internetwork Packet Exchange) systems. Defines managed objects for monitoring and managing IPX network protocol components and their interactions with other network protocols.

Start monitoring Microsoft Windows NT/Server host running legacy IPX routing 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 MSIPX-MIB