QTECH-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
QTECH-CLUSTER-MIB
Last revised
Identity
qtechClusterMIB
Base OID
1.3.6.1.4.1.27514.1.1.10.2.31
Imported Objects
P-BRIDGE-MIB EnabledStatus
QTECH-SMI qtechMgmt
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 qtech 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 'QTECH-CLUSTER-MIB' -M '/opt/observium/mibs/qtech:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'QTECH-CLUSTER-MIB::qtechClusterMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'QTECH-CLUSTER-MIB' -M '/opt/observium/mibs/qtech:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'QTECH-CLUSTER-MIB::qtechClusterMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (84)
.1.3.6.1.4.1.27514.1.1.10.2.31
.1.3.6.1.4.1.27514.1.1.10.2.31.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.10
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.11
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.12
.1.3.6.1.4.1.27514.1.1.10.2.31.1.13
Enumeration
.1.3.6.1.4.1.27514.1.1.10.2.31.1.14
.1.3.6.1.4.1.27514.1.1.10.2.31.1.15
.1.3.6.1.4.1.27514.1.1.10.2.31.1.16
.1.3.6.1.4.1.27514.1.1.10.2.31.1.16.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.16.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.17
.1.3.6.1.4.1.27514.1.1.10.2.31.1.17.1
Enumeration
.1.3.6.1.4.1.27514.1.1.10.2.31.1.17.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.17.3
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.17.4
.1.3.6.1.4.1.27514.1.1.10.2.31.1.18
.1.3.6.1.4.1.27514.1.1.10.2.31.1.18.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.18.1.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.18.1.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.18.1.3
.1.3.6.1.4.1.27514.1.1.10.2.31.1.19
.1.3.6.1.4.1.27514.1.1.10.2.31.1.19.1
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.19.1.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.19.1.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.19.1.3
.1.3.6.1.4.1.27514.1.1.10.2.31.1.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.10
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.11
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.12
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.13
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.14
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.15
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.16
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.17
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.3
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.4
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.5
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.6
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.7
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.8
.1.3.6.1.4.1.27514.1.1.10.2.31.1.20.1.9
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1.3
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1.4
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1.5
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1.6
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1.7
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1.8
.1.3.6.1.4.1.27514.1.1.10.2.31.1.21.1.9
.1.3.6.1.4.1.27514.1.1.10.2.31.1.22
.1.3.6.1.4.1.27514.1.1.10.2.31.1.22.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.22.1.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.22.1.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.1.1
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.1.1.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.1.1.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.1.1.3
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.2.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.2.1.1
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.2.1.2
.1.3.6.1.4.1.27514.1.1.10.2.31.1.23.2.1.3
.1.3.6.1.4.1.27514.1.1.10.2.31.1.3
.1.3.6.1.4.1.27514.1.1.10.2.31.1.4
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.5
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.6
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.7
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.8
Integer32
.1.3.6.1.4.1.27514.1.1.10.2.31.1.9
.1.3.6.1.4.1.27514.1.1.10.2.31.2
.1.3.6.1.4.1.27514.1.1.10.2.31.3
.1.3.6.1.4.1.27514.1.1.10.2.31.3.1
.1.3.6.1.4.1.27514.1.1.10.2.31.3.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. SNMPv2-TCrfc
  3. IANAifType-MIBrfc
  4. SNMPv2-CONFrfc
  5. SNMPv2-MIBrfc
  6. IF-MIBrfc
  7. BRIDGE-MIBrfc
  8. P-BRIDGE-MIBrfc
  9. QTECH-SMIqtech
  10. QTECH-CLUSTER-MIBqtechselected
Conformance Groups (9)
The collection of objects which are used to represent
the status of the cluster.
.1.3.6.1.4.1.27514.1.1.10.2.31.3.2.1
The collection of objects which are used to represent
the status of the cluster member. These objects are accessible
on the cluster members and the manager device.
.1.3.6.1.4.1.27514.1.1.10.2.31.3.2.2
The collection of objects which are used to represent
the status of single devices which are not in any cluster.
These objects are accessible on any single device.
.1.3.6.1.4.1.27514.1.1.10.2.31.3.2.3
The collection of objects which are used to represent
the members of a cluster.
.1.3.6.1.4.1.27514.1.1.10.2.31.3.2.4
The collection of objects which are used to represent
cluster candidates. These objects are accessible
on the manager device only.
.1.3.6.1.4.1.27514.1.1.10.2.31.3.2.5
The collection of objects which are used to represent
cluster Member add operate. These objects are accessible
on the manager device only.
.1.3.6.1.4.1.27514.1.1.10.2.31.3.2.6
The collection of objects which are used to represent
cluster blackList. These objects are accessible
on the manager device only.
.1.3.6.1.4.1.27514.1.1.10.2.31.3.2.7
The collection of objects which are used to represent
cluster auth password pool. These objects are accessible
on the manager device only.
.1.3.6.1.4.1.27514.1.1.10.2.31.3.2.8
The collection of objects which are used to represent
cluster device auth Password. These objects are accessible
on the manager device only.
.1.3.6.1.4.1.27514.1.1.10.2.31.3.2.9
Compliance Statements (1)

OID .1.3.6.1.4.1.27514.1.1.10.2.31.3.1.1
The compliance statement for the CLUSTER MIB.
Required groups
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.4.1.27514.1.1.10.2.31.2.1
While the state of member device changed, then this trap will be sent.
The qtechClusterMemberState 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.27514.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.27514.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.27514.1.1.10.2.31.2.4
The number of cluster member including members reaches the maximum allowed,
then this trap will be sent.