mscBtdsPlcMpathtable
View at oid-info.com
This attribute is optional and specifies the sequence of trunks to be
used as the route for the path, thus bypassing PORS' automatic
route selection. If the path fails the validation, no other path can be
selected1. This attribute should only be used in special cases since
the route selection algorithm is able to find and maintain the best
routes. A related path attribute, the pathType, determines if this
route will be used as a manual or forced path type.
As an example, the trunk component name for the third trunk on
node MoonBase is 'EM/MoonBase Trk/3'. Note that only the first
end of the trunk that the packet would encounter is provisioned.
These strings are case insensitive but the complete component name
must be input.
Note 1: the trunk designation must be a 3-letter form, e.g., 'trk'.
Note 2: only the outbound trunks component names are used to
provision the manualPath.
Note 3: It is recommended to have two independent routes specified
for a manual path by specifying a different manualPath
(non-symmetric) for each end. In this case, there is no way to select
which route will be used (first up wins) but if one path is torn down
due to a failure then the other manualPath may be used to reroute
the path.
Parsed from file nortelPC-bitTransparentV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-BitTransparentMIB
This attribute is optional and specifies the sequence of trunks to be
used as the route for the path, thus bypassing PORS' automatic
route selection. If the path fails the validation, no other path can be
selected1. This attribute should only be used in special cases since
the route selection algorithm is able to find and maintain the best
routes. A related path attribute, the pathType, determines if this
route will be used as a manual or forced path type.
As an example, the trunk component name for the third trunk on
node MoonBase is 'EM/MoonBase Trk/3'. Note that only the first
end of the trunk that the packet would encounter is provisioned.
These strings are case insensitive but the complete component name
must be input.
Note 1: the trunk designation must be a 3-letter form, e.g., 'trk'.
Note 2: only the outbound trunks component names are used to
provision the manualPath.
Note 3: It is recommended to have two independent routes specified
for a manual path by specifying a different manualPath
(non-symmetric) for each end. In this case, there is no way to select
which route will be used (first up wins) but if one path is torn down
due to a failure then the other manualPath may be used to reroute
the path.
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]
mscBtdsPlcMpathTable OBJECT-TYPE SYNTAX SEQUENCE OF MscBtdsPlcMpathEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This attribute is optional and specifies the sequence of trunks to be used as the route for the path, thus bypassing PORS' automatic route selection. If the path fails the validation, no other path can be selected1. This attribute should only be used in special cases since the route selection algorithm is able to find and maintain the best routes. A related path attribute, the pathType, determines if this route will be used as a manual or forced path type. As an example, the trunk component name for the third trunk on node MoonBase is 'EM/MoonBase Trk/3'. Note that only the first end of the trunk that the packet would encounter is provisioned. These strings are case insensitive but the complete component name must be input. Note 1: the trunk designation must be a 3-letter form, e.g., 'trk'. Note 2: only the outbound trunks component names are used to provision the manualPath. Note 3: It is recommended to have two independent routes specified for a manual path by specifying a different manualPath (non-symmetric) for each end. In this case, there is no way to select which route will be used (first up wins) but if one path is torn down due to a failure then the other manualPath may be used to reroute the path." ::= { mscBtdsPlc 262 }
mscBtdsPlcMpathTable OBJECT-TYPE SYNTAX SEQUENCE OF MscBtdsPlcMpathEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This attribute is optional and specifies the sequence of trunks to be used as the route for the path, thus bypassing PORS' automatic route selection. If the path fails the validation, no other path can be selected1. This attribute should only be used in special cases since the route selection algorithm is able to find and maintain the best routes. A related path attribute, the pathType, determines if this route will be used as a manual or forced path type. As an example, the trunk component name for the third trunk on node MoonBase is 'EM/MoonBase Trk/3'. Note that only the first end of the trunk that the packet would encounter is provisioned. These strings are case insensitive but the complete component name must be input. Note 1: the trunk designation must be a 3-letter form, e.g., 'trk'. Note 2: only the outbound trunks component names are used to provision the manualPath. Note 3: It is recommended to have two independent routes specified for a manual path by specifying a different manualPath (non-symmetric) for each end. In this case, there is no way to select which route will be used (first up wins) but if one path is torn down due to a failure then the other manualPath may be used to reroute the path." ::= { mscBtdsPlc 262 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.36.2.1.81.3.262.1 | mscBtdsPlcMpathEntry | 2 | 2 | An entry in the mscBtdsPlcMpathTable. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.36.2.1.81.3.1 | mscBtdsPlcRowStatusTable | 1 | 5 | This entry controls the addition and deletion of mscBtdsPlc components. |
| 1.3.6.1.4.1.562.36.2.1.81.3.10 | mscBtdsPlcProvTable | 1 | 22 | This group contains all provisionable attributes for a permanent logical connection. Note that all of the attributes are valid a… |