Firepower Migration Tool - Config file size limits and socket errors

[toormehdi]

Hi there,

@Aditya Ganjoo  

s there a workaround to the size limit the Firepower migration tool has for configuration file upload? It says the limit is 1MB. For multi-context the requirement is to upload "show tech" which in our case is currently 7MB with just over 60 contexts. 

If I attempt to do via live connection to ASA, it eventually times out while gathering the multi context config info. See below

2023-08-05 10:43:39,473 [INFO | device_connection_utils.py] > LiveConnect:Multi Context Supported.
2023-08-05 10:43:39,475 [INFO | asa_server_model.py] > Persisting server
2023-08-05 10:43:39,529 [INFO | connect_asa.py] > Multi Context Collected Successfully
2023-08-05 10:44:06,365 [INFO | asa_server_model.py] > Persisting server
2023-08-05 10:44:06,373 [INFO | asa_server_model.py] > Persisting server
2023-08-05 10:44:06,398 [DEBUG | common.py] > session table records count:1
2023-08-05 10:44:06,418 [INFO | device_connection_utils.py] > LiveConnect:Connecting the ASA remote device
2023-08-05 10:44:10,561 [INFO | device_connection_utils.py] > LiveConnect:Successfully Connected to Remote Device
2023-08-05 10:44:10,562 [INFO | device_connection_utils.py] > LiveConnect:Connection is Alive
2023-08-05 10:44:10,563 [INFO | device_connection_utils.py] > LiveConnect:Executing context check: sh mode

2023-08-05 10:44:14,569 [INFO | device_connection_utils.py] > LiveConnect: Started gathering the context
2023-08-05 10:44:14,570 [INFO | device_connection_utils.py] > LiveConnect:Connection is Alive
2023-08-05 10:44:14,571 [INFO | device_connection_utils.py] > LiveConnect: Extracting multi context config
2023-08-05 10:59:14,676 [ERROR | device_connection_utils.py] > LiveConnect: Socket is closed
2023-08-05 10:59:14,678 [ERROR | connect_asa.py] > Error In Connecting To Device - Please Check The Logs

[hemohemoh]

hey @toormehdi,

Will it solve if you split your “show tech” file into smaller files that are less than 1MB in size and upload them separately?

[toormehdi · Accepted solution]

Thanks. It seems the limitation only exists in demo mode. The normal mode doesn’t seems to error out and it went ahead and processed the entire show tech in one shot. Unfortunately this isn’t documented and I struggled for few days. Hope this helps. 

[balaji.bandi]

glad all good and able to resolve the issue.

[balaji.bandi]

How about for testing only 1 Context and see if that works as expected - before move to next level ?

How much time does the Secure Firewall migration tool take to successfully migrate a configuration?
A.	The time that is taken during migration depends on numerous factors like latency on network, load on the management center, config size, number of objects, ACL, and so on. In internal testing, it was observed that a config file of 2.0 MB with 7000+ Access Control List, 7000+ NAT Translations, and 3000+ Network Objects takes around 6 minutes to successfully complete the migration.