MY-CLUSTER-MIB Table View

Table-centric layout grouping table, row, and column objects.

Tables
2
Rows
2
Columns
6
.1.3.6.1.4.1.4881.1.1.10.2.31.1.2.1 · 1 row entry · 5 columns
Uses the ruijie variant from /opt/observium/mibs/ruijie.
Command help
Walk scMemberTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'MY-CLUSTER-MIB' -M '/opt/observium/mibs/ruijie:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MY-CLUSTER-MIB::scMemberTable'
This table contains one row per cluster member,
including the command switch.
scMemberEntry row .1.3.6.1.4.1.4881.1.1.10.2.31.1.2.1.1
An entry containing cluster management information
applicable to a particular cluster member. If the
entry contain the command switch, this entry cannot
be modified.
Column Syntax OID
The management MAC address of the member device.
SNMPv2-TCMacAddress
Type Constraints:
range: 6
Description:
Represents an 802 MAC address represented in the
`canonical' order defined by IEEE 802.1a, i.e., as if it
were transmitted least significant bit first, even though
802.5 (in contrast to other 802.x protocols) requires M…
.1.3.6.1.4.1.4881.1.1.10.2.31.1.2.1.1.1
An arbitrary value which uniquely identifies the
cluster member switch number. It ranges from 0 to
scStatusMaxNumberOfMembers - 1. incluing the command
switch.
Unsigned32r/w
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.4881.1.1.10.2.31.1.2.1.1.2
The status of cluster management connectivity between
the command switch and a cluster member. Cluster management
connectivity is determined by the exchange of cluster
management messages between the command switch and …
Enumeration
Enumerated Values:
1active
2inactive
.1.3.6.1.4.1.4881.1.1.10.2.31.1.2.1.1.3
The value of MacAddress used for identify the device in lldp pdu.
SNMPv2-TCMacAddress
Type Constraints:
range: 6
Description:
Represents an 802 MAC address represented in the
`canonical' order defined by IEEE 802.1a, i.e., as if it
were transmitted least significant bit first, even though
802.5 (in contrast to other 802.x protocols) requires M…
.1.3.6.1.4.1.4881.1.1.10.2.31.1.2.1.1.4
The status of this conceptual row.The
devices currently eligible to be added into the
cluster are listed in the scCandidateTable.
An attempt to add a new member may fail. See
scStatusLastFailureAddMember for possible r…
SNMPv2-TCRowStatusr/w
Type Values:
1active
2notInService
3notReady
4createAndGo
5createAndWait
6destroy
Description:
The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row (as described in Section 7.7.1 of …
.1.3.6.1.4.1.4881.1.1.10.2.31.1.2.1.1.5
.1.3.6.1.4.1.4881.1.1.10.2.31.1.3.1 · 1 row entry · 1 columns
Uses the ruijie variant from /opt/observium/mibs/ruijie.
Command help
Walk scCandidateTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'MY-CLUSTER-MIB' -M '/opt/observium/mibs/ruijie:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MY-CLUSTER-MIB::scCandidateTable'
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 supports the cluster management protocol.
          
          
The entries in this table and the entries in 
scMemberTable are mutually exclusive at all
times.  That is, any device that is a cluster
member never shows up in the scCandidateTable
or is never a candidate at the same time .  Also, any 
candidate that shows up in scCandidateTable should not
appear in scMemberTable.
scCandidateEntry row .1.3.6.1.4.1.4881.1.1.10.2.31.1.3.1.1
An entry pertaining to a single candidate device.
Column Syntax OID
The management MAC address of a device qualified to
to be a cluster member of the command switch
cluster.
SNMPv2-TCMacAddress
Type Constraints:
range: 6
Description:
Represents an 802 MAC address represented in the
`canonical' order defined by IEEE 802.1a, i.e., as if it
were transmitted least significant bit first, even though
802.5 (in contrast to other 802.x protocols) requires M…
.1.3.6.1.4.1.4881.1.1.10.2.31.1.3.1.1.1