Ad Widget

Collapse

Massive Problems with Discovery Actions

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Starko
    Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Aug 2012
    • 93

    #1

    Massive Problems with Discovery Actions

    Hello,

    I am trying to solve the following problem for over a week now.

    We setup a Zabbix Server 2.0.1 to monitor different customer networks which are attached via VPN. I want to spend as little time as possible with adding hosts, sorting into groups and linking templates.

    So I wanted to use Discovery und Discovery Actions. But I really cant get it to work. I have one Discovery rule for every customer. I checks their subnet for hosts by checking:
    Code:
    SSH (22,8800)	
    TCP (1494)	
    TCP (3389)	
    TCP (10050)	
    Zabbix agent "agent.ping"	
    Zabbix agent "system.uname"
    The "Monitoring -> Discovery" view looks very good after a few hours. Every Host was found with the right Checks.

    So now I want to use actions on these discoverys. To simply it for you I summary it and dont describe every rule.
    I have an action for every device found. They get linked with a simple ping check. That works. Every device gets linked to that template.
    Every Device
    -
    Discovery status = "Up"
    -
    Link to templates: Template ICMP Echo Request
    After that I have a rule for every Windows Server. It checks if the host is up and checks if port 3389 is open. If thats the case, the following should happen. But it never does. I dont know why and I dont know where to look for errors.
    Windows Server
    -
    Discovery status = "Up"
    Service port = "3389"
    Service port = "10050"
    -
    Add to host groups: Windows servers
    Remove from host groups: Discovered hosts
    Link to templates: Template agentless Windows, Template ICMP Echo Request, Template OS Windows
    The same is here. It checks for SSH and should link the template. But it never does.
    Linux Server
    -
    Auto discovery Linux servers
    -
    Discovery status = "Up"
    Service port = "10050"
    Service type = "SSH"
    -
    Add to host groups: Linux servers
    Remove from host groups: Discovered hosts
    Link to templates: Template ICMP Echo Request, Template OS Linux
    What have I done wrong, or is there a log for Discovery Actions?!
  • heaje
    Senior Member
    Zabbix Certified Specialist
    • Sep 2009
    • 325

    #2
    Discovery status = "Up"
    Service port = "3389"
    Service port = "10050"
    To me it looks like you're checking for the service port to be 3389 AND 10050 at the same time. As a result, that condition will never pass (because the service can only be running on one port ). Is your "Type of calculation" combo box set to "AND/OR"? That's what it should be set to for this action to work. If it already is, let me know and I'll brainstorm on this a bit more.

    The same idea applies to:
    Discovery status = "Up"
    Service port = "10050"
    Service type = "SSH"
    It looks like that action is checking for you service type on port 10050 to be SSH. I assume that's not what you want.

    Comment

    • Starko
      Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Aug 2012
      • 93

      #3
      Hello,

      first of all, I'm very sorry I didn't answer yet. But I was so busy at work, I had no time.

      I set this parameters on purpose. The goal was the following:
      "The Server has to be online" AND "The Server is a Windows Server which runs the RDP Service" AND "The Zabbix Agent is installed and running"
      If these three conditions combine, the server should be linked to the "Windows OS" Template.

      What do I have to do, to achieve this?

      Comment

      • heaje
        Senior Member
        Zabbix Certified Specialist
        • Sep 2009
        • 325

        #4
        I'll try and respond in a few days. I could be. a little slow cause I just started a new job.......

        Comment

        Working...