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

FortiGate 600F not correctly named

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery

    Description

      Hello,

      FortiGate 600F units are detected as

      Vendor/Hardware : Fortinet FortiGate 60

      Could you fix as

      Vendor/Hardware : Fortinet FortiGate 600F

      Thanks,

      Regards,

      Boris

      Attachments

        Activity

          [OBS-4460] FortiGate 600F not correctly named
          landy Mike Stupalov added a comment -

          Improved in r12620.

          landy Mike Stupalov added a comment - Improved in r12620.
          bpascault Boris PASCAULT added a comment -

          Hello Mike,

          You will find output logs below,

          FG600F_observium.log

          Thanks,

          Regards,

          Boris

          bpascault Boris PASCAULT added a comment - Hello Mike, You will find output logs below, FG600F_observium.log Thanks, Regards, Boris
          landy Mike Stupalov added a comment -

          Please make poller debug for this device:

          ./poller.php -d -r -m os -h <device>

          landy Mike Stupalov added a comment - Please make poller debug for this device: ./poller.php -d -r -m os -h <device>
          bpascault Boris PASCAULT added a comment -

          I have uploaded the latest FortiGate MIBS which contains 400F, 600F and some new models.

          bpascault Boris PASCAULT added a comment - I have uploaded the latest FortiGate MIBS which contains 400F, 600F and some new models.
          bpascault Boris PASCAULT added a comment -

          Sorry after a quick check, the latest MIB doesn't contains FortiGate 400F and 600F.

          bpascault Boris PASCAULT added a comment - Sorry after a quick check, the latest MIB doesn't contains FortiGate 400F and 600F.
          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
            bpascault Boris PASCAULT
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: