htdsLCoPathtype
View at oid-info.com
This attribute indicates whether the path for this PLC was
determined automatically or by static provisioning. Normal
pathTypes are selected automatically by Route Selector.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 nortelPP-hdlcTransparentV1_BG00S4C.mib.txt
Company: None
Module: Nortel-Magellan-Passport-HdlcTransparentMIB
This attribute indicates whether the path for this PLC was
determined automatically or by static provisioning. Normal
pathTypes are selected automatically by Route Selector.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-Magellan-Passport-HdlcTransparentMIB.mib
Module: Nortel-Magellan-Passport-HdlcTransparentMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-Magellan-Passport-HdlcTransparentMIB
[Automatically extracted from oidview.com]
htdsLCoPathType OBJECT-TYPE SYNTAX INTEGER { normal(0), manual(1), forced(2) } ACCESS read-only STATUS mandatory DESCRIPTION "This attribute indicates whether the path for this PLC was determined automatically or by static provisioning. Normal pathTypes are selected automatically by Route Selector.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." ::= { htdsLCoPathDataEntry 17 }
htdsLCoPathType OBJECT-TYPE SYNTAX INTEGER { normal(0), manual(1), forced(2) } ACCESS read-only STATUS mandatory DESCRIPTION "This attribute indicates whether the path for this PLC was determined automatically or by static provisioning. Normal pathTypes are selected automatically by Route Selector.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." ::= { htdsLCoPathDataEntry 17 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.1 | htdsLCoState | 0 | 0 | This attribute reflects the current state of the connection. The pathDown state indicates a connection that has no remote end pro… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.2 | htdsLCoOverrideRemoteName | 0 | 0 | If set and the current PLC remoteName is blank this remoteName will override the blank PLC remoteName. Usually you would set this… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.3 | htdsLCoEnd | 0 | 0 | This attribute identifies whether this is the calling or called end of the path. |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.4 | htdsLCoCostMetric | 0 | 0 | This attribute gives the route's total cost metric. It is calculated as the sum of the cost metric of all trunks in the path at … |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.5 | htdsLCoDelayMetric | 0 | 0 | This attribute gives the total delay of the route as the one way delay for a 512 byte packet. It is calculated as the sum of the… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.6 | htdsLCoRoundTripDelay | 0 | 0 | This attribute contains the time taken for a packet (cell) of 44 bytes to be transmitted to the remote LCo and return to this LC… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.7 | htdsLCoSetupPriority | 0 | 0 | This attribute gives the priority at which the current path is established. Zero is the highest priority and four is the lowest.… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.8 | htdsLCoHoldingPriority | 0 | 0 | This attribute gives the priority at which a path holds its current path once the path is established. Zero is the highest prior… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.9 | htdsLCoRequiredTxBandwidth | 0 | 0 | This attribute gives the actual bandwidth (in bits per second) reserved by this path on each of the trunks of its route. This at… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.10 | htdsLCoRequiredRxBandwidth | 0 | 0 | This attribute gives the actual bandwidth (in bits per second) reserved by this path on each of trunks of its route. This attrib… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.11 | htdsLCoRequiredTrafficType | 0 | 0 | This operational attribute indicates the type of traffic transmitted over the path. There are eight possible traffic types, and … |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.12 | htdsLCoPermittedTrunkTypes | 0 | 0 | This operational attribute lists up to eight types of trunk that can be used on the route. The originating end of the connection… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.13 | htdsLCoRequiredSecurity | 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.2.4.1.82.4.10.1.14 | htdsLCoRequiredCustomerParameter | 0 | 0 | This attribute indicates the allowed customer defined parameter of the trunks on the route.The originating end of the connection… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.15 | htdsLCoEmissionPriority | 0 | 0 | This attribute indicates the urgency with which packets on the path are emitted by the trunks on the route. The originating end … |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.16 | htdsLCoDiscardPriority | 0 | 0 | This attribute indicates the importance of the packets on the path.The originating end of the connection sets discardPriority. O… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.18 | htdsLCoRetryCount | 0 | 0 | This attribute is the count of the number of times the path chosen during route selection could not be instantiated. This count … |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.19 | htdsLCoPathFailureCount | 0 | 0 | This attribute is the count of the number of times the path has successfully connected. It is set to zero the first time the pat… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.20 | htdsLCoReasonForNoRoute | 0 | 0 | This attribute is the route selection's reasonForNoRoute and provides a brief reason for which a route was not selected. The reas… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.21 | htdsLCoLastTearDownReason | 0 | 0 | This attribute reflects the last tear down reason for a connection (LCo). In many cases this displays the reason for a momentary… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.22 | htdsLCoPathFailureAction | 0 | 0 | This attribute displays whether the application is set to tolerate momentary interruption of a path while a new path is selected… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.23 | htdsLCoBumpPreference | 0 | 0 | This attribute specifies when bumping will occur during route selection process. Bumping may occur when necessary or always. It w… |
| 1.3.6.1.4.1.562.2.4.1.82.4.10.1.24 | htdsLCoOptimization | 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.2.4.1.82.4.10.1.25 | htdsLCoPathUpDateTime | 0 | 0 | This is the time stamp when the current path was established or reestablished. |