clusterv2CandidateTable
ZELAX-MIB ·
.1.3.6.1.4.1.7840.2.1.100.22.4.5
Object
table
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.
Context
- MIB
- ZELAX-MIB
- OID
.1.3.6.1.4.1.7840.2.1.100.22.4.5- Type
- table
- Status
- current
- Parent
- clusterv2Commander
- Children
- 1
Net-SNMP examples
How SNMP and these commands workUse a bulk walk to inspect objects and instances beneath this OID.
Walk the subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ZELAX-MIB' -M '/opt/observium/mibs/zelax:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZELAX-MIB::clusterv2CandidateTable'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'ZELAX-MIB' -M '/opt/observium/mibs/zelax:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ZELAX-MIB::clusterv2CandidateTable'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.