| ♥ 0 |
 All of a sudden this switch is showing very high memory usage. top – 10:21:04 up 3:29, 2 users, load average: 0.21, 0.36, 0.32 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND —— Uptime: 10 hours and 38 minutes |
|
When you say “all of a sudden” what exactly do you mean? Have you seen this switch using less memory for a long time, and then suddenly the state of the memory usage changed, or do you mean that you just noticed that it appears to be using a lot of memory? In fact the system is not using much memory. Notice that your “show version” output shows 2.5MB free out of 4. The top output is showing different numbers because of the way UNIX uses memory. The UNIX kernel will maximize memory usage because memory is expensive. If the user processes on the system don’t need the memory, the kernel will fill up the memory with buffers and file caching. Notice the two numbers at right side of the memory output in top: 208,096 buffers and 2,298,888 cached. That’s 2.5MB of memory used by the kernel. If a user process needs the memory the kernel will release it and allocate it to the user processes. The output from “show version” is taking that into account and only showing you the actual user process memory being consumed. In other words, this is not a problem, this system is operating normally. |
|
|
I would suggest reading the following EOS Central articles which explains more details regarding memory handling on Linux/EOS. https://eos.arista.com/introduction-to-managing-eos-devices-memory-utilisation/ Hope this helps. |
|
|
Yes, it was using less memory around 750xxx to 700xx range normally and the behavior is consistent across the network. I have 2 switches at every pop (4 pops). 2 weeks ago I created MLAG with TOR switches nothing major has changed since then only added some VXLAN configs (these are all vxlan evpn nodes). 2 switches stopped forwarding this morning and had to be rebooted, after the reboot the memory starts decreasing gradually. Currently its 162448 and with this rate it may crash again. Anything related to Security Advisory 0037? |
|
|
Hi Aftab. Sorry to hear about the issues you have experienced. I would suggest to open a support ticket with Arista TAC (support@arista.com) in order to collect additional information and investigate this further. |
|
|
attached the file |
Post your Answer
You must be logged in to post an answer.
After a reboot the buffers and cache would be cleared, so for several hours/days after reboot the memory will be used by the kernel when it’s not needed by the agents. So again, that sounds like normal behavior, but certainly if the agents are continuing to use up memory that isn’t getting released that could be a more serious issue.
I suggest you open a case with TAC so they can investigate the logs and determine the cause of why the switch stopped forwarding.