I have seen this happen though I cannot explain it. The workaround is to create a new Address Group with the correct name and members, edit the NAT policy to use the new AG, then delete the old Address Group.
It seems editing an Address Group used in a NAT policy is now frowned upon with a generic error.
Answers
I have seen this happen though I cannot explain it. The workaround is to create a new Address Group with the correct name and members, edit the NAT policy to use the new AG, then delete the old Address Group.
It seems editing an Address Group used in a NAT policy is now frowned upon with a generic error.