topic Re: Import format issue in Expedition Discussions

Import format issue

rodill — Fri, 14 Feb 2020 14:30:39 GMT

I am importing rules from a Cisco 5585 ASA in prep to move to a 5260. I have noticed that when I go through the log file from the ASA trying to clean up the objects starting with invalid characters or edit objects that exceed 31 characters that I have issue with what is imported. Example is I import 220 lines based on the count in ultra edit and Expedition shows 60 security policies. Is there a certain format that the text in the log file has to be? Anything I can check prior to import?

Re: Import format issue

dgildelaig — Mon, 17 Feb 2020 08:24:57 GMT

Are you 100% sure that you are not altering the format for the file?

I would suggest that you do not clean the original ASA configuration as Expedition has already a few controls and name corrections in place that may do this work for you.

Also, there would be less changes that while cleaning, you misplace a quote or similar making part of the configuration invalid.

If it still fails this way, let us know and we will try to identify the characters that are bothering and give support for them in Expedition.

Our goal is that you need to do 0 cleaning on the configuration file besides any standard approach that the vendor may specify.

Re: Import format issue

rodill — Mon, 24 Feb 2020 14:41:32 GMT

if there is an object group that begins with a - that is an invalid field, it will fail an api call to load it. If you manual import the config, you can bring it up but if you try to commit it, it will error out and possible reboot the palo. The 220 I have for testing has been doing this. If a name is over 31 characters this will cause another error. I have not seen anything in expedition that seems to re-mediate these issues. A reason that manual editing needs to be done on coming from the Cisco ASA is that I have to split the zones on the firewall into different vsys per the design that was implemented. I have also discovered that if have a rule to an ip address that has a nat that the rule in expedition becomes to the nat while that is not how a cisco asa works. That was confusing to find.

Re: Import format issue

dgildelaig — Mon, 24 Feb 2020 15:28:24 GMT

Could you put as an email regarding the NAT issue to fwmigrate@paloaltonetworks.com?

I would like to check that with you to improve the logic in Expedition.

Regarding the invalid objects, doesn't Expedition filter you those objects as invalid? We have a feature to, for instance, add a prefix on all selected objects, which you could use to alter their names starting with whatever you want instead of the "-".

However, out of curiosity, is this a valid naming in Cisco?

Re: Import format issue

rodill — Mon, 24 Feb 2020 16:35:09 GMT

sent the email with examples.

expedition does not filter, only shows unused and used on the object tab. I only found the error on export attempts.

that is a valid format in the cisco asa.

if you test and make a new object with a - you get a message telling that it must start with alphanumeric and can contain 0 or more alphanumeric characters, underscore, hyphen, dot, or spaces. So it has to start with a letter or number. I don't see a way to correct the 31 character limit or the - beginning.

Re: Import format issue

dgildelaig — Tue, 25 Feb 2020 10:23:41 GMT

We will make a release today that will catch those address objects as invalid, so you can spot them and apply the global Prefix addition.

Thanks for letting us know