OID reference

sleMplsTpLpsCfgControlMode

1.3.6.1.4.1.6296.101.16.18.1.2.7

Description

The architectural mode of the Protection group. This can either be 1+1, 1:1, 1:n. 1+1 In the 1+1 protection scheme, a fully dedicated protection entity is allocated. Data traffic is copied and fed at the source to both the working and the protection entities. The traffic on the working and the protection entities is t…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6296.101.16.18.1.2 (sleMplsTpLpsCfgControl)
Node code
7
Node name
sleMplsTpLpsCfgControlMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6296.101.16.18.1.2.7
URN notation
urn:oid:1.3.6.1.4.1.6296.101.16.18.1.2.7
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6296 101 16 18 1 2 7}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleMpls(16) sleMplsTpLps(18) sleMplsTpLpsCfg(1) sleMplsTpLpsCfgControl(2) sleMplsTpLpsCfgControlMode(7)}
OID-IRI notation
  • /1/3/6/1/4/1/6296/101/16/18/1/2/7
  • /ISO/Identified-Organization/6/1/4/1/6296/101/16/18/1/2/7
  • /ISO/3/6/1/4/1/6296/101/16/18/1/2/7
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/6296/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/identified-organization/dod/internet/private/enterprise/dasan/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/identified-organization/dod/internet/private/enterprises/6296/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/identified-organization/dod/internet/private/enterprises/dasan/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/6296/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/dasan/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/6296/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/dasan/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/org/dod/internet/private/enterprise/6296/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/org/dod/internet/private/enterprise/dasan/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/org/dod/internet/private/enterprises/6296/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/org/dod/internet/private/enterprises/dasan/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/org/dod/internet/private/ldap-enterprise/6296/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/org/dod/internet/private/ldap-enterprise/dasan/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/org/dod/internet/private/vendor-objects/6296/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • /iso/org/dod/internet/private/vendor-objects/dasan/sleMgmt/sleMpls/sleMplsTpLps/sleMplsTpLpsCfg/sleMplsTpLpsCfgControl/sleMplsTpLpsCfgControlMode
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
oneColonOne

Enumerated values

ValueName
1onePlusOne
2oneColonOne
3oneColonN

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.6296.101.16.18.1.2.7.0

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.

sleMplsTpLpsCfgControlMode OBJECT-TYPE
			SYNTAX INTEGER
				{
				onePlusOne(1),
				oneColonOne(2),
				oneColonN(3)
				}
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
				"The architectural mode of the Protection group. This can
				either be 1+1, 1:1, 1:n.
				
				1+1
				
				In the 1+1 protection scheme, a fully dedicated
				protection entity is allocated. Data traffic is copied
				
				
				
				and fed at the source to both the working and the
				protection entities.  The traffic on the working and the
				protection entities is transmitted simultaneously to
				the sink of the protection domain, where selection
				between the working and protection entities is performed
				
				1:1
				
				In the 1:1 scheme, a protection path is allocated to
				protect against a defect, failure, or a degradation in a
				working path. In normal conditions, data traffic is
				transmitted over the working entity, while the
				protection entity functions in the idle state. If there
				is a defect on the working entity or a specific
				administrative request, traffic is switched to the
				protection entity.
				
				1:n
				
				In case of 1:n linear protection, one protection entity
				is allocated to protect n working entities. The protection
				entity might not have sufficient resources to protect all the
				working entities that may be affected by fault conditions at a
				specific time. In this case, in order to guaranteed
				protection, the protection entity should support enough
				capacity and bandwidth to protect any of the n working
				entities."
			DEFVAL { oneColonOne }
			::= { sleMplsTpLpsCfgControl 7 }

Meaning

Descriptions

1 unique

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

The architectural mode of the Protection group. This can either be 1+1, 1:1, 1:n. 1+1 In the 1+1 protection scheme, a fully dedicated protection entity is allocated. Data traffic is copied and fed at the source to both the working and the protection entities. The traffic on the working and the protection entities is transmitted simultaneously to the sink of the protection domain, where selection between the working and protection entities is performed 1:1 In the 1:1 scheme, a protection path is allocated to protect against a defect, failure, or a degradation in a working path. In normal conditions, data traffic is transmitted over the working entity, while the protection entity functions in the idle state. If there is a defect on the working entity or a specific administrative request, traffic is switched to the protection entity. 1:n In case of 1:n linear protection, one protection entity is allocated to protect n working entities. The protection entity might not have sufficient resources to protect all the working entities that may be affected by fault conditions at a specific time. In this case, in order to guaranteed protection, the protection entity should support enough capacity and bandwidth to protect any of the n working entities.

