DPS-MIB-V38

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsDPS-MIB-V38

Category: Domain: Telco/Transport, Vendor: DPS Telecom

Description: Manages DPS Telecom V38 series network element controllers for remote alarm and status monitoring.

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 DPS-MIB-V38?

DPS-MIB-V38 is a vendor MIB from DPS Telecom for its T/Mon V38-series remote telemetry/alarm monitoring units used in telecom and utility network operations. It exposes device identification and inventory data plus extensive alarm-monitoring tables covering the state, severity, and description of external contact-closure or discrete alarm points wired into the unit. Its central purpose is monitoring hardware status indirectly through alarms — it reports manufacturer, model, and software version identification, then a live table of alarm conditions (with severity level, site identification, and last-change timestamp) representing hardware faults such as door-open, power loss, HVAC failure, or generator status at a remote site. A DPS-MIB-V38 MIB Browser session is often the fastest way for an operator to confirm object names before writing automated alarm-polling scripts, since as a proprietary DPS product MIB it has no strong dependency on other standard MIBs beyond basic SNMP conventions. It is typically deployed in remote telecom huts, cell sites, and utility substations where a T/Mon device aggregates dry-contact alarms for central NOC monitoring.

IPNetwork Monitor allows you to monitor SNMP objects defined in DPS-MIB-V38. 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

  • DPS Telecom NetGuardian 832A G5 — current-gen advanced remote telemetry unit (RTU)
  • DPS Telecom T/Mon LNX — current alarm master station monitoring legacy and SNMP RTUs

Monitoring Examples

An operator would poll tmonAlarmTable/tmonAlarmEntry indexed by tmonAIndex to retrieve tmonADesc, tmonAState, and tmonASeverity for each configured alarm point, flagging any point in an active alarm state with high severity. tmonAChgDate and tmonAChgTime show when an alarm last transitioned, useful for correlating an outage window. tmonIdentManufacturer, tmonIdentModel, and tmonIdentSoftwareVersion let an inventory system confirm the exact unit and firmware version deployed at a site.

What Can Be Monitored

  • alarm point state
  • alarm severity level
  • alarm description/site
  • time of last alarm change
  • device manufacturer/model/software version
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

enterprises

From RFC1213-MIB

DisplayString
OIDs

RFC description

DPS Telecom alarm control hierarchy MIB defining SNMP management objects for TMON/XM monitoring and alarm devices.

Start monitoring DPS Telecom T/Mon V38-series remote telemetry/alarm unit 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 DPS-MIB-V38