Ad Widget

Collapse

Auto Discovery not working as expected

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • r0k5t4r
    Member
    • Jun 2009
    • 91

    #1

    Auto Discovery not working as expected

    Hi,

    we are currently evaluating zabbix 1.6 for our network. I have setup 3 Auto discovery rules and none of them seem to be working correctly.

    From the manual it says that discovery is the first part and then an action can take place. I used the preconfigured actions to add discovered machines with a zabbix client installed.

    My discovery looks like this:

    IP Range: 172.20.205.1-255
    Delay: 600

    Checks: Zabbix agent
    Status: active

    I can also see in the zabbix-server.log that the discovery is running:

    [172.20.200.189]:10050 [No route to host]
    6284:20090603:135158 Get value from agent failed. Error: *** Cannot connect to [vb5891.vegagroup.net]:10050 [No route to host]
    6298:20090603:135159 Get value from agent failed. Error: *** Cannot connect to [172.20.200.190]:10050 [No route to host]

    i installed an agent on 172.20.205.8 and i can successfully manually add it to the hosts. But the action combined with the discovery doesn't seem to work.

    My action looks like this:

    Name: Auto discovery. Windows servers.

    Event Source: Discovery

    Status: Enabled

    Type of calculation: (A) and (B) and (C)

    Action Operations: Add to group "Windows servers"
    Link to template "Template_Windows"

    But the machine is not shown in e.g. latest data? I must be missing something but I don't know what it is?

    Can someone please shed light on this?

    Regards,
    r0k5t4r
  • Cray
    Member
    • Mar 2009
    • 72

    #2
    Checks: Zabbix agent
    Status: active
    And what item do you check against the Zabbix agent to see it's responding ?

    (you can check system.hostname for instance...)

    Usually, it works this way :

    - setup an auto-discovery action that checks an item against a potential Zabbix agent (listenning on whatever is the port you specified)

    - setup an action with the source event set on 'discovery' (and not triggers !), a match calculation based on 'source == Zabbix agent' (as far as I can remember), and the effective action set to add the host found to a logical group.

    If you're not getting any hosts added, verify :
    - the subnet you're scanning
    - your action conditions and source event
    - your action steps

    Comment

    • r0k5t4r
      Member
      • Jun 2009
      • 91

      #3
      Hi,

      thanks for pointing this out. I just didn't see that i have to choose an item of the zabbix agent to check against.

      Now I'm checking against "system.uname". Hopefully the actions are now working. I will have a look at the dashboard to see if the hosts are now discovered.

      Thanks and Regards,
      r0k5t4r

      Comment

      • r0k5t4r
        Member
        • Jun 2009
        • 91

        #4
        Now it works. Thanks a lot.

        Comment

        Working...