This attribute specifies whether the application can tolerate
momentary interruption of a path while a new path is selected. If
disconnectConnection is chosen, the application is informed as
soon as possible about a failure by disconnection. If the attribute is
set to reRoutePath, the path may attempt an immediate reroute,
provided the failure is a recoverable failure. If rerouting fails, the
application is informed of the failure.
With this option set to reRoutePath, the LCo may wait up to 30
seconds before informing the service of complete disconnection in
order to allow both ends to attempt to reconnect. Note that if PLC
components are different at both ends only the calling end is
allowed to reconnect.
All pathTypes respect this attribute. Also on a manualPath with
both ends provisioned with independent paths (at least with respect
to the failure) this option will have the desired effect that the path is
rerouted without complete disconnection at both ends.
Parsed from file nortelPC-vncsCallServerV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-VncsCallServerMIB
This attribute specifies whether the application can tolerate
momentary interruption of a path while a new path is selected. If
disconnectConnection is chosen, the application is informed as
soon as possible about a failure by disconnection. If the attribute is
set to reRoutePath, the path may attempt an immediate reroute,
provided the failure is a recoverable failure. If rerouting fails, the
application is informed of the failure.
With this option set to reRoutePath, the LCo may wait up to 30
seconds before informing the service of complete disconnection in
order to allow both ends to attempt to reconnect. Note that if PLC
components are different at both ends only the calling end is
allowed to reconnect.
All pathTypes respect this attribute. Also on a manualPath with
both ends provisioned with independent paths (at least with respect
to the failure) this option will have the desired effect that the path is
rerouted without complete disconnection at both ends.
Parsed from file Nortel-MsCarrier-MscPassport-VncsCallServerMIB.mib
Module: Nortel-MsCarrier-MscPassport-VncsCallServerMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-MsCarrier-MscPassport-VncsCallServerMIB
[Automatically extracted from oidview.com]
mscVncsVpPathFailureAction OBJECT-TYPE SYNTAX INTEGER { disconnectConnection(0), reRoutePath(1) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute specifies whether the application can tolerate momentary interruption of a path while a new path is selected. If disconnectConnection is chosen, the application is informed as soon as possible about a failure by disconnection. If the attribute is set to reRoutePath, the path may attempt an immediate reroute, provided the failure is a recoverable failure. If rerouting fails, the application is informed of the failure. With this option set to reRoutePath, the LCo may wait up to 30 seconds before informing the service of complete disconnection in order to allow both ends to attempt to reconnect. Note that if PLC components are different at both ends only the calling end is allowed to reconnect. All pathTypes respect this attribute. Also on a manualPath with both ends provisioned with independent paths (at least with respect to the failure) this option will have the desired effect that the path is rerouted without complete disconnection at both ends." DEFVAL { reRoutePath } ::= { mscVncsVpLCOpsEntry 15 }
mscVncsVpPathFailureAction OBJECT-TYPE SYNTAX INTEGER { disconnectConnection(0), reRoutePath(1) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute specifies whether the application can tolerate momentary interruption of a path while a new path is selected. If disconnectConnection is chosen, the application is informed as soon as possible about a failure by disconnection. If the attribute is set to reRoutePath, the path may attempt an immediate reroute, provided the failure is a recoverable failure. If rerouting fails, the application is informed of the failure. With this option set to reRoutePath, the LCo may wait up to 30 seconds before informing the service of complete disconnection in order to allow both ends to attempt to reconnect. Note that if PLC components are different at both ends only the calling end is allowed to reconnect. All pathTypes respect this attribute. Also on a manualPath with both ends provisioned with independent paths (at least with respect to the failure) this option will have the desired effect that the path is rerouted without complete disconnection at both ends." DEFVAL { reRoutePath } ::= { mscVncsVpLCOpsEntry 15 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.36.2.1.44.3.2.1.1 | mscVncsVpSetupPriority | 0 | 0 | This attribute specifies the priority at which a path is established. Zero is the highest priority and four is the lowest. When … |
| 1.3.6.1.4.1.562.36.2.1.44.3.2.1.2 | mscVncsVpHoldingPriority | 0 | 0 | This attribute specifies the priority that a path holds once it is established. Zero is the highest priority and four is the low… |
| 1.3.6.1.4.1.562.36.2.1.44.3.2.1.3 | mscVncsVpBumpPreference | 0 | 0 | This attribute specifies when bumping occurs in the route selection process. A connection with higher (numerically less) setupPr… |
| 1.3.6.1.4.1.562.36.2.1.44.3.2.1.6 | mscVncsVpRequiredTrafficType | 0 | 0 | This attribute specifies the type of traffic transmitted over the path. There are eight possible traffic types, and the path can… |
| 1.3.6.1.4.1.562.36.2.1.44.3.2.1.7 | mscVncsVpPermittedTrunkTypes | 0 | 0 | This attribute specifies up to eight types of trunks that can be used on the route. The terrestrial and satellite trunk types ha… |
| 1.3.6.1.4.1.562.36.2.1.44.3.2.1.8 | mscVncsVpRequiredSecurity | 0 | 0 | This attribute specifies 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.44.3.2.1.9 | mscVncsVpRequiredCustomerParm | 0 | 0 | This attribute specifies 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.44.3.2.1.10 | mscVncsVpPathAttributeToMinimize | 0 | 0 | This attribute specifies 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.44.3.2.1.11 | mscVncsVpMaximumAcceptableCost | 0 | 0 | This attribute specifies 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.44.3.2.1.12 | mscVncsVpMaximumAcceptableDelay | 0 | 0 | This attribute specifies an upper bound on the delay of a route, which is the sum of the delays of all trunks on the route. It s… |
| 1.3.6.1.4.1.562.36.2.1.44.3.2.1.13 | mscVncsVpEmissionPriority | 0 | 0 | This attribute specifies 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.44.3.2.1.14 | mscVncsVpDiscardPriority | 0 | 0 | This attribute specifies 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.44.3.2.1.16 | mscVncsVpOptimization | 0 | 0 | This attribute specifies whether this connection should attempt to optimize its path when requested by the Rtg Pors component. E… |
| 1.3.6.1.4.1.562.36.2.1.44.3.2.1.17 | mscVncsVpMaximumAcceptableGatewayCost | 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… |