Import configuration process stuck due to memory exhausted

Printer Friendly Page
Did you find this article helpful? Yes No
No ratings

Symptoms

When Importing either PAN-OS configuration or 3rd party vendor configuration, the import progress bar stuck in the middle without throwing any errors. 

 

Diagnosis

All migrations in Expedition 1 leave traces for debugging in the error file located in /tmp/error. Below we present an example of an error that could be reported on a migration: 

 

Screen Shot 2020-10-22 at 12.45.26 PM.png

In this specific case, the migration parser could not complete due to a limit amount of RAM allowed to be used in the migration process (Allowed memory size of 4GB exhausted)

Solution

Fortunately, this is RAM limit simple to handle.

In your Expedition WEBUI, go to "Settings" -> "CUSTOM PARAMS", increase the allowed RAM ("PARSER_max_execution_memory") to a larger value without exceeding your VM RAM. If you have 16G RAM in your expedition VM, you could change the value up to "16G"  as shown in the below screenshot below. Notice that in most of the cases, your configuration won't be as large that becomes necessary to allocate such a large amount of "Allowed RAM". For most scenarios, 4GB should be enough, therefore try allocating 6GB or 8GB until your migration can be completed.

 

Screen Shot 2020-10-26 at 1.40.39 PM.png