Ad Widget

Collapse

Hosts discovered by proxy not added

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

    #1

    Hosts discovered by proxy not added

    Hi, I have two rules in place for discovery. Both rules are working. I can lookup the log files on the zabbix server and proxy. And the IP ranges are beeing scanned. On the zabbix clients I can see that they are responding with value "system.uname".

    I added an action to automatically add discovered hosts with a zabbix client. For the hosts discovered by the zabbix server this is working ok. Except that {HOSTNAME} and {IPADDRESS} are shown as UNKNOWN and I receive notifications again and again for hosts that have already been added??? Maybe I'm missing something here. Hosts discovered by the proxy are not added.

    Discovery action for zabbix server:

    Host ip = "172.20.100.1-254"
    Service type = "ZABBIX agent"
    Discovery status = "Up"
    Received value like "Windows"

    Discovery action for zabbix proxy:

    Host ip = "10.1.0.1-254"
    Service type = "ZABBIX agent"
    Discovery status = "Up"
    Received value like "SunOS"

    The only difference is the OS for the actions.

    Any ideas?
  • r0k5t4r
    Member
    • Jun 2009
    • 91

    #2
    No one? If more infos are needed, I'm happy to provide them.

    Comment

    • r0k5t4r
      Member
      • Jun 2009
      • 91

      #3
      I did some more testing and it seems to be a problem with the SunOS zabbix agent. Using a windows agent works as expected.

      I will test more workstations with Sun Solaris 8 and 10 next week.

      Cheers,
      r0k5t4r

      Comment

      • r0k5t4r
        Member
        • Jun 2009
        • 91

        #4
        I had linked the sunos machine against a newly created template. This was
        not working somehow.

        Ok the hosts are now appearing, but the status is shown as unknown...

        Comment

        • r0k5t4r
          Member
          • Jun 2009
          • 91

          #5
          After a while the status was showing up. There seems to be a bit of delay when machines are monitored by a proxy.

          Comment

          Working...