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

[21.12.11831] Arista RAM statistics

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Discovery, Web Interface
    • None
    • Various EOS versions, such as Arista EOS 4.23.3M & Arista EOS 4.25.5M

    Description

      Since upgrading to 21.12.11831 it seems that the RAM statistics under Memory for Arista don't work well. RAM is now showing 0B/0B. Also, it seems that less statistics are available.

      A device just after upgrading to the new release (where RAM is already showing 0B/0B):

       

      After removing and adding the device again during polling:

      Note that here it does show RAM data here.

       

      And when the polling is done:

       

      Here it's 0B/0B again and as you can see there are less statistics then before.

       

      Note: I tried to do this in another browser and incognito mode, so it's not cache related for sure.

       

      Could you fix this?

      Attachments

        Activity

          [OBS-3985] [21.12.11831] Arista RAM statistics
          timvanderleedenadjust Tim van der Leeden added a comment -

          I've updated and all looks fine ! Sorry for the delay in adding the logs, but I guess you found out what was wrong without them thanks!

          timvanderleedenadjust Tim van der Leeden added a comment - I've updated and all looks fine ! Sorry for the delay in adding the logs, but I guess you found out what was wrong without them thanks!
          landy Mike Stupalov added a comment -

          Should be fixed in r11848.

          landy Mike Stupalov added a comment - Should be fixed in r11848.
          landy Mike Stupalov added a comment -

          yes, make new poller/discovery debugs exactly for this broken devices.

          landy Mike Stupalov added a comment - yes, make new poller/discovery debugs exactly for this broken devices.
          timvanderleedenadjust Tim van der Leeden added a comment -

          Thanks! It seems that it works again for this specific and other Arista devices:

           

          But for a set of Aristas it seems that it also broke something:

          Could you maybe check that ? Do you need new logs for it?

          timvanderleedenadjust Tim van der Leeden added a comment - Thanks! It seems that it works again for this specific and other Arista devices:   But for a set of Aristas it seems that it also broke something: Could you maybe check that ? Do you need new logs for it?
          landy Mike Stupalov added a comment -

          Fixed in r11846.

          List of "RAM" memory pools was correct (should be only single RAM entry), this is how Arista report their memory: https://eos.arista.com/memory-utilization-on-eos-devices/

          But polling was little broken, now should be fixed (but currently only in rolling channel).
          You can switch temporary to Rolling or wait for next Stable sync:
          https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

          landy Mike Stupalov added a comment - Fixed in r11846. List of "RAM" memory pools was correct (should be only single RAM entry), this is how Arista report their memory: https://eos.arista.com/memory-utilization-on-eos-devices/ But polling was little broken, now should be fixed (but currently only in rolling channel). You can switch temporary to Rolling or wait for next Stable sync: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains
          timvanderleedenadjust Tim van der Leeden added a comment - - edited

          [^poller.out]

          [^discovery.out]

          timvanderleedenadjust Tim van der Leeden added a comment - - edited [^poller.out] [^discovery.out]
          landy Mike Stupalov added a comment -

          Please attach discovery/poller debugs as Bot requested.

          landy Mike Stupalov added a comment - Please attach discovery/poller debugs as Bot requested.
          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
            timvanderleedenadjust Tim van der Leeden
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: