<?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: Fortigate 5.6.X migration -&amp;gt; QoS policies and DSCP marking missing in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/fortigate-5-6-x-migration-gt-qos-policies-and-dscp-marking/m-p/349317#M2967</link>
    <description>&lt;P&gt;Hi Lychiang,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Think we all agree that QoS policies are of paramount relevance when planning and implementing a migration. Being able to convert these using Expedition will significantly increase the value provided by this tool to all its users &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking forward to seeing this new feature added soon. What´s the ETA for this new development?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Sep 2020 11:03:29 GMT</pubDate>
    <dc:creator>HonoAl</dc:creator>
    <dc:date>2020-09-15T11:03:29Z</dc:date>
    <item>
      <title>Fortigate 5.6.X migration -&gt; QoS policies and DSCP marking missing</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/fortigate-5-6-x-migration-gt-qos-policies-and-dscp-marking/m-p/349166#M2964</link>
      <description>&lt;P&gt;Hi Community,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently working on a Forti to Palo migration. To my surprise, after uploading the current Forti´s configuration to the Migration tool, I noticed that the QoS polices had not been converterd//were missing. Also, the Forti, within the "config firewall shaper traffic-shaper" section does some "set diffservcode X" for some of the "firewall shaper traffic-shaper" polcies, which are not available within the new Palo Alto configuration-&amp;gt; security policies (where DSCP is configured).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyone know why these 2 problems are occurring and how could they be fixed?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;HonoAl&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2020 16:20:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/fortigate-5-6-x-migration-gt-qos-policies-and-dscp-marking/m-p/349166#M2964</guid>
      <dc:creator>HonoAl</dc:creator>
      <dc:date>2020-09-14T16:20:32Z</dc:date>
    </item>
    <item>
      <title>Re: Fortigate 5.6.X migration -&gt; QoS policies and DSCP marking missing</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/fortigate-5-6-x-migration-gt-qos-policies-and-dscp-marking/m-p/349185#M2965</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/155472"&gt;@HonoAl&lt;/a&gt;&amp;nbsp;, Those two sections of the Fortinet configuration won't get converted automatically in the current version of Expedition.&amp;nbsp; &amp;nbsp;The current version of Expedition will auto convert address, services objects, security rules, and NAT rules, but not QOS policy.&amp;nbsp; If you would like to help us to develop a new feature, please open a TAC case and attach your Fortinet config so we can validate to see if it's possible to auto map the QOS policy from Fortinet to Palo Alto Networks.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2020 17:04:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/fortigate-5-6-x-migration-gt-qos-policies-and-dscp-marking/m-p/349185#M2965</guid>
      <dc:creator>lychiang</dc:creator>
      <dc:date>2020-09-14T17:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: Fortigate 5.6.X migration -&gt; QoS policies and DSCP marking missing</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/fortigate-5-6-x-migration-gt-qos-policies-and-dscp-marking/m-p/349317#M2967</link>
      <description>&lt;P&gt;Hi Lychiang,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Think we all agree that QoS policies are of paramount relevance when planning and implementing a migration. Being able to convert these using Expedition will significantly increase the value provided by this tool to all its users &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking forward to seeing this new feature added soon. What´s the ETA for this new development?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 11:03:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/fortigate-5-6-x-migration-gt-qos-policies-and-dscp-marking/m-p/349317#M2967</guid>
      <dc:creator>HonoAl</dc:creator>
      <dc:date>2020-09-15T11:03:29Z</dc:date>
    </item>
    <item>
      <title>Re: Fortigate 5.6.X migration -&gt; QoS policies and DSCP marking missing</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/fortigate-5-6-x-migration-gt-qos-policies-and-dscp-marking/m-p/349402#M2968</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/155472"&gt;@HonoAl&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once you opened a TAC case , Please send your TAC case # to fwmigrate@paloaltonetworks.com. Thanks !&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 15:46:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/fortigate-5-6-x-migration-gt-qos-policies-and-dscp-marking/m-p/349402#M2968</guid>
      <dc:creator>lychiang</dc:creator>
      <dc:date>2020-09-15T15:46:01Z</dc:date>
    </item>
  </channel>
</rss>

