All MIBs › PDN-DHCP-MIB
Organization: Paradyne Networks MIB Working Group Other information about group editing the MIB
Last Updated: 2004-09-13
Category: IP Services
Description: Manages DHCP relay agent configuration, Option 82 subscriber-circuit-id policies, and forwarded-packet counters on Paradyne DSLAM equipment.
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-DHCP-MIB?
PDN-DHCP-MIB is a Paradyne enterprise MIB for managing an interface's DHCP relay-agent behavior on Paradyne DSLAM equipment, notably including DHCP Option 82 (relay agent information) configuration per subscriber VLAN. It exposes a VLAN-configuration table specifying whether Option 82 insertion is enabled for a given VLAN, plus notification objects for DHCP-related events. Its monitoring role is configuration/service health for subscriber provisioning -- confirming Option 82 circuit-ID insertion is correctly enabled on the VLANs where the upstream DHCP server relies on it to identify subscriber lines, since a misconfigured setting would break automatic IP address assignment or subscriber identification. It does not declare an explicit standards dependency but implements behavior aligned with the DHCP relay-agent-information option defined in RFC 3046. It is deployed on Paradyne DSLAM equipment acting as a DHCP relay agent for broadband subscribers, where PDN-DHCP-MIB SNMP monitoring confirms Option 82 insertion stays enabled on the correct VLANs.
IPNetwork Monitor allows you to monitor SNMP objects defined in PDN-DHCP-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 DSLAM (DHCP relay agent)
Monitoring Examples
An operator reads pdnDhcpVlanConfigTable/Entry (per VLAN) to confirm pdnDhcpVlanConfigOption82 is enabled on subscriber-facing VLANs, since disabling it would strip circuit-ID information the upstream DHCP server needs to assign the correct subscriber IP/policy. pdnDhcpNotifications would alert an operator to DHCP relay-related events such as configuration changes. Because this MIB centers on relay configuration rather than packet counters, it is used more for confirming correct provisioning than for tracking DHCP traffic volume.
What Can Be Monitored
- Option 82 insertion status per VLAN
- DHCP relay configuration state
- DHCP-related notification events
Imported Objects
From PDN-HEADER-MIB
| pdn-common |
From PDN-TC
| SwitchState |
From Q-BRIDGE-MIB
| dot1qVlanStaticEntry | OBJECT-TYPE |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE |
OIDs
RFC description
Manages DHCP configuration options on a per-VLAN basis for Paradyne network interfaces.
Start monitoring Paradyne DSLAM, DHCP relay agent (Option 82 configuration) 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.