<?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: synchronization in progress issue in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/synchronization-in-progress-issue/m-p/22380#M16317</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you should from the cli follow the devsrvr.log or the ms.log to see how far the sync is going before it fails. also on the passive device do you seen a ha sync job when you run show jobs processed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if it does not give you a clear error message i would suggest opening a case online and uploading the tech support files from both devices.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 23 Jul 2011 00:03:19 GMT</pubDate>
    <dc:creator>jnguyen</dc:creator>
    <dc:date>2011-07-23T00:03:19Z</dc:date>
    <item>
      <title>synchronization in progress issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/synchronization-in-progress-issue/m-p/22379#M16316</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We're new PA users - we've brought up a pair of 5050s running 4.0.3 with the HA patch for virtual systems and we're getting a "synchronization in progress" message for prolonged periods.&amp;nbsp; It then eventually reverts to not synchronized.&amp;nbsp; We can't find anything in the logs and doing a config diff has us a little stumped - it shows a diff in areas like global protect (one box has a few lines, the other doesn't), we're not licensed for global protect.&amp;nbsp; Any thoughts/experience would be appreciated.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Corbett&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jul 2011 20:56:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/synchronization-in-progress-issue/m-p/22379#M16316</guid>
      <dc:creator>migration</dc:creator>
      <dc:date>2011-07-22T20:56:34Z</dc:date>
    </item>
    <item>
      <title>Re: synchronization in progress issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/synchronization-in-progress-issue/m-p/22380#M16317</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you should from the cli follow the devsrvr.log or the ms.log to see how far the sync is going before it fails. also on the passive device do you seen a ha sync job when you run show jobs processed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if it does not give you a clear error message i would suggest opening a case online and uploading the tech support files from both devices.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Jul 2011 00:03:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/synchronization-in-progress-issue/m-p/22380#M16317</guid>
      <dc:creator>jnguyen</dc:creator>
      <dc:date>2011-07-23T00:03:19Z</dc:date>
    </item>
    <item>
      <title>Re: synchronization in progress issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/synchronization-in-progress-issue/m-p/22381#M16318</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Thanks very much!&amp;nbsp; We've added that to our documentation area.&amp;nbsp; We're getting a little more comfortable with learning a) what synchs in HA and b) looking at CLI logs, we've gotten past that issue now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jul 2011 18:25:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/synchronization-in-progress-issue/m-p/22381#M16318</guid>
      <dc:creator>migration</dc:creator>
      <dc:date>2011-07-25T18:25:33Z</dc:date>
    </item>
  </channel>
</rss>

