PDN-BRIDGE-EXT-MIB :: pdnDot1dTrafficProfileNextIndex

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › PDN-BRIDGE-EXT-MIB › pdnDot1dTrafficProfileNextIndex

pdnDot1dTrafficProfileNextIndex

Module: PDN-BRIDGE-EXT-MIB

OID (symbolic): PDN-BRIDGE-EXT-MIB::pdnDot1dTrafficProfileNextIndex

OID (numeric): 1.3.6.1.4.1.1795.2.24.2.58.1.2.1

Node type: OBJECT-TYPE

Type: TestAndIncr

Access: read-write

Description: This object is used to establish the next unused index (pdnDot1dTrafficProfileIndex) for the pdnDot1dTrafficProfileTable.

This object is used to assist the manager in selecting a value for pdnDot1dTrafficProfileIndex. Because this object is of syntax TestAndIncr (see the SNMPv2-TC document, RFC 2579), it can also be used to avoid race conditions with multiple managers trying to create rows in the table.

If the result of the SET for pdnDot1dTrafficProfileIndex is not success, this means the value has been changed from index (i.e. another manager used the value), so a new value is required.

The algorithm is: done = false while done == false index = GET (pdnDot1dTrafficProfileNextIndex.0) SET (pdnDot1dTrafficProfileNextIndex.0=index) if (set failed) done = false else pdnDot1dTrafficProfileRowStatus.index=createAndGo SET (pdnDot1dTrafficProfileRowStatus.index) if (set failed) done = false else done = true other error handling

This description was modeled from RFC2494, DS0BUNDLE-MIB.

What is pdnDot1dTrafficProfileNextIndex?

This read-write value implements a TestAndIncr counter used to hand out the next unused index for creating a new row in the pdnDot1dTrafficProfileTable. A management station reads it, then writes that same value back to atomically claim the index before creating the traffic profile row, which avoids two managers colliding on the same index. If the write-back fails because another manager already advanced the counter, the manager simply re-reads and retries with the new value, per the described create-index algorithm.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.2.58.1.2.1
snmpwalk -v2c -c public <target> PDN-BRIDGE-EXT-MIB::pdnDot1dTrafficProfileNextIndex

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.2.58.1.2.1.1
snmpget -v2c -c public <target> PDN-BRIDGE-EXT-MIB::pdnDot1dTrafficProfileNextIndex.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.1795.2.24.2.58.1.2.1.1 s <value>

Start monitoring Paradyne/Zhone Ethernet-bridging DSL access equipment (QinQ/traffic-profile extensions) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PDN-BRIDGE-EXT-MIB::pdnDot1dTrafficProfileNextIndex OID value, configure state conditions and alerts, and monitor any Paradyne/Zhone Ethernet-bridging DSL access equipment (QinQ/traffic-profile extensions) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1795pdynPDN-HEADER-MIB
1.3.6.1.4.1.1795.2pdn_mgmtPDN-HEADER-MIB
1.3.6.1.4.1.1795.2.24paradynePDN-HEADER-MIB
1.3.6.1.4.1.1795.2.24.2pdn_commonPDN-HEADER-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1795.2.24.2.58pdnBridgeExtMIBPDN-BRIDGE-EXT-MIB
1.3.6.1.4.1.1795.2.24.2.58.1pdnBridgeExtObjectsPDN-BRIDGE-EXT-MIB
1.3.6.1.4.1.1795.2.24.2.58.1.2pdnDot1dTrafficProfilePDN-BRIDGE-EXT-MIB
1.3.6.1.4.1.1795.2.24.2.58.1.2.1pdnDot1dTrafficProfileNextIndexPDN-BRIDGE-EXT-MIB