Ad Widget

Collapse

Detecting a Windows Server that is down using active client

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rlangle
    Junior Member
    • May 2013
    • 10

    #1

    Detecting a Windows Server that is down using active client

    Hi

    We have just upgrade to v2.0.4 and are re-visiting of Zabbix configuration. We monitor a number of windows 2008 clients with an active agent and receive the basic items such as CPU, disk space with out issue.

    However if the server fails or even if I stop the zabbix agent on the monitored server we get no notification. I have read a number of posts on this but still do not have a solution.

    The most promising was creating a zabbix.internal item and using a key of zabbix[host,agent,available] https://www.zabbix.com/forum/showthread.php?t=38633
    However this always remains up even when I stop the agent or shutdown the server.

    I have also started to play with the External Service icmpping[
    {HOST.CONN} I assuming in this case HOST.CONN is the address of the server being monitored?? But again no success. fping is installed and ran from the command line returns the correct status of the server.

    What is the best way to detect when a Windows Server is down / unavailable??

    Thanks

    Rob
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    I am not sure what version this started in, but in 2.0.6, the current way to detect an agent being down is this trigger which is applied at the template level: (Agent not reachable for a 5 minute period)

    Code:
    {Template App Zabbix Agent:agent.ping.nodata(5m)}=1
    That trigger, by default, is part of Template App Zabbix Agent which is linked to all OS Templates. If you don't have that template, you could simply apply that trigger to all of your OS templates manually.

    Comment

    • rlangle
      Junior Member
      • May 2013
      • 10

      #3
      Thanks. Thats got me going

      Comment

      Working...