PDN-UPLINK-TAGGING-MIB

All MIBs › PDN-UPLINK-TAGGING-MIB

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

Last Updated: 2003-03-12

Category: Switching

Description: Manages VLAN tagging and uplink port encapsulation policies for subscriber traffic aggregation on Paradyne DSLAM uplinks.

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-UPLINK-TAGGING-MIB?

PDN-UPLINK-TAGGING-MIB is a Paradyne (PDN) enterprise MIB for DSL access equipment that configures Uplink Tagging, a feature that assigns a unique VLAN tag per subscriber port so that traffic can be aggregated and identified on a shared uplink toward the WAN. It exposes configuration-oriented objects for setting base VLAN tags on a per-port and per-chassis basis (including model-specific 24-port and 48-port variants), and for coordinating tagging behavior when multiple DSLAM units are interconnected into a shared 'ULT Domain'. Its monitoring value is chiefly configuration verification -- confirming that each subscriber port's VLAN tag assignment matches provisioning intent -- rather than classical hardware health telemetry, since misconfigured tagging directly causes subscriber traffic misrouting or loss of uplink connectivity. It is a self-contained Paradyne enterprise extension with no strong dependency on external standard MIBs beyond general SNMPv2 conventions. It is deployed in broadband access network operator environments managing DSLAM chassis stacks that aggregate many subscriber lines onto shared backhaul links, where PDN-UPLINK-TAGGING-MIB SNMP monitoring confirms per-port VLAN tag assignments match provisioning intent.

IPNetwork Monitor allows you to monitor SNMP objects defined in PDN-UPLINK-TAGGING-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 chassis (24-port and 48-port variants)

Monitoring Examples

An operator would poll pdnUltIndex alongside pdnGenUltBaseVlanTag (or the model-specific pdn48UltBaseVlanTag/pdn24UltBaseVlanTag variants) to verify each uplink port's assigned base VLAN tag matches the subscriber-to-VLAN provisioning plan. If a port's ultBaseVlanTag value does not match its expected VLAN, subscriber traffic from that port could collide with or be misrouted relative to another subscriber's VLAN on the same aggregated uplink, a configuration fault this MIB is specifically designed to expose.

What Can Be Monitored

per-port base VLAN tag assignment
uplink tagging domain configuration
port-to-VLAN mapping index
chassis-specific tagging state

Imported Objects

From PDN-HEADER-MIB

pdn-common

From Q-BRIDGE-MIB

VlanId

From SNMPv2-CONF

OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

OIDs

OID symbolic	OID numeric	Type	Access	Description
pdnUplinkTagging	1.3.6.1.4.1.1795.2.24.2.37			This MIB contains objects that are used to configure Uplink Tagging (ULT). Uplink Tagging is a term used to describe a feature that simplifies the setup and administration of networks where a service provider wants to use a unique VLAN per subscriber port. Ingress frames will get tagged with a VLAN and these tagged frame will be transmitted on the uplink port towards the WAN. In cases where the hardware implementation permits, multiple units can be interconnected together to form a 'Uplink Tagging Domain (ULT Domain)'. A ULT domain is defined as the set of interconnected Paradyne DSLAMs that share a common block of VLAN IDs. The maximum number of Paradyne DSLAMs that can be interconnected is implementation dependent. Generally, all DSLAMs in a ULT Domain will be configured with the same block of VLAN IDs. Each chassis/unit will be assigned a unique ULT Index within the ULT Domain. There are two parts of configuring Uplink Tagging: 1. Uplink Base VLAN Tag - This object specifies the beginning VLAN ID for a particular common block of VLAN IDs. This object will be defined as an enumeration whose values will depend on the number of port in a chassis/unit. 2. Uplink Tag Index - This object specifies the index within some block of VLAN IDs. Generally, this index can thought of a chassis/unit number as can be seen with the examples below.
pdnUplinkTaggingObjects	1.3.6.1.4.1.1795.2.24.2.37.1
INT ultBaseVlanTag	1.3.6.1.4.1.1795.2.24.2.37.1.1	INTEGER	read-write	This object represents Uplink Tagging base index. This object has been deprecated. Please use an object defined in pdnUplinkTaggingObjectsR2.
INT ultIndex	1.3.6.1.4.1.1795.2.24.2.37.1.2	INTEGER	read-write	This object represents VLAN tag index which represents an index into a block of VLAN Tags the unit will use. This object has been deprecated. Please use pdnUltIndex, which is more general below.
pdnUplinkTaggingConformance	1.3.6.1.4.1.1795.2.24.2.37.2
pdnUplinkTaggingGroups	1.3.6.1.4.1.1795.2.24.2.37.2.1
pdn48PortUpLinkTaggingGroup	1.3.6.1.4.1.1795.2.24.2.37.2.1.1			Uplink Tagging Objects for 48-Port chassis/units.
pdn24PortUpLinkTaggingGroup	1.3.6.1.4.1.1795.2.24.2.37.2.1.2			Uplink Tagging Objects for 24-Port chassis/units.
pdnUplinkTaggingCompliances	1.3.6.1.4.1.1795.2.24.2.37.2.2
pdnUplinkTaggingDeprecatedGroup	1.3.6.1.4.1.1795.2.24.2.37.2.3
upLinkTaggingDeprecatedGroup	1.3.6.1.4.1.1795.2.24.2.37.2.3.1			Objects not to use.
pdnUplinkTaggingObjectsR2	1.3.6.1.4.1.1795.2.24.2.37.3
U32 pdnUltIndex	1.3.6.1.4.1.1795.2.24.2.37.3.1	Unsigned32	read-write	This object represents VLAN tag index which is an index into a block of VLAN Tags the unit will use. Generally, this can be also thought of as the chassis/unit number in the case where multiple units are interconnected and form a ULT Domain described above. It is strongly encouraged that the upper limit for a particular implementation be clearly documented in the product's SNMP Op Spec.
VLA pdnGenUltBaseVlanTag	1.3.6.1.4.1.1795.2.24.2.37.3.2	VlanId	read-write	This object can be used to allow any Uplink Tagging Base Index to be entered when they don't like the 'canned' list defined in the objects below.
INT pdn48UltBaseVlanTag	1.3.6.1.4.1.1795.2.24.2.37.3.3	INTEGER	read-write	This object represents Uplink Tagging base index which is the starting VLAN ID for a particular common block of VLAN IDs for chassis/units that contain 48 DSL subscriber ports.
INT pdn24UltBaseVlanTag	1.3.6.1.4.1.1795.2.24.2.37.3.4	INTEGER	read-write	This object represents Uplink Tagging base index which is the starting VLAN ID for a particular common block of VLAN IDs for chassis/units that contain 24 DSL subscriber ports.

RFC description

Configures Uplink Tagging to simplify VLAN management across interconnected Paradyne DSLAMs.

Start monitoring Paradyne DSLAM chassis, 24-port and 48-port variants (uplink VLAN tagging) 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-UPLINK-TAGGING-MIB

What Is PDN-UPLINK-TAGGING-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description