How to see real memory allocated in firewalls

[Apadilla]

Hello community, 

Currently I have a couple PA-200 with high cpu and memory. The process that is consuming high cpu is the pan_task. I know this process is related to thread analizys. 

I need to know what is the best command to show the real memory allocated by each process.

I see the memomy for each process with the command  >show system resource follow.  

But I need to know if exist another command , because my monitoring tool is taking the values from ´top tool ´ (show system resource) to check the health system,  and every day the monitoring tool is opening tickets due to these couple PA-200 are working  over 90% your memory.

So, I need your help to know,  if exist another command with more accurate values.

Best Regards

Andres

[TranceforLife]

Hi,

l think values are accurate but unfortunately l am not aware of any other (alternative) command. Do you think you can "tune" that sensor so it will be warning you at let's says 95%? What is your monitoring tool?

Thx,

Myky

[Apadilla]

Hello Myky, 

We use Nagios to monitoring all our firewalls. currently our nagios open a ticket as alerm when the firewall memory is over 90%.

The memory values nagios extracted from >show system resources results.

Best regards

Andres Padilla 

[Apadilla]

Sorry, 

I forgot mention the firewall are running PANOS 7.0.9

[TranceforLife]

pan_task always will be high. Maybe other members will be able to advice.

[reaper · Accepted solution]

That's where the big difference between the PA-200's architecture and the larger platforms comes in

pan_task is actually the packetprocessing daemon and will always try to pre-load available resources to max (to improve performance)

on the larger platforms it runs on the dataplane so will not be visible in show system resources (as it 'lives' in running , you can see it through > less dp-log dp-monitor.log on the larger platforms ... show system resources only shows management plane resources)

on the pa-200 there is one single 'plane' (hardware) that is split up through software, so daemons share one hardware space