<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Vcenter plugin, Notify Groups, Inherited address objects, and matching in VM-Series in the Private Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-private-cloud/vcenter-plugin-notify-groups-inherited-address-objects-and/m-p/507484#M59</link>
    <description>&lt;P&gt;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.&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It appears if the object is in the local device group, panorama populates dynamic tags, address objects into the group, and everything works.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp; &amp;nbsp;However, the firewalls still receive the mappings normally, and updates as expected.&amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;BR /&gt;Any feedback/experiences with this?&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jun 2022 18:08:21 GMT</pubDate>
    <dc:creator>Sec101</dc:creator>
    <dc:date>2022-06-30T18:08:21Z</dc:date>
    <item>
      <title>Vcenter plugin, Notify Groups, Inherited address objects, and matching</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-private-cloud/vcenter-plugin-notify-groups-inherited-address-objects-and/m-p/507484#M59</link>
      <description>&lt;P&gt;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.&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It appears if the object is in the local device group, panorama populates dynamic tags, address objects into the group, and everything works.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp; &amp;nbsp;However, the firewalls still receive the mappings normally, and updates as expected.&amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;BR /&gt;Any feedback/experiences with this?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 18:08:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-private-cloud/vcenter-plugin-notify-groups-inherited-address-objects-and/m-p/507484#M59</guid>
      <dc:creator>Sec101</dc:creator>
      <dc:date>2022-06-30T18:08:21Z</dc:date>
    </item>
  </channel>
</rss>

