AVAS-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsAVAS-MIB

Category: Telephony and VoIP, Vendor: Avaya

Description: Monitors Avaya availability and service management, providing system uptime, failover state, and redundancy status.

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 AVAS-MIB?

AVAS-MIB is a Siemens vendor-specific MIB, originally written for the BS2000 mainframe environment, that models the AVAS batch job scheduling and network automation subsystem — tracking process states (avasPUpamStat, avasPPlamStat, avasPCentrStat), job/procedure/condition network elements in the avasNTab, avasETab, and avasCTab tables, and their lifecycle states such as running, hold, abended, or error. It exposes summary health data through avasPSumStat (a rollup of whether the UPAM/PLAM subsystems and their scheduled nets are ready, running, or erroring) plus a rich set of TRAP-TYPE notifications (avasNetAbended, avasJobError, avasProcCancelled, avasUJobAbended) for job/procedure/net failures across Unix, NT, and mainframe job types. Rather than hardware telemetry, this MIB surfaces control-plane/software job-scheduling status, making it useful for detecting stalled or abended batch nets and jobs before they cascade into missed processing windows. It depends on the underlying AVAS automation engine (UPAM-ZD/PLAM-ZD processes) running on the host system it instruments. Administrators supporting Siemens BS2000-based batch automation environments can download the AVAS-MIB file to load it into their MIB browser and monitor scheduling health directly.

IPNetwork Monitor allows you to monitor SNMP objects defined in AVAS-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 in the sense of running on BS2000/mainframe hosts, but Siemens-authored and specific to the AVAS batch automation product, not a general-purpose hardware MIB

Monitoring Examples

An operator polls avasPSumStat to get the overall AVAS health rollup, then walks avasNTab (indexed by avasNTabIndex) checking avasNState for each net; a state of abended or error, paired with an avasNetAbended or avasNetError trap, would indicate a scheduled batch net failed and needs manual intervention before dependent jobs are affected.

What Can Be Monitored

  • process state (UPAM/PLAM/CENTRAL)
  • net table state and error/hold/restart flags
  • job/procedure/condition element states
  • AVAK (automatic variable key) table state
  • job/net/procedure abend and error traps
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

enterprises

From RFC1213-MIB

DisplayString
OIDs

RFC description

Management MIB for AVAS (Audio/Visual Alerting System) devices. Manages status, alarms, and configuration of alert and announcement systems.

Start monitoring Siemens BS2000 mainframe automation (AVAS) 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 AVAS-MIB