We'd love to hear about it! Click here to go to the product suggestion community
We have 2 XGs in HA mode (a/p) based on SG210 hardware. SFOS 17.5.4 is installed. Both systems are up since 14 days now. Memory util is stable at 37%, cpu util is somewhere between 3% and 14%. It sometimes increases to 20%. System util is just below 4.0 (whatever that means).
The performance icon on the dashboard shows up in orange color but I don't really know what's the problem. Where can I take a look at? Didn't have this during the last 18 months.
From what I understand, the system utilisation number is a reference to how much load is currently hitting the appliance across all of its services and daemons. Generally the load number can be kind of referenced against each full number being equivalent to a CPU core. So if you have a load of 4, it is expected you are regularly hitting 4 CPU cores worth of processing.
The performance being amber could be because your load has dramatically increased recently so the amber status is because it is warning of a sudden change. Have you made any config changes recently?
In reply to EmileBelcourt:
No, the last changes where about some exclusions regarding HTTPS scanning and they were made before the last restart.
From my understanding such a warning like you described should have the possibility to acknowledge it. When will the performance indicator switch back to green?
I currently don't see anything I can do. Even if most people are offline and there is little traffic it still shows up.
In reply to Jelle:
have you had a look at the diagnostics tab -> system graphs?
That shows the system load, then look at top to see which of the applications are running high utilisation.
In reply to rfcat_vk:
I don't see somethng regarding applications there?
And the graphs about cpu, memory, disk, users, zones and ports look good. It's only the system util at an average of 3.75 of 5. Whereever that comes from.
i was talking about running top in the system console. Something appears to stuck from that load graph.
Something seems to be wrong with these worker processes.
now you have found the cause, lets us hope Emile has another look and can provide some assistance.
Could you take a screenshot of an atop from the CLI for me, (just "atop").
You could put a atop Logging in the background.
(There is not atop, so you will put the atop logging into the background).
atop -w /tmp/log/atop.log 5 &
Keep in Mind, this will run "forever" or until the next reboot / takeover.
Read the atop log and get a overview over your spikes. This atop command will write a snapshot each 5 seconds.
This Load is the "Linux Load".http://www.brendangregg.com/blog/2017-08-08/linux-load-averages.html