FS-CLUSTER-MIB

        The MIB module for the management of a group of
devices called a 'cluster'.  A cluster comprises:
        
1. A manager device, which is a device that can provide
   a single point of management (including SNMP, Web
   Console and CLI/Telnet Console) for the devices
   in the cluster;
        
2. Zero or more expansion devicees, or called the
   cluster members throughout the context of this MIB,
   which are devices that can be managed via a manager
   device.  The manager device is also considered as a
   cluster member.  Thus it has an entry in the MIB tables
   defined below for cluster members.
        
Only the manager device IP address, passwords, and SNMP
community strings need to be configured in order to
provide management access to members of the cluster.
        
The Entity MIB is not cross-referenced from this MIB.
        
To determine if a particular device can be a manager device
or a member device please refer to the device's
user's guide.
    
Source file
FS-CLUSTER-MIB
Last revised
Identity
fsClusterMIB
Base OID
1.3.6.1.4.1.52642.1.1.10.2.31
Imported Objects
FS-SMI fsMgmt
P-BRIDGE-MIB EnabledStatus
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString MacAddress RowStatus TimeStamp
Net-SNMP examples using the fscom MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'FS-CLUSTER-MIB' -M '/opt/observium/mibs/fscom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FS-CLUSTER-MIB::fsClusterMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'FS-CLUSTER-MIB' -M '/opt/observium/mibs/fscom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'FS-CLUSTER-MIB::fsClusterMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (81)
.1.3.6.1.4.1.52642.1.1.10.2.31
.1.3.6.1.4.1.52642.1.1.10.2.31.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.10
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.11
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.12
.1.3.6.1.4.1.52642.1.1.10.2.31.1.13
Enumeration
.1.3.6.1.4.1.52642.1.1.10.2.31.1.14
.1.3.6.1.4.1.52642.1.1.10.2.31.1.15
.1.3.6.1.4.1.52642.1.1.10.2.31.1.16
.1.3.6.1.4.1.52642.1.1.10.2.31.1.16.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.16.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.17
.1.3.6.1.4.1.52642.1.1.10.2.31.1.17.1
Enumeration
.1.3.6.1.4.1.52642.1.1.10.2.31.1.17.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.17.3
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.17.4
.1.3.6.1.4.1.52642.1.1.10.2.31.1.18
.1.3.6.1.4.1.52642.1.1.10.2.31.1.18.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.18.1.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.18.1.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.18.1.3
.1.3.6.1.4.1.52642.1.1.10.2.31.1.19
.1.3.6.1.4.1.52642.1.1.10.2.31.1.19.1
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.19.1.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.19.1.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.19.1.3
.1.3.6.1.4.1.52642.1.1.10.2.31.1.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.10
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.11
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.12
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.13
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.14
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.15
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.16
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.17
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.3
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.4
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.5
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.6
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.7
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.8
.1.3.6.1.4.1.52642.1.1.10.2.31.1.20.1.9
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1.3
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1.4
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1.5
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1.6
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1.7
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1.8
.1.3.6.1.4.1.52642.1.1.10.2.31.1.21.1.9
.1.3.6.1.4.1.52642.1.1.10.2.31.1.22
.1.3.6.1.4.1.52642.1.1.10.2.31.1.22.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.22.1.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.22.1.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.1.1
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.1.1.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.1.1.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.1.1.3
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.2.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.2.1.1
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.2.1.2
.1.3.6.1.4.1.52642.1.1.10.2.31.1.23.2.1.3
.1.3.6.1.4.1.52642.1.1.10.2.31.1.3
.1.3.6.1.4.1.52642.1.1.10.2.31.1.4
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.5
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.6
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.7
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.8
Integer32
.1.3.6.1.4.1.52642.1.1.10.2.31.1.9
.1.3.6.1.4.1.52642.1.1.10.2.31.2
Dependencies (9) 5 direct · 4 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. FS-SMIfscom
  3. SNMPv2-TCrfc
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. BRIDGE-MIBrfc
  9. P-BRIDGE-MIBrfc
  10. FS-CLUSTER-MIBfscomselected
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.4.1.52642.1.1.10.2.31.2.1
While the state of member device changed, then this trap will be sent.
The fsClusterMemberState node is as follow, 1 indicates Ready status,
2 indicates Active status, 3 indicates Connect status,
and 4 indicates Disconnect status. The node value is as follow.
.1.3.6.1.4.1.52642.1.1.10.2.31.2.2
When a device add cluster failure, send a snmp trap to the network
management. then this trap will be sent.
.1.3.6.1.4.1.52642.1.1.10.2.31.2.3
The number of cluster devices including candidates and members reaches the maximum allowed,
then this trap will be sent.
.1.3.6.1.4.1.52642.1.1.10.2.31.2.4
The number of cluster member including members reaches the maximum allowed,
then this trap will be sent.