Ad Widget

Collapse

Auto-Discovery

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Villain
    Member
    • Aug 2006
    • 84

    #1

    Auto-Discovery

    I'm not sure if I understand how the auto-discovery is supposed to work. I have turned it on for a subnet that has several 1.1 agents installed. Do these agents need to be upgraded to 1.4 for them to be seen by the server?

    Also, is there a way to cover a class B subnet? If so, how would I do that? We run a 10.2.0.0/8 subnet internally, and I would like to start including all of my Windows clients as part of the Zabbix reporting. To do that, I would like ot auto-discover them by name (not IP address), to avoid duplicates being created on a DHCP client network. Is this possible?

    Thanks
  • StanZoid
    Member
    • Oct 2005
    • 47

    #2
    Villain:

    I am running everything from 1.4 to 1.0beta5, and I can discover them by checking for TCP port 10050. Sorry, no joy on the second question...

    Stanzoid

    Comment

    • zombiehunter
      Member
      • Jun 2007
      • 31

      #3
      no joy?

      Does this mean that it's just not possible to monitor class B nets? We support a few businesses that have class B. Not having available monitoring for them wouldn't really be an option. I'm trying to get 1.4 setup on debian now (tried last week to compile our own but kept getting failures and mysql issues.) and I'm hoping i'm not wasting my time. Maybe I should start looking at Zenoss?

      Comment

      • Villain
        Member
        • Aug 2006
        • 84

        #4
        You can monitor them just fine.. the new auto-discovery features are where I had questions. I have been monitoring a couple class B networks with no issues, I just wanted to work with the new features and wasn't sure how they would handle it.

        Comment

        Working...