Generating Schedules vsys/dg:vsys1 merge hanging for a specific firewall conversion

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Generating Schedules vsys/dg:vsys1 merge hanging for a specific firewall conversion

L1 Bithead

HI - we are trying to migrate from a Cisco ASA to PA5250 at a large datacentre. When running the config through expedition it hangs on the merge step - last output displayed is "Generating Schedules vsys/dg:vsys1"

 

Note: we have migrated successfully using expedition about 10 other sites so far so this is our first major hiccup.


See below errors from the logs - anyone able to help determine what our next steps are?

 

Warning: simplexml_load_string(): Entity: line 6: parser error : Opening and ending tag mismatch: entry line 1 and schedule-type in /var/www/html/libs/common/xml/panosxml.php on line 1691

Warning: simplexml_load_string(): </schedule-type> in /var/www/html/libs/common/xml/panosxml.php on line 1691

Warning: simplexml_load_string(): ^ in /var/www/html/libs/common/xml/panosxml.php on line 1691

Warning: simplexml_load_string(): Entity: line 7: parser error : Extra content at the end of the document in /var/www/html/libs/common/xml/panosxml.php on line 1691

Warning: simplexml_load_string(): </entry> in /var/www/html/libs/common/xml/panosxml.php on line 1691

Warning: simplexml_load_string(): ^ in /var/www/html/libs/common/xml/panosxml.php on line 1691

Warning: get_class() expects parameter 1 to be object, boolean given in /var/www/html/libs/xmlapi.php on line 1838
object(SimpleXMLElement)#88 PHP Fatal error: Un
Fatal error: Uncaught Exception: Wrong type of input parameters, expected SimpleXMLElement key:value: in /var/www/html/libs/xmlapi.php:1857
Stack trace:
#0 /var/www/html/libs/common/xml/panosxml.php(1693): SimpleXMLElement_append(Object(SimpleXMLElement), false)
#1 /var/www/html/bin/configurations/output/output_function.php(293): xml_schedules(Object(SimpleXMLElement), Array, Array)
#2 /var/www/html/bin/configurations/output/output_function.php(25): generate_xml(Array, '3')
#3 {main}
thrown in /var/www/html/libs/xmlapi.php on line 1857

 

 

define ('NumCPUs',1);
define ('TotalCPUs',2);
define ('SparkRAM','1592m');

 

userDefinitions.php

define ('PARSER_max_execution_time','10000');
define ('PARSER_max_execution_memory','1G');
define ('DBSQL_LOG_BIN',0);

6 REPLIES 6

L4 Transporter

Hello @Nathan_Klym 

 

What version of expedition are you using? Also when it says you are using schedules, are you using schedules on your firewall policy rules?

We are running Expedition 1.1.91 currently.

 

I am not familiar with either our ASA or current PA configuration using schedules. Is there somewhere I can look in the config to confirm this? Will just search for schedules to see manually as well.

Hello @Nathan_Klym 

 

Try updating to the latest version of expedition and attempt to merge it again, if it doesn't work then send an email over to fwmigrate@paloaltonetworks.com and we can perform a session. The latest version of expedition is on 1.2.2 so you are few revisions behind.

OK - just upgraded to 1.2.2 and will try again. Will let you know, thanks!

L1 Bithead

Update - we are now able to merge the config and export the new xml. I found the scheudle area and deleted the objects.

 

All items came across except for the remapped interfaces, re running expedition again to see if we made a mistake during that steps.

 

 

Hello @Nathan_Klym 

 

Thanks for the update!

  • 3079 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!