OACOMMON-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › OACOMMON-MIB

Organization: Open Access Pty Ltd.

Last Updated: 2016-10-05

Description: Open Access Pty Ltd MIB providing common identity, alarm status, uptime, and configuration objects for their NetSpire network devices

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

OACOMMON-MIB is a vendor MIB from Open Access Pty Ltd (per module_desc, titled "NetSpire Device Common Detail") providing a common set of identity, status, and environmental objects shared across their NetSpire family of network devices. It exposes device identity data (name, unit location, serial number, production date), a general alarm status, and system health telemetry including uptime, current time/time source, restart count, storage used, CPU load, and system temperature. This MIB is squarely aimed at hardware/software status monitoring: netSpireDeviceUptime and netSpireDeviceRestartCount reveal stability and unexpected reboots, netSpireDeviceCPULoad and netSpireDeviceStorageUsed reveal resource exhaustion, netSpireDeviceSystemTemperature reveals thermal/environmental problems, and netSpireDeviceAlarmStatus surfaces an aggregate fault indicator. As a vendor-common MIB, it likely serves as a base module referenced by other NetSpire product-specific MIBs rather than depending on external standards itself. It is used to monitor the overall health of Open Access NetSpire network devices in field or carrier deployments, with OACOMMON-MIB SNMP polling as the primary mechanism.

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

  • Open Access NetSpire network device

Monitoring Examples

A monitoring system would poll netSpireDeviceUptime and netSpireDeviceRestartCount together to detect an unexpected reboot, and check netSpireDeviceCPULoad, netSpireDeviceStorageUsed, and netSpireDeviceSystemTemperature to catch resource exhaustion or overheating before it causes an outage. netSpireDeviceAlarmStatus provides a quick top-level "device has an active alarm" flag that would trigger deeper investigation into the other counters. netspireDeviceName and netspireDeviceUnitLocation help identify which physical unit and site an alert refers to during triage.

What Can Be Monitored

  • device uptime
  • restart count
  • CPU load
  • storage used
  • system temperature
  • alarm status
Imported Objects

From OA-SMI

oacommonOBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using netSpireDeviceFaultActive OID:

Select an Open Access NetSpire network device (identity, alarm, and system health telemetry) 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 netSpireDeviceFaultActive into the Find box to locate it in the OID tree, then select it and click OK. It reports the whether the fault is active or not. 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 an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'Inactive', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Common device management objects for NetSpire devices. Provides device identification, status, alarm information, and system parameters.

Start monitoring Open Access NetSpire network device (identity, alarm, and system health telemetry) 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 OACOMMON-MIB