OID reference

fsErpsRingMonitorMechanism

1.3.6.1.4.1.29601.2.40.2.1.1.10

Description

This object indicates the type of monitoring mechanism used for detecting faults of the ring link. Currently 'cfm' is supported as monitoring mechanism. For 'cfm' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable. For su…

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

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

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

SNMP properties

Value type
RingMonitorMechanismType
Maximum access defined by MIB
read-only, read-write
Status in MIB
current
Default value
cfm

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — Belden, GarrettCom and Hirschmann IT official standalone MIBs

Value type
RingMonitorMechanismType
Maximum access defined by MIB
read-only
Status in MIB
current

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

Value type
RingMonitorMechanismType
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
cfm

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

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

fsErpsRingMonitorMechanism · current

fsErpsRingMonitorMechanism OBJECT-TYPE
   SYNTAX      RingMonitorMechanismType
   MAX-ACCESS  read-only
   STATUS      current
   DESCRIPTION
      "This object indicates the type of monitoring mechanism used for 
       detecting faults of the ring link. 

       Currently 'cfm' is supported as monitoring mechanism. For 'cfm' 
       monitoring mechanism to monitor the ring ports, appropriate down 
       MEPs on the R-APS VLAN of the ring has to be provisioned through 
       fsErpsRingCfmTable.
       For sub-rings, a Up & Down MEP on the sub-ring R-APS VLAN needs to
       be installed on fsErpsRingPort1 of the interconnecting nodes using
       the same fsErpsRingCfmTable."
   ::= { fsErpsRingEntry 10 }

fsErpsRingMonitorMechanism · current

fsErpsRingMonitorMechanism OBJECT-TYPE
   SYNTAX      RingMonitorMechanismType
   MAX-ACCESS  read-write
   STATUS      current
   DESCRIPTION
      "This object indicates the type of monitoring mechanism used for 
       detecting faults of the ring link. 

       Currently 'cfm' and 'MPLS OAM' is supported as monitoring mechanism. 
       For 'cfm' monitoring mechanism to monitor the ring ports, appropriate 
       down MEPs on the R-APS VLAN of the ring has to be provisioned through 
       fsErpsRingCfmTable.
       For sub-rings, a Up & Down MEP on the sub-ring R-APS VLAN needs to
       be installed on fsErpsRingPort1 of the interconnecting nodes using
       the same fsErpsRingCfmTable.
       
       For 'MPLS OAM' monitoring mechanism to monitor the ring ports, appropriate
       down MEPs on the R-APS VLAN of the ring has to be provisioned through
       fsErpsRingCfmTable and pseudo-wire identifiers need to be provisioned through
       fsErpsRingMplsTable.
       For sub-rings, Down MEP on the sub-ring R-APS VLAN needs to be installed on
       fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable
       and pseudo-wire identifier of the monitoring pseudo-wire of fsErpsRingPort1 of 
       interconnecting nodes needs to be provisioned"
   
   DEFVAL { cfm } 
   ::= { fsErpsRingEntry 10 }

Meaning

Descriptions

2 unique

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

Description 1

This object indicates the type of monitoring mechanism used for detecting faults of the ring link. Currently 'cfm' is supported as monitoring mechanism. For 'cfm' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable. For sub-rings, a Up & Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Description 2

This object indicates the type of monitoring mechanism used for detecting faults of the ring link. Currently 'cfm' and 'MPLS OAM' is supported as monitoring mechanism. For 'cfm' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable. For sub-rings, a Up & Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable. For 'MPLS OAM' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable and pseudo-wire identifiers need to be provisioned through fsErpsRingMplsTable. For sub-rings, Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable and pseudo-wire identifier of the monitoring pseudo-wire of fsErpsRingPort1 of interconnecting nodes needs to be provisioned

Sources for this description

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

See 1 matching source record

Evidence

Source records

2 records

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

Records for description 1Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 1

fsErpsRingMonitorMechanism · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: fsErpsRingMonitorMechanism

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsErpsRingMonitorMechanism",
    "OBJECT-TYPE",
    "SYNTAX",
    "RingMonitorMechanismType",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object indicates the type of monitoring mechanism used for detecting faults of the ring link. Currently 'cfm' is supported as monitoring mechanism. For 'cfm' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable. For sub-rings, a Up & Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable.\"",
    "::=",
    "{",
    "fsErpsRingEntry",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RingMonitorMechanismType"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object indicates the type of monitoring mechanism used for detecting faults of the ring link. Currently 'cfm' is supported as monitoring mechanism. For 'cfm' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable. For sub-rings, a Up & Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

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

Status in source: current.

Names: fsErpsRingMonitorMechanism

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsErpsRingMonitorMechanism",
    "OBJECT-TYPE",
    "SYNTAX",
    "RingMonitorMechanismType",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object indicates the type of monitoring mechanism used for detecting faults of the ring link. Currently 'cfm' and 'MPLS OAM' is supported as monitoring mechanism. For 'cfm' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable. For sub-rings, a Up & Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable. For 'MPLS OAM' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable and pseudo-wire identifiers need to be provisioned through fsErpsRingMplsTable. For sub-rings, Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable and pseudo-wire identifier of the monitoring pseudo-wire of fsErpsRingPort1 of interconnecting nodes needs to be provisioned\"",
    "DEFVAL",
    "{",
    "cfm",
    "}",
    "::=",
    "{",
    "fsErpsRingEntry",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RingMonitorMechanismType"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object indicates the type of monitoring mechanism used for detecting faults of the ring link. Currently 'cfm' and 'MPLS OAM' is supported as monitoring mechanism. For 'cfm' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable. For sub-rings, a Up & Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable. For 'MPLS OAM' monitoring mechanism to monitor the ring ports, appropriate down MEPs on the R-APS VLAN of the ring has to be provisioned through fsErpsRingCfmTable and pseudo-wire identifiers need to be provisioned through fsErpsRingMplsTable. For sub-rings, Down MEP on the sub-ring R-APS VLAN needs to be installed on fsErpsRingPort1 of the interconnecting nodes using the same fsErpsRingCfmTable and pseudo-wire identifier of the monitoring pseudo-wire of fsErpsRingPort1 of interconnecting nodes needs to be provisioned"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "cfm"
    ]
  ]
}

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