Ad Widget

Collapse

Discovery process time & subnet size...best practices?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Amber_Waves
    Junior Member
    • Sep 2021
    • 6

    #1

    Discovery process time & subnet size...best practices?

    I've created my first Zabbix instance and implemented an test discovery rule (for a single /24 subnet segment) just to validate that I can actually configure a function rule. My SNMP OID Discovery rule works fine but I now need to apply the Discovery rule out to all network subnets. My concern is how much processing time and network bandwidth will be consumed if I discovered a larger (e.g. /16 or /8) network? I would prefer to run Discovery every 24 hours but I could delay it to a maximum of 7 days...if necessary.

    I'm hoping someone can clarify the Discovery network resource consumption and let me know if there's a best practice for Discovery network subnet sizes? I'm willing to create multiple Discovery processes but I'm simply not sure what best practice might be for the Discovery maximium subnet size. Also, can I schedule the Discovery process to run during a non-peak time (e.g. 1am -5am)? I'll greatly appreciate any advise that anyone can provide!!! zz0.115l9fbj1y6zz​
  • Hamardaban
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • May 2019
    • 2713

    #2
    First of all - https://www.zabbix.com/documentation...work_discovery
    The network discovery is not fast (waiting for a response is regulated by a timeout in the server/proxy config) and all hosts and ports are sequentially searched.
    Therefore, even a network /16 scan with a single check will take a very long time.
    It is recommended to create separate rules on a network of size /24.
    The network traffic during the search is small.
    There is no execution schedule. only the launch frequency.
    Create a test rule and you will understand everything yourself.

    Comment

    • Amber_Waves
      Junior Member
      • Sep 2021
      • 6

      #3
      Thank You...I appreciate the clarifications!

      Comment

      Working...