Reference record for OID 1.3.6.1.4.1.562.2.4.1.80.3.207



parent
1.3.6.1.4.1.562.2.4.1.80.3 (vsPlc)
node code
207
node name
vsPlcMpathTable
dot oid
1.3.6.1.4.1.562.2.4.1.80.3.207
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nortel(562) magellan(2) passport(4) components(1) vs(80) vsPlc(3) vsPlcMpathTable(207)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) northernTelecom(562) magellan(2) passport(4) components(1) vs(80) vsPlc(3) vsPlcMpathTable(207)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) northernTelecom(562) magellan(2) passport(4) components(1) vs(80) vsPlc(3) vsPlcMpathTable(207)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nt(562) magellan(2) passport(4) components(1) vs(80) vsPlc(3) vsPlcMpathTable(207)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nortel(562) magellan(2) passport(4) components(1) vs(80) vsPlc(3) vsPlcMpathTable(207)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) northernTelecom(562) magellan(2) passport(4) components(1) vs(80) vsPlc(3) vsPlcMpathTable(207)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) northernTelecom(562) magellan(2) passport(4) components(1) vs(80) vsPlc(3) vsPlcMpathTable(207)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nt(562) magellan(2) passport(4) components(1) vs(80) vsPlc(3) vsPlcMpathTable(207)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/nortel/magellan/passport/components/vs/vsPlc/vsPlcMpathTable
  • /iso/identified-organization/dod/internet/private/enterprise/northernTelecom/magellan/passport/components/vs/vsPlc/vsPlcMpathTable
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/northernTelecom/magellan/passport/components/vs/vsPlc/vsPlcMpathTable
  • /iso/org/dod/internet/private/enterprise/nt/magellan/passport/components/vs/vsPlc/vsPlcMpathTable
  • /iso/org/dod/internet/private/enterprises/nortel/magellan/passport/components/vs/vsPlc/vsPlcMpathTable
  • /iso/org/dod/internet/private/enterprises/northernTelecom/magellan/passport/components/vs/vsPlc/vsPlcMpathTable
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/northernTelecom/magellan/passport/components/vs/vsPlc/vsPlcMpathTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/nt/magellan/passport/components/vs/vsPlc/vsPlcMpathTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/562/2/4/1/80/3/207

    Description by oid_info

    vsPlcMpathtable
    View at oid-info.com

    Description by mibdepot

    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 nortelPP-voiceV1_BG00S4C.mib.txt
    Company: None
    Module: Nortel-Magellan-Passport-VoiceMIB

    Description by circitor

    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-Magellan-Passport-VoiceMIB.mib
    Module: Nortel-Magellan-Passport-VoiceMIB

    Information by oid_info

    Vendor: Northern Telecom, Ltd.
    Module: Nortel-Magellan-Passport-VoiceMIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    vsPlcMpathTable OBJECT-TYPE SYNTAX SEQUENCE OF VsPlcMpathEntry 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." ::= { vsPlc 207 }

    Information by circitor

    vsPlcMpathTable OBJECT-TYPE SYNTAX SEQUENCE OF VsPlcMpathEntry 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." ::= { vsPlc 207 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.562)

    Sharon Chisholm

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.562)

    Mike Bobbitt

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.562.2.4.1.80.3.207.1 vsPlcMpathEntry 2 2 An entry in the vsPlcMpathTable.

    Brothers (2)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.562.2.4.1.80.3.1 vsPlcRowStatusTable 1 5 This entry controls the addition and deletion of
    vsPlc components.
    1.3.6.1.4.1.562.2.4.1.80.3.10 vsPlcProvTable 1 19 This group contains all provisionable attributes for a permanent
    logical connection. Note that all of the attributes are valid a…