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

Cant see the hardware type for Fortinet devices in newer versions

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • None
    • Default
    • None

    Description

      I cant see the fgmodel mib at observium

      The hardware showing empty

      The observium version is 

      22.8.12250 (16th August 2022)

      Attachments

        Activity

          [OBS-4227] Cant see the hardware type for Fortinet devices in newer versions
          landy Mike Stupalov added a comment - - edited

          I need to see extra information about device.
          Please attach as minimum debug for poller:

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

          landy Mike Stupalov added a comment - - edited I need to see extra information about device. Please attach as minimum debug for poller: ./poller.php -d -h <device>
          Shama Tarek added a comment -

          Did you have a chance to look into it?

          Shama Tarek added a comment - Did you have a chance to look into it?
          Shama Tarek added a comment -

          Its taking ages to collect these files, i started with the first one, it had more than 319K rows, i had to stop it

          If you can send me the exact mib for the hardware that its showing empty when running the poller that would be great.

          I looked at https://mibs.observium.org/mib/FORTINET-FORTIGATE-MIB/ and i dont see the model that we are using which is 1800F, maybe that is the problem? 

           

          Shama Tarek added a comment - Its taking ages to collect these files, i started with the first one, it had more than 319K rows, i had to stop it If you can send me the exact mib for the hardware that its showing empty when running the poller that would be great. I looked at https://mibs.observium.org/mib/FORTINET-FORTIGATE-MIB/ and i dont see the model that we are using which is 1800F, maybe that is the problem?   
          landy Mike Stupalov added a comment -

          It's unknown issue.

          Please attach information requested by Observium Bot above.

          landy Mike Stupalov added a comment - It's unknown issue. Please attach information requested by Observium Bot above.
          Shama Tarek added a comment -

          Is this a known issue?
          Let me know if you need any information from my end

          Shama Tarek added a comment - Is this a known issue? Let me know if you need any information from my end
          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.

          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
            Shama Tarek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: