<?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: Active/Passive HA Sync Issues in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31284#M22873</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Could you share the output of "show high-availability all" from both firewalls?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Jul 2014 16:42:04 GMT</pubDate>
    <dc:creator>ajbool</dc:creator>
    <dc:date>2014-07-14T16:42:04Z</dc:date>
    <item>
      <title>Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31269#M22858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm in the process of testing out two PAN-M-100's in the lab and more specifically testing the HA functionality at this point.&lt;/P&gt;&lt;P&gt;The issue that I am running into:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have changed the Primary to Passive and the Secondary to Active, made a change to the Active/Secondary and then reverted the M-100's back to Active/Primary - Passive/Secondary. After doing this, instead of the Active/Primary pulling the latest config from the Passive/Secondary, it tries to overwrite the config with it's own. So in a nut shell, when we are failed over to our secondary M-100, all the changes we make will have to be redone on the Primary upon fail back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running version 5.1.3 (STIG compliance disallows us to upgrade, trust me I wish I could).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 16:15:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31269#M22858</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-11T16:15:21Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31270#M22859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Davecorwin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please try below mentioned command before doing a failover.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;admin@114-PANORAMA&amp;gt; request high-availability sync-to-remote&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;gt; &lt;SPAN class="GINGER_SOFTWARE_mark"&gt;candidate&lt;/SPAN&gt;-config&amp;nbsp;&amp;nbsp; Sync candidate configuration to peer&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;gt; &lt;SPAN class="GINGER_SOFTWARE_mark"&gt;clock&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Sync the local time and date &lt;SPAN class="GINGER_SOFTWARE_mark"&gt;to&lt;/SPAN&gt; the peer&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;gt; &lt;SPAN class="GINGER_SOFTWARE_mark"&gt;running&lt;/SPAN&gt;-config&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Sync running configuration to peer&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;admin@114-PANORAMA&amp;gt; request high-availability sync-to-remote running-config&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;admin@114-PANORAMA&amp;gt; show jobs all --- just to ensure that &lt;SPAN class="GINGER_SOFTWARE_mark"&gt;sync job&lt;/SPAN&gt; has been completed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then do a failover test and let us know the result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 16:34:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31270#M22859</guid>
      <dc:creator>HULK</dc:creator>
      <dc:date>2014-07-11T16:34:47Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31271#M22860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Forgot to mention, please verify JOBS on the secondary box as well. It should show that, Secondary received a config-sync job from primary and completed successfully.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 16:40:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31271#M22860</guid>
      <dc:creator>HULK</dc:creator>
      <dc:date>2014-07-11T16:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31272#M22861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Roger that...stand by...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 16:45:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31272#M22861</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-11T16:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31273#M22862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah, only the PEER will show the sync job. We have successfully performed the sync. Our next step is to unplug the primary M-100 from the switch (totally take it off the network) to cause the secondary to take over as Active/Passive on it's own. I will then make a config change on the Active/Secondary. Once that is complete, I am going to plug the Primary back into the switch...this should automatically make the Primary Active. The issue is that when we do this, the Primary wants to overwrite the config. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 17:08:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31273#M22862</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-11T17:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31274#M22863</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, so when the Primary came back in line, as assumed it went straight into active mode. When you go to sync it overwrites the changes you made on the secondary. I was able to get the primary, once back online, to go into passive state and push the sync from the secondary, which worked! The issue is, after only a minute or two, the primary automatically reverts back to active. The M-100 is currently in preemptive mode, so I don't see why this is happening. These devices should successfully/correctly sync without me having to do all of this extra.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 17:42:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31274#M22863</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-11T17:42:08Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31275#M22864</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dave,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your situation try disabling pre-emptive on both firewalls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hari Yadavalli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 17:55:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31275#M22864</guid>
      <dc:creator>hyadavalli</dc:creator>
      <dc:date>2014-07-11T17:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31276#M22865</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I actually just got done doing that and disconnected the primary from the switch. The secondary automatically switched to active (as expected) and I created another rule. Once the commit is done, I will plug the primary back into the network. Hopefully the primary stays as passive (since preemptive is turned off). I also hope that the sync process kicks off automatically.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 18:06:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31276#M22865</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-11T18:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31277#M22866</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, once the primary was plugged back into the network, it automatically went into ACTIVE mode...how is this?? That tells me that there is absolutely NOTHING different between preemptive and non-preemptive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What we are trying now is to leave preemptive off on the primary but turn it on the secondary and see what happens.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 18:12:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31277#M22866</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-11T18:12:33Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31278#M22867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Still the same issue. We set up a case with Palo...hopefully they can figure out the issue. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 18:58:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31278#M22867</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-11T18:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31279#M22868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dave,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sure you commit the changes and disabled pre-emptive on both firewalls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hari Yadavalli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 19:13:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31279#M22868</guid>
      <dc:creator>hyadavalli</dc:creator>
      <dc:date>2014-07-11T19:13:35Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31280#M22869</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've done all that...makes no difference. I have tried every kind of way imaginable and the outcome is always the same: The primary automatically switches back to active and the changes on the secondary don't sync with the primary. I have to manually push the sync from the cli of the secondary to properly sync them...I shouldn't have to do that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 19:19:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31280#M22869</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-11T19:19:37Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31281#M22870</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Perhaps worth checking the time on the two units.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the primary has a clock time further into the future than the secondary; perhaps this causing its config to be considered more fresh than the secondary and therefore the version that gets pushed out?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 20:05:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31281#M22870</guid>
      <dc:creator>ajbool</dc:creator>
      <dc:date>2014-07-11T20:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31282#M22871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The preemptive feature has to be activated on both devices to use it. If it's activated the device with the higher priority(lower number) becomes active/(primary). If it's not active the device with the longer uptime and lower MAC will be active. Can you post a screenshot of the HA configuration?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2014 08:26:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31282#M22871</guid>
      <dc:creator>Wenar</dc:creator>
      <dc:date>2014-07-14T08:26:30Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31283#M22872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I understand all of that...the issue is, I want the "Secondary" to be able to send any new configs to the now, "Active/Primary" upon reinstatement. With the preemptive setting in place, upon reinstatement of the Primary device (making it Active), that device wants to sync it's config with the secondary...I don't want that! By this happening, I'm erasing any config changes that I made, on the secondary, while the primary was down.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2014 15:42:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31283#M22872</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-14T15:42:36Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31284#M22873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Could you share the output of "show high-availability all" from both firewalls?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2014 16:42:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31284#M22873</guid>
      <dc:creator>ajbool</dc:creator>
      <dc:date>2014-07-14T16:42:04Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31285#M22874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;These are not firewalls, they are M-100 Panoramas (managers). Below is the the "show high-availability all" of our current VM enviroment. The M-100's that we are testing in the lab have been uploaded with the exact configuration snap-shot of our live VM Panoramas. I cannot provide the read out from the M-100s but it shouldn't matter since everything is the same (Config, licneses, software, dynamic updates, etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PRIMARY:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;High-Availability:&lt;/P&gt;&lt;P&gt;&amp;nbsp; Local Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version: 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; State: active&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Device Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Election Option Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Priority: primary&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Preemptive: yes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Promotion Hold Interval: 2000 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Hello Message Interval: 8000 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Heartbeat Ping Interval: 1000 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Preemption Hold Interval: 1 min&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Monitor Fail Hold Up Interval: 0 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Addon Master Hold Up Interval: 7000 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Build Release: 5.1.3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; URL Database: Not Installed&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Application Content: 445-2292&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Threat Content: 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Anti-Virus: 1317-1787&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version Compatibility:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Software Version: Match&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Application Content Compatibility: Match&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Threat Content Compatibility: Match&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Anti-Virus Compatibility: Match&lt;/P&gt;&lt;P&gt;&amp;nbsp; Peer Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Connection status: up&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version: 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; State: passive&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Device Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Connection up; Primary HA1 link&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Election Option Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Priority: secondary&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Preemptive: yes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Build Release: 5.1.3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; URL Database: Not Installed&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Application Content: 445-2292&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Threat Content: 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Anti-Virus: 1317-1787&lt;/P&gt;&lt;P&gt;&amp;nbsp; Configuration Synchronization:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Enabled: yes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Running Configuration: synchronized&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SECONDARY:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;High-Availability:&lt;/P&gt;&lt;P&gt;&amp;nbsp; Local Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version: 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; State: passive &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Last suspended state reason: User requested&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Device Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Election Option Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Priority: secondary&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Preemptive: yes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Promotion Hold Interval: 2000 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Hello Message Interval: 8000 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Heartbeat Ping Interval: 1000 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Preemption Hold Interval: 1 min&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Monitor Fail Hold Up Interval: 0 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Addon Master Hold Up Interval: 7000 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Build Release: 5.1.3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; URL Database: Not Installed&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Application Content: 445-2292&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Threat Content: 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Anti-Virus: 1317-1787&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version Compatibility:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Software Version: Match&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Application Content Compatibility: Match&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Threat Content Compatibility: Match&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Anti-Virus Compatibility: Match&lt;/P&gt;&lt;P&gt;&amp;nbsp; Peer Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Connection status: up&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version: 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; State: active&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Last suspended state reason: User requested&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Device Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Connection up; Primary HA1 link&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Election Option Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Priority: primary&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Preemptive: yes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Build Release: 5.1.3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; URL Database: Not Installed&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Application Content: 445-2292&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Threat Content: 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Anti-Virus: 1317-1787&lt;/P&gt;&lt;P&gt;&amp;nbsp; Path Monitoring Information:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Enabled: yes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failure condition: any&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Groups:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; No path monitoring groups&lt;/P&gt;&lt;P&gt;&amp;nbsp; Configuration Synchronization:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Enabled: yes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Running Configuration: synchronized&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Again, the preemptive function works correctly up to the point where it doesn't Sync the recently config changes from the secondary to the primary. I have to manually run the sync command from the secondary CLI in order to make the sync work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2014 17:16:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31285#M22874</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-14T17:16:19Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31286#M22875</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looks pretty good to me (I have lots of A/P devices; but my VMware Panorama is just standalone - so can't compare directly).&amp;nbsp; Clocks synced between the two devices OK?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2014 19:03:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31286#M22875</guid>
      <dc:creator>ajbool</dc:creator>
      <dc:date>2014-07-14T19:03:31Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31287#M22876</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, the clocks are synced. It's almost as if there is a bug with the software version that isn't allowing changes made on the secondary device (while in active mode) to transfer to the primary device upon reinstatement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What's even stranger, is that after turning OFF the preemptive mode on both devices (committing, etc), the primary device still automatically becomes active upon reinstatement to the network. It's like there is no difference between preemptive and non-preemptive. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2014 19:12:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31287#M22876</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-07-14T19:12:42Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Passive HA Sync Issues</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31288#M22877</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok I overlooked that you said it's a M-100. The passive/secondary isn't able to manage policies and if the active/primary comes online again it will sync it's configuration because it's the only device which is allowed to manage the policies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-6590"&gt;Panorama Administrator's Guide 6.0 (English)&amp;nbsp; Page 127&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: line-through;"&gt;I think you have to put them in active/primary and active/secondary if you want the secondary device to be able to sync the configuration.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whoops my mistake. That is not possible. If this still doesn't work if preemptive is deactivated on both devices you should open a case. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can't test this here and see how a suspended device behaves if the other peer commits a configuration. Could you see if there is a job running on the suspended device after you commit the configuration on the secondary? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the guide is right the secondary should still be active after you make the primary functional again and preemptive is disabled on both devices.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jul 2014 07:31:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/active-passive-ha-sync-issues/m-p/31288#M22877</guid>
      <dc:creator>Wenar</dc:creator>
      <dc:date>2014-07-15T07:31:38Z</dc:date>
    </item>
  </channel>
</rss>

