06-16-2021 08:42 AM
Expedition ver 1.1.98
Case:
Migrating 2 ASA configs to single PA.
After cleanup on both ASA configs removal of dups and invalids. Merged the configs to the base config from a set of clean 3250's.
Generated .xml and set commands. Downloaded, imported and loaded.
Navigate to commit - validate receive the following errors:
vsys -> vsys1 -> service -> tcp-tacacs -> tag 'merged' is not a valid reference
vsys -> vsys1 -> service -> tcp-tacacs -> tag is invalid
vsys -> vsys1 -> service -> udp-tacacs -> tag 'merged' is not a valid reference
vsys -> vsys1 -> service -> udp-tacacs -> tag is invalid
vsys -> vsys1 -> service -> tcp-domain -> tag 'merged' is not a valid reference
vsys -> vsys1 -> service -> tcp-domain -> tag is invalid
vsys -> vsys1 -> service -> domain -> tag 'merged' is not a valid reference
vsys -> vsys1 -> service -> domain -> tag is invalid
To clear this issue I have to pull the pretty.xml from the .zip download and locate all of the tags for:
<tag>
<member>merged</member>
</tag>
From each service. Once this is completed save the new .xml and repeat the process to import, load and commit - validate
Validate comes back clean. Can now commit config and complete migration of ASA to PA.
Just an FYI for anyone who runs into the same issue. I am not positive if the "merged" tag originated because of the actual merge to base config or if this is a result of removing a tag that was being deprecated and then the merge generated the empty field "merged" for a placeholder.
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!
