I have a traditional Microsoft SQL Server 2016 active / passive cluster, which consists of 2 Windows Server 2016 as nodes.
Node1 : 10.76.217.33 - I have installed the Zabbix Agent on this ip adress and monitors the server just as all the other Windows servers
Node2 : 10.76.217.34 - I have also installed Zabbix agent on this ip and it works ...
Cluster : 10.76.217.35 - I cannot install an agent on this ip, as it is virtual ip
I have then added the 3 hosts inside Zabbix - each node and then the cluster host.
The 2 nodes response as expected, but the cluster host ofcourse failed as it has no agent installed.
So I went into the config file, and added the cluster ip adress to the "listenIP" option, and on the active node it works - and I can query both the node and the cluster host.
But on the second node (currently passive), after I added cluster ip and restarted the service - it failed to start, probably as it cannot listen on the cluster ip adress, as it does not currently have it assigned.
Any ideas how to solve this ?
Node1 : 10.76.217.33 - I have installed the Zabbix Agent on this ip adress and monitors the server just as all the other Windows servers
Node2 : 10.76.217.34 - I have also installed Zabbix agent on this ip and it works ...
Cluster : 10.76.217.35 - I cannot install an agent on this ip, as it is virtual ip
I have then added the 3 hosts inside Zabbix - each node and then the cluster host.
The 2 nodes response as expected, but the cluster host ofcourse failed as it has no agent installed.
So I went into the config file, and added the cluster ip adress to the "listenIP" option, and on the active node it works - and I can query both the node and the cluster host.
But on the second node (currently passive), after I added cluster ip and restarted the service - it failed to start, probably as it cannot listen on the cluster ip adress, as it does not currently have it assigned.
Any ideas how to solve this ?
Comment