Sources for this description

DASAN Networks MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1DASAN Networks MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

sleMplsTpLpsCfgControlMode · currentDASAN Networks MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: sleMplsTpLpsCfgControlMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "sleMplsTpLpsCfgControlMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "onePlusOne",
    "(",
    "1",
    ")",
    ",",
    "oneColonOne",
    "(",
    "2",
    ")",
    ",",
    "oneColonN",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The architectural mode of the Protection group. This can either be 1+1, 1:1, 1:n. 1+1 In the 1+1 protection scheme, a fully dedicated protection entity is allocated. Data traffic is copied and fed at the source to both the working and the protection entities. The traffic on the working and the protection entities is transmitted simultaneously to the sink of the protection domain, where selection between the working and protection entities is performed 1:1 In the 1:1 scheme, a protection path is allocated to protect against a defect, failure, or a degradation in a working path. In normal conditions, data traffic is transmitted over the working entity, while the protection entity functions in the idle state. If there is a defect on the working entity or a specific administrative request, traffic is switched to the protection entity. 1:n In case of 1:n linear protection, one protection entity is allocated to protect n working entities. The protection entity might not have sufficient resources to protect all the working entities that may be affected by fault conditions at a specific time. In this case, in order to guaranteed protection, the protection entity should support enough capacity and bandwidth to protect any of the n working entities.\"",
    "DEFVAL",
    "{",
    "oneColonOne",
    "}",
    "::=",
    "{",
    "sleMplsTpLpsCfgControl",
    "7",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "onePlusOne",
            1
          ],
          [
            "oneColonOne",
            2
          ],
          [
            "oneColonN",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The architectural mode of the Protection group. This can either be 1+1, 1:1, 1:n. 1+1 In the 1+1 protection scheme, a fully dedicated protection entity is allocated. Data traffic is copied and fed at the source to both the working and the protection entities. The traffic on the working and the protection entities is transmitted simultaneously to the sink of the protection domain, where selection between the working and protection entities is performed 1:1 In the 1:1 scheme, a protection path is allocated to protect against a defect, failure, or a degradation in a working path. In normal conditions, data traffic is transmitted over the working entity, while the protection entity functions in the idle state. If there is a defect on the working entity or a specific administrative request, traffic is switched to the protection entity. 1:n In case of 1:n linear protection, one protection entity is allocated to protect n working entities. The protection entity might not have sufficient resources to protect all the working entities that may be affected by fault conditions at a specific time. In this case, in order to guaranteed protection, the protection entity should support enough capacity and bandwidth to protect any of the n working entities."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "oneColonOne"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6296)

Lee Wonhee

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6296.101.16.18.1.2.1 sleMplsTpLpsCfgControlRequest00
1.3.6.1.4.1.6296.101.16.18.1.2.2 sleMplsTpLpsCfgControlStatus00
1.3.6.1.4.1.6296.101.16.18.1.2.3 sleMplsTpLpsCfgControlTimer00
1.3.6.1.4.1.6296.101.16.18.1.2.4 sleMplsTpLpsCfgControlTimeStamp00
1.3.6.1.4.1.6296.101.16.18.1.2.5 sleMplsTpLpsCfgControlReqResult00
1.3.6.1.4.1.6296.101.16.18.1.2.6 sleMplsTpLpsCfgControlGroupName00
1.3.6.1.4.1.6296.101.16.18.1.2.8 sleMplsTpLpsCfgControlProtectionScheme00
1.3.6.1.4.1.6296.101.16.18.1.2.9 sleMplsTpLpsCfgControlRevertive00
1.3.6.1.4.1.6296.101.16.18.1.2.10 sleMplsTpLpsCfgControlWtr00
1.3.6.1.4.1.6296.101.16.18.1.2.11 sleMplsTpLpsCfgControlContinualTxInterval00
1.3.6.1.4.1.6296.101.16.18.1.2.12 sleMplsTpLpsCfgControlRapidTxInterval00
1.3.6.1.4.1.6296.101.16.18.1.2.13 sleMplsTpLpsCfgControlswitchOver00
1.3.6.1.4.1.6296.101.16.18.1.2.14 sleMplsTpLpsCfgControlLockOut00
1.3.6.1.4.1.6296.101.16.18.1.2.15 sleMplsTpLpsCfgControlHoldOffTimer00