This attribute reflects the last tear down reason for a connection
(LCo). In many cases this displays the reason for a momentary
service interruption. This attribute applies to the last path failure
only. If a path is no longer up, this may give an indication to the
reason that the path has failed. In many cases an alarm will also be
generated with more specific information. The following is a brief
description of the reasons:
none - This path has no information for the teardown this is typical
of a path provisioned with no remoteName that has not been up.
normalShutDown - This path has gone down due to normal call
termination.
insufficientTxLcOrBandwidth - At present there is either no
available bandwidth or logical channel numbers available on one or
more of the trunks for this path in the transmit direction.
insufficientRxLcOrBandwidth - At present there is either no
available bandwidth or logical channel numbers available on one or
more of the trunks for this path in the receive direction.
trunkFailure- A trunk on the path has failed or has gone down due
to a provisioning change of a critical attribute.
trunkCardFailure- A trunk FP card has failed along the path.
accessCardFailure- The FP on which the peer access service was
running has failed.
operatorForced- The path has terminated due to the operator
locking a trunk along the path.
lostLcnClash- The path has terminated because the PA's at both
ends of an intermediate trunk have allocated the same LC to
different calls. When this happens both calls must go down and then
try to come up again a fraction of a second later (effectively
ensuring that they will now be assigned different LC's). It is normal
to get the odd clash especially when the PA's usedLC is
approaching the PA's maxLC.
networkCongestion - The path has failed due to control information
being lost and not recoverable.
trunkNotFound - Occurs on a manual path usually. Check for
trunks not up or names provisioned incorrectly.
farEndNotFound - The far end is not provisioned or is not up.
Check remote Name.
wrongModuleReached - This may occur on a manual path. Check
provisioning for correct trunk and service names. For a normal
path, the network Topology may be changing check remoteName.
farEndBusy - The far end has been reached but it is busy. Check
remoteName and remote end provisioning.
callLoopedBack - This LCo is provisioned to call itself. Re-
provision since this is invalid.
unknownReason - The failure was not resolved.
farEndNotReady - The remote end was reached but the connection
was refused due to the remote end not being enabled.
remoteNameMismatch - The remote end has alarmed and rejected
this setup due to remoteName provisioning.
serviceTypeMismatch - The remote Service Type does not match
this service type. Check provisioning.
reconnectFromFarEnd - The remote end re-established this
connection. Check the remote end lastTearDownReason to
determine the real reason.
bumped - Another call bumped this path from a trunk to get
bandwidth (or an LC) which it required to come up. This other path
had a higher setupPriority than this path's holdingPriority hence it
was allowed to steal the bandwidth (or LC) from this path.
optimized - This call has been rerouted due to the optimization
feature. The call is still active this just indicates why the path
changed.
trunkOrFarEndDidNotSupportMode - This call was unable to
complete because a mode required by the service was not supported
by one of the trunks the route went through or by the far end service
it connected to. Currently the only mode that this applies to is the
map/mux mode on TRUNK PA ATM component. Map mode was
required by the application (CES/FrAtm etc.) but was not available
on the TRUNK PA ATM component through which the call was
routed or the far end CES/FrAtm component did not specify the
same mode.
Parsed from file nortelPP-hdlcTransparentV1_BG00S4C.mib.txt
Company: None
Module: Nortel-Magellan-Passport-HdlcTransparentMIB
This attribute reflects the last tear down reason for a connection
(LCo). In many cases this displays the reason for a momentary
service interruption. This attribute applies to the last path failure
only. If a path is no longer up, this may give an indication to the
reason that the path has failed. In many cases an alarm will also be
generated with more specific information. The following is a brief
description of the reasons:
none - This path has no information for the teardown this is typical
of a path provisioned with no remoteName that has not been up.
normalShutDown - This path has gone down due to normal call
termination.
insufficientTxLcOrBandwidth - At present there is either no
available bandwidth or logical channel numbers available on one or
more of the trunks for this path in the transmit direction.
insufficientRxLcOrBandwidth - At present there is either no
available bandwidth or logical channel numbers available on one or
more of the trunks for this path in the receive direction.
trunkFailure- A trunk on the path has failed or has gone down due
to a provisioning change of a critical attribute.
trunkCardFailure- A trunk FP card has failed along the path.
accessCardFailure- The FP on which the peer access service was
running has failed.
operatorForced- The path has terminated due to the operator
locking a trunk along the path.
lostLcnClash- The path has terminated because the PA's at both
ends of an intermediate trunk have allocated the same LC to
different calls. When this happens both calls must go down and then
try to come up again a fraction of a second later (effectively
ensuring that they will now be assigned different LC's). It is normal
to get the odd clash especially when the PA's usedLC is
approaching the PA's maxLC.
networkCongestion - The path has failed due to control information
being lost and not recoverable.
trunkNotFound - Occurs on a manual path usually. Check for
trunks not up or names provisioned incorrectly.
farEndNotFound - The far end is not provisioned or is not up.
Check remote Name.
wrongModuleReached - This may occur on a manual path. Check
provisioning for correct trunk and service names. For a normal
path, the network Topology may be changing check remoteName.
farEndBusy - The far end has been reached but it is busy. Check
remoteName and remote end provisioning.
callLoopedBack - This LCo is provisioned to call itself. Re-
provision since this is invalid.
unknownReason - The failure was not resolved.
farEndNotReady - The remote end was reached but the connection
was refused due to the remote end not being enabled.
remoteNameMismatch - The remote end has alarmed and rejected
this setup due to remoteName provisioning.
serviceTypeMismatch - The remote Service Type does not match
this service type. Check provisioning.
reconnectFromFarEnd - The remote end re-established this
connection. Check the remote end lastTearDownReason to
determine the real reason.
bumped - Another call bumped this path from a trunk to get
bandwidth (or an LC) which it required to come up. This other path
had a higher setupPriority than this path's holdingPriority hence it
was allowed to steal the bandwidth (or LC) from this path.
optimized - This call has been rerouted due to the optimization
feature. The call is still active this just indicates why the path
changed.
trunkOrFarEndDidNotSupportMode - This call was unable to
complete because a mode required by the service was not supported
by one of the trunks the route went through or by the far end service
it connected to. Currently the only mode that this applies to is the
map/mux mode on TRUNK PA ATM component. Map mode was
required by the application (CES/FrAtm etc.) but was not available
on the TRUNK PA ATM component through which the call was
routed or the far end CES/FrAtm component did not specify the
same mode.
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]
htdsLCoLastTearDownReason OBJECT-TYPE SYNTAX INTEGER { none(0), normalShutDown(1), insufficientTxLcOrBandwidth(2), insufficientRxLcOrBandwidth(3), trunkFailure(4), trunkCardFailure(5), operatorForced(6), lostLcnClash(7), networkCongestion(8), trunkNotFound(9), farEndNotFound(10), wrongModuleReached(11), farEndBusy(12), callLoopedBack(13), unknownReason(14), farEndNotReady(15), remoteNameMismatch(16), serviceTypeMismatch(17), reconnectFromFarEnd(18), bumped(19), accessCardFailure(20), optimized(21), overrideRemoteName(22), trunkOrFarEndDidNotSupportMode(23) } ACCESS read-only STATUS mandatory DESCRIPTION "This attribute reflects the last tear down reason for a connection (LCo). In many cases this displays the reason for a momentary service interruption. This attribute applies to the last path failure only. If a path is no longer up, this may give an indication to the reason that the path has failed. In many cases an alarm will also be generated with more specific information. The following is a brief description of the reasons: none - This path has no information for the teardown this is typical of a path provisioned with no remoteName that has not been up. normalShutDown - This path has gone down due to normal call termination. insufficientTxLcOrBandwidth - At present there is either no available bandwidth or logical channel numbers available on one or more of the trunks for this path in the transmit direction. insufficientRxLcOrBandwidth - At present there is either no available bandwidth or logical channel numbers available on one or more of the trunks for this path in the receive direction. trunkFailure- A trunk on the path has failed or has gone down due to a provisioning change of a critical attribute. trunkCardFailure- A trunk FP card has failed along the path. accessCardFailure- The FP on which the peer access service was running has failed. operatorForced- The path has terminated due to the operator locking a trunk along the path. lostLcnClash- The path has terminated because the PA's at both ends of an intermediate trunk have allocated the same LC to different calls. When this happens both calls must go down and then try to come up again a fraction of a second later (effectively ensuring that they will now be assigned different LC's). It is normal to get the odd clash especially when the PA's usedLC is approaching the PA's maxLC. networkCongestion - The path has failed due to control information being lost and not recoverable. trunkNotFound - Occurs on a manual path usually. Check for trunks not up or names provisioned incorrectly. farEndNotFound - The far end is not provisioned or is not up. Check remote Name. wrongModuleReached - This may occur on a manual path. Check provisioning for correct trunk and service names. For a normal path, the network Topology may be changing check remoteName. farEndBusy - The far end has been reached but it is busy. Check remoteName and remote end provisioning. callLoopedBack - This LCo is provisioned to call itself. Re- provision since this is invalid. unknownReason - The failure was not resolved. farEndNotReady - The remote end was reached but the connection was refused due to the remote end not being enabled. remoteNameMismatch - The remote end has alarmed and rejected this setup due to remoteName provisioning. serviceTypeMismatch - The remote Service Type does not match this service type. Check provisioning. reconnectFromFarEnd - The remote end re-established this connection. Check the remote end lastTearDownReason to determine the real reason. bumped - Another call bumped this path from a trunk to get bandwidth (or an LC) which it required to come up. This other path had a higher setupPriority than this path's holdingPriority hence it was allowed to steal the bandwidth (or LC) from this path. optimized - This call has been rerouted due to the optimization feature. The call is still active this just indicates why the path changed. trunkOrFarEndDidNotSupportMode - This call was unable to complete because a mode required by the service was not supported by one of the trunks the route went through or by the far end service it connected to. Currently the only mode that this applies to is the map/mux mode on TRUNK PA ATM component. Map mode was required by the application (CES/FrAtm etc.) but was not available on the TRUNK PA ATM component through which the call was routed or the far end CES/FrAtm component did not specify the same mode." DEFVAL { none } ::= { htdsLCoPathDataEntry 21 }
htdsLCoLastTearDownReason OBJECT-TYPE SYNTAX INTEGER { none(0), normalShutDown(1), insufficientTxLcOrBandwidth(2), insufficientRxLcOrBandwidth(3), trunkFailure(4), trunkCardFailure(5), operatorForced(6), lostLcnClash(7), networkCongestion(8), trunkNotFound(9), farEndNotFound(10), wrongModuleReached(11), farEndBusy(12), callLoopedBack(13), unknownReason(14), farEndNotReady(15), remoteNameMismatch(16), serviceTypeMismatch(17), reconnectFromFarEnd(18), bumped(19), accessCardFailure(20), optimized(21), overrideRemoteName(22), trunkOrFarEndDidNotSupportMode(23) } ACCESS read-only STATUS mandatory DESCRIPTION "This attribute reflects the last tear down reason for a connection (LCo). In many cases this displays the reason for a momentary service interruption. This attribute applies to the last path failure only. If a path is no longer up, this may give an indication to the reason that the path has failed. In many cases an alarm will also be generated with more specific information. The following is a brief description of the reasons: none - This path has no information for the teardown this is typical of a path provisioned with no remoteName that has not been up. normalShutDown - This path has gone down due to normal call termination. insufficientTxLcOrBandwidth - At present there is either no available bandwidth or logical channel numbers available on one or more of the trunks for this path in the transmit direction. insufficientRxLcOrBandwidth - At present there is either no available bandwidth or logical channel numbers available on one or more of the trunks for this path in the receive direction. trunkFailure- A trunk on the path has failed or has gone down due to a provisioning change of a critical attribute. trunkCardFailure- A trunk FP card has failed along the path. accessCardFailure- The FP on which the peer access service was running has failed. operatorForced- The path has terminated due to the operator locking a trunk along the path. lostLcnClash- The path has terminated because the PA's at both ends of an intermediate trunk have allocated the same LC to different calls. When this happens both calls must go down and then try to come up again a fraction of a second later (effectively ensuring that they will now be assigned different LC's). It is normal to get the odd clash especially when the PA's usedLC is approaching the PA's maxLC. networkCongestion - The path has failed due to control information being lost and not recoverable. trunkNotFound - Occurs on a manual path usually. Check for trunks not up or names provisioned incorrectly. farEndNotFound - The far end is not provisioned or is not up. Check remote Name. wrongModuleReached - This may occur on a manual path. Check provisioning for correct trunk and service names. For a normal path, the network Topology may be changing check remoteName. farEndBusy - The far end has been reached but it is busy. Check remoteName and remote end provisioning. callLoopedBack - This LCo is provisioned to call itself. Re- provision since this is invalid. unknownReason - The failure was not resolved. farEndNotReady - The remote end was reached but the connection was refused due to the remote end not being enabled. remoteNameMismatch - The remote end has alarmed and rejected this setup due to remoteName provisioning. serviceTypeMismatch - The remote Service Type does not match this service type. Check provisioning. reconnectFromFarEnd - The remote end re-established this connection. Check the remote end lastTearDownReason to determine the real reason. bumped - Another call bumped this path from a trunk to get bandwidth (or an LC) which it required to come up. This other path had a higher setupPriority than this path's holdingPriority hence it was allowed to steal the bandwidth (or LC) from this path. optimized - This call has been rerouted due to the optimization feature. The call is still active this just indicates why the path changed. trunkOrFarEndDidNotSupportMode - This call was unable to complete because a mode required by the service was not supported by one of the trunks the route went through or by the far end service it connected to. Currently the only mode that this applies to is the map/mux mode on TRUNK PA ATM component. Map mode was required by the application (CES/FrAtm etc.) but was not available on the TRUNK PA ATM component through which the call was routed or the far end CES/FrAtm component did not specify the same mode." DEFVAL { none } ::= { htdsLCoPathDataEntry 21 }
| 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.17 | htdsLCoPathType | 0 | 0 | htdsLCoPathtype |
| 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.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. |