OID reference

fsErpsRingProtectionType

1.3.6.1.4.1.29601.2.40.2.1.1.18

Description

This object specifies the type of protection being provided by this ring instance. The following two protection switching types are possible: portBased - Port Based Protection This ring applies the protection switching mechanism for all traffic that pass through its ring ports. Hence when ERP control process decides t…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.29601.2.40.2.1.1 (fsErpsRingEntry)
Node code
18
Node name
fsErpsRingProtectionType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.29601.2.40.2.1.1.18
URN notation
urn:oid:1.3.6.1.4.1.29601.2.40.2.1.1.18
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 29601 2 40 2 1 1 18}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingProtectionType(18)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/40/2/1/1/18
  • /ISO/Identified-Organization/6/1/4/1/29601/2/40/2/1/1/18
  • /ISO/3/6/1/4/1/29601/2/40/2/1/1/18
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/org/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/org/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/org/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingProtectionType

SNMP properties

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

Enumerated values

ValueName
1portBased
2serviceBased

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: fsErpsContextId, fsErpsRingId.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.29601.2.40.2.1.1.18

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.

fsErpsRingProtectionType OBJECT-TYPE
   SYNTAX      INTEGER { portBased(1), serviceBased(2) }
   MAX-ACCESS  read-write
   STATUS      current
   DESCRIPTION
      "This object specifies the type of protection being provided by this
      ring instance. The following two protection switching types are
      possible:
           portBased - Port Based Protection 
                       This ring applies the protection switching mechanism
                       for all traffic that pass through its ring ports.
                       Hence when ERP control process decides to block or
                       unblock a ring port, all data traffic that passes 
                       through that port gets affected.
           serviceBased - Service Based Protection.
                       This ring applies the protection switching mechanism
                       only for the set of vlans mapped to this ring instance.
                       Hence when ERP control process decides to block or
                       unblock a ring port, only the data traffic of the vlans
                       that are mapped to this ring instance and that passes 
                       through that port gets affected.
      
      All ring nodes in a single ring instance must be configured with the
      same protection type.

      In a single virtual context one ring can run in port based protection
      mode and another ring can run in service based protection mode. 

      It is not recommended to configure a port as ring port in a port based
      ring instance as well as in a service based  ring instance.

      It is not recommended to configure a port as ring port in multiple port 
      based ring instance.

      The ring protection type can be modified only when the row status of 
      the ring entry in not in service."

   DEFVAL { portBased }
   ::= { fsErpsRingEntry 18 }

Meaning

Descriptions

1 unique

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

This object specifies the type of protection being provided by this ring instance. The following two protection switching types are possible: portBased - Port Based Protection This ring applies the protection switching mechanism for all traffic that pass through its ring ports. Hence when ERP control process decides to block or unblock a ring port, all data traffic that passes through that port gets affected. serviceBased - Service Based Protection. This ring applies the protection switching mechanism only for the set of vlans mapped to this ring instance. Hence when ERP control process decides to block or unblock a ring port, only the data traffic of the vlans that are mapped to this ring instance and that passes through that port gets affected. All ring nodes in a single ring instance must be configured with the same protection type. In a single virtual context one ring can run in port based protection mode and another ring can run in service based protection mode. It is not recommended to configure a port as ring port in a port based ring instance as well as in a service based ring instance. It is not recommended to configure a port as ring port in multiple port based ring instance. The ring protection type can be modified only when the row status of the ring entry in not in service.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBs

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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 2 sources

Description 1

fsErpsRingProtectionType · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs2 sources

Status in source: current.

