PDN-MPE-MIB2-MIB

All MIBs › PDN-MPE-MIB2-MIB

Category: DSL and Broadband

Description: Extends standard MIB-II interface and system objects for the Paradyne Multi-Port Ethernet module.

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-MIB2-MIB?

PDN-MPE-MIB2-MIB is a Paradyne-specific extension to the standard MIB-II system group, tailored for the Multi-Port Ethernet (MPE) module used in Paradyne access and aggregation equipment. It exposes the same class of basic identification and status data as RFC 1213's system group, but scoped to each MPE module instance, including descriptors, object identifiers, contact and location strings, and supported services. Its main monitoring value is device-level health and identity tracking: administrators use it to confirm that a module is up (via a system uptime counter), correctly identified by descriptor and object ID, and configured with accurate contact/location/name information for inventory and fault-management purposes. It is built directly on the structure of the standard MIB-II system group (RFC 1213/1907), effectively duplicating it in a vendor-specific subtree for per-module scoping. It is typically deployed in legacy Paradyne/Zhone multi-port Ethernet access devices managed by NMS platforms performing basic reachability and inventory polling. Network engineers evaluating or troubleshooting this functionality can download the PDN-MPE-MIB2-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in PDN-MPE-MIB2-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 Multi-Port Ethernet (MPE) module
Paradyne/Zhone access/aggregation equipment

Monitoring Examples

An operator would poll the mpeSystemsTable, walking mpeSystemsEntry rows to retrieve mpeSysDescr, mpeSysObjectID, and mpeSysUpTime for each Multi-Port Ethernet module in the chassis. A sudden reset of mpeSysUpTime to a low value would indicate the module rebooted unexpectedly, while a mismatch in mpeSysServices could reveal a misconfigured module. mpeSysContact, mpeSysName, and mpeSysLocation are typically checked during inventory audits to ensure asset records are current.

What Can Be Monitored

module uptime
system descriptor/object ID
system contact and location strings
system name
supported services bitmask
module reboot detection

Imported Objects

From ENTITY-MIB

entPhysicalIndex

OBJECT-TYPE

From PDN-HEADER-MIB

mpe-mib2

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

TimeTicks

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
mpeMib2MIBObjects	1.3.6.1.4.1.1795.2.24.12.4.1
mpeSystem	1.3.6.1.4.1.1795.2.24.12.4.1.1
mpeSystemsTable	1.3.6.1.4.1.1795.2.24.12.4.1.1.1		not-accessible	A table that contains general information about an Entity .
mpeSystemsEntry	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1		not-accessible	A list of system information about an Entity .
STR mpeSysDescr	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.1	DisplayString	read-only	A textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating-system, and networking software. It is mandatory that this only contain printable ASCII characters.
OID mpeSysObjectID	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.2	OBJECT IDENTIFIER	read-only	The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.
TIK mpeSysUpTime	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.3	TimeTicks	read-only	The time (in hundredths of a second) since the network management portion of the system was last re-initialized.
STR mpeSysContact	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.4	DisplayString	read-write	The textual identification of the contact person for this managed node, together with information on how to contact this person.
STR mpeSysName	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.5	DisplayString	read-write	An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name.
STR mpeSysLocation	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.6	DisplayString	read-write	The physical location of this node (e.g., `telephone closet, 3rd floor').
INT mpeSysServices	1.3.6.1.4.1.1795.2.24.12.4.1.1.1.1.7	INTEGER	read-only	A value which indicates the set of services that this entity primarily offers. The value is a sum. This sum initially takes the value zero, Then, for each layer, L, in the range 1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which performs primarily routing functions would have a value of 4 (2^(3-1)). In contrast, a node which is a host offering application services would have a value of 72 (2^(4-1) + 2^(7-1)). Note that in the context of the Internet suite of protocols, values should be calculated accordingly: layer functionality 1 physical (e.g., repeaters) 2 datalink/subnetwork (e.g., bridges) 3 internet (e.g., IP gateways) 4 end-to-end (e.g., IP hosts) 7 applications (e.g., mail relays) For systems including OSI protocols, layers 5 and 6 may also be counted.
mpeMib2MIBTraps	1.3.6.1.4.1.1795.2.24.12.4.2

RFC description

Manages system information and entity-level details for Paradyne MPE (Multi-Protocol Engine) devices.

Start monitoring Paradyne Multi-Port Ethernet (MPE) module, Paradyne/Zhone access/aggregation equipment (per-module MIB-II system group) 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-MIB2-MIB

What Is PDN-MPE-MIB2-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description