About Jamiefitzgerald

Jamiefitzgerald · ‎05-01-2012

One way to do this today is to create a rule that only applies between 8am and 6pm and then create a report on that rule.

Jamiefitzgerald · ‎04-26-2012

Appweb3 is our internal webserver. It is normal for this process to hit 100% CPU. This is responsible for making all data displayable. 4.1 increased the number of threads this process could spawn which can increase the CPU % but should help speed up the UI. Thank you, ~Jamie Fitz-Gerald

Jamiefitzgerald · ‎04-19-2012

Report area of the disk is not configurable and differs per platform. The reports partition is quite large, and is self managed by the device. You can check your report partition by running the following command from the CLI: show system disk-space PA-200> show system disk-space Filesystem Size Used Avail Use% Mounted on /dev/sda2 1.9G 1.2G 661M 64% / /dev/sda5 6.6G 3.4G 2.9G 55% /opt/pancfg /dev/sda6 1.9G 1.1G 775M 58% /opt/panrepo tmpfs 1.3G 67M 1.2G 6% /dev/shm /dev/sda8 2.4G 712M 1.6G 32% /opt/panlogs

Jamiefitzgerald · ‎04-19-2012

You can do a high level csv export of the (app eq unknown-tcp) and (zone.dst eq sample.com) and (receive_time in last-24-hrs) and then use a spreadsheet application to complete the rest of the filtering.

Jamiefitzgerald · ‎04-17-2012

Chris it is planned to be corrected in the next Panorama release.

Jamiefitzgerald · ‎04-13-2012

Some things that will increase your commit times are high logging rates, high log forwarding to panorama, sysloging all logs, large number of rules, large number of objects. If you can reduce your logging by being more selective on exactly what you need to log, reduce the nubmer of rules and focusing on application based rules, reducing the number of objects, and reducing your log forwarding will all help reduce your commit time. I hope this helps, ~Jamie

Jamiefitzgerald · ‎04-12-2012

JoChristian, I would suggest you open a case. This sounds like you are experiencing something that should be looked into by support. Thank you, ~Jamie

Jamiefitzgerald · ‎04-12-2012

My suggestion is not upgrade because of commit performance. You should upgrade for a feature needed in your network or a bug fix that could not be back ported to 3.1. On the performance of commit, it depends on your configuration. In many cases the commit time will go down when upgrading to 4.1, but it may not change the commit time at all. I hope this helps.

Jamiefitzgerald · ‎04-04-2012

In 4.1 if you type https://<ip address>/API, you can see a full list of support API commands. https://<ip address>/php/rest/browse.php

Jamiefitzgerald · ‎03-28-2012

Today, this is seen as detailed information that is better served from the detailed logs. This could be a valid feature request to add the URL information to the ACC to a future release. Please contact your SE and ask them to file a feature request on the behalf of your company.

Jamiefitzgerald · ‎03-28-2012

The behavior you described is working as designed. The workflow that you are looking to achieve can be accomplished by looking at the top destinations or by clicking on the link at the top of the ACC page to jump to the URL logs. See the attached images...

Jamiefitzgerald · ‎03-27-2012

CLI guide: https://live.paloaltonetworks.com/docs/DOC-2032 Here is a quick run through: Download the image. SCP the image: scp import software from username@host:/Users/username/Desktop/PanOS_200-4.1.4.tgz List the image: debug swm list Install the image: debug swm install image-name Reboot: request restart system These are quick notes, I am sorry that I did not have time to double check this, but this should get you going. Thank you

Jamiefitzgerald · ‎03-27-2012

Was this a manual file upload or a download from the update server? What browser were you using? There is a known bug with Firefox and manual upgrades. If you use a different browser, this should work with 4.1.3 and above. There is a work around as well which is to use the CLI. I hope this helps.

Jamiefitzgerald · ‎03-21-2012

Once you add too many columns to a report, the report starts to get cutoff. We are addressing this issue and there will be a change in behavior in future releases to grow the page as you add columns. Another option is to export the report in CSV. This will guarantee that the report will not be cutoff.

Jamiefitzgerald · ‎03-21-2012

We are constantly working to improve the UI speed. 4.0.9 fixed some memory leaks and improved commit times for many customers with large rule-bases. The 4.1 release has been received by the customer community as being faster in terms of UI responsiveness. We made some improvements to the way the pages load, caching, and leaned the code-base. We will continue to work on making the UI as snappy as possible.

Member Since	‎06-02-2011 02:50 PM
Date Last Visited	‎07-21-2021 07:08 PM
Posts	142
Total Likes Received	27

Online Status	Offline
Date Last Visited	‎07-21-2021 07:08 PM

About Jamiefitzgerald

Re: Slack

SOC Duck

Re: Replace a device (s/n) in Panorama Policy with an RMA s/n

Re: Custom Reports takes ages

Re: Report creating Question

Re: REST API and HA

Re: Custom Reports takes ages

Re: Custom Reports takes ages

Re: What am I gonna do? (delete language.txt)

Re: Email scheduler and Report names

SOC Duck

Re: Negative experience from PA/PAN?

Re: SNMP OID's

Re: Possible solution to slow commit

Re: qos or what?

SOC Duck

Re: Daily Report from 8am to 6pm

Re: what is the processor named webapp3?

Re: How long are keept scheduled report

Re: Filter length

Re: Firefox11 log details not showing up

Re: PA-2050 commit frustration

Re: PA-5020 4.1.5 issue

Re: PA-2050 commit frustration

Re: Is there a list of type & action for the xml api?

Re: ACC Not displaying drop-down boxes when filtering is applied

Re: ACC Not displaying drop-down boxes when filtering is applied

Re: PA 5050 Upgrade to 4.1.X

Re: PA 5050 Upgrade to 4.1.X

Re: Cutoff Reports

Re: slow GUI

Seattle Hardware Beta

Seattle Beta

Unlock your full community experience!

About Jamiefitzgerald