For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Pavlos_Parissis's avatar
Pavlos_Parissis
Icon for Nimbostratus rankNimbostratus
Jul 25, 2012

Query cluster status over SNMP

Hi all,     I am trying to find out if a node is either in Active or in Standby status using SNMP but when I query sysClusterTable I get nothing back     snmptable -r 1 -r 1 -v2c -c publ...
config
design
Pavlos_Parissis's avatar
Pavlos_Parissis
Icon for Nimbostratus rankNimbostratus
Jul 31, 2012
Found it via our support channel,

 

The F5-BIGIP-SYSTEM-MIB file contains an OID, 1.3.6.1.4.1.3375.2.1.1.1.1.19, that can be queried through SNMP to determine the failover status of a BIG-IP LTM. The .1.3.6.1.4.1.3375.2.1.1.1.1.19 OID (referenced as sysAttrFailoverUnitMask within the MIB) uses an integer value to specify whether the BIG-IP LTM pair is in active/standby mode or active-active mode.

 

 

In an active/standby configuration, the active unit is reported as a value of 3, and the standby unit as a value of 0.

 

 

In an active-active configuration, both units will be active, and the value returned will either be 1 for Unit 1, or 2 for Unit 2.

 

 

To determine the failover status of your BIG-IP LTM from the command line, use the following syntax:

 

 

snmpget -v 2c -c localhost .1.3.6.1.4.1.3375.2.1.1.1.1.19.0

 

 

For example:

 

 

snmpget -On -v 2c -c public localhost .1.3.6.1.4.1.3375.2.1.1.1.1.19.0

 

.1.3.6.1.4.1.3375.2.1.1.1.1.19.0 = INTEGER: 3

 

==========================

 

 

  • Peter_Soppe_715's avatar
    Peter_Soppe_715
    Icon for Nimbostratus rankNimbostratus
    Mar 23, 2015
    I am unable to reproduce this on an BigIP 1600 - 11.5.1 HF6 Cluster: [admin@lb1:Active:In Sync] log snmpget -v 2c -c xxx localhost .1.3.6.1.4.1.3375.2.1.1.1.1.19.0 F5-BIGIP-SYSTEM-MIB::sysAttrFailoverUnitMask.0 = INTEGER: 0 [admin@lb2:Standby:In Sync] log snmpget -v 2c -c xxx localhost .1.3.6.1.4.1.3375.2.1.1.1.1.19.0 F5-BIGIP-SYSTEM-MIB::sysAttrFailoverUnitMask.0 = INTEGER: 0 According to the MIB file (/usr/local/www/docs/mibs/mibs_f5.tar.gz) this is deprecated and you should query another OID: sysCmTrafficGroupStatus [admin@lb1:Active:In Sync] log snmpget -v 2c -c xxx localhost .1.3.6.1.4.1.3375.2.1.14.3.4.0 F5-BIGIP-SYSTEM-MIB::sysCmFailoverStatusSummary.0 = STRING: 1/1 active [admin@lb2:Standby:In Sync] log snmpget -v 2c -c xxx localhost .1.3.6.1.4.1.3375.2.1.14.3.4.0 F5-BIGIP-SYSTEM-MIB::sysCmFailoverStatusSummary.0 = STRING: 1/1 standby This works in my setup.