Application-Monitoring-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsApplication-Monitoring-MIB

Category: Network Monitoring (RMON)

Description: Generic application availability and performance monitoring including response time and uptime.

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 Application-Monitoring-MIB?

Application-Monitoring-MIB provides generic application availability and performance monitoring, originating from Siemens Nixdorf ("sni" enterprise prefix) and organized under sniProductMibs/sniAppMon. It exposes subsystem-level inventory and state data — each monitored software subsystem's name, version, running state, and active task count — plus a related BCAM (Basic Communication Access Method) application table for tracking individual applications. It is explicitly a software-status monitoring MIB: appMonSubsysState reveals whether a subsystem is running/stopped/faulted, appMonSubsysTasks indicates process/task load, and appMonSubsysVersion supports software-version auditing across a fleet, directly analogous to process/service status and version monitoring on a host. It depends on the Siemens Nixdorf ("sni") enterprise OID tree and is a vendor-neutral-style generic monitoring schema layered under that vendor root. It is typically deployed on Siemens Nixdorf/BCAM-based host and application-server environments to give an NMS visibility into application/subsystem health without vendor-specific instrumentation. Engineers can download the Application-Monitoring-MIB file directly to load it into their MIB browser.

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

  • Siemens Nixdorf (BCAM-based) host or application server
  • vendor-neutral generic application monitoring, applicable to any monitored subsystem/application

Monitoring Examples

An admin would poll appMonSubsysTable/appMonSubsysEntry, keyed by appMonSubsysIndex, to check each subsystem's appMonSubsysState and appMonSubsysTasks — a subsystem showing a stopped/error state or an unexpectedly low task count would indicate an application outage. appMonSubsysVersion lets the operator audit software versions across subsystems during a rollout. appMonBcamApplTable/appMonBcamApplEntry, keyed by appMonBcamApplIndex, gives a parallel view into individual BCAM-managed applications' presence and status.

What Can Be Monitored

  • subsystem name and version
  • subsystem running state
  • subsystem task/process count
  • BCAM application presence/index
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

enterprises

From RFC1213-MIB

DisplayString
OIDs

RFC description

Monitors BS2000 mainframe applications with support for subsystems, user applications, DCAM applications, and event logging.

Start monitoring Siemens Nixdorf (BCAM) hosts/application servers 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 Application-Monitoring-MIB