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

Can't get FDB table from 3Com devices

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Poller

    Description

      I can't get FDB table from 3Com devices,

      Attachments

        1. image (1).png
          image (1).png
          14 kB
        2. unnamed.png
          unnamed.png
          44 kB

        Activity

          [OBS-4183] Can't get FDB table from 3Com devices

          snmpdump sent to you it's an 3Com4210

          arnoldo.vidal Arnoldo Vidal added a comment - snmpdump sent to you it's an 3Com4210

          Derp Vendors....
          Attach new snmpdump for 4210.

          landy Mike Stupalov added a comment - Derp Vendors.... Attach new snmpdump for 4210.

          thanks,

           

          Now works, but only on 3Com 4500, not on devices 3Com 4210 (with or without PoE)

          arnoldo.vidal Arnoldo Vidal added a comment - thanks,   Now works, but only on 3Com 4500, not on devices 3Com 4210 (with or without PoE)
          • rediscovery device(s)
          landy Mike Stupalov added a comment - Switch to rolling updates (not in stable): https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains rediscovery device(s)

          I updated to r12205 on a testing server, I have added 3Com and HP devices, only on HP i can find a mac-address

           
          Search-->FDB  tables... no 3Com devices, only HP

          arnoldo.vidal Arnoldo Vidal added a comment - I updated to r12205 on a testing server, I have added 3Com and HP devices, only on HP i can find a mac-address   Search-->FDB  tables... no 3Com devices, only HP

          Fixed in r12205.

          landy Mike Stupalov added a comment - Fixed in r12205.

          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 -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

          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 -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 This comment is added automatically.

          People

            landy Mike Stupalov
            arnoldo.vidal Arnoldo Vidal
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: