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

Meraki MR44 Not Recognized

Details

    • Add New Device / OS
    • Resolution: Unresolved
    • Minor
    • None
    • CE-22.5
    • OS

    Description

      I just replaced my Meraki MR36 and MR42 APs with MR44's and Observium recognizes them as generic devices.

      Attachments

        1. discover.rtf
          43 kB
        2. myagent1.snmpwalk
          0.1 kB
        3. myagent-1.snmpwalk
          14 kB
        4. poller.rtf
          81 kB

        Activity

          [OBS-4564] Meraki MR44 Not Recognized
          landy Mike Stupalov added a comment -

          Hrm, but os correctly detected..

           o OS Type              meraki-ap
          		 
           o OS Group             meraki

          landy Mike Stupalov added a comment - Hrm, but os correctly detected.. o OS Type meraki-ap o OS Group meraki
          TyShawn Sean Woods added a comment -

          Files have been uploaded

          TyShawn Sean Woods added a comment - Files have been uploaded
          TyShawn Sean Woods added a comment -

          Can we put this back into waiting for me and I can add the files sorry for the delay.

          TyShawn Sean Woods added a comment - Can we put this back into waiting for me and I can add the files sorry for the delay.
          TyShawn Sean Woods added a comment -

          [^myagent.snmpwalk]

          Here you go

          TyShawn Sean Woods added a comment - [^myagent.snmpwalk] Here you go
          adama Adam Armstrong added a comment -

          No walk

          adama Adam Armstrong added a comment - No walk
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 This comment is added automatically.

          People

            adama Adam Armstrong
            TyShawn Sean Woods
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: