OID reference

h3cRrppRingNodeMode

1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.5

Description

There are four RRPP node modes for the switch on a RRPP ring, such as master, transit, edge and assistant-edge. Each RRPP ring has a single designated master-node. All other nodes except edge-node and assistant-edge-node on that ring are referred to as transit-nodes. The node mode of edge and assistant-edge should be …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1 (h3cRrppRingEntry)
Node code
5
Node name
h3cRrppRingNodeMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.5
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 10 2 45 2 2 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cRrpp(45) h3cRrppTable(2) h3cRrppRingTable(2) h3cRrppRingEntry(1) h3cRrppRingNodeMode(5)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/45/2/2/1/5
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/45/2/2/1/5
  • /ISO/3/6/1/4/1/43/45/1/10/2/45/2/2/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cRrpp/h3cRrppTable/h3cRrppRingTable/h3cRrppRingEntry/h3cRrppRingNodeMode
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-create
Status in MIB
current

Enumerated values

ValueName
1master
2transit
3edge
4assistantEdge

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.

In A3COM-HUAWEI-RRPP-MIB, the row index consists of these components in order:

  1. h3cRrppDomainID (Integer32): one numeric subidentifier for the non-negative value.
  2. h3cRrppRingID (Integer32): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.5.<h3cRrppDomainID>.<h3cRrppRingID>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.5

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

h3cRrppRingNodeMode · current

h3cRrppRingNodeMode OBJECT-TYPE
    SYNTAX      INTEGER{master(1),transit(2),edge(3),assistantEdge(4)}
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "There are four RRPP node modes for the switch on a RRPP
        ring, such as master, transit, edge and assistant-edge.
        Each RRPP ring has a single designated master-node.  All
        other nodes except edge-node and assistant-edge-node on
        that ring are referred to as transit-nodes.
        The node mode of edge and assistant-edge should be
        configured only on sub-ring.  When there is a common link
        between a sub-ring and its major-ring, the node mode of
        the sub-ring must be edge or assistant-edge, and they must
        be configured in pairs.
        If node mode is designated as edge or assistant-edge,
        several points should be noticed:
        Major-ring must be created before a sub-ring is created;
        Major-ring can't be deleted unless all its sub-rings are
        deleted;
        The node mode of the switch on major-ring must be
        transit;
        Major-ring and sub-ring must have only a common port.
        This value can't be modified after created."
    ::= { h3cRrppRingEntry 5 }

h3cRrppRingNodeMode · current

h3cRrppRingNodeMode OBJECT-TYPE
    SYNTAX      INTEGER{master(1),transit(2),edge(3),assistantEdge(4)}
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "There are four RRPP node modes for the switch on a RRPP
        ring, such as master, transit, edge and assistant-edge.
        Each RRPP ring has a single designated master-node.  All
        other nodes except edge-node and assistant-edge-node on
        that ring are referred to as transit-nodes.
        The node mode of edge and assistant-edge should be
        configured only on sub-ring.  When there is a common link
        between a sub-ring and its major-ring, the node mode of
        the sub-ring must be edge or assistant-edge, and they must
        be configured in pairs.
        If node mode is designated as edge or assistant-edge,
        several points should be noticed:
        Major-ring must be created before a sub-ring is created;
        Major-ring can't be deleted unless all its sub-rings are
        deleted;
        The node mode of the switch on major-ring must be
        transit;
        Major-ring and sub-ring must have only a common port.
        This value can't be modified after created."
    ::= { h3cRrppRingEntry 5 }

Meaning

Descriptions

1 unique

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

There are four RRPP node modes for the switch on a RRPP ring, such as master, transit, edge and assistant-edge. Each RRPP ring has a single designated master-node. All other nodes except edge-node and assistant-edge-node on that ring are referred to as transit-nodes. The node mode of edge and assistant-edge should be configured only on sub-ring. When there is a common link between a sub-ring and its major-ring, the node mode of the sub-ring must be edge or assistant-edge, and they must be configured in pairs. If node mode is designated as edge or assistant-edge, several points should be noticed: Major-ring must be created before a sub-ring is created; Major-ring can't be deleted unless all its sub-rings are deleted; The node mode of the switch on major-ring must be transit; Major-ring and sub-ring must have only a common port. This value can't be modified after created.

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

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 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cRrppRingNodeMode · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cRrppRingNodeMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cRrppRingNodeMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "master",
    "(",
    "1",
    ")",
    ",",
    "transit",
    "(",
    "2",
    ")",
    ",",
    "edge",
    "(",
    "3",
    ")",
    ",",
    "assistantEdge",
    "(",
    "4",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"There are four RRPP node modes for the switch on a RRPP ring, such as master, transit, edge and assistant-edge. Each RRPP ring has a single designated master-node. All other nodes except edge-node and assistant-edge-node on that ring are referred to as transit-nodes. The node mode of edge and assistant-edge should be configured only on sub-ring. When there is a common link between a sub-ring and its major-ring, the node mode of the sub-ring must be edge or assistant-edge, and they must be configured in pairs. If node mode is designated as edge or assistant-edge, several points should be noticed: Major-ring must be created before a sub-ring is created; Major-ring can't be deleted unless all its sub-rings are deleted; The node mode of the switch on major-ring must be transit; Major-ring and sub-ring must have only a common port. This value can't be modified after created.\"",
    "::=",
    "{",
    "h3cRrppRingEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "master",
            1
          ],
          [
            "transit",
            2
          ],
          [
            "edge",
            3
          ],
          [
            "assistantEdge",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "There are four RRPP node modes for the switch on a RRPP ring, such as master, transit, edge and assistant-edge. Each RRPP ring has a single designated master-node. All other nodes except edge-node and assistant-edge-node on that ring are referred to as transit-nodes. The node mode of edge and assistant-edge should be configured only on sub-ring. When there is a common link between a sub-ring and its major-ring, the node mode of the sub-ring must be edge or assistant-edge, and they must be configured in pairs. If node mode is designated as edge or assistant-edge, several points should be noticed: Major-ring must be created before a sub-ring is created; Major-ring can't be deleted unless all its sub-rings are deleted; The node mode of the switch on major-ring must be transit; Major-ring and sub-ring must have only a common port. This value can't be modified after created."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.1 h3cRrppRingID00
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.2 h3cRrppRingEnableStatus00
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.3 h3cRrppRingActive00
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.4 h3cRrppRingState00
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.6 h3cRrppRingPrimaryPort00
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.7 h3cRrppRingSecondaryPort00
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.8 h3cRrppRingLevel00
1.3.6.1.4.1.43.45.1.10.2.45.2.2.1.9 h3cRrppRingRowStatus00