Names: fsErpsRingProtectionType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsErpsRingProtectionType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "portBased",
    "(",
    "1",
    ")",
    ",",
    "serviceBased",
    "(",
    "2",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object specifies the type of protection being provided by this ring instance. The following two protection switching types are possible: portBased - Port Based Protection This ring applies the protection switching mechanism for all traffic that pass through its ring ports. Hence when ERP control process decides to block or unblock a ring port, all data traffic that passes through that port gets affected. serviceBased - Service Based Protection. This ring applies the protection switching mechanism only for the set of vlans mapped to this ring instance. Hence when ERP control process decides to block or unblock a ring port, only the data traffic of the vlans that are mapped to this ring instance and that passes through that port gets affected. All ring nodes in a single ring instance must be configured with the same protection type. In a single virtual context one ring can run in port based protection mode and another ring can run in service based protection mode. It is not recommended to configure a port as ring port in a port based ring instance as well as in a service based ring instance. It is not recommended to configure a port as ring port in multiple port based ring instance. The ring protection type can be modified only when the row status of the ring entry in not in service.\"",
    "DEFVAL",
    "{",
    "portBased",
    "}",
    "::=",
    "{",
    "fsErpsRingEntry",
    "18",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "portBased",
            1
          ],
          [
            "serviceBased",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object specifies the type of protection being provided by this ring instance. The following two protection switching types are possible: portBased - Port Based Protection This ring applies the protection switching mechanism for all traffic that pass through its ring ports. Hence when ERP control process decides to block or unblock a ring port, all data traffic that passes through that port gets affected. serviceBased - Service Based Protection. This ring applies the protection switching mechanism only for the set of vlans mapped to this ring instance. Hence when ERP control process decides to block or unblock a ring port, only the data traffic of the vlans that are mapped to this ring instance and that passes through that port gets affected. All ring nodes in a single ring instance must be configured with the same protection type. In a single virtual context one ring can run in port based protection mode and another ring can run in service based protection mode. It is not recommended to configure a port as ring port in a port based ring instance as well as in a service based ring instance. It is not recommended to configure a port as ring port in multiple port based ring instance. The ring protection type can be modified only when the row status of the ring entry in not in service."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "portBased"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Siblings (29)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.40.2.1.1.1 fsErpsRingId00
1.3.6.1.4.1.29601.2.40.2.1.1.2 fsErpsRingVlanId00
1.3.6.1.4.1.29601.2.40.2.1.1.3 fsErpsRingName00
1.3.6.1.4.1.29601.2.40.2.1.1.4 fsErpsRingPort100
1.3.6.1.4.1.29601.2.40.2.1.1.5 fsErpsRingPort200
1.3.6.1.4.1.29601.2.40.2.1.1.6 fsErpsRingRplPort00
1.3.6.1.4.1.29601.2.40.2.1.1.7 fsErpsRingPortBlockingOnVcRecovery00
1.3.6.1.4.1.29601.2.40.2.1.1.8 fsErpsRingNodeType00
1.3.6.1.4.1.29601.2.40.2.1.1.9 fsErpsRingOperatingMode00
1.3.6.1.4.1.29601.2.40.2.1.1.10 fsErpsRingMonitorMechanism00
1.3.6.1.4.1.29601.2.40.2.1.1.11 fsErpsRingPort1Status00
1.3.6.1.4.1.29601.2.40.2.1.1.12 fsErpsRingPort2Status00
1.3.6.1.4.1.29601.2.40.2.1.1.13 fsErpsRingSemState00
1.3.6.1.4.1.29601.2.40.2.1.1.14 fsErpsRingNodeStatus00
1.3.6.1.4.1.29601.2.40.2.1.1.15 fsErpsRingRowStatus00
1.3.6.1.4.1.29601.2.40.2.1.1.16 fsErpsRingMacId00
1.3.6.1.4.1.29601.2.40.2.1.1.17 fsErpsRingProtectedVlanGroupId00
1.3.6.1.4.1.29601.2.40.2.1.1.19 fsErpsRingRAPSCompatibleVersion00
1.3.6.1.4.1.29601.2.40.2.1.1.20 fsErpsRingRplNeighbourPort00
1.3.6.1.4.1.29601.2.40.2.1.1.21 fsErpsRingRAPSSubRingWithoutVC00
1.3.6.1.4.1.29601.2.40.2.1.1.22 fsErpsRingRplNextNeighbourPort00
1.3.6.1.4.1.29601.2.40.2.1.1.23 fsErpsRingPort1NodeID00
1.3.6.1.4.1.29601.2.40.2.1.1.24 fsErpsRingPort2NodeID00
1.3.6.1.4.1.29601.2.40.2.1.1.25 fsErpsRingPort1BPRBitVal00
1.3.6.1.4.1.29601.2.40.2.1.1.26 fsErpsRingPort2BPRBitVal00
1.3.6.1.4.1.29601.2.40.2.1.1.27 fsErpsRingProtectedVlanGroupList00
1.3.6.1.4.1.29601.2.40.2.1.1.28 fsErpsRingServiceType00
1.3.6.1.4.1.29601.2.40.2.1.1.29 fsErpsRingPort1SubPortList00
1.3.6.1.4.1.29601.2.40.2.1.1.30 fsErpsRingPort2SubPortList00