System Monitoring Elements

Solved1.56K viewsoperating system monitoring System configuraton system monitoring Windows domain
1
0 Comments

Hi All,

We have some Windows Server Monitoring elements which displays data such as disk space, memory usage etc.. which uses the SNMP protocol.

We have successfully got this monitoring element working for elements monitoring the local host in the IP, but elements in a failover pair it is unsuccessful at displaying data setting the IPs to the machine names instead of using "localhost". Is there any set up that is required to for windows monitoring elements in failover pairs?

Thanks in advance!

ryan yahia Selected answer as best 18th April 2023

2 Answers

0
1.17K 3 Comments

Hi,
any luck so far? We are interested in monitoring both our DMAs in our failover pair as well – so far only monitoring 127.0.0.1 is working, but that does not give us the full picture, obviously.
Thanks!

(sorry, re-post as an "answer" to be able to find it again)

Nils Hoven [DevOps Advocate] Posted new comment 6th July 2022
Nils Hoven [DevOps Advocate] commented

We are trying to implement Windows HW/OS monitoring based on Windows Platform protocol for our two DMAs in failover pair configuration, but so far it does not want to work for the remote DMA in our failover pair, despite following the instructions given here: https://catalog.dataminer.services/result/driver/251

Latest error is “Contacting server failed: Connection to [//[remote_IP]/root/cimv2] failed. Zugriff verweigert (hr = 0x80070005)”. However, the solution given in the description does not solve it…
ryan yahia commented

What worked for me was the following:

Navigate to the Services page on both machines that are in the failover pair.
Right Click on SNMP Service and open up the properties.
On the Agent tab ensure all checkboxes are selected under the Service heading.
Under Security add “public” to the “Accepted community names”
Under “Accept SNMP packets from these hosts” add the remote ip of the machine you want to monitor, the local ip of the current machine and the name of the machine you want to monitor and the name of the current machine. Also add in the corporate ip of both machines.

Thanks,
Ryan
Nils Hoven [DevOps Advocate] commented

Hi Ryan,
thanks a lot! This sounds indeed very helpful and straight forward – I’m still having trouble with the configuration of the community string and accepted hosts. But that is due to our group policies, and I am dealing with our IT departement regarding this. We will see if we can solve this, and if this will enable our Windows monitoring capabilities.
BR
Nils
You are viewing 1 out of 2 answers, click here to view all answers.