All MIBs › PDN-PPP-BRIDGE-NCP-EXT-MIB
Organization: Paradyne Networks MIB Working Group Other information about group editing the MIB
Last Updated: 2004-09-10
Category: DSL and Broadband
Description: Extends PPP Bridge NCP (BCP) with Paradyne-specific bridging negotiation options and parameter configuration objects.
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-PPP-BRIDGE-NCP-EXT-MIB?
PDN-PPP-BRIDGE-NCP-EXT-MIB is a Paradyne Networks vendor extension to the standard PPP-BRIDGE-MIB, adding enterprise-specific objects for negotiating and configuring the Bridge Control Protocol (BCP) on PPP-based subnetwork interfaces. It exposes per-interface BCP link status (current negotiation state) and 802.1Q tagging direction settings (local-to-remote and remote-to-local), plus a media configuration extension table controlling IEEE 802 tagging behavior, along with a notifications group for BCP-related events. Its monitoring focus is software/protocol status - pdnPppBridgeBcpLinkStatusCurrState reveals whether BCP negotiation on a given PPP link has succeeded, failed, or is still in progress, which is essential for diagnosing bridged-Ethernet-over-PPP connectivity problems. It explicitly depends on and extends the standard PPP-BRIDGE-MIB (as referenced in RFC 1474) and the broader PPP Network Control Protocol suite, adding vendor tagging/negotiation detail on top of the standard framework. The PDN-PPP-BRIDGE-NCP-EXT-MIB MIB is deployed on Paradyne access equipment that bridges Ethernet traffic over PPP links, such as DSL access concentrators using BCP to carry subscriber Ethernet frames.
IPNetwork Monitor allows you to monitor SNMP objects defined in PDN-PPP-BRIDGE-NCP-EXT-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 Networks access equipment (DSL access concentrator using PPP bridging)
Monitoring Examples
An administrator would poll pdnPppBridgeExtTable/pdnPppBridgeExtEntry to check pdnPppBridgeBcpLinkStatusCurrState for a subscriber's PPP link, confirming whether BCP negotiation completed successfully; a link stuck in a non-established state points to a BCP option mismatch with the peer. pdnPppBridgeLocalToRemote802Tagged and pdnPppBridgeRemoteToLocal802Tagged reveal whether 802.1Q tagging is being applied asymmetrically across the link, and pdnPppBridgeMediaConfigExtTable/pdnPppBridgeMediaIeee802Tagged would be checked to confirm media-level tagging configuration matches expectations end-to-end.
What Can Be Monitored
- BCP link negotiation status
- 802.1Q tagging direction settings
- media-level IEEE 802 tagging configuration
Imported Objects
From PDN-HEADER-MIB
| pdn-interfaces |
From PDN-TC
| PdnPPPState | |
| SwitchState |
From PPP-BRIDGE-NCP-MIB
| pppBridgeEntry | OBJECT-TYPE |
| pppBridgeMediaConfigEntry | OBJECT-TYPE |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE |
OIDs
RFC description
Provides enterprise extensions for Bridge Control Protocol (BCP) management on point-to-point protocol interfaces.
Start monitoring Paradyne Networks access equipment, DSL access concentrator using PPP bridging (Bridge Control Protocol extensions) 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.