OID reference

fsErpsRingVlanId

1.3.6.1.4.1.29601.2.40.2.1.1.2

Description

This object identifies the dedicated VLAN Id used by a ring for its R-APS messages communication. It is recommended that the, * R-APS VLANs should be used only for ring R-APS message communication and should not be used for data switching and management purposes. It is recommended that R-APS VLAN is created first thro…

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
2
Node name
fsErpsRingVlanId
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.29601.2.40.2.1.1.2
URN notation
urn:oid:1.3.6.1.4.1.29601.2.40.2.1.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {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) fsErpsRingVlanId(2)}
  • {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) fsErpsRingVlanId(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsErpsMIB(40) fsErpsRing(2) fsErpsRingTable(1) fsErpsRingEntry(1) fsErpsRingVlanId(2)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/40/2/1/1/2
  • /ISO/Identified-Organization/6/1/4/1/29601/2/40/2/1/1/2
  • /ISO/3/6/1/4/1/29601/2/40/2/1/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/org/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/org/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/org/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/fsErpsMIB/fsErpsRing/fsErpsRingTable/fsErpsRingEntry/fsErpsRingVlanId

SNMP properties

Value type
VlanId
Maximum access defined by MIB
read-write
Status in MIB
current

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.

fsErpsRingVlanId OBJECT-TYPE
    SYNTAX      VlanId
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
      "This object identifies the dedicated VLAN Id used by a ring for its 
       R-APS messages communication.  

       It is recommended that the,
         * R-APS VLANs should be used only for ring R-APS message 
           communication  and should not be used for data switching and 
           management purposes.

       It is recommended that R-APS VLAN is created first through the VLAN 
       configuration before making the ring entry active, in order to avoid 
       any loss of R-APS PDU Tx/Rx. 
 
       It is not recommended to use the same R-APS VLAN ID for more than 
       one ring."
   ::= { fsErpsRingEntry 2 }

Meaning

Descriptions

1 unique

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

This object identifies the dedicated VLAN Id used by a ring for its R-APS messages communication. It is recommended that the, * R-APS VLANs should be used only for ring R-APS message communication and should not be used for data switching and management purposes. It is recommended that R-APS VLAN is created first through the VLAN configuration before making the ring entry active, in order to avoid any loss of R-APS PDU Tx/Rx. It is not recommended to use the same R-APS VLAN ID for more than one ring.

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

fsErpsRingVlanId · 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: fsErpsRingVlanId

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsErpsRingVlanId",
    "OBJECT-TYPE",
    "SYNTAX",
    "VlanId",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object identifies the dedicated VLAN Id used by a ring for its R-APS messages communication. It is recommended that the, * R-APS VLANs should be used only for ring R-APS message communication and should not be used for data switching and management purposes. It is recommended that R-APS VLAN is created first through the VLAN configuration before making the ring entry active, in order to avoid any loss of R-APS PDU Tx/Rx. It is not recommended to use the same R-APS VLAN ID for more than one ring.\"",
    "::=",
    "{",
    "fsErpsRingEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "VlanId"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object identifies the dedicated VLAN Id used by a ring for its R-APS messages communication. It is recommended that the, * R-APS VLANs should be used only for ring R-APS message communication and should not be used for data switching and management purposes. It is recommended that R-APS VLAN is created first through the VLAN configuration before making the ring entry active, in order to avoid any loss of R-APS PDU Tx/Rx. It is not recommended to use the same R-APS VLAN ID for more than one ring."
    ],
    null,
    null,
    null,
    null
  ]
}

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.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.18 fsErpsRingProtectionType00
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