Ad Widget

Collapse

SNMP DIscovery Action not Working

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bharned
    Junior Member
    • Aug 2024
    • 9

    #1

    SNMP DIscovery Action not Working

    New to Zabbix. Trying to replace my PRTG with it.

    I setup a quick server and installed Zabbix for testing. Created a discovery rule to find network switches, using SNMPv3 checks. My discovery action will use one of the checks to look for a value and then add it as a host. This worked.

    Created a new server for production and created the discovery rules and actions exactly the same. Initially only 8 devices were found. Thinking I did something wrong, I reverted my server back to pre-Zabbix installation and reinstalled. Now no devices are being found.

    The only difference between my test server and production server is the subnet it is on. I know the switches are accessible from the new subnet as I've tested with an SNMP tester as well as snmpwalk on the Zabbix server.

    Any assistance would be greatly appreciated.

    Click image for larger version

Name:	image.png
Views:	1298
Size:	37.8 KB
ID:	493839Click image for larger version

Name:	image.png
Views:	1182
Size:	16.6 KB
ID:	493840Click image for larger version

Name:	image.png
Views:	1187
Size:	11.1 KB
ID:	493841
  • bharned
    Junior Member
    • Aug 2024
    • 9

    #2
    To add some more information, believing that it might be a firewall issue, I moved my installation to the same network as the devices I am trying to discover but that still did not work.

    Using the same credentials, I am able to add a device individually but not through discovery.

    I was using macro variables for the username and password, but have since replaced them with static values

    Comment

    • bharned
      Junior Member
      • Aug 2024
      • 9

      #3
      Here's some more follow up, in case anyone is able to help.

      I found some more tutorials about SNMP discovery and one of them included showing a tcpdump of snmp packets to verify devices are responding.

      Code:
      tcpdump -n -s0 port 161 and udp
      After running the command, and recreating my discovery rule, again, I did indeed see that devices were responding to the SNMP request, but still only 7 devices show up in Monitoring>Discovery. No errors show in the server log either.

      Click image for larger version  Name:	image.png Views:	0 Size:	55.7 KB ID:	494266

      Comment

      • bharned
        Junior Member
        • Aug 2024
        • 9

        #4
        For those of you keeping up, I added SNMPv2 to a test switch I have, and created a discovery rule using that community. This test was successful. The problem is we cannot use anything but SNMPv3 due to security protocols.

        For some S&Gs, I created another discovery rule, only for my test switch, using SNMPv3. And it was discovered.

        I've cleared the cache before and recreated the original rule with a long update interval, but the rule never would find anything new.

        ANY help will be appreciated.

        Comment

        • bharned
          Junior Member
          • Aug 2024
          • 9

          #5
          Bumping.

          Anyone with any thoughts?

          Comment

          • cyber
            Senior Member
            Zabbix Certified SpecialistZabbix Certified Professional
            • Dec 2006
            • 4807

            #6
            I have one thought... you may not like it... Ditch that discovery and add your devices manually (or over API from your cmdb, if you happen to have one...)

            Comment

            • bharned
              Junior Member
              • Aug 2024
              • 9

              #7
              Originally posted by cyber
              I have one thought... you may not like it... Ditch that discovery and add your devices manually (or over API from your cmdb, if you happen to have one...)
              That is probably what I will end up doing. It's just frustrating and odd how it worked on my PoC and not the production system.

              Comment

              Working...