PDN-MPE-DSLAM-SYSTEM-MIB

All MIBs › PDN-MPE-DSLAM-SYSTEM-MIB

Organization: Paradyne Corporation MIB Working Group

Last Updated: 2004-05-13

Category: DSL and Broadband

Description: Manages system-level objects for the Paradyne MPE DSLAM configuration, slot status, and chassis inventory.

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 PDN-MPE-DSLAM-SYSTEM-MIB?

PDN-MPE-DSLAM-SYSTEM-MIB is a Paradyne (PDN) enterprise MIB that extends the standard entPhysicalTable to provide system-level management for the Paradyne MPE DSLAM chassis, covering slot inventory, alarm relays, and physical entity extensions. It exposes objects for external alarm inputs, alarm relay contact state, and extended physical entity attributes such as uptime and location. Administrators use it to monitor the hardware status of DSLAM chassis components, including external alarm contact closures (e.g., door open, temperature threshold) and per-slot/module uptime, which helps detect environmental faults or unexpected card resets. It explicitly builds on and extends the IETF Entity MIB's entPhysicalTable, tying its extended attributes back to standard physical entity indices. It is deployed on Paradyne MPE DSLAM chassis used by telecom carriers to deliver DSL broadband access. Engineers can download the PDN-MPE-DSLAM-SYSTEM-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in PDN-MPE-DSLAM-SYSTEM-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

Paradyne MPE DSLAM chassis

Monitoring Examples

An operator would poll mpeEntExtAlarmTable/mpeEntExtAlarmEntry and mpeEntExtAlarm to check whether an external alarm input (such as a cabinet door or environmental sensor) has been triggered, and mpeAlarmRelayTable/mpeAlarmRelayInputContactState to see the current state of alarm relay contacts. mpeEntPhysicalExtTable's mpeEntPhysicalExtUpTime would be checked per slot/card to detect an unexpected reset (uptime reset to near zero), while mpeEntPhysicalExtLocation helps map the alarm back to a physical rack/shelf position for dispatch.

What Can Be Monitored

external alarm input state
alarm relay contact state
per-slot/card uptime
physical entity location
chassis inventory extensions

Imported Objects

From ENTITY-MIB

entPhysicalEntry	OBJECT-TYPE
entPhysicalIndex	OBJECT-TYPE

From PDN-HEADER-MIB

pdn-mpe

From PDN-MPE-MIB2-MIB

mpeSysObjectID

OBJECT-TYPE

From PDN-TC

ContactState

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using mpeEntPhysicalExtUpTime OID:

Select a Paradyne MPE DSLAM chassis (slot inventory/alarm relay, entPhysicalTable extension) 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 mpeEntPhysicalExtUpTime into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The time, in hundredths of a second (just like sysUpTime), since the entity was last re-initialized. 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 a TimeTicks-type OID, Value bounds is the most useful condition here — trigger an alert if the value is unexpectedly low (e.g. under 10 minutes), since that indicates a recent, possibly unplanned, reboot or restart. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
mpe_dslam	1.3.6.1.4.1.1795.2.24.12.24			The mpe dslam MIB. This MIB is written specifically to extend entPhysicalTable.
mpeSysDevDslamMIBObjects	1.3.6.1.4.1.1795.2.24.12.24.1
mpeEntExtAlarms	1.3.6.1.4.1.1795.2.24.12.24.1.1
mpeEntExtAlarmTable	1.3.6.1.4.1.1795.2.24.12.24.1.1.1		not-accessible	This table lists the alarm states of the objects listed in the entity-MIB entPhysicalTable.
mpeEntExtAlarmEntry	1.3.6.1.4.1.1795.2.24.12.24.1.1.1.1		not-accessible	An mpeEntExtAlarmTable entry indicates the alarm state of the physical entity.
T/F mpeEntExtAlarm	1.3.6.1.4.1.1795.2.24.12.24.1.1.1.1.1	TruthValue	read-only	This variable indicates the alarm state of the physical entity.
mpeAlarmRelay	1.3.6.1.4.1.1795.2.24.12.24.1.2
I32 mpeAlarmRelayEquipIndex	1.3.6.1.4.1.1795.2.24.12.24.1.2.1	Integer32	accessible-for-notify	This variable is the index of the equipment whose alarms are being relayed. It is a integer number starting from 1 until the max number of physical connectors the DSLAM device has to support relay. NOTE: This object has been deprecated. Please consider using the mpeAlarmRelayTable and mpeAlarmRelayInputStateChanged objects.
CON mpeAlarmRelayInputContactState	1.3.6.1.4.1.1795.2.24.12.24.1.2.2	ContactState	accessible-for-notify	This variable indicates the alarm state of the Input Contact (open/closed). NOTE: This object has been deprecated. Please consider using the mpeAlarmRelayTable and mpeAlarmRelayInputStateChanged objects.
mpeAlarmRelayTable	1.3.6.1.4.1.1795.2.24.12.24.1.2.3		not-accessible	This table holds objects that relate to Alarm Relay input or output.
mpeAlarmRelayEntry	1.3.6.1.4.1.1795.2.24.12.24.1.2.3.1		not-accessible	An entry in this table is a sparse augmentation of the entPhysicalEntry. As such, it is indexed by the entPhysicalIndex and not an augmentation of the entPhysicalTable.
CON mpeAlarmRelayState	1.3.6.1.4.1.1795.2.24.12.24.1.2.3.1.1	ContactState	read-write	This object is used to read or write the state an alarm relay input or output.
mpeEntExtMibObjects	1.3.6.1.4.1.1795.2.24.12.24.1.3
mpeEntPhysicalExtTable	1.3.6.1.4.1.1795.2.24.12.24.1.3.1		not-accessible	This table contains entity information that is not defined in the standard ENTITY-MIB.
mpeEntPhysicalExtEntry	1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1		not-accessible	An entry extends the entPhysicalEntry defined in the ENTITY-MIB.
TIK mpeEntPhysicalExtUpTimeEx	1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1.1	TimeTicks	read-only	The time (in hundredths of a second --just like the sysUpTime) since the entity was last re-initialized.
STR mpeEntPhysicalExtLocation	1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1.2	SnmpAdminString	read-write	This object allows the manager to enter the location of the physical entity where applicable. For example, in a stack, chassis or units may be in different locations. In this case, it would be logical for the manager to set this object to the location of the associated chassis. Where the location doesn't make sense, it is recommended that the object return a zero-length string.
STR mpeEntPhysicalExtAdminStatus	1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1.3	MpeEntExtAdminStatus	read-write	The desired state of the entity.
STR mpeEntPhysicalExtOperStatus	1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1.4	MpeEntExtOperStatus	read-only	The current operational state of the entity.
mpeSysDevDslamMIBTraps	1.3.6.1.4.1.1795.2.24.12.24.2
mpeSysDevDslamMIBNotifications	1.3.6.1.4.1.1795.2.24.12.24.2.0
NTF mpeAlarmRelayInputStateChanged	1.3.6.1.4.1.1795.2.24.12.24.2.0.26			This trap signifies that the state of the Alarm Relay Input has changed.
NTF mpeFanEntityModuleFailure	1.3.6.1.4.1.1795.2.24.12.24.2.0.27			This trap indicates the failure of the fan module on the device.
NTF mpeFanEntityModuleOperational	1.3.6.1.4.1.1795.2.24.12.24.2.0.28			This trap indicates the indicates the fan module on the device is back to operational.
NTF mpePowerSourceAFailure	1.3.6.1.4.1.1795.2.24.12.24.2.0.29			This trap indicates that power source A has failed.
NTF mpePowerSourceBFailure	1.3.6.1.4.1.1795.2.24.12.24.2.0.30			This trap indicates that power source B has failed.
NTF mpePowerSourceAOperational	1.3.6.1.4.1.1795.2.24.12.24.2.0.31			This trap indicates that the power source A is operational. This trap compliments powerSourceAFailure trap.
NTF mpePowerSourceBOperational	1.3.6.1.4.1.1795.2.24.12.24.2.0.32			This trap indicates that the power source B is operational. This trap compliments powerSourceBFailure trap.
NTF mpeCcn	1.3.6.1.4.1.1795.2.24.12.24.2.7			This trap signifies a Configuration change or software upgrade in the xDSL card. This trap is of 'warning' class
NTF mpeDeviceFailure	1.3.6.1.4.1.1795.2.24.12.24.2.15			This trap signifies that the sending protocol's device has failed and the failure was not a result of a device test. Note there are no variable bindings for this trap
NTF mpeDeviceFailureCleared	1.3.6.1.4.1.1795.2.24.12.24.2.16			This trap signifies that the sending protocol's device has failed but now it is operational. Failure was not a result of a device test.
NTF mpeNonSupportedMCC	1.3.6.1.4.1.1795.2.24.12.24.2.20			AN has detected MCC firmware release too low to support this device
NTF mpeNonSupportedChassis	1.3.6.1.4.1.1795.2.24.12.24.2.21			AN in slot xx has been installed in a chassis that cannot support one or more of its features.
NTF mpeAlarmRelayInputContactStateChanged	1.3.6.1.4.1.1795.2.24.12.24.2.22			This trap signifies that the state of the InputContact Alarm has changed since last time. NOTE: This object has been deprecated. Please consider using the mpeAlarmRelayInputStateChanged notification.
NTF mpeEntPhysicalExtEntityCreated	1.3.6.1.4.1.1795.2.24.12.24.2.23			This trap signifies that an instance of this entity has been created in the entPhysicalTable. This trap is generated in addition to the entConfigChange notification defined in RFC2737.
NTF mpeEntPhysicalExtEntityDeleted	1.3.6.1.4.1.1795.2.24.12.24.2.24			This trap signifies that an instance of this entity has been deleted from the entPhysicalTable. This trap is generated in addition to the entConfigChange notification defined in RFC2737.
NTF mpeEntPhysicalExtEntityChanged	1.3.6.1.4.1.1795.2.24.12.24.2.25			This trap signifies that an instance of this entity has been modified in the entPhysicalTable as a result of a change in any of the objects in that table. This trap is generated in addition to the entConfigChange notification defined in RFC2737.
mpeSysDevDslamConformance	1.3.6.1.4.1.1795.2.24.12.24.3
mpeSysDevDslamGroups	1.3.6.1.4.1.1795.2.24.12.24.3.1
mpeSysDevDslamAlarmStateGroup	1.3.6.1.4.1.1795.2.24.12.24.3.1.1			The collection of objects which are used to describe alarm states for equipments physically connected to a DSLAM device.
mpeEntityExtNotificationGroup	1.3.6.1.4.1.1795.2.24.12.24.3.1.2			The collection of objects which are used to notify that trap conditions are met.
mpeSysDevDslamAlarmRelayGroup	1.3.6.1.4.1.1795.2.24.12.24.3.1.3			The collection of objects which are used for Alarm Relay objects.
mpeEntPhysicalExtGroup	1.3.6.1.4.1.1795.2.24.12.24.3.1.4			The collection of objects which are used in extending the entPhysicalTable.
mpeEntPhysicalExtNotificationObjectGroup	1.3.6.1.4.1.1795.2.24.12.24.3.1.5			A collection of objects that are included in the OBJECTS clause of notifications.
mpeEntityExtPowerFailureNotificationGroup	1.3.6.1.4.1.1795.2.24.12.24.3.1.6			The collection of objects which are used to notify that trap conditions are met.
mpeSysDevDslamCompliances	1.3.6.1.4.1.1795.2.24.12.24.3.2
mpeSysDevDslamAlarmCompliances	1.3.6.1.4.1.1795.2.24.12.24.3.2.1			The compliance statement for entities and their alarms states.
mpeSysDevDslamAlarmDeprecatedCompliances	1.3.6.1.4.1.1795.2.24.12.24.3.2.2			The compliance statement for deprecated groups
mpeSysDevDslamDeprecatedGroup	1.3.6.1.4.1.1795.2.24.12.24.3.3
mpeDslamDeprecatedObjectsGroup	1.3.6.1.4.1.1795.2.24.12.24.3.3.1			The collection of objects that have been deprecated.
mpeDslamDeprecatedNotificationsGroup	1.3.6.1.4.1.1795.2.24.12.24.3.3.2			The collection of traps/notifications that have been deprecated.

RFC description

Paradyne DSLAM system MIB extending physical entity management with fan, power supply, and alarm monitoring.

Start monitoring Paradyne MPE DSLAM chassis (slot inventory/alarm relay, entPhysicalTable extension) 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 PDN-MPE-DSLAM-SYSTEM-MIB