All MIBs › PRVT-DRY-CONTACTS-MIB
Organization: BATM Advanced Communication
Last Updated: 2007-11-27
Category: Environmental Monitoring
Description: Monitors BATM Advanced Communication dry contact environmental input/output states for external alarm and sensor integration.
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 PRVT-DRY-CONTACTS-MIB?
PRVT-DRY-CONTACTS-MIB is a private BATM Advanced Communications MIB providing external-alarm management for dry-contact input/output points, letting the device integrate with third-party sensors (door contacts, smoke detectors, water sensors, etc.) via simple open/closed contact circuits. It exposes a configuration/status table describing each configured contact's sensor type, name, description, enable status, current alarm status, severity, and signal polarity, plus a timestamp of the last state change. This is a hardware/environmental fault monitoring MIB in the purest sense: its entire purpose is to expose the current status and severity of external alarm inputs so operators can be notified of physical events such as a door being opened, a temperature threshold sensor tripping, or a flood sensor activating, with corresponding notification traps. No dependency on other standard MIBs is evident beyond general SNMP notification conventions. It is typically deployed on BATM (and BATM-OEM) network/transport equipment installed in equipment rooms, cabinets, or remote sites where external environmental or security sensors need SNMP-based alarm reporting. Engineers can download the PRVT-DRY-CONTACTS-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in PRVT-DRY-CONTACTS-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
- BATM Advanced Communications transport/network equipment with dry-contact alarm interface
- external alarm/sensor integration point (door, smoke, water sensors)
Monitoring Examples
An administrator would poll cfgTable/cfgEntry, keyed by prvtAlarmID, to read prvtSensorType, prvtName, and prvtDescription identifying each connected sensor, then check prvtAlarmStatus and prvtAlarmSeverity to see which contacts are currently in an alarm state. prvtLastChange indicates when a given contact last transitioned, useful for correlating an alarm with an access-control or environmental event. dryContactsNotifications would fire an SNMP trap the moment prvtAlarmStatus changes, allowing near-real-time alerting on events like an open cabinet door (governed by prvtPolarity and prvtEnableStatus configuration).
What Can Be Monitored
- per-contact alarm status
- alarm severity
- sensor type and description
- contact enable status
- last state-change timestamp
Imported Objects
From PRVT-SWITCH-MIB
| switch | OBJECT-IDENTITY |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| TimeTicks |
OIDs
RFC description
Vendor-specific MIB for monitoring dry contact I/O devices via SNMP; manages voltage-free switch states for facility monitoring.
Start monitoring BATM Advanced Communications transport/network equipment (dry-contact alarm interface) 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.