All MIBs › TANDEM-EMS-MIB
Category: Alarms and Events, Server and Hardware Management, Vendor-Specific Device Management
Description: Manages Tandem fault-tolerant server EMS event monitoring, process state, and system alerts.
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 TANDEM-EMS-MIB?
TANDEM-EMS-MIB is a vendor-specific MIB for Tandem (HP NonStop/legacy Tandem Computers) fault-tolerant server systems, exposing data from the Tandem Event Management Service (EMS), the subsystem responsible for collecting and distributing system and application events across a NonStop cluster. It generally covers categories such as process state, subsystem event logging, and system alert/notification data drawn from the EMS event stream. Its role in monitoring is centered on software and system health status: it lets an operator track process states, EMS-reported system alerts, and event conditions that indicate faults or abnormal conditions on a NonStop server, which is important given these systems' emphasis on continuous, fault-tolerant operation. As an EMS-focused MIB it likely depends on or complements standard SNMP notification mechanisms to forward Tandem EMS events as SNMP traps to a management station. It is typically deployed in data centers running HP NonStop/Tandem fault-tolerant servers for telecom, banking, or other high-availability transaction processing environments. Engineers can download the TANDEM-EMS-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TANDEM-EMS-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
- HP NonStop / Tandem fault-tolerant servers
Monitoring Examples
No sample objects were provided for this module, so specific object or table names cannot be grounded here. In practice such a MIB would typically be polled or would emit traps carrying EMS event identifiers, process names, and severity codes so an operator can see which NonStop process or subsystem raised an event, but a concrete example is not fabricated without source object names.
What Can Be Monitored
- EMS event/alert occurrences
- process state
- subsystem event severity
- system alert conditions
Imported Objects
From RFC1155-SMI
| enterprises |
OIDs
RFC description
Tandem NonStop systems event management service (EMS) traps for centralized monitoring and alerting.
Start monitoring HP NonStop / Tandem fault-tolerant server (Event Management Service process/alert 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.