About sjanita

sjanita · ‎08-11-2019

As a workaround can you add the device after the project has been created. This seems to be an issue with the currenrt release.

sjanita · ‎08-11-2019

can you describe in detail the specific setting or configuraation in the template stack you are making that is not saving.

sjanita · ‎08-11-2019

Does the VM have internet access? As part of the installation process, the scripts need to download packages from internet based servers. If a proxy is used in your network you must then configure the ubuntu server to redirect its internet requests to your web proxy.

sjanita · ‎08-07-2019

The html files by default are in the exported package and do not cause an issue with the migration of the files. Can you post the output from the file: $tail -f /tmp/error

sjanita · ‎08-06-2019

Try importing the .tar.gz file that had been generated. The import of the files does not have to be in zip format.

sjanita · ‎08-05-2019

Hi, migration of cyberroam configurations are not currently supported by the Expedition migration parsers. You can contact your Palo alto Networks professional services partner for assistance with your migration.

sjanita · ‎07-16-2019

ok I know the field you are looking to filter on. I will submit a FR.

sjanita · ‎07-16-2019

the current version 1.1.28 support policy names up to 63 characters which is the max supported by PanOS 8.0, 8.1 and 9.0.

sjanita · ‎07-16-2019

To clarify are you looking for a filter to isolate NAT policies that are configured to NAT using an address-type of 'Interface' Or are you looking for a filter for a source interface if configured?

sjanita · ‎07-09-2019

MFA is not fully supported in the current release as far as I know. The current RADIUS/LDAP implementations are not capable of passing an additional token for auth but will verify.

sjanita · ‎07-09-2019

There are certainly improvements that need to be made to the CSV import specifically for import of NAT policies using CSV. The current supported field mappings are described in the link below. The current CSV for NAT does not support the interface option as a field mapping. https://live.paloaltonetworks.com/t5/Expedition-Articles/A-How-To-guide-on-the-Import-CSV-option/ta-p/258388

sjanita · ‎07-08-2019

Hello Expedition Community, The process to install and deploy Expedition has been changed by offering an installable script that can be used to deploy onto your own instance of Ubuntu 16.04 LTS. Cloud and On-Prem Ready The changes in the Expedition installation provides greater flexibility allowing users to deploy Expedition on-prem onto their local hyper-visor or onto a cloud compute resource in AWS, Azure, and Google Cloud. The attached document describes the OS requirements (Ubuntu 16.0.4) and recommend compute resources. Download and read the attached Expedition installer guide. To get started with your Expedition installation, download the Expedition installer script: https://conversionupdates.paloaltonetworks.com/expeditionInstaller.tgz Additional Information Download and follow the use case examples in the available Expedition Admin Guide and Technotes: https://live.paloaltonetworks.com/t5/Expedition-Articles/Expedition-Documentation/ta-p/215619 Ask questions in the Expedition Community https://live.paloaltonetworks.com/t5/Expedition-Discussions/bd-p/ExpeditionDiscussions

sjanita · ‎07-04-2019

@kenvizena can you export project file and email to fwmigrate @ paloaltonetworks.com for debugging.

sjanita · ‎07-04-2019

can you create a new project, import the panorama config again and let me know if you are ablew to see the policies in the new project? i'm trying to narrow the issue to a global issue with your Expedition or something that may be specific to the project.

sjanita · ‎07-04-2019

we are moving the hosting to the Expedition files to a different hosting provider. the links to download will be corrected in the next few days.

sjanita · ‎07-03-2019

You have to process the traffic logs from the actual device and cannot process the log files from Panorama. This was a change in behavior to address internal changes.

sjanita · ‎07-03-2019

this is due to a change in default behavior - introduced in 1.1.24 - choosing 'All' displays all policies from all DG's for example.

sjanita · ‎07-03-2019

I can reproduce the issue you described. I will open a report for review.

sjanita · ‎07-03-2019

yes collapsing a multi-vsys into a single vsys configuration is a use case for Expedition. Think of Expedition as a PanOS configuration editor. After importing the 2 configurations you can then use Expedition to move objects from one configuration to the other. In your use case you will want to set the single VSYS config as your base configuration (where you are moving configurations to). Prior to starting the recommendations is to have a design in mind. For example, when you collapse the multi-vsys config into a single vsys, you will want to consider design options to include: -if both vsys are layer-3, will you be collapsing to a single VR or use multi-VR's in the single vsys config. -will you be consolidating VLAN's onto a single trunk -will some interfaces be combined into same zones there are many other design considerations, but its recommended to have a design goal prior to starting.

sjanita · ‎07-03-2019

Also, how much memory and CPU's have you made available to the Expedition VM? Can you check the output from the file below also: expedition@Expedition : ~ $ cd /home/userSpace/ expedition@Expedition : /home/userSpace $ cat environmentParameters.php <?php define ('NumCPUs',3); define ('TotalCPUs',4); define ('SparkRAM','4743m'); expedition@Expedition : /home/userSpace $

sjanita · ‎07-03-2019

Can you post the output from the error file: $cat /tmp error

sjanita · ‎07-03-2019

Will look into it and get back to you.

sjanita · ‎06-30-2019

try adjusting the permissions on the '/PALogs' on your Expedition server. $sudo chmod -R /PALogs Try the scheduled log export test again.

sjanita · ‎06-28-2019

we had resolved this issue by applying an update to the latest version

sjanita · ‎06-27-2019

A few feature added in the ver 1.1.9 release is the identification of "Ghost" objects which may require special handling based on the configuration file sources. What are "Ghost" objects Ghost objects are temporary address objects (address objects only) that were learned from the migration of the Security and NAT policies. The ghost objects are displayed under OBJECTS > Address along with a new counter in the project dashboard. The attached document provides background information on what causes ghost objects and how to mitigate them within a configuration. This document will discuss the following topics: What are Ghost objects Handling of Ghost objects

sjanita · ‎06-27-2019

When seeing counters increment for Duplicated Policies, this is indicating there are policies with the exact same name, which can cause a conflict within PAN-OS and cause a commit to fail. The Duplicated Policies do not indicate an overlap or "Shadow" of policies. The duplicated policy count can be seen in the PROJECT STATISTICS dashboard. To view the policies with duplicated names you can use the filter by creating a filter for: POLICIES > Security > FILTER > MERGE > POLICIES > Security Policies > Click the box for Rule Name Clicking on each case listed in the results will display the policies with the same name in the background. The policies displayed in the backgroud can be edited to change the names.

sjanita · ‎06-27-2019

I've worked with other ASA 9.x config files and I see the NAT's being migrated. what version of expedition are you running? if not version 1.1.25 I suggest updating then trying the import and migration again. To update: $sudo apt-get update $sudo apt-get install expedition-beta

sjanita · ‎06-25-2019

go ahead and send an email to fwmigrate 2 paloaltonetworks.com and we can schedule a time to run the debug on the query. Please reference this discussion when sending the email.

sjanita · ‎06-24-2019

are you running Expedition on your laptop/local machine and accessing the cloud based Panorama via the VPN? this connection should not cause an issue. The important connection is with Panorama connecting to the Cortex data lake to query the traffic log.

sjanita · ‎06-21-2019

with Cortex, you must use the app-ID adoption Fast option. The app-ID adoption slow option is not currently supported.

Date Registered	‎05-01-2009 04:59 PM
Date Last Visited	‎08-11-2019 11:49 PM
Total Messages Posted	237
Total Likes Received	48

Online Status	Offline
Date Last Visited	‎08-11-2019 11:49 PM

Strata

Prisma

Cortex

About sjanita