Ad Widget

Collapse

Monitoring Netgear ReadyNAS using zabbox

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pietro1685
    Junior Member
    • Oct 2021
    • 4

    #1

    Monitoring Netgear ReadyNAS using zabbox

    Firstly, three apologies:
    1. This is my first post to the Zabbix forum
    2. I'm still very much a beginner with Zabbix
    3. I don't know a lot about SNMP, MIBs etc
    I am using Zabbix to monitor my home systems, 3 x Raspberry Pis, a shuttle, two PCs and a laptop - all Linux. Also a Netgear WNDR4500 router running DD-WRT firmware. These are all successfully monitored using zabbix_agent

    I also have two Netgear ReadyNAS 214s, running 6.10.5 firmware, which I would like to monitor.

    I have imported the template from https://github.com/a-schild/zabbix - one problem with this is that the instructions say "Enable SNMP on the device(s) and set a password". SNMP is certainly enabled on the two ReadyNASs, but I can see no way to enable a password on them.

    I have checked that all the SNMP OIDs mentioned in the template return the appropriate details using snmp_walk

    When I add the ReadyNASs to Zabbix, specify SNMP for the interfaces, and assign the template, the status shows up as "enabled". I see that there are 8 "items", but these show as "Status: Not supported", 6 of the items have "Info:" like the following: snmp_parse_oid(): cannot parse OID "SNMPv2-MIB::sysContact.0"

    For nasMgrSoftwareVersion and nasMgrSerialNum, the info is like: SNMP Error: (noSuchName) There is no such variable name in this MIB.

    As I said above, I checked that all the OIDs in the template were correct using snmp_walk.

    As a side issue, I also get

    root@piacenza:~# zabbix_get -s nas -p 161 -k agent.ping
    zabbix_get [22970]: Get value error: cannot connect to [[nas]:161]: [111] Connection refused
    root@piacenza:~# zabbix_get -s nas2 -p 161 -k agent.ping
    zabbix_get [1803]: Get value error: cannot connect to [[nas2]:161]: [111] Connection refused

    Can anybody suggest what I am doing wrong?

    Thanks in advance.

    Best wishes -- Peter





  • pietro1685
    Junior Member
    • Oct 2021
    • 4

    #2
    Thanks for responding

    If "agent.ping" is not appropriate for SNMP, what what be the appropriate zabbix_get syntax for querying *something* from a host using SNMP? (If this can be done)

    I downloaded the MIB file from the nas, and using a MIB browser, I checked that all the OIDs in the template are correct. And they return relevant information when queried using snmpwalk. For example

    root@piacenza:~# snmpwalk -v1 -c public nas 1.3.6.1.4.1.4526.22.3.1.10.1
    iso.3.6.1.4.1.4526.22.3.1.10.1 = INTEGER: 40 (which is a disk temperature, and matches what I see in the NAS web browser view.

    And that is the correct OID is seen in both the MIB browser and the template file.

    So as far as I can tell, all the information in the template file correctly matches what is available from the NAS.

    Thanks again.

    Best wishes -- Peter

    Comment

    • pietro1685
      Junior Member
      • Oct 2021
      • 4

      #3
      So snmpwalk etc is fine - and it confirms that I have the right OIDs and that the ReadyNAS is returning data that I can check against the device's GUI.

      And the OIDs match what is in the Template file.

      Also, in the "Monitoring>Hosts" view, the two NAS devices show as SNMP/Green and Status/Enabled, which suggests to me (with admittedly minimal understanding of Zabbix internals) that the Zabbix server has connected to the NASs via SNMP.

      But still no data, and the error messages from the previous posts when I look at the "items" in the configuration.

      Can anybody suggest any debugging hints on how to get a handle on where the problem lies?

      Thanks

      Best wishes -- Peter

      Comment

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

        #4
        Green is good, means zabbix was able to poll some data. But I still cannot help you with debugging......

        Comment

        Working...