Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3337

Add support for NEC/Nera radio equipment

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Discovery
    • None

    Description

      Hi.

      NEC / Nera equipment is added as generic device.

      Can you please add support for this devices.

       

      Attached full snmp-dump.

       

      I dont have MIB files (yet), but hopefully I'll get them soon..

      Attachments

        Activity

          [OBS-3337] Add support for NEC/Nera radio equipment

          Updated now. First impression is good! The device itself behaves strangely, but I can monitor the most critical parameters like radio RX levels.

          I also have some Ceragon links that I would love to add support for radio RX/TX levels as well.

          I will create a new ticket for that.

          Stoffen Christoffer Smørås added a comment - Updated now. First impression is good! The device itself behaves strangely, but I can monitor the most critical parameters like radio RX levels. I also have some Ceragon links that I would love to add support for radio RX/TX levels as well. I will create a new ticket for that.

          Added basic support in r10903.

          I should say:

          • derp MIBs (seem as incomplete and not very described)
          • derp device snmp output.. really it is a great waste of time to understand what was meant in data.
          landy Mike Stupalov added a comment - Added basic support in r10903. I should say: derp MIBs (seem as incomplete and not very described) derp device snmp output.. really it is a great waste of time to understand what was meant in data.

          There doesn't seem to be much in the way of the standard "easy" things we collect. There's a lot of messy stuff it takes a lot of work to collect, but there's likely not enough interest in these devices for that.

          adama Adam Armstrong added a comment - There doesn't seem to be much in the way of the standard "easy" things we collect. There's a lot of messy stuff it takes a lot of work to collect, but there's likely not enough interest in these devices for that.

          Thats a fair question.. I will get back to the vendor and see if they can do some sort of proper SNMP implementation on the device.. 

          I guess the provided MIBs does not provide us with a doable workaround?

          Stoffen Christoffer Smørås added a comment - Thats a fair question.. I will get back to the vendor and see if they can do some sort of proper SNMP implementation on the device..  I guess the provided MIBs does not provide us with a doable workaround?

          How do you get to be the person in charge of building the SNMP stack for a network device, but not know you need to implement ifTable?

          adama Adam Armstrong added a comment - How do you get to be the person in charge of building the SNMP stack for a network device, but not know you need to implement ifTable?

          The walk doesn't seem to include ifTable. Can you try to walk ifTable and see if you get any data?

          adama Adam Armstrong added a comment - The walk doesn't seem to include ifTable. Can you try to walk ifTable and see if you get any data?

          MIB attached

          Stoffen Christoffer Smørås added a comment - MIB attached

          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community>  --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> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --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
            Stoffen Christoffer Smørås
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: