SNA-NAU-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsSNA-NAU-MIB

Organization: IETF SNA NAU MIB Working Group

Last Updated: 1994-05-12

Category: SNA and Legacy Protocols

Description: Defines managed objects for configuring, monitoring, and controlling SNA Network Addressable Units (Physical Units and Logical Units).

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring SNA-NAU-MIB with a free 30-day trial of IPNetwork Monitor.

What Is SNA-NAU-MIB?

SNA-NAU-MIB is a vendor-neutral, standards-based IETF MIB for managing IBM Systems Network Architecture (SNA) Network Addressable Units, covering both Physical Units (PUs) and Logical Units (LUs). It exposes configuration data such as node administration parameters, XID formats, block/ID numbers, node enabling methods, and maximum LU counts, alongside operational status and fault traps for SNA nodes and LUs. Its monitoring value centers on device/software status: it lets an administrator track whether SNA nodes are enabled and operational, monitor LU session activity, and receive traps (snaNodeTraps, snaLuTraps) when SNA connectivity or session failures occur. It is designed to complement other SNA-related MIBs (e.g., for DLC/SDLC links) as part of a broader SNA management framework rather than standing entirely alone. Typical deployment is in legacy mainframe/midrange environments where SNA gateways, controllers, or communication servers bridge SNA traffic into IP-managed networks. Engineers implementing or auditing this functionality typically reference the SNA-NAU-MIB RFC/standard documentation for the authoritative specification.

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

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • SNA gateway/controller or communication server bridging SNA traffic

Monitoring Examples

A network operator would poll the snaNodeAdminTable (indexed by snaNodeAdminIndex) to review each configured SNA node's snaNodeAdminName, snaNodeAdminType, and snaNodeAdminMaxLu settings, confirming a gateway is provisioned with the expected number of logical units. If a node's enabling method or XID format is misconfigured, session establishment failures would occur and be reported via snaNodeTraps. Monitoring snaLuTraps would reveal when individual logical units drop or fail to activate, pointing to session-level problems on that PU.

What Can Be Monitored

  • SNA node admin configuration
  • node enabling method/status
  • logical unit (LU) count and state
  • node and LU fault traps
Imported Objects

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
mib-2

From SNMPv2-TC

DisplayString
InstancePointer
RowStatus
TimeStamp

How to Use in IPNetwork Monitor

Example using snaNodeOperActFailures OID:

Select a device implementing SNA-NAU-MIB 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 snaNodeOperActFailures into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This value identifies the number of failed Node activation attempts. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

MIB for managing SNA network devices including PU types 1.0, 2.0, 2.1 and LU types 0-7 and 6.2.

Start monitoring vendor-neutral, standards-based MIB, SNA gateway/controller or communication server (PU/LU node status/fault traps) 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 SNA-NAU-MIB