OID reference

fsErpsRingNodeStatus

1.3.6.1.4.1.29601.2.40.2.1.1.14

Description

A 32 bit mask giving the current status of the ring by specifying the events/status currently present. Bit 1 - Signal-failure on Ring Port 1 Bit 2 - Signal-failure on Ring Port 2 Bit 3 - Remote-signal-failure received on Ring Port 1 Bit 4 - Remote-signal-failure received on Ring Port 2 Bit 5 - Rpl-blocked Bit 6 - Wait…

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

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

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

SNMP properties

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

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

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.

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

Show 2 published definitions

fsErpsRingNodeStatus · current

fsErpsRingNodeStatus OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
      "A 32 bit mask giving the current status of the ring by specifying the
       events/status currently present.

         Bit 1  - Signal-failure on Ring Port 1
         Bit 2  - Signal-failure on Ring Port 2
         Bit 3  - Remote-signal-failure received on Ring Port 1
         Bit 4  - Remote-signal-failure received on Ring Port 2
         Bit 5  - Rpl-blocked
         Bit 6  - Wait-to-restore-timer-running
         Bit 7  - Hold-timer-running
         Bit 8  - Guard-timer-running
         Bit 9  - Periodic-timer-running
         Bit 10 - Wait-to-block-timer-running

      Value 1 of the bit signifies the presence of the event associated with
      that bit and value zero signifies the absence of that event
      For example: If a signal failure is received on Ring port 1 and R-APS(SF)
      is received on port 2, then Bit 1 and 4 will have the value as 1.

      Signal failure on a port represents Port failure indication received from 
      the monitoring entity. This does not depend on hold off timer status. 
      If signal failure is received on ring port 1 and hold-off timer is 
      started, then both Bit 1 and Bit 7 will have the value as 1.
      
      Bit 9 indicates periodic timer and Bit 10 will have the value 1 when 
      WTB timer is triggered."
   ::= { fsErpsRingEntry 14 }

fsErpsRingNodeStatus · current

fsErpsRingNodeStatus OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
      "A 32 bit mask giving the current status of the ring by specifying the
       events/status currently present.

         Bit 1  - Signal-failure on Ring Port 1
         Bit 2  - Signal-failure on Ring Port 2
         Bit 3  - Remote-signal-failure received on Ring Port 1
         Bit 4  - Remote-signal-failure received on Ring Port 2
         Bit 5  - Rpl-blocked
         Bit 6  - Wait-to-restore-timer-running
         Bit 7  - Hold-timer-running
         Bit 8  - Guard-timer-running

      Value 1 of the bit signifies the presence of the event associated with
      that bit and value zero signifies the absence of that event
      For example: If a signal failure is received on Ring port 1 and R-APS(SF)
      is received on port 2, then Bit 1 and 4 will have the value as 1.

      Signal failure on a port represents Port failure indication received from 
      the monitoring entity. This does not depend on hold off timer status. 
      If signal failure is received on ring port 1 and hold-off timer is 
      started, then both Bit 1 and Bit 7 will have the value as 1."
   ::= { fsErpsRingEntry 14 }

Meaning

Descriptions

2 unique

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

Description 1

A 32 bit mask giving the current status of the ring by specifying the events/status currently present. Bit 1 - Signal-failure on Ring Port 1 Bit 2 - Signal-failure on Ring Port 2 Bit 3 - Remote-signal-failure received on Ring Port 1 Bit 4 - Remote-signal-failure received on Ring Port 2 Bit 5 - Rpl-blocked Bit 6 - Wait-to-restore-timer-running Bit 7 - Hold-timer-running Bit 8 - Guard-timer-running Bit 9 - Periodic-timer-running Bit 10 - Wait-to-block-timer-running Value 1 of the bit signifies the presence of the event associated with that bit and value zero signifies the absence of that event For example: If a signal failure is received on Ring port 1 and R-APS(SF) is received on port 2, then Bit 1 and 4 will have the value as 1. Signal failure on a port represents Port failure indication received from the monitoring entity. This does not depend on hold off timer status. If signal failure is received on ring port 1 and hold-off timer is started, then both Bit 1 and Bit 7 will have the value as 1. Bit 9 indicates periodic timer and Bit 10 will have the value 1 when WTB timer is triggered.

Sources for this description

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

See 1 matching source record

Description 2

A 32 bit mask giving the current status of the ring by specifying the events/status currently present. Bit 1 - Signal-failure on Ring Port 1 Bit 2 - Signal-failure on Ring Port 2 Bit 3 - Remote-signal-failure received on Ring Port 1 Bit 4 - Remote-signal-failure received on Ring Port 2 Bit 5 - Rpl-blocked Bit 6 - Wait-to-restore-timer-running Bit 7 - Hold-timer-running Bit 8 - Guard-timer-running Value 1 of the bit signifies the presence of the event associated with that bit and value zero signifies the absence of that event For example: If a signal failure is received on Ring port 1 and R-APS(SF) is received on port 2, then Bit 1 and 4 will have the value as 1. Signal failure on a port represents Port failure indication received from the monitoring entity. This does not depend on hold off timer status. If signal failure is received on ring port 1 and hold-off timer is started, then both Bit 1 and Bit 7 will have the value as 1.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

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

Status in source: current.

Names: fsErpsRingNodeStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsErpsRingNodeStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"A 32 bit mask giving the current status of the ring by specifying the events/status currently present. Bit 1 - Signal-failure on Ring Port 1 Bit 2 - Signal-failure on Ring Port 2 Bit 3 - Remote-signal-failure received on Ring Port 1 Bit 4 - Remote-signal-failure received on Ring Port 2 Bit 5 - Rpl-blocked Bit 6 - Wait-to-restore-timer-running Bit 7 - Hold-timer-running Bit 8 - Guard-timer-running Bit 9 - Periodic-timer-running Bit 10 - Wait-to-block-timer-running Value 1 of the bit signifies the presence of the event associated with that bit and value zero signifies the absence of that event For example: If a signal failure is received on Ring port 1 and R-APS(SF) is received on port 2, then Bit 1 and 4 will have the value as 1. Signal failure on a port represents Port failure indication received from the monitoring entity. This does not depend on hold off timer status. If signal failure is received on ring port 1 and hold-off timer is started, then both Bit 1 and Bit 7 will have the value as 1. Bit 9 indicates periodic timer and Bit 10 will have the value 1 when WTB timer is triggered.\"",
    "::=",
    "{",
    "fsErpsRingEntry",
    "14",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "A 32 bit mask giving the current status of the ring by specifying the events/status currently present. Bit 1 - Signal-failure on Ring Port 1 Bit 2 - Signal-failure on Ring Port 2 Bit 3 - Remote-signal-failure received on Ring Port 1 Bit 4 - Remote-signal-failure received on Ring Port 2 Bit 5 - Rpl-blocked Bit 6 - Wait-to-restore-timer-running Bit 7 - Hold-timer-running Bit 8 - Guard-timer-running Bit 9 - Periodic-timer-running Bit 10 - Wait-to-block-timer-running Value 1 of the bit signifies the presence of the event associated with that bit and value zero signifies the absence of that event For example: If a signal failure is received on Ring port 1 and R-APS(SF) is received on port 2, then Bit 1 and 4 will have the value as 1. Signal failure on a port represents Port failure indication received from the monitoring entity. This does not depend on hold off timer status. If signal failure is received on ring port 1 and hold-off timer is started, then both Bit 1 and Bit 7 will have the value as 1. Bit 9 indicates periodic timer and Bit 10 will have the value 1 when WTB timer is triggered."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 2

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

Status in source: current.

Names: fsErpsRingNodeStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsErpsRingNodeStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"A 32 bit mask giving the current status of the ring by specifying the events/status currently present. Bit 1 - Signal-failure on Ring Port 1 Bit 2 - Signal-failure on Ring Port 2 Bit 3 - Remote-signal-failure received on Ring Port 1 Bit 4 - Remote-signal-failure received on Ring Port 2 Bit 5 - Rpl-blocked Bit 6 - Wait-to-restore-timer-running Bit 7 - Hold-timer-running Bit 8 - Guard-timer-running Value 1 of the bit signifies the presence of the event associated with that bit and value zero signifies the absence of that event For example: If a signal failure is received on Ring port 1 and R-APS(SF) is received on port 2, then Bit 1 and 4 will have the value as 1. Signal failure on a port represents Port failure indication received from the monitoring entity. This does not depend on hold off timer status. If signal failure is received on ring port 1 and hold-off timer is started, then both Bit 1 and Bit 7 will have the value as 1.\"",
    "::=",
    "{",
    "fsErpsRingEntry",
    "14",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "A 32 bit mask giving the current status of the ring by specifying the events/status currently present. Bit 1 - Signal-failure on Ring Port 1 Bit 2 - Signal-failure on Ring Port 2 Bit 3 - Remote-signal-failure received on Ring Port 1 Bit 4 - Remote-signal-failure received on Ring Port 2 Bit 5 - Rpl-blocked Bit 6 - Wait-to-restore-timer-running Bit 7 - Hold-timer-running Bit 8 - Guard-timer-running Value 1 of the bit signifies the presence of the event associated with that bit and value zero signifies the absence of that event For example: If a signal failure is received on Ring port 1 and R-APS(SF) is received on port 2, then Bit 1 and 4 will have the value as 1. Signal failure on a port represents Port failure indication received from the monitoring entity. This does not depend on hold off timer status. If signal failure is received on ring port 1 and hold-off timer is started, then both Bit 1 and Bit 7 will have the value as 1."
    ],
    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.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.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