<?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 Re: Checkpoint nested address groups in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/250460#M1175</link>
    <description>&lt;P&gt;if possible can you share your config with the email alias fwmigrate@paloaltonetworks so a feature enhancement can be submitted to support the migration of the nested groups.&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/102804"&gt;@JonasVanGestel&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;We are busy converting a checkpoint (version R80.10) to palo alto, but when we upload our checkpoint configuration in expedition, we get a lot of errors like the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Group called 'abc' is missing this member UID: 97aeb3ba-..."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We figured out that these groupmembers are groups itself and in the exported json file, they are located below the creating of group abc.&lt;/P&gt;
&lt;P&gt;The problem is that the zone mapping is not correct anymore, since there are subnet's missing in the source zone, there are also missing source zones.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible to solve this (in an automated way, since we have a lot of nested groups)?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Jonas&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 19 Feb 2019 15:19:47 GMT</pubDate>
    <dc:creator>sjanita</dc:creator>
    <dc:date>2019-02-19T15:19:47Z</dc:date>
    <item>
      <title>Checkpoint nested address groups</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/250374#M1172</link>
      <description>&lt;P&gt;We are busy converting a checkpoint (version R80.10) to palo alto, but when we upload our checkpoint configuration in expedition, we get a lot of errors like the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Group called 'abc' is missing this member UID: 97aeb3ba-..."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We figured out that these groupmembers are groups itself and in the exported json file, they are located below the creating of group abc.&lt;/P&gt;
&lt;P&gt;The problem is that the zone mapping is not correct anymore, since there are subnet's missing in the source zone, there are also missing source zones.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible to solve this (in an automated way, since we have a lot of nested groups)?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Jonas&lt;/P&gt;</description>
      <pubDate>Mon, 18 Feb 2019 14:57:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/250374#M1172</guid>
      <dc:creator>JonasVanGestel</dc:creator>
      <dc:date>2019-02-18T14:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint nested address groups</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/250460#M1175</link>
      <description>&lt;P&gt;if possible can you share your config with the email alias fwmigrate@paloaltonetworks so a feature enhancement can be submitted to support the migration of the nested groups.&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/102804"&gt;@JonasVanGestel&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;We are busy converting a checkpoint (version R80.10) to palo alto, but when we upload our checkpoint configuration in expedition, we get a lot of errors like the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Group called 'abc' is missing this member UID: 97aeb3ba-..."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We figured out that these groupmembers are groups itself and in the exported json file, they are located below the creating of group abc.&lt;/P&gt;
&lt;P&gt;The problem is that the zone mapping is not correct anymore, since there are subnet's missing in the source zone, there are also missing source zones.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible to solve this (in an automated way, since we have a lot of nested groups)?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Jonas&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Feb 2019 15:19:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/250460#M1175</guid>
      <dc:creator>sjanita</dc:creator>
      <dc:date>2019-02-19T15:19:47Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint nested address groups</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/250461#M1176</link>
      <description>&lt;P&gt;if possible can you share your config with the email alias fwmigrate@paloaltonetworks so a feature enhancement can be submitted to support the migration of the nested groups.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Feb 2019 15:20:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/250461#M1176</guid>
      <dc:creator>sjanita</dc:creator>
      <dc:date>2019-02-19T15:20:07Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint nested address groups</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/250600#M1180</link>
      <description>&lt;P&gt;config has been sent to&amp;nbsp;'fwmigrate@paloaltonetworks.com'&lt;/P&gt;</description>
      <pubDate>Wed, 20 Feb 2019 08:47:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/250600#M1180</guid>
      <dc:creator>JonasVanGestel</dc:creator>
      <dc:date>2019-02-20T08:47:12Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint nested address groups</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/534124#M4476</link>
      <description>&lt;P&gt;Hello, I have exactly the same problem. Could you share what was the solution? Thanks, I need help.&lt;/P&gt;</description>
      <pubDate>Sun, 12 Mar 2023 14:53:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-nested-address-groups/m-p/534124#M4476</guid>
      <dc:creator>gtognola</dc:creator>
      <dc:date>2023-03-12T14:53:19Z</dc:date>
    </item>
  </channel>
</rss>

