PDN-HDSL2-SHDSL-LINE-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PDN-HDSL2-SHDSL-LINE-MIB

Organization: Paradyne Networks MIB Working Group Other information about group editing the MIB

Last Updated: 2005-01-28

Category: DSL and Broadband

Description: Manages HDSL2 and SHDSL line configuration, attainable rates, loop attenuation, and error counts on Paradyne DSL gear.

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-HDSL2-SHDSL-LINE-MIB?

PDN-HDSL2-SHDSL-LINE-MIB is a Paradyne (later part of Zhone/DZS) enterprise MIB for managing HDSL2 and G.shdsl.bis DSL lines, created as an interim vendor extension to support G.shdsl.bis ahead of updates to the IETF standard HDSL2-SHDSL-LINE-MIB (RFC 3276). It exposes extended span status, endpoint configuration (including wire pair and alarm-configuration profile), and current endpoint performance objects such as attainable and actual line rate, attenuation, and SNR margin. This is a hardware/line-health monitoring MIB used to assess the physical quality of copper DSL loops — degrading attenuation or SNR margin readings, or an actual line rate falling below the attainable rate, indicate a failing or noisy line before it drops entirely. It explicitly depends on and extends the IETF standard HDSL2-SHDSL-LINE-MIB (RFC 3276) and the related G.shdsl.bis ITU specification, reusing that standard's endpoint indexing model while adding vendor-specific fields. It is deployed on Paradyne DSL access/transport equipment in carrier or enterprise access networks delivering symmetric high-speed DSL service over copper, with the PDN-HDSL2-SHDSL-LINE-MIB MIB serving as the vendor's interim extension of the IETF standard.

IPNetwork Monitor allows you to monitor SNMP objects defined in PDN-HDSL2-SHDSL-LINE-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 DSL access/transport equipment

Monitoring Examples

An operator would poll pdnHdsl2ShdslEndpointCurrTable/pdnHdsl2ShdslEndpointCurrEntry for pdnHdsl2ShdslEndpointCurrAtn (attenuation) and pdnHdsl2ShdslEndpointCurrSnrMgn (SNR margin) per pdnHdsl2ShdslEndpointWirePair, and a rising attenuation or falling SNR margin signals a deteriorating copper pair. Comparing pdnHdsl2ShdslStatusActualLineRate against pdnHdsl2ShdslStatusMaxAttainableLineRate in pdnHdsl2ShdslSpanStatusExtTable reveals whether the line is running below its potential capacity, and pdnHdsl2ShdslLineNotifications would alert when an alarm profile configured via pdnHdsl2ShdslEndpointAlarmConfProfile is triggered.

What Can Be Monitored

  • line attenuation
  • SNR margin
  • actual vs. maximum attainable line rate
  • endpoint alarm profile status
  • wire pair configuration
Imported Objects

From HDSL2-SHDSL-LINE-MIB

Hdsl2Shdsl1DayIntervalCount
Hdsl2ShdslPerfCurrDayCount
Hdsl2ShdslPerfTimeElapsed
hdsl2ShdslEndpointSideOBJECT-TYPE
hdsl2ShdslEndpointThreshCRCanomaliesOBJECT-TYPE
hdsl2ShdslEndpointThreshESOBJECT-TYPE
hdsl2ShdslEndpointThreshLOSWSOBJECT-TYPE
hdsl2ShdslEndpointThreshLoopAttenuationOBJECT-TYPE
hdsl2ShdslEndpointThreshSESOBJECT-TYPE
hdsl2ShdslEndpointThreshSNRMarginOBJECT-TYPE
hdsl2ShdslEndpointThreshUASOBJECT-TYPE
hdsl2ShdslInvIndexOBJECT-TYPE
hdsl2ShdslSpanConfProfileNameOBJECT-TYPE

From IF-MIB

ifIndexOBJECT-TYPE

From PDN-HEADER-MIB

pdn-interfaces

From PerfHist-TC-MIB

PerfCurrentCount
PerfIntervalCount

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using pdnHdsl2ShdslEndpointES OID:

Select a Paradyne DSL access/transport equipment (HDSL2/G.shdsl.bis line quality) 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 pdnHdsl2ShdslEndpointES 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. It reports the count of Errored Seconds (ES) on this endpoint since the xU was last restarted. 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 Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Monitors HDSL2 and SHDSL digital subscriber line performance metrics and configuration for Paradyne devices.

Start monitoring Paradyne DSL access/transport equipment (HDSL2/G.shdsl.bis line quality) 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-HDSL2-SHDSL-LINE-MIB