OID reference

clusterv2CandidateTable

1.3.6.1.4.1.7840.2.1.100.22.4.5

Description

This table contains one row per cluster candidate, A cluster candidate is a device that is currently eligible to be added to the cluster of a command switch. A device is eligible if it satisfies the following conditions: 1. It start the cluster func. 2. It is in a same L2 LAN with commander switch The entries in this …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.7840.2.1.100.22.4 (clusterv2Commander)
Node code
5
Node name
clusterv2CandidateTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.7840.2.1.100.22.4.5
URN notation
urn:oid:1.3.6.1.4.1.7840.2.1.100.22.4.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 7840 2 1 100 22 4 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zelax(7840) zelaxCommonMIBs(2) switchGroup(1) os(100) prClusterv2(22) clusterv2Commander(4) clusterv2CandidateTable(5)}
OID-IRI notation
  • /1/3/6/1/4/1/7840/2/1/100/22/4/5
  • /ISO/Identified-Organization/6/1/4/1/7840/2/1/100/22/4/5
  • /ISO/3/6/1/4/1/7840/2/1/100/22/4/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/7840/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/identified-organization/dod/internet/private/enterprise/zelax/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/identified-organization/dod/internet/private/enterprises/7840/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/identified-organization/dod/internet/private/enterprises/zelax/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/7840/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zelax/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/7840/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/zelax/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/org/dod/internet/private/enterprise/7840/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/org/dod/internet/private/enterprise/zelax/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/org/dod/internet/private/enterprises/7840/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/org/dod/internet/private/enterprises/zelax/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/org/dod/internet/private/ldap-enterprise/7840/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/org/dod/internet/private/ldap-enterprise/zelax/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/org/dod/internet/private/vendor-objects/7840/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • /iso/org/dod/internet/private/vendor-objects/zelax/zelaxCommonMIBs/switchGroup/os/prClusterv2/clusterv2Commander/clusterv2CandidateTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF Clusterv2CandidateEntry
Maximum access defined by MIB
not-accessible
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.

clusterv2CandidateTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Clusterv2CandidateEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "This table contains one row per cluster candidate,
             A cluster candidate is a device that is currently
             eligible to be added to the cluster of a command
             switch.  A device is eligible if it satisfies the
             following conditions:
             1. It start the cluster func.
             2. It is in a same L2 LAN with commander switch
       
             The entries in this table and the entries in 
             clusterMemberTable are mutually exclusive at all
             times.  That is, any device that is a cluster
             member never shows up in the clusterCandidateTable
             or is never a candidate at the same time .  Also, any 
             candidate that shows up in clusterCandidateTable should not
             appear in clusterMemberTable."
    ::= { clusterv2Commander 5 }

Meaning

Descriptions

1 unique

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

This table contains one row per cluster candidate, A cluster candidate is a device that is currently eligible to be added to the cluster of a command switch. A device is eligible if it satisfies the following conditions: 1. It start the cluster func. 2. It is in a same L2 LAN with commander switch The entries in this table and the entries in clusterMemberTable are mutually exclusive at all times. That is, any device that is a cluster member never shows up in the clusterCandidateTable or is never a candidate at the same time . Also, any candidate that shows up in clusterCandidateTable should not appear in clusterMemberTable.

Sources for this description

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

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)1 record · 1 source

Description 1

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

Status in source: current.

Names: clusterv2CandidateTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "clusterv2CandidateTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "Clusterv2CandidateEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table contains one row per cluster candidate, A cluster candidate is a device that is currently eligible to be added to the cluster of a command switch. A device is eligible if it satisfies the following conditions: 1. It start the cluster func. 2. It is in a same L2 LAN with commander switch The entries in this table and the entries in clusterMemberTable are mutually exclusive at all times. That is, any device that is a cluster member never shows up in the clusterCandidateTable or is never a candidate at the same time . Also, any candidate that shows up in clusterCandidateTable should not appear in clusterMemberTable.\"",
    "::=",
    "{",
    "clusterv2Commander",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "Clusterv2CandidateEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table contains one row per cluster candidate, A cluster candidate is a device that is currently eligible to be added to the cluster of a command switch. A device is eligible if it satisfies the following conditions: 1. It start the cluster func. 2. It is in a same L2 LAN with commander switch The entries in this table and the entries in clusterMemberTable are mutually exclusive at all times. That is, any device that is a cluster member never shows up in the clusterCandidateTable or is never a candidate at the same time . Also, any candidate that shows up in clusterCandidateTable should not appear in clusterMemberTable."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.7840)

Suhman Sergey

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.7840.2.1.100.22.4.5.1 clusterv2CandidateEntry44

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.7840.2.1.100.22.4.1 clusterv2CommanderAutoAddMem00
1.3.6.1.4.1.7840.2.1.100.22.4.2 clusterv2MemberCounter00
1.3.6.1.4.1.7840.2.1.100.22.4.3 clusterv2MemberTable17
1.3.6.1.4.1.7840.2.1.100.22.4.4 clusterv2CandidateCounter00
1.3.6.1.4.1.7840.2.1.100.22.4.6 clusterv2RebootMem00