Troubleshooting FAQs

Q.	Why does it take a longer time to parse?
A.	If the ASA configuration file size is large, then it takes longer time to parse. Your ASA's running configuration file must be less than 4.5 MB and 22,000 lines. For more information, see Confirming ASA Running Configuration Size.

Q.	What must I do when I find parsing errors during migration?
A.	Refer to the Review Migration Report and Review Migration Logs for the error details.

Q.	I am encountering parsing errors during migration. How do I fix them?
A.	Navigate to the Migration page, click Download Logs, for the specific device and fix the errors.

Q.	I get conversion errors during FTD template generation. What must I do?
A.	Navigate to the Migration page, click Workflows for the specific device to view the errors.

Q.	What to do when an FTD template is created with errors?
A.	If your FTD template is created with validation errors, you can search for the FTD template in the Devices & Services page. Click Workflows from the Devices Actions pane where you can view the error details.

CDO fails to write to the change log. Why?

When you onboard an ASA to CDO, CDO stores copy of the ASA's running configuration file in its database. Generally, if that running configuration file is too large (4.5 MB or larger), or it contains too many lines (approximately 22,000 lines), or there are too many access-list entries for a single access group, CDO will not be able to predictably manage that device. For more information, see Confirming ASA Running Configuration Size.

You can also contact your Cisco account team for help to safely reduce the size of your configuration file without disrupting your security policies.

Q.	Does CDO validate the syntax of the ASA configuration file before it migrates?
A.	No. CDO does not validate the syntax of the ASA configuration file before it migrates it to an FTD template. If you are trying to migrate an ASA model that you have onboarded to CDO, and the migration fails, review the migration report and review the migration log in the FTD migration screen. You may need to verify the syntax of the configuration file.