rtgPorsMpathLastSetupFailureReason 1.3.6.1.4.1.562.2.4.1.40.6.8.12.1.1

This attribute indicates the reason for the most recent failure for an attempted connection using this ManualPath's route. The following is a brief description of the reasons: none - This path has no information for the teardown. 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. If a trunk in the route attribute was previously locked, or has a Trk PA subcomponent that is not in the up state , that Trunk is considered as having no available bandwidth. If the Trunk PA is in mapped mode, the inability to allocate an Atmif Vcc also results in this failure reason. 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. If a trunk in the route attribute was previously locked, or has a Trk PA subcomponent that is not in the up state , that Trunk is considered as having no available bandwidth. trunkFailure- A Trunk on the path has failed or has gone down, due to a provisioning change of a critical attribute, as the path was being established. trunkCardFailure- A Trunk FP card has failed along the path as the path was being established. accessCardFailure- The FP on which the peer access service was running has failed as the path was being established. operatorForced- The path has terminated due to the operator locking a Trunk along the path as the path was being established. lostLcnClash- The path has terminated because the Trk PA's at both ends of an intermediate trunk have allocated the same Trk 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 Trk LC's). It is normal to get the odd clash especially when the Trk PA usedLC is approaching the Trk PA maxLC. An LCN clash results in the path failing to instantiate only if the application disabled rerouting. By default rerouting is enabled for all applications. Applications can disable rerouting by using a Rtg Pors Prof/n component with pathFailureAction set to disconnectConnection. networkCongestion - The path has failed to establish due to control information being lost and not being recoverable. trunkNotFound - Check for Trunks not up or names provisioned incorrectly in route attribute . farEndNotFound - The far end is not provisioned or is not up. The called NSAP address cannot be reached through the last node in the Rtg Pors ManualPath path. farEndBusy - The far end has been reached but it is busy. Check remote end provisioning. 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. serviceTypeMismatch - The remote service type does not match this service type. Check provisioning. bumped - Another call bumped this path, as it was being established, 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. A manual path that is bumped fails to instantiate if it cannot bump another path along the same route, or if it has pathFailureAction set to disconnectConnection. 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 Trk Pa Atm component.