OID reference

qtechMplsPsType

1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.3

Description

The MPLS PS architecture can be a 1+1 type, a 1:1 type, a shared mesh type, or a packet 1+1 type. 1. In the 1+1 architecture type, a protection LSP is dedicated to each working LSP with the working LSP bridged onto the protection LSP at the source of the protection domain. 2. In the 1:1 architecture type, a protection…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1 (qtechMplsPsEntry)
Node code
3
Node name
qtechMplsPsType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.3
URN notation
urn:oid:1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 27514 1 1 10 2 93 1 3 1 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) qtech(27514) products(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) qtech(27514) dataCom(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) qtech(27514) products(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) qtech(27514) dataCom(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) qtech(27514) products(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) qtech(27514) dataCom(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) qtech(27514) products(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) qtech(27514) dataCom(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) qtech(27514) products(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) qtech(27514) dataCom(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) qtech(27514) products(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) qtech(27514) dataCom(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) qtech(27514) products(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) qtech(27514) dataCom(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) qtech(27514) products(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) qtech(27514) dataCom(1) switch(1) switchMib(10) qtechMgmt(2) qtechMplsOam(93) qtechMplsOamPs(1) qtechMplsPsObjects(3) qtechMplsPsTable(1) qtechMplsPsEntry(1) qtechMplsPsType(3)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/27514/1/1/10/2/93/1/3/1/1/3
  • /ISO/Identified-Organization/6/1/4/1/27514/1/1/10/2/93/1/3/1/1/3
  • /ISO/3/6/1/4/1/27514/1/1/10/2/93/1/3/1/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/27514/products/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/enterprise/27514/dataCom/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/enterprise/qtech/products/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/enterprise/qtech/dataCom/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/enterprises/27514/products/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/enterprises/27514/dataCom/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/enterprises/qtech/products/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/enterprises/qtech/dataCom/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/27514/products/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/27514/dataCom/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/qtech/products/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/qtech/dataCom/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/vendor-objects/27514/products/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/vendor-objects/27514/dataCom/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/vendor-objects/qtech/products/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • /iso/identified-organization/dod/internet/private/vendor-objects/qtech/dataCom/switch/switchMib/qtechMgmt/qtechMplsOam/qtechMplsOamPs/qtechMplsPsObjects/qtechMplsPsTable/qtechMplsPsEntry/qtechMplsPsType
  • Additional combinations skipped.

SNMP properties

Value type
Integer32
Maximum access defined by MIB
read-only
Status in MIB
current
Allowed ranges
1–4

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: qtechMplsPsIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.3

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

qtechMplsPsType OBJECT-TYPE
            SYNTAX Integer32 (1..4)
            MAX-ACCESS read-only
            STATUS current
            DESCRIPTION
                "The MPLS PS architecture can be a 1+1 type, a 1:1 type, a shared mesh type,
				or a packet 1+1 type.
				1. In the 1+1 architecture type, a protection LSP is dedicated to each working
				   LSP with the working LSP bridged onto the protection LSP at the source of
				   the protection domain.
				2. In the 1:1 architecture type, a protection LSP is dedicated to each working LSP.
				3. In the shared mesh architecture type, possible sharing of protection capacity
				   between disjoint link, node, or SRG failures in the network is achieved while
				   guaranteeing recovery from a single failure. For each link in the network, it
				   keeps track of all the working paths whose traffic will be switched onto it
				   after a given failure. By keeping track of this, it only needs to reserve the
				   maximum of the protection capacity required to protect a single failure in the
				   network.
				4. In the packet 1+1 architecture type, the traffic is transmitted simultaneously
				   onto two possibly disjoint routed LSPs to the sink of the protection domain. 
				   Each pair of duplicate transmitted packets is assigned the same identifier(sequence number)
				   but distinct from the other pairs of duplicate packets. At the sink of the 
				   protection domain, packet level selection mechanism is employed to select one
				   of the two possibly received copies of each packet. The following list provides
				   principles for MPLS protection architectures and mechanisms development.
				1: 1:1 protection switching;
				2: 1+1 protection switching;
				3: shared mesh protection swiching;
				4: packet 1+1 protection switching."
            ::= { qtechMplsPsEntry 3 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The MPLS PS architecture can be a 1+1 type, a 1:1 type, a shared mesh type, or a packet 1+1 type. 1. In the 1+1 architecture type, a protection LSP is dedicated to each working LSP with the working LSP bridged onto the protection LSP at the source of the protection domain. 2. In the 1:1 architecture type, a protection LSP is dedicated to each working LSP. 3. In the shared mesh architecture type, possible sharing of protection capacity between disjoint link, node, or SRG failures in the network is achieved while guaranteeing recovery from a single failure. For each link in the network, it keeps track of all the working paths whose traffic will be switched onto it after a given failure. By keeping track of this, it only needs to reserve the maximum of the protection capacity required to protect a single failure in the network. 4. In the packet 1+1 architecture type, the traffic is transmitted simultaneously onto two possibly disjoint routed LSPs to the sink of the protection domain. Each pair of duplicate transmitted packets is assigned the same identifier(sequence number) but distinct from the other pairs of duplicate packets. At the sink of the protection domain, packet level selection mechanism is employed to select one of the two possibly received copies of each packet. The following list provides principles for MPLS protection architectures and mechanisms development. 1: 1:1 protection switching; 2: 1+1 protection switching; 3: shared mesh protection swiching; 4: packet 1+1 protection switching.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; representative source files are shown for each definition.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

qtechMplsPsType · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: qtechMplsPsType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "qtechMplsPsType",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "4",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The MPLS PS architecture can be a 1+1 type, a 1:1 type, a shared mesh type, or a packet 1+1 type. 1. In the 1+1 architecture type, a protection LSP is dedicated to each working LSP with the working LSP bridged onto the protection LSP at the source of the protection domain. 2. In the 1:1 architecture type, a protection LSP is dedicated to each working LSP. 3. In the shared mesh architecture type, possible sharing of protection capacity between disjoint link, node, or SRG failures in the network is achieved while guaranteeing recovery from a single failure. For each link in the network, it keeps track of all the working paths whose traffic will be switched onto it after a given failure. By keeping track of this, it only needs to reserve the maximum of the protection capacity required to protect a single failure in the network. 4. In the packet 1+1 architecture type, the traffic is transmitted simultaneously onto two possibly disjoint routed LSPs to the sink of the protection domain. Each pair of duplicate transmitted packets is assigned the same identifier(sequence number) but distinct from the other pairs of duplicate packets. At the sink of the protection domain, packet level selection mechanism is employed to select one of the two possibly received copies of each packet. The following list provides principles for MPLS protection architectures and mechanisms development. 1: 1:1 protection switching; 2: 1+1 protection switching; 3: shared mesh protection swiching; 4: packet 1+1 protection switching.\"",
    "::=",
    "{",
    "qtechMplsPsEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The MPLS PS architecture can be a 1+1 type, a 1:1 type, a shared mesh type, or a packet 1+1 type. 1. In the 1+1 architecture type, a protection LSP is dedicated to each working LSP with the working LSP bridged onto the protection LSP at the source of the protection domain. 2. In the 1:1 architecture type, a protection LSP is dedicated to each working LSP. 3. In the shared mesh architecture type, possible sharing of protection capacity between disjoint link, node, or SRG failures in the network is achieved while guaranteeing recovery from a single failure. For each link in the network, it keeps track of all the working paths whose traffic will be switched onto it after a given failure. By keeping track of this, it only needs to reserve the maximum of the protection capacity required to protect a single failure in the network. 4. In the packet 1+1 architecture type, the traffic is transmitted simultaneously onto two possibly disjoint routed LSPs to the sink of the protection domain. Each pair of duplicate transmitted packets is assigned the same identifier(sequence number) but distinct from the other pairs of duplicate packets. At the sink of the protection domain, packet level selection mechanism is employed to select one of the two possibly received copies of each packet. The following list provides principles for MPLS protection architectures and mechanisms development. 1: 1:1 protection switching; 2: 1+1 protection switching; 3: shared mesh protection swiching; 4: packet 1+1 protection switching."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.27514)

Basil Budko

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.1 qtechMplsPsIndex00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.2 qtechMplsPsGroupName00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.4 qtechMplsPsWorkLspName00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.5 qtechMplsPsWorkLspId00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.6 qtechMplsPsProtectLspName00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.7 qtechMplsPsProtectLspId00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.8 qtechMplsPsRevertiveMode00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.9 qtechMplsPsWTR00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.10 qtechMplsPsHoldOff00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.11 qtechMplsPsSwitchCondition00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.12 qtechMplsPsWorkLspState00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.13 qtechMplsPsProtLspState00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.14 qtechMplsPsSwitchResult00
1.3.6.1.4.1.27514.1.1.10.2.93.1.3.1.1.15 qtechMplsPsRowStatus00