mscBtdsPlcPathtype
View at oid-info.com
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.
Parsed from file nortelPC-bitTransparentV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-BitTransparentMIB
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.
Parsed from file Nortel-MsCarrier-MscPassport-BitTransparentMIB.mib
Module: Nortel-MsCarrier-MscPassport-BitTransparentMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-MsCarrier-MscPassport-BitTransparentMIB
[Automatically extracted from oidview.com]
mscBtdsPlcPathType OBJECT-TYPE SYNTAX INTEGER { normal(0), manual(1), forced(2) } ACCESS read-write STATUS mandatory 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." DEFVAL { normal } ::= { mscBtdsPlcProvEntry 16 }
mscBtdsPlcPathType OBJECT-TYPE SYNTAX INTEGER { normal(0), manual(1), forced(2) } ACCESS read-write STATUS mandatory 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." DEFVAL { normal } ::= { mscBtdsPlcProvEntry 16 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.2 | mscBtdsPlcRemoteName | 0 | 0 | This attribute is the PLC's remote end point's address in the format of a Passport component name. The syntax of a component is:… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.3 | mscBtdsPlcSetupPriority | 0 | 0 | This attribute gives the priority at which a path is established. Zero is the highest priority and four is the lowest. When PORS… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.4 | mscBtdsPlcHoldingPriority | 0 | 0 | This attribute gives the priority that a path holds once it is established. Zero(0) is the highest priority and four(4) is the l… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.5 | mscBtdsPlcRequiredTxBandwidth | 0 | 0 | This attribute gives the bandwidth (in bits per second) reserved by a path on each of the trunks of its route. This attribute re… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.6 | mscBtdsPlcRequiredRxBandwidth | 0 | 0 | This attribute gives the bandwidth (in bits per second) reserved by a path on each of trunks of its route. This attribute repres… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.7 | mscBtdsPlcRequiredTrafficType | 0 | 0 | This attribute indicates the type of traffic transmitted over the path. There are eight(8) possible traffic types, and the path … |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.8 | mscBtdsPlcPermittedTrunkTypes | 0 | 0 | This attribute lists up to eight(8) types of trunk that can be used on the route. The terrestrial and satellite trunk types have… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.9 | mscBtdsPlcRequiredSecurity | 0 | 0 | This attribute indicates the required minimum level of security of the trunks on the route. Zero represents the most secure and … |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.10 | mscBtdsPlcRequiredCustomerParm | 0 | 0 | This attribute indicates the allowed customer defined parameter of the trunks on the route. Its value, a number from zero to sev… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.11 | mscBtdsPlcPathAttributeToMinimize | 0 | 0 | This attribute indicates whether a route is selected on the basis of minimizing the cost or the delay. Each trunk has a cost and… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.12 | mscBtdsPlcMaximumAcceptableCost | 0 | 0 | This attribute indicates an upper bound on the cost metric of a route, which is the sum of the cost metrics of all trunks on the… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.13 | mscBtdsPlcMaximumAcceptableDelay | 0 | 0 | This attribute indicates an upper bound on the delay of a route, which is the sum of the delay of all trunks on the route. It sh… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.14 | mscBtdsPlcEmissionPriority | 0 | 0 | This attribute indicates the urgency with which packets on the path are emitted by the trunks on the route. EmissionPriority of … |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.15 | mscBtdsPlcDiscardPriority | 0 | 0 | This attribute indicates the importance of the packets on the path. One is used for paths carrying the most important traffic, a… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.17 | mscBtdsPlcPathFailureAction | 0 | 0 | This attribute is used to specify whether the application can tolerate momentary interruption of a path while a new path is sele… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.18 | mscBtdsPlcBumpPreference | 0 | 0 | This attribute controls when bumping occurs in the route selection process. A connection with higher (numerically less) setupPri… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.19 | mscBtdsPlcOptimization | 0 | 0 | This attribute is used to specify whether this connection should attempt to optimize its path when requested by the routing PORS… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.20 | mscBtdsPlcAddressToCall | 0 | 0 | This attribute is the PLC's remote end point's address in the format of a NSAP address. As such it must consist of a string of h… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.21 | mscBtdsPlcLocalAddress | 0 | 0 | This attribute is the PLC's end point address in the format of an NSAP address. As such it must consist of a string of hex digit… |
| 1.3.6.1.4.1.562.36.2.1.81.3.10.1.22 | mscBtdsPlcMaximumAcceptableGatewayCost | 0 | 0 | This attribute indicates an upper bound on the gateway cost metric of a route, which is the sum of the gateway cost metrics of a… |