PDN-MPE-DSLAM-SYSTEM-MIB

        The mpe dslam MIB. This MIB is written specifically to
extend entPhysicalTable.
    
Source file
PDN-MPE-DSLAM-SYSTEM-MIB
Last revised
Identity
mpe-dslam
Base OID
1.3.6.1.4.1.1795.2.24.12.24
Imported Objects
ENTITY-MIB entPhysicalEntry entPhysicalIndex
PDN-HEADER-MIB pdn-mpe
PDN-MPE-MIB2-MIB mpeSysObjectID
PDN-TC ContactState
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) TimeTicks
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the paradyne MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'PDN-MPE-DSLAM-SYSTEM-MIB' -M '/opt/observium/mibs/paradyne:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'PDN-MPE-DSLAM-SYSTEM-MIB::mpe-dslam'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'PDN-MPE-DSLAM-SYSTEM-MIB' -M '/opt/observium/mibs/paradyne:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'PDN-MPE-DSLAM-SYSTEM-MIB::mpe-dslam'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (25)
.1.3.6.1.4.1.1795.2.24.12.24
.1.3.6.1.4.1.1795.2.24.12.24.1
.1.3.6.1.4.1.1795.2.24.12.24.1.1
.1.3.6.1.4.1.1795.2.24.12.24.1.1.1
.1.3.6.1.4.1.1795.2.24.12.24.1.1.1.1
.1.3.6.1.4.1.1795.2.24.12.24.1.1.1.1.1
.1.3.6.1.4.1.1795.2.24.12.24.1.2
.1.3.6.1.4.1.1795.2.24.12.24.1.2.1
.1.3.6.1.4.1.1795.2.24.12.24.1.2.2
.1.3.6.1.4.1.1795.2.24.12.24.1.2.3
.1.3.6.1.4.1.1795.2.24.12.24.1.2.3.1
.1.3.6.1.4.1.1795.2.24.12.24.1.2.3.1.1
.1.3.6.1.4.1.1795.2.24.12.24.1.3
.1.3.6.1.4.1.1795.2.24.12.24.1.3.1
.1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1
.1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1.1
.1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1.2
.1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1.3
.1.3.6.1.4.1.1795.2.24.12.24.1.3.1.1.4
.1.3.6.1.4.1.1795.2.24.12.24.2
.1.3.6.1.4.1.1795.2.24.12.24.2.0
.1.3.6.1.4.1.1795.2.24.12.24.3
.1.3.6.1.4.1.1795.2.24.12.24.3.1
.1.3.6.1.4.1.1795.2.24.12.24.3.2
.1.3.6.1.4.1.1795.2.24.12.24.3.3
Dependencies (13) 8 direct · 5 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (2)
Enumeration
up(1)
down(2)
testing(3)
Enumeration
up(1)
down(2)
testing(3)
unknown(4)
dormant(5)
notPresent(6)
reserved1(7)
Conformance Groups (8)
The collection of objects which are used
to describe alarm states for equipments
physically connected to a DSLAM device.
.1.3.6.1.4.1.1795.2.24.12.24.3.1.1
The collection of objects which are used
to notify that trap conditions are met.
.1.3.6.1.4.1.1795.2.24.12.24.3.1.2
The collection of objects which are used
for Alarm Relay objects.
.1.3.6.1.4.1.1795.2.24.12.24.3.1.3
The collection of objects which are used
in extending the entPhysicalTable.
.1.3.6.1.4.1.1795.2.24.12.24.3.1.4
A collection of objects that are included in the OBJECTS
clause of notifications.
.1.3.6.1.4.1.1795.2.24.12.24.3.1.5
The collection of objects which are used
to notify that trap conditions are met.
.1.3.6.1.4.1.1795.2.24.12.24.3.1.6
The collection of objects that have been deprecated.
.1.3.6.1.4.1.1795.2.24.12.24.3.3.1
The collection of traps/notifications that have been deprecated.
.1.3.6.1.4.1.1795.2.24.12.24.3.3.2
Compliance Statements (2)

OID .1.3.6.1.4.1.1795.2.24.12.24.3.2.1
The compliance statement for entities and their
alarms states.
Required groups
optional mpeSysDevDslamAlarmStateGroup The conditional objects in the group
optional mpeEntityExtNotificationGroup Notification group
optional mpeSysDevDslamAlarmRelayGroup Alarm Relay group
optional mpeEntPhysicalExtGroup Entity Physical Ext group
optional mpeEntPhysicalExtNotificationObjectGroup Notification objects group
optional mpeEntityExtPowerFailureNotificationGroup Power Supply notification objects group
Object refinements
ObjectAccessSyntaxDescription
mpeEntExtAlarm
Write access is not required.

OID .1.3.6.1.4.1.1795.2.24.12.24.3.2.2
The compliance statement for deprecated groups
Required groups
optional mpeDslamDeprecatedObjectsGroup Entity Physical Ext group
optional mpeDslamDeprecatedNotificationsGroup Notification objects group
Notifications / Traps (16)
NameOIDDescription
.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.
.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.
.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.
.1.3.6.1.4.1.1795.2.24.12.24.2.0.29
This trap indicates that power source A
has failed.
.1.3.6.1.4.1.1795.2.24.12.24.2.0.30
This trap indicates that power source B
has failed.
.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.
.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.
.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
.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.
.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
.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.
.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.
.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.
.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.
.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.
.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