== Title and thread adjusted from original post, since it’s been confirmed that it works fine for recent f5 versions ==
I don’t know if this should be feature request, or if there’s a way to do it “manually”. I’d like to track the HA status of f5 and Netscaler load balancers, so that we can alert on failover changes. Both of them have different means to check this over SNMP.
For the Netscaler, the single OID that would had out immediate value actually gives value for the peer unit, and not the unit being queried. That could be the only query, or, for more detailed information, could check the following values:
- haPeerState (188.8.131.52.4.1.59184.108.40.206.23.3): State of the peer unit (primary/secondary)
- haCurStatus (220.127.116.11.4.1.5918.104.22.168.23.23): Whether a NetScaler appliance is configured for high availability. Possible values are YES and NO. If the value is NO, the high availability statistics below are invalid.
- haCurState (22.214.171.124.4.1.59126.96.36.199.23.24): Health state of the HA node and not active/standby state. Possible values are: UP, DISABLED, INIT, PARTIALFAIL, COMPLETEFAIL, DUMB, PARTIALFAILSSL, ROUTEMONITORFAIL.
More details here: https://developer-docs.citrix.com/projects/netscaler-snmp-oid-reference/en/12.0/#nsHighAvailabilityGroup
== Disregard below ==
f5 has a single OID that will give the current status of the unit being queried. As per f5 documentation the OID has changed based on the OS version:
- 9.x - 11.1.0: sysAttrFailoverUnitMask (188.8.131.52.4.1.33184.108.40.206.220.127.116.11)
- 11.2.0 and later: sysCmFailoverStatusId (18.104.22.168.4.1.3322.214.171.124.3.1)
They could also have deeper analysis, but haven’t driven too deep into it yet.