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

Fortiswitch wrong values for memory and temperature.

Details

    • Vendor Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • Fortiswitch versions:
      6.4.4
      6.4.5
      6.2.5

    Description

      We're monitoring a couple of Fortinet switches in Observium running different firmwares and have the same issue on all

       

      Used memory is in TB which is wrong, looks correct doing a snmpwalk (attached). This makes the graph not drawable, for example we're having a switch showing 49,2TB/7,79GB.

      Temperature is showing to low, for example 4,3 Degrees Celsius instead of the correct value of 43 Degree Celsius. 

      On the Fortigates everything seems correct.

      Attachments

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. OBS-3526 Fortiswitch Memory Data not Presented

          • Major - Major loss of function.
          • Resolved

          Activity

            [OBS-3658] Fortiswitch wrong values for memory and temperature.
            landy Mike Stupalov added a comment -

            re-discovery again please..

            landy Mike Stupalov added a comment - re-discovery again please..
            gmad_invid Gustav Madeland added a comment -

            Hi Mike!

            The memory seems to be polling correct now, thanks for that.

             

            Temperature sensors are still a bit off tho, see picture.

            Correct values are:

            38

            47

            46

            36

            gmad_invid Gustav Madeland added a comment - Hi Mike! The memory seems to be polling correct now, thanks for that.   Temperature sensors are still a bit off tho, see picture. Correct values are: 38 47 46 36
            landy Mike Stupalov added a comment -

            Fixed in r11052.

            landy Mike Stupalov added a comment - Fixed in r11052.
            gmad_invid Gustav Madeland added a comment -

            Hi Mike.

            Files attached, I've also linked this ticket to "OBS-3526".

            [^FS1048E.snmpwalk]

            [^FORTINET-CORE-MIB-build1803.mib][^FORTINET-FORTISWITCH-MIB (1).mib]

            gmad_invid Gustav Madeland added a comment - Hi Mike. Files attached, I've also linked this ticket to " OBS-3526 ". [^FS1048E.snmpwalk] [^FORTINET-CORE-MIB-build1803.mib] [^FORTINET-FORTISWITCH-MIB (1).mib]
            landy Mike Stupalov 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.

            • additionally attach device and/or vendor specific MIB files
            landy Mike Stupalov 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. additionally attach device and/or vendor specific MIB files

            People

              landy Mike Stupalov
              gmad_invid Gustav Madeland
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: