Nortel-Magellan-Passport-HdlcTransparentMIB :: htdsPlcPathType

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Nortel-Magellan-Passport-HdlcTransparentMIB › htdsPlcPathType

htdsPlcPathType

Module: Nortel-Magellan-Passport-HdlcTransparentMIB

OID (symbolic): Nortel-Magellan-Passport-HdlcTransparentMIB::htdsPlcPathType

OID (numeric): 1.3.6.1.4.1.562.2.4.1.82.3.10.1.16

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This attribute specifies if the path for this PLC is determined automatically or by static provisioning. The default (normal) is to automatically choose a route with Route Selection. Normal pathTypes require less provisioning and can dynamically handle path failures. The other pathTypes are both manual pathTypes where the operator must specify, through provisioning, a static route termed the manualPath. A manual pathType connection is nearly identical to a normal path type connection with the exception that the route is pre-provisioned. For a manual pathType, bandwidth reservations are respected along the path exactly as in a normal path. The last type, the forced pathType, is also a manual path but regardless of the bandwidth available the route is granted provided the trunks are operational and there are sufficient Logical Channels (LChs). The forced pathType could result in over committing the reserved bandwidth allowed on a trunk. A better way to achieve the effects of a forced pathType is to use a manual pathType with setupPriority = 0 and holdingPriority = 0. In this manner the path will reserve correct bandwidth and it will bump other paths if required while not being bumped itself.

What is htdsPlcPathType?

Selects whether this connection's path is chosen automatically by route selection (normal, the default), follows a statically provisioned route (manual), or is forced onto a static route regardless of available bandwidth (forced). Forced paths can over-commit trunk bandwidth, so a manual path with setupPriority=holdingPriority=0 is usually a safer way to get the same effect.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.562.2.4.1.82.3.10.1.16
snmpwalk -v2c -c public <target> Nortel-Magellan-Passport-HdlcTransparentMIB::htdsPlcPathType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.562.2.4.1.82.3.10.1.16.1
snmpget -v2c -c public <target> Nortel-Magellan-Passport-HdlcTransparentMIB::htdsPlcPathType.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.562.2.4.1.82.3.10.1.16.1 i <value>

Start monitoring Nortel Magellan Passport multiservice switch (HDLC transparent leased-line service) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Nortel-Magellan-Passport-HdlcTransparentMIB::htdsPlcPathType OID value, configure state conditions and alerts, and monitor any Nortel Magellan Passport multiservice switch (HDLC transparent leased-line service) 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.562nortelCPM-NORTEL-MIB
1.3.6.1.4.1.562.2magellanNortel-Magellan-Passport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.2.4passportNortel-Magellan-Passport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.2.4.1componentsNortel-Magellan-Passport-UsefulDefinitionsMIB
Numeric OIDNameModule
1.3.6.1.4.1.562.2.4.1.82htdsNortel-Magellan-Passport-HdlcTransparentMIB
1.3.6.1.4.1.562.2.4.1.82.3htdsPlcNortel-Magellan-Passport-HdlcTransparentMIB
1.3.6.1.4.1.562.2.4.1.82.3.10htdsPlcProvTableNortel-Magellan-Passport-HdlcTransparentMIB
1.3.6.1.4.1.562.2.4.1.82.3.10.1htdsPlcProvEntryNortel-Magellan-Passport-HdlcTransparentMIB
1.3.6.1.4.1.562.2.4.1.82.3.10.1.16htdsPlcPathTypeNortel-Magellan-Passport-HdlcTransparentMIB