All MIBs › PEM-STANDARD
Organization: Ericsson Diax A/S - Denmark
Last Updated: 2006-02-02
Category: Environmental Monitoring
Description:
Manages Ericsson Diax power and equipment module (PEM) operational status, power feeds, and alarm conditions.
Imported Objects
From DXD-SMI
| diaxMIB | MODULE-IDENTITY |
From PEM-STANDARD-TC
| IANAItuEventType | |
| IANAItuProbableCause | |
| ItuPerceivedSeverity |
From RFC1213-MIB
| DisplayString |
From SNMPv2-CONF
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DateAndTime | |
| TEXTUAL-CONVENTION |
What Is PEM-STANDARD?
PEM-STANDARD models power and equipment module (PEM) status for Ericsson's Diax access/transmission platform, using an ITU-T X.733-style standard alarm reporting model. Its categories are entirely fault/alarm-oriented: managed-object class and instance identifiers, perceived severity, probable cause, and alarm sequencing/timing for the power module and its power feeds. It is built explicitly for monitoring hardware status — power feed alarms, alarm severity escalation or clearing, and probable-cause codes tied to specific equipment instances — functioning as a structured power-supply/equipment health reporting mechanism rather than exposing counters. It follows the ITU-T X.733 alarm model (managedObjectClass/Instance, perceivedSeverity, probableCause), a pattern shared across several Ericsson standard-alarm MIBs. It is deployed on Ericsson Diax network elements at telecom sites, monitored by an EMS/NMS for power and equipment alarm conditions. PEM-STANDARD SNMP monitoring is typically carried out by an EMS/NMS that both polls managedObjectInstance rows and listens for the alarm traps this MIB defines.
IPNetwork Monitor allows you to monitor SNMP objects defined in PEM-STANDARD. 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.
What Can Be Monitored
- alarm perceived severity
- alarm probable cause
- power feed/equipment alarm events
- alarm event sequence and timestamp
Supported Devices
- Ericsson Diax access/transmission network element
- telecom power and equipment module (PEM)
Monitoring Examples
An operator would poll or trap-receive rows keyed by managedObjectInstance to see which PEM hardware component raised an alarm, with perceivedSeverity indicating whether it's critical, major, minor, or a clearing event, and probableCause narrowing it to something like a power feed failure. sequenceNumber and eventTime let a management station order and correlate alarm events chronologically when multiple power-related alarms fire in a short window. A rising perceivedSeverity on a managedObjectClass tied to a specific power feed instance would tell an admin that PEM power redundancy on that Diax node is degrading.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| pemStandardObjects | 1.3.6.1.4.1.193.72.500 | This document describe the standard alarm objects. | ||
| alarmObjects | 1.3.6.1.4.1.193.72.500.1 | |||
| STR managedObjectClass | 1.3.6.1.4.1.193.72.500.1.1 | DisplayString | accessible-for-notify | Specifies the class of the Managed Object issuing the alarm |
| STR managedObjectInstance | 1.3.6.1.4.1.193.72.500.1.2 | DisplayString | accessible-for-notify | Specifies the specific instance of the Managed Object |
| C32 sequenceNumber | 1.3.6.1.4.1.193.72.500.1.3 | Counter32 | accessible-for-notify | Specifies a unique trap/notification number. |
| ITU perceivedSeverity | 1.3.6.1.4.1.193.72.500.1.4 | ItuPerceivedSeverity | accessible-for-notify | ITU perceived severity values as per [M.3100] and [X.733]. |
| DAT eventTime | 1.3.6.1.4.1.193.72.500.1.5 | DateAndTime | accessible-for-notify | A date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11 10 11 minutes from UTC 0..59 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. |
| IAN eventTypePem | 1.3.6.1.4.1.193.72.500.1.6 | IANAItuEventType | accessible-for-notify | Represents the event type values for the alarms as per [M.3100], [X.733] and [X.736] |
| IAN probableCause | 1.3.6.1.4.1.193.72.500.1.7 | IANAItuProbableCause | accessible-for-notify | ITU probable cause values as per [M.3100], [X.733] and [X.736]. |
| alarmObjectsGroups | 1.3.6.1.4.1.193.72.500.2 | |||
| alarmObjectsGroup | 1.3.6.1.4.1.193.72.500.2.1 | Objects for the Alarm Group |
FAQ
What does PEM-STANDARD track for Ericsson Diax power modules?
It models the power and equipment module (PEM) status using an ITU-T X.733-style alarm framework, exposing managed-object class/instance identifiers, perceived severity, probable cause codes, and alarm sequencing/timestamps for power feeds and equipment. An EMS/NMS uses it to detect and prioritize power-feed alarms, judging urgency from the perceived severity and probable cause.
How would an EMS use PEM-STANDARD to monitor a power feed alarm on a Diax network element?
The EMS polls managedObjectInstance rows and listens for the alarm traps this MIB defines; when a power feed alarm is raised, the perceivedSeverity and probableCause fields tell the operator how serious it is and why, while the alarm sequence/timestamp objects let them track when it was raised and cleared.
RFC description
Power Endpoint Monitoring MIB for managing power supply and electrical device monitoring in network infrastructure.
Start monitoring Ericsson Diax access/transmission network element, telecom power and equipment module (PEM alarm reporting) 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.