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

Fortiswitch Memory Data not Presented

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Alerting, OS
    • Fortinet Fortiswitch running latest observium professional version (20.11.10814 (stable))

    Description

      Hi all,

      We've been experiencing an issue where all of our Fortinet Fortiswitches are not able to display memory data on the Observium web GUI.

       

      1.Fortinet Fortiswtich MIB is enabled in OBS and memory data is included.
      2. They're able to report traffic, CPU usage, temperature, and port information.
      3. Only Fortinet switches have this issue in our environment, fortigates are fine. (screenshot attached)
      4. Running version 20.11.10814 (11th November 2020), so official support is present.
      5. Googled around and couldn't find someone reporting this issue.
      6. Tested snmpwalk from the OBS box to one of the switches and it's able to report back memory usage and total capacity as well as all other memory MIBs. (screenshot attached)

      Based on the what I've tested it seems it's a display issue with OBS, has this been reported before?

       

      Let me know if you need anymore info.

       

      Chris

      Attachments

        1. fortiswitch_mib_installed.png
          fortiswitch_mib_installed.png
          28 kB
        2. image-2021-02-25-13-43-50-032.png
          image-2021-02-25-13-43-50-032.png
          13 kB
        3. image-2021-02-25-13-44-33-642.png
          image-2021-02-25-13-44-33-642.png
          39 kB
        4. image-2021-02-25-14-10-13-799.png
          image-2021-02-25-14-10-13-799.png
          14 kB
        5. obs_fortiswitch_mib.PNG
          obs_fortiswitch_mib.PNG
          84 kB
        6. obs_fortiswitch_os.PNG
          obs_fortiswitch_os.PNG
          55 kB
        7. obs_memory_issue.PNG
          obs_memory_issue.PNG
          25 kB
        8. obs_snmpwalk.PNG
          obs_snmpwalk.PNG
          43 kB

        Issue Links

          Activity

            [OBS-3526] Fortiswitch Memory Data not Presented
            landy Mike Stupalov added a comment - you on stable.. switch to rolling: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

            Yup I updated it about an hour and a half ago, it's been polled since then

             

            Kristofen Chris Evans added a comment - Yup I updated it about an hour and a half ago, it's been polled since then  

            for memory really should be fixed after next poll..

            landy Mike Stupalov added a comment - for memory really should be fixed after next poll..

            Hi Mike,

             

            I've just updated Observium to r11052 but no luck, I've also tried to rediscover the device to test.

             

             

             

            Kristofen Chris Evans added a comment - Hi Mike,   I've just updated Observium to r11052 but no luck, I've also tried to rediscover the device to test.      

            Cheers Mike.

             

            I'll get it updated and will report back.

            Kristofen Chris Evans added a comment - Cheers Mike.   I'll get it updated and will report back.

            Seems as should be fixed after r11052.
            Check please.

            landy Mike Stupalov added a comment - Seems as should be fixed after r11052. Check please.

            Hi, what's the status on this?

            We have the same issue on our Fortiswitches aswell on above versions and a some below/above aswell.

            gmad_invid Gustav Madeland added a comment - Hi, what's the status on this? We have the same issue on our Fortiswitches aswell on above versions and a some below/above aswell.

            Hi Adam,

            Thanks for getting back to me.

            All of the devices having the issue are Fortinet FortiSwitches:

            248E-POE
            448D
            124E-POE

            Running a mixture of the following versions:

            Fortinet FortiSwitch 6.4.2
            Fortinet FortiSwitch 6.4.1
            Fortinet FortiSwitch 6.2.1

            I've attached another two screenshots to the ticket. One being the MIB with OID's that we have installed and what models/OS's we're running.

            Thanks again.

            Chris

            Kristofen Chris Evans added a comment - Hi Adam, Thanks for getting back to me. All of the devices having the issue are Fortinet FortiSwitches: 248E-POE 448D 124E-POE Running a mixture of the following versions: Fortinet FortiSwitch 6.4.2 Fortinet FortiSwitch 6.4.1 Fortinet FortiSwitch 6.2.1 I've attached another two screenshots to the ticket. One being the MIB with OID's that we have installed and what models/OS's we're running. Thanks again. Chris

            What's the OS / sysObjectID for these devices?

            adama Adam Armstrong added a comment - What's the OS / sysObjectID for these devices?

            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.

            • 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

            Note, this comment is added automatically.

            bot Observium Bot 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. 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 Note, this comment is added automatically.

            People

              landy Mike Stupalov
              Kristofen Chris Evans
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: