Details

    • Improvement
    • Resolution: Incomplete
    • Major
    • None
    • Professional Edition
    • Default
    • None

    Description

      We're using Observium to collect data from Zyxel switch ( ES3148 ES2024A MES3528 ES2226 ES-2108G GS4012F)
      Unfortunately, there is no separation by Model switch / OS / Version OS / s/n /Featureset. All the listed switches are described as "ZyXEL ES Series" (right to talk about "ZyNOS").
      At the same time, it would be great to see CPU utilization, sensors monitoring (where possible). 
      But I was unable to get a complete dump from any device. Just in case I have attached some mib files. I hope they help.
      Thanks

      P.S. hmm ... it seems the site https://mibs.observium.org/ already contains these mibs, but are these mibs used?

      Attachments

        1. 10909172.discovery
          116 kB
          Yuri
        2. 10909172.poller
          219 kB
          Yuri
        3. GS2210.discovery
          9 kB
          Yuri
        4. GS2210.poller
          6 kB
          Yuri
        5. image-2021-09-16-23-53-08-884.png
          96 kB
          Yuri

        Activity

          [OBS-3869] improved support Zyxel switch

          Devices in this series have support for common ZYXEL-ES-COMMON, which already supported.

          But very old hardware (and old firmware) not support this MIB and use per model MIB schemas.

          We not have access or snmpdumps for such devices.

          landy Mike Stupalov added a comment - Devices in this series have support for common ZYXEL-ES-COMMON, which already supported. But very old hardware (and old firmware) not support this MIB and use per model MIB schemas. We not have access or snmpdumps for such devices.

          Added discovery PoE sensors in r11716.

          landy Mike Stupalov added a comment - Added discovery PoE sensors in r11716.
          uriby Yuri added a comment -

          Oops.. I dumped after I turned off the device in the observium. I think this is the case. besides, at the moment we have temporarily turned off such a switch. attached dumps another switch ( gs4012f)

          uriby Yuri added a comment - Oops.. I dumped after I turned off the device in the observium. I think this is the case. besides, at the moment we have temporarily turned off such a switch. attached dumps another switch ( gs4012f)

          The poll and discover you did didn't actually poll or discovery anything: 

          "WARNING: 0 devices polled. Did you specify a device that does not exist?"

          adama Adam Armstrong added a comment - The poll and discover you did didn't actually poll or discovery anything:  "WARNING: 0 devices polled. Did you specify a device that does not exist?"
          uriby Yuri added a comment -

          later I added a switch GS2210-24HP to monitoring. observium found sensors, processor, memory in this device (only fans were not found). the operating system is the same named "ZyXEL ES Series" (correctly ZyNOS), version os observium named "4.50" (correctly 4.50(AANE.4) ), serial number found but the inventory bookmarks did not appear, and it was not possible to find the device by serial number in the observium. I tried to get a full dump of this device and it seems to me that I succeeded

          I hope this will be useful for structuring zyxel devices in the observium

          uriby Yuri added a comment - later I added a switch GS2210-24HP to monitoring. observium found sensors, processor, memory in this device (only fans were not found). the operating system is the same named "ZyXEL ES Series" (correctly ZyNOS), version os observium named "4.50" (correctly 4.50(AANE.4) ), serial number found but the inventory bookmarks did not appear, and it was not possible to find the device by serial number in the observium. I tried to get a full dump of this device and it seems to me that I succeeded I hope this will be useful for structuring zyxel devices in the observium

          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files Note, this comment is added automatically.

          People

            landy Mike Stupalov
            uriby Yuri
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: