In working with the panorama vcenter plugin, I've noticed unexpected results when panorama uses inherited ancestor address group objects when trying to pull vcenter tag matches.
It appears if the object is in the local device group, panorama populates dynamic tags, address objects into the group, and everything works.
When using inherited address groups (notify group is mapped to descendant), panorama will no longer populate the dynamic tags from vcenter, nor will it show the actual addresses. However, the firewalls still receive the mappings normally, and updates as expected. It makes it impossible to search/match when the address group is at a higher level, but if you get the matches right (manually type the vcenter path), it appears to populate the firewalls as expected.
Wondering if there is some mapping on the backend of panorama that isn't populating, or if the plugin is expecting everything to be at a single device group level?
Any feedback/experiences with this?
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!