<?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: More big problems with the Foritgate parser in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/more-big-problems-with-the-foritgate-parser/m-p/560145#M4750</link>
    <description>&lt;P&gt;Sure thing. It's on its way.&lt;/P&gt;</description>
    <pubDate>Sun, 01 Oct 2023 20:25:36 GMT</pubDate>
    <dc:creator>crose_mcnc</dc:creator>
    <dc:date>2023-10-01T20:25:36Z</dc:date>
    <item>
      <title>More big problems with the Foritgate parser</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/more-big-problems-with-the-foritgate-parser/m-p/560139#M4748</link>
      <description>&lt;P&gt;I am still having major issues with Expedition with the Fortigate configuration parser.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The last bug fix took care of some of the issues, but I have again reached a standstill where I have objects that can not be deleted. I didn't figure this out till after I spent hours manipulating this config to get objects into our engineering format. Now I am stuck. I am very behind on getting this migration done for my customer to everyone's frustration so I am desperate to get this fixed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think the import is still not working correctly. When I import the configuration I sent you, I get the following objects created in the "shared" vdom. But the objects contain self references. As an example the shared vdom service object group DNS contains mebers DNS and DNS as seen int he attached screenshot.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is this way also for the following list of protocols&lt;/P&gt;
&lt;P&gt;DCE-RPC&lt;/P&gt;
&lt;P&gt;DNS&lt;/P&gt;
&lt;P&gt;H232&lt;/P&gt;
&lt;P&gt;Kerberos&lt;/P&gt;
&lt;P&gt;L2TP&lt;/P&gt;
&lt;P&gt;NFS&lt;/P&gt;
&lt;P&gt;NTP&lt;/P&gt;
&lt;P&gt;PC-Anywhere&lt;/P&gt;
&lt;P&gt;RTSP&lt;/P&gt;
&lt;P&gt;SIP&lt;/P&gt;
&lt;P&gt;SNMP&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once I work through the configuration and clean things up I wind up with objects that can not be deleted and prevent me from finishing my cleanup and migration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can send you the config file again by way of a Palo support case or export backups of my project in expedition. I am running the most current hotfix.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anything you can do to get this moving again is greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Sun, 01 Oct 2023 20:06:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/more-big-problems-with-the-foritgate-parser/m-p/560139#M4748</guid>
      <dc:creator>crose_mcnc</dc:creator>
      <dc:date>2023-10-01T20:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: More big problems with the Foritgate parser</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/more-big-problems-with-the-foritgate-parser/m-p/560144#M4749</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/247856"&gt;@crose_mcnc&lt;/a&gt;&amp;nbsp;,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm sorry to hear about the issues you're encountering.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Could you please upload the latest original configuration along with your current Expedition project into a TAC case? Once you've done that, please send the TAC case number to&amp;nbsp;&lt;/SPAN&gt;&lt;A href="mailto:fwmigrate@paloaltonetworks.com" target="_blank"&gt;fwmigrate@paloaltonetworks.com&lt;/A&gt;&lt;SPAN&gt;. As I'm based in the CEST time zone, I'll take a look at it first thing tomorrow morning. It would be really helpful if you could also describe your execution workflow in your email. This way, I can check if there's a possibility of automating some of the steps you're currently doing manually.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I appreciate your understanding and cooperation in advance, and I apologise for any inconvenience caused.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;David&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 01 Oct 2023 20:24:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/more-big-problems-with-the-foritgate-parser/m-p/560144#M4749</guid>
      <dc:creator>dpuigdomenec</dc:creator>
      <dc:date>2023-10-01T20:24:28Z</dc:date>
    </item>
    <item>
      <title>Re: More big problems with the Foritgate parser</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/more-big-problems-with-the-foritgate-parser/m-p/560145#M4750</link>
      <description>&lt;P&gt;Sure thing. It's on its way.&lt;/P&gt;</description>
      <pubDate>Sun, 01 Oct 2023 20:25:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/more-big-problems-with-the-foritgate-parser/m-p/560145#M4750</guid>
      <dc:creator>crose_mcnc</dc:creator>
      <dc:date>2023-10-01T20:25:36Z</dc:date>
    </item>
  </channel>
</rss>

