CMK version:
2.1.0p27
OS version:
Rocky 9.3
Error message:
F5 cluster monitoring works fine on-prem with the current configuration, but Azure-based F5 image seems really odd.
The cluster configuration is the same but the output comes back as the following:
OK [BIG-IP Cluster Status] Best: [az-bigip0], Node is standby, Additional results from: [az-bigip1]
az-bigip1 is active, and az-bigip0 is the standby. Why is the “Best” coming back as az-bigip0?
Also, all the pools return as OK when there are 0 members.
OK [Load Balancing Pool /Common/www] Best: [az-bigip0], 0 of 0 members are up, Additional results from: [az-bigip1]
Very strange indeed.
Does anyone on here have any clue as to what is going on?
Rules:
[Clustered services] are set the same from on-prem to azure hosts
[Aggregation options] are set the same from on-prem to azure hosts
[Cluster status] is different in azure using the f5_bigip_vcmpfailer setting to active/passive. On-prem does not have a rule for this.