04-07-2022 12:40 PM
04-07-2022 04:29 PM
Have you looked at the configuration and ensure that the address object was actually carried over in the configuration migration without issue? That object could have not been carried over in the configuration migration.
04-08-2022 06:19 AM - edited 04-08-2022 06:23 AM
Have you looked at the configuration and ensure that the address object was actually carried over in the configuration migration without issue?
It is like for like.
That object could have not been carried over in the configuration migration.
All objects were carried over and show in the UI. Its weird because I've had to replace or clone service/address/groups/objects and remove the original object and replace that in the various sec and nat policies then try to push it. I get a failure on the local firewall for objects that have already existed in previous code but are now unacceptable references and must be changed and when I clone the object whatever it is remove the old object add the new one to the old policies and push the firewall moves on to the next object. This is beyond tedious at this point.
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!
