Discovery rules are working and hosts which are matching ip range and running zabbix agents are getting discovered but actions are not getting applied. Since version 2.2.3, Zabbix uses GetNextRequest-PDU for low-level discovery on SNMPv1 devices and GetBulkRequest-PDU for SNMPv2 and SNMPv3 devices, because GetBulkRequest-PDU was introduced in SNMPv2. Powered by a free Atlassian Jira open source license for ZABBIX SIA. !Remember to restart the zabbix_server after you have edited the file.!!! XML Word Printable. Actions created for every discovery rule to assign discovered devices to host groups, all actions are similar with . Steps to reproduce: Host network discovery is done by Zabbix active proxy. This is using for the hostname as well. First, we need to install the FPING package to enable Zabbix to perform ICMP checks. In Trigger prototype, choose a name, then click Add and Select prototype. Even the server receives the discovery data correctly: 12278:20120703:140537.757 In substitute_key_macros () data:'net.if.discovery'. Log In. I have a .130.x range that is working fine, but a .120.x range that is not working. For some reason, the discovery rule isn't working, returning the message "Cannot obtain object's localized name" instead of any disk . I can't see any errors on the items since they are not present (e.g. After a successful login, you will be sent to the Zabbix Dashboard. I have setup 3 Auto discovery rules and none of them seem to be working correctly. . Create db.odbc.discovery rule to discover some data from Sybase DB with the query. Create item prototype to make items by discovery; Result: Discovery runs without errors, but items has not being created. It seems that suddently it stopped discovering Network Interfaces and all are lost from my Windows Hosts. On the dashboard screen, access the Configuration menu and select the Discovery option. Delete the # in front of StartDiscoverer. I noticed that the OS Linux/Windows Templates already have the filesystem discovery built in. In log I can see messages: Authentication failure (incorrect password, community or key). No errors in the server logfile. I followed the instructions from the blog on setting up a network device discovery rule using snmp. Administrators. sudo apt-get install snmp sudo apt-get install snmp-mibs-downloader i did setup zabbix same problem i couldnt get discovery while with green snmp then i found i needed to install those. Monitoring -> Discovery reports multiple hosts as discovered and up for each discovery rule. Posted by 4 years ago. On the Host discovery configuration screen, you will have to enter the following information: Working on network discovery with Ubnt PBE-M5/5AC CPEs using "Template Net Ubiquiti AirOS SNMPv1" for M5 CPEs and "Template Net Ubiquiti AirOS SNMPv1-Prism" for 5AC CPEs. How can we troubleshoot this? . Inside logs i am seeing two discovered hosts related errors. Up to version 2.2.2, Zabbix used GetNextRequest-PDU for low-level discovery. Installed version is Zabbix 2.2 in Linux Centos 6.4. Created May 2, 2012. It relies on deprecated functionality. Creating triggers from low-level discovery is very simple. Both zabbix-server and zabbix-agent is v3.0.2 I have a problem with discover any hosts and discovery rules don't working with zabbix agent and snmp configuration. My understanding is that its supposed to list all the different FS and the respective names in Latest Data, but all I am getting is: "Free disk space on / " etc. Phy discovery works great as well as "Mounted filesystem discovery". Windows disk discovery not working. On the top right of the screen, click on the Create discovery rule button. Export. 1. We'll also need our Zabbix server. We've just migrated to a new Zabbix server (4.4 -> 6.2); almost all of it is working beautifully, with the exception of physical disk discovery on two of our Windows hosts. Reinstalled the script with a fresh and clean one (same error).Checked and confirmed all the data works (IP's and credentials). From the manual it says that discovery is the first part and then an action can take place. Same behaviour for filesystems. ! Yes the failing lua UserParameter command was my initial suspicion on why the agent does not work on LEDE. Rebooted the server multiple times. On the Host discovery configuration screen, you will have to enter the following information: Steps Tried: Tried updating Windows Powershell V5.1 to the higher build, but cant find an update or install file. !!! It does not just not work -- it sometimes can pull the data, but the next round it fails.. this is what items list looks like, some items are OK, some are failed. Tried PS7 with no success. Then I create action for automatic registration of discovered hosts. Selecting item prototype. Filesystem Discovery not working So I'm new to Zabbix and wanted to get into LLD. Windows service discovery exclusions not working. Set it to StartDiscoverer=1. I have created the discovery rule gave it an ip range and added snmp check using 1.3.6.1.2.1.1.5. Please provide the output of the following command: zabbix_agentd -V. Arturs Lontons added a comment - 2021 Feb 18 00:46. Ex. To get started with network discovery, we are going to need a host that we can monitor with SNMP. Resolution: Fixed . no items for eth0). In our example, the FPING program was found at: Next, we need to edit the Zabbix server configuration file and enable the ICMP monitor feature. Type: Incident report Status: Closed. Discovered hosts are not getting added inside zabbix for monitoring. We then head to Configuration>Discovery Rules and set the ip range as 192.168..1-192.168..254 (or /24.. or /22). This is the Zabbix server interfac. Hello, I'm currently running Zabbix 5.4 in an Ubuntu 20.04 Server VM. Check SQL query for discovery in isql in zabbix user shell, all work good. Attachments Zabbix . I have even tried graphic design software creating new discover rules and that isn't working. Zabbix is Open Source and comes at no cost. For Discovery checks, I have checks on device name, which contains the model of radio. I have the same templates used before, I see the Zabbix raw data created by the net.if.discovery Key but they are not created afterwards in the Items. Top posts may 23rd 2018 Top posts of may, 2018 Top posts 2018. help Reddit coins Reddit premium. Now it not working My discovery looks like this: IP Range: 172.20.205.1-255. Try Jira - bug tracking software for your team. Multiple discovery rules defined for different networks. Template is imported and assigned to Host, but descovery rules gets status "Not supported" and "Value should be a JSON object" as info message. When they are found they are then added to the inventory. When we specify singular explicit IP,s like 192.168..4, 192.168..22, 192.168..176. FirstLast-PBE-5AC-GEN2. sit0 does not report any problem. Priority: Major . After a successful login, you will be sent to the Zabbix Dashboard. Closing due to lack of activity. On the dashboard screen, access the Configuration menu and select the Discovery option. I used the preconfigured actions to add discovered machines with a zabbix client installed. But discovery rules doesn't seem to work. Join. I am facing an issue with my Zabbix system, v5.0.7. 10. Zabbix discovers the nodes I want. We check the SNMPv3 agent for the OID by hostname. It takes 3 queries. On the top right of the screen, click on the Create discovery rule button. If you don't know how to set up a host such as this, check out the Working with SNMP monitoring recipe in Chapter 2, Setting up Zabbix Monitoring. Not working auto discovery in proxy. I see their uptime in Monitoring - > Discovery. I presently have working discovery rules and action setup to scan an ip range and find hosts. service.discovery in Zabbix returns a JSON array of all current running services (based on filters) for each host. 6.0k. Your problem seems to be that the device does not support . This has been working great and from what I can tell still is. 2. I'm having an issue with my Zabbix 3.4.13 setup. If that is commented out then it will not discover hosts. The snmpstatus works correctly in all hosts and zabbix server I have these iptables rules configured in the Firewall: During test I have changing rules of discovery and host registration, then delete all discovered hosts from web-interface to see how it will works with new rules. Use the WHICH command to find out the FPING program location. Everything is configured the same for the two ranges in discovery, and if I add a host manually from the .120.x range it is working fine. Expected: Items has been successfully created. If you want to create a new trigger prototype, go to Configuration > Hosts > Discovery rules, click Trigger prototypes and Create trigger prototype. Details. We also need to take note of the FPING program location. The problem is that it's randomly failing to get its data. Online. I would like to create a template hierarchy where i have a parent template that contains the service.discovery LLD service, and than add this template to child templates that will extract the respective data that they need for their particular role, Skype, MySQL, Antivirus and so on. Close. On your Zabbix server there is a setting in the /etc/zabbix/zabbix_server.conf file that has to do with StartDiscoverers. SNMP Discovery Rule not working. Let's double check the version of the Zabbix agent. The issue I'm seeing is there are system in the Monitoring--Discovery listing that . OpenWrt Forum [Solved] Zabbix server can't discover LEDE interfaces.