<?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: Expedition migrates ASA vxlan protocol to wrong port in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/546685#M4608</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/125671"&gt;@crabevil&lt;/a&gt;,&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Thanks for reaching out.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;As I included in the answer by email.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Expedition has a mapping file for each vendor to map known vendor services with defined port/protocol service or Palo Alto Networks app_id.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;You can edit your file but take in mind it will be overridden once you update Expedition.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;The file is located in&amp;nbsp;/var/www/html/contents/parsers on the VM and named like 'vendor' - services.csv or 'vendor' - groups.csv (for group service objects).&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I will include the vxlan service in the default mapping file for cisco in release 1.2.64.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Let me know if you have any further questions,&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Best regards,&lt;/DIV&gt;</description>
    <pubDate>Wed, 21 Jun 2023 10:06:33 GMT</pubDate>
    <dc:creator>dpuigdomenec</dc:creator>
    <dc:date>2023-06-21T10:06:33Z</dc:date>
    <item>
      <title>Expedition migrates ASA vxlan protocol to wrong port</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/543618#M4585</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;we had an issue with a connection after migrating from ASA to PaloAlto Firewall because Expedition was migrating the vxlan protocol to the wrong port udp/6500, but it should be udp/4789.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you fix this bug?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Sat, 27 May 2023 05:47:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/543618#M4585</guid>
      <dc:creator>crabevil</dc:creator>
      <dc:date>2023-05-27T05:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition migrates ASA vxlan protocol to wrong port</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/544050#M4588</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/125671"&gt;@crabevil&lt;/a&gt;&amp;nbsp; Can you please open a TAC case and attach the original ciscoasa config in the case, please write an email to &lt;A href="mailto:fwmigrate@paloaltonetworks.com" target="_blank"&gt;fwmigrate@paloaltonetworks.com&lt;/A&gt;&amp;nbsp;with the TAC&amp;nbsp; case#&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 May 2023 20:12:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/544050#M4588</guid>
      <dc:creator>lychiang</dc:creator>
      <dc:date>2023-05-30T20:12:30Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition migrates ASA vxlan protocol to wrong port</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/544691#M4593</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/38629"&gt;@lychiang&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;how to open a TAC Case for Expedition?&lt;/P&gt;
&lt;P&gt;In the costumer support portal there is no possability to open a TAC case for product type Expedition.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;NOTE&lt;/STRONG&gt;&lt;SPAN&gt;: Expedition is supported by the community as best effort. The Palo Alto Networks TAC does not provide support, so please post your questions in the &lt;/SPAN&gt;&lt;A title="Ask your questions" href="https://live.paloaltonetworks.com/t5/expedition-discussions/bd-p/ExpeditionDiscussions" target="_blank"&gt;&lt;STRONG&gt;Expedition discussions&lt;/STRONG&gt;&lt;/A&gt;&lt;SPAN&gt;area.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jun 2023 06:11:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/544691#M4593</guid>
      <dc:creator>crabevil</dc:creator>
      <dc:date>2023-06-04T06:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition migrates ASA vxlan protocol to wrong port</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/544968#M4595</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/125671"&gt;@crabevil&lt;/a&gt;&amp;nbsp; You will select pan-os , and select serial# of the device, then you can open the case, the case is opened so you can secure share files with expedition team.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2023 16:43:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/544968#M4595</guid>
      <dc:creator>lychiang</dc:creator>
      <dc:date>2023-06-06T16:43:18Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition migrates ASA vxlan protocol to wrong port</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/546685#M4608</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/125671"&gt;@crabevil&lt;/a&gt;,&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Thanks for reaching out.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;As I included in the answer by email.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Expedition has a mapping file for each vendor to map known vendor services with defined port/protocol service or Palo Alto Networks app_id.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;You can edit your file but take in mind it will be overridden once you update Expedition.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;The file is located in&amp;nbsp;/var/www/html/contents/parsers on the VM and named like 'vendor' - services.csv or 'vendor' - groups.csv (for group service objects).&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I will include the vxlan service in the default mapping file for cisco in release 1.2.64.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Let me know if you have any further questions,&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Best regards,&lt;/DIV&gt;</description>
      <pubDate>Wed, 21 Jun 2023 10:06:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/546685#M4608</guid>
      <dc:creator>dpuigdomenec</dc:creator>
      <dc:date>2023-06-21T10:06:33Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition migrates ASA vxlan protocol to wrong port</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/549438#M4624</link>
      <description>&lt;P&gt;Interesting - I just had the same issue. migrated the obj "domain" to udp 6500. This wasn't from an ASA but from an old FWSM.&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jul 2023 11:58:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/549438#M4624</guid>
      <dc:creator>MichaelBredell</dc:creator>
      <dc:date>2023-07-15T11:58:00Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition migrates ASA vxlan protocol to wrong port</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/549547#M4625</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/170469"&gt;@MichaelBredell&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Thanks for reaching out.&lt;/P&gt;
&lt;P&gt;You could use the same solution above adding the domain service. &lt;BR /&gt;Also if you share with us the mapping you used we could add it as default value.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;David&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jul 2023 09:58:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-migrates-asa-vxlan-protocol-to-wrong-port/m-p/549547#M4625</guid>
      <dc:creator>dpuigdomenec</dc:creator>
      <dc:date>2023-07-17T09:58:19Z</dc:date>
    </item>
  </channel>
</rss>

