<?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 Import of ASA config stuck at ‘Fixing rules based on Destination Nats”…. in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/import-of-asa-config-stuck-at-fixing-rules-based-on-destination/m-p/235617#M650</link>
    <description>&lt;P&gt;Expedition 1.0.105&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ASA 9.1.7(29)&lt;/P&gt;
&lt;P&gt;Importing ASA config via pasting or browsing local computer gets stuck at ‘Fixing rules based on Destination Nats”.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Rules/configs/etc seem to load when i check them on Expedition, but i am worried about completeness/integrity because the import process never really completes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also on the Projects Library, my project is listed - but no 'vendor' count is on available vendors (all are zeroes).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note: I did have to create /datastore and do a chown on it (for parquet unit) , and did have to enable msql reconnects on apache and cli. These were recommended remediation steps provided by the support community and Expedition gui.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Oct 2018 19:14:02 GMT</pubDate>
    <dc:creator>cheumoua</dc:creator>
    <dc:date>2018-10-16T19:14:02Z</dc:date>
    <item>
      <title>Import of ASA config stuck at ‘Fixing rules based on Destination Nats”….</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/import-of-asa-config-stuck-at-fixing-rules-based-on-destination/m-p/235617#M650</link>
      <description>&lt;P&gt;Expedition 1.0.105&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ASA 9.1.7(29)&lt;/P&gt;
&lt;P&gt;Importing ASA config via pasting or browsing local computer gets stuck at ‘Fixing rules based on Destination Nats”.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Rules/configs/etc seem to load when i check them on Expedition, but i am worried about completeness/integrity because the import process never really completes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also on the Projects Library, my project is listed - but no 'vendor' count is on available vendors (all are zeroes).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note: I did have to create /datastore and do a chown on it (for parquet unit) , and did have to enable msql reconnects on apache and cli. These were recommended remediation steps provided by the support community and Expedition gui.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Oct 2018 19:14:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/import-of-asa-config-stuck-at-fixing-rules-based-on-destination/m-p/235617#M650</guid>
      <dc:creator>cheumoua</dc:creator>
      <dc:date>2018-10-16T19:14:02Z</dc:date>
    </item>
    <item>
      <title>Re: Import of ASA config stuck at ‘Fixing rules based on Destination Nats”….</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/import-of-asa-config-stuck-at-fixing-rules-based-on-destination/m-p/235882#M654</link>
      <description>&lt;P&gt;Thanks to alestevez!&amp;nbsp; Issue resovled for me..... alestevez informed references to IPV6 is not supported by the tool... so i removed IPV6 components (addresses, any6, etc). This allowed the import to complete. I will add IPV6 info back manually on the Palo side.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Oct 2018 20:19:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/import-of-asa-config-stuck-at-fixing-rules-based-on-destination/m-p/235882#M654</guid>
      <dc:creator>cheumoua</dc:creator>
      <dc:date>2018-10-17T20:19:26Z</dc:date>
    </item>
  </channel>
</rss>

