There currently is a bug in Panorama (6.1.x), I'll try to explain it best I can.
Have a shared service-group and an address-group both with the SAME name. Each group is used on different Device Group (DG) policies, and each has at least one member that's not employed anywhere in the other DG's policy. Let me see if this helps...
The Panorama setting to share unused objects is NOT enabled (Panorama->Setup->Management->Panorama Settings::Share Unused Address and Service Objects with Devices).
When you commit to a DG1 device, Panorama incorrectly includes the service-group in the package BUT it does not include its members. So basically the ABCD service-group is sent to DG1, but not svc1. Since svc1 isn't being used anywhere in DG1's policy, validation fails with an invalid error.
So you can imagine scenario, converting a policy from a vendor that allows same name address and service groups, import that into Panorama and create conflicts to any existing DGs that might have the same name group. We've actually encountered this situation twice already in our shop.
Would like to see MT identify such conflicts when merging configs.
P.S. If you'd like, we can run a webmtg and show you what's going on. Ron Johns also has the details.
Do you have the bug id number from the ticket so we can track when the resolution shows up in the release notes?
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 Live Community as a whole!
The Live Community thanks you for your participation!