APPC-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsAPPC-MIB

Organization: IETF SNA NAU MIB Working Group

Last Updated: 1995-12-15

Category: SNA and Legacy Protocols

Description: Defines managed objects for configuring, monitoring, and controlling network devices with SNA Advanced Program-to-Program Communication (APPC/LU 6.2) capabilities.

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

What Is APPC-MIB?

APPC-MIB is a vendor-neutral IETF-style MIB module for managing network devices that implement IBM's SNA Advanced Program-to-Program Communication (APPC/LU 6.2) protocol, commonly found in legacy mainframe-connected networking gear. It exposes configuration objects for administrative control (like admin status, resource control, and tracing) alongside operational-state counterparts that reflect the live running condition of the APPC control point. Objects such as appcCntrlAdminStat/appcCntrlOperStat let an administrator monitor whether APPC control is enabled and functioning, appcCntrlOperTrace and its parameters reveal whether protocol tracing is active for diagnostics, and appcUpTime tracks how long the APPC subsystem has been running — directly supporting software/service status monitoring. It builds on general SNMP framework conventions and is typically deployed alongside other SNA/APPN management MIBs on gateways bridging SNA and IP networks. Typical deployment context is legacy enterprise or financial-services environments still running SNA-based host connectivity through APPC-capable routers or protocol converters. Engineers implementing or auditing this functionality typically reference the APPC-MIB RFC/standard documentation for the authoritative specification.

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

  • SNA/APPC gateway or protocol converter
  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer

Monitoring Examples

An administrator would poll appcCntrlOperStat against appcCntrlAdminStat to detect a mismatch indicating the APPC control point failed to come up as configured, and check appcUpTime to confirm the APPC subsystem hasn't unexpectedly restarted. appcCntrlOperTrace and appcCntrlOperTraceParm reveal whether diagnostic tracing was left running (a performance drag) versus the administratively requested appcCntrlAdminTrace state. appcCntrlOperRscvTime/appcCntrlOperStatTime give timestamps for the last state or resource-control change, useful for correlating APPC outages with other network events.

What Can Be Monitored

  • APPC control point admin vs operational status
  • APPC subsystem uptime
  • trace enable state and parameters
  • resource control state
  • time of last status/resource change
Imported Objects

From SNA-NAU-MIB

snanauMIBMODULE-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

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

From SNMPv2-TC

DateAndTime
DisplayString
InstancePointer
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using appcSessStatsSentFmdBytes OID:

Select an SNA/APPC gateway or protocol converter 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 appcSessStatsSentFmdBytes 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. The number of function management data (FMD) bytes sent by the local LU. 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

APPC (Advanced Program-to-Program Communication) LU and session management for SNA.

Start monitoring SNA/APPC gateway or protocol converter 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 APPC-MIB