To understand why the CPU is used by system item, we can use the command “ debug system ps“. Using keyboard-interactive authentication.īad terminal type: "xterm". In our case the CPU is occupied with a system item (currentrly 51%) and by user (currently 47%).
For instance, if CPU time would have been spent on “softirq” it would have mean that the CPU was occupied with traffic load. To analyze the problem, it is therefore necessary to connect to the Zywall via SSH.Īs explained on the Zyxel support webpage, we can use the command line “debug system show cpu status” to see the CPU usage details. Unfortunately the ZyWALL graphical interface does not give more details about the use of resources and does not allow to see what the processor or memory resources are used for. Processor consumption at nearly 100% Problem analysis Logging into the ZyWALL USG GUI, we quickly saw that the processor resources were being used at over 90%. In this case it was a ZyWALL USG 50 firewall. Thanks to UDITIS, we were able to quickly isolate the problem and understood that it came from the firewall. As shown below, the pings performed sometimes went up to more than a hundred milliseconds, Pinging 8.8.8.8 with 32 bytes of data The performance problems resulted in very slow access to a remote system.
Users first reported sporadic access problems and then these problems became permanent. Introductionįrom one day to the next, network performance deteriorated. Are you experiencing performance problems with your Zyxel ZyWALL USG firewall? You will find in this blog an example of a real case I faced and how I solved it.
0 kommentar(er)
