<?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 High Availability weirdness in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16908#M12318</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a pair of 2020's (I know, don't comment - they're getting upgraded soon, I hope!) which run in active/passive HA pairing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This morning, I noticed the following entries in the logs on my primary (normally active) device&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;ras&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;rasmgr- 0&amp;nbsp; RASMGR daemon sync all user info to HA peer exit.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;vpn&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;keymgr- 0&amp;nbsp; KEYMGR sync all IPSec SA to HA peer exit.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;ras&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;rasmgr- 0&amp;nbsp; RASMGR daemon sync all user info to HA peer started.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;vpn&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;keymgr- 0&amp;nbsp; KEYMGR sync all IPSec SA to HA peer started.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;satd&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;satd-ha 0&amp;nbsp; SATD daemon sync all gateway infos to HA peer started.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;routing&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;routed- 0&amp;nbsp; FIB HA sync started when peer device becomes passive.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 info &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;connect 0&amp;nbsp; HA Group 1: HA1 connection up&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 high &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha3-lin 0&amp;nbsp; HA3 peer link down&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 high &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha2-lin 0&amp;nbsp; HA2-Backup peer link down&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 info &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha2-lin 0&amp;nbsp; HA2 peer link up&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 high &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha1-lin 0&amp;nbsp; HA1-Backup peer link down&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 info &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha1-lin 0&amp;nbsp; HA1 peer link up&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 info &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;connect 0&amp;nbsp; HA Group 1: Control link running on HA1 connection&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:36 info &lt;/TD&gt;&lt;TD&gt;satd&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;satd-ha 0&amp;nbsp; SATD daemon sync all gateway infos to HA peer no longer needed.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:36 info &lt;/TD&gt;&lt;TD&gt;vpn&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;keymgr- 0&amp;nbsp; KEYMGR sync all IPSec SA to HA peer no longer needed.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:35 info &lt;/TD&gt;&lt;TD&gt;ras&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;rasmgr- 0&amp;nbsp; RASMGR daemon sync all user info to HA peer no longer needed.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:34 critical ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;connect 0&amp;nbsp; HA Group 1: All HA1 connections down&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:34 critical ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;connect 0&amp;nbsp; HA Group 1: HA1 connection down&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(that's a backwards view - the oldest event is at the bottom). The standby (normally passive) device has similar entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trouble is, I 100% *know* the links didn't go down - there is nobody available to physically remove them (the devices are in a locked cabinet in another building which only two people are authorised to access, and both of them are sitting in the office right now), and both devices show uptimes which exceed 70 days&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone shed some light on what may have caused this? From memory, this isn't the first time I've noticed this, but on the last occasion I wrote it off as some environmental thing - maybe I should have chased it earlier.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any input appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Jun 2014 23:11:28 GMT</pubDate>
    <dc:creator>darren_g</dc:creator>
    <dc:date>2014-06-24T23:11:28Z</dc:date>
    <item>
      <title>High Availability weirdness</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16908#M12318</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a pair of 2020's (I know, don't comment - they're getting upgraded soon, I hope!) which run in active/passive HA pairing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This morning, I noticed the following entries in the logs on my primary (normally active) device&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;ras&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;rasmgr- 0&amp;nbsp; RASMGR daemon sync all user info to HA peer exit.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;vpn&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;keymgr- 0&amp;nbsp; KEYMGR sync all IPSec SA to HA peer exit.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;ras&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;rasmgr- 0&amp;nbsp; RASMGR daemon sync all user info to HA peer started.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;vpn&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;keymgr- 0&amp;nbsp; KEYMGR sync all IPSec SA to HA peer started.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;satd&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;satd-ha 0&amp;nbsp; SATD daemon sync all gateway infos to HA peer started.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:58:37 info &lt;/TD&gt;&lt;TD&gt;routing&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;routed- 0&amp;nbsp; FIB HA sync started when peer device becomes passive.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 info &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;connect 0&amp;nbsp; HA Group 1: HA1 connection up&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 high &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha3-lin 0&amp;nbsp; HA3 peer link down&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 high &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha2-lin 0&amp;nbsp; HA2-Backup peer link down&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 info &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha2-lin 0&amp;nbsp; HA2 peer link up&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 high &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha1-lin 0&amp;nbsp; HA1-Backup peer link down&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 info &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;ha1-lin 0&amp;nbsp; HA1 peer link up&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:37 info &lt;/TD&gt;&lt;TD&gt;ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;connect 0&amp;nbsp; HA Group 1: Control link running on HA1 connection&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:36 info &lt;/TD&gt;&lt;TD&gt;satd&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;satd-ha 0&amp;nbsp; SATD daemon sync all gateway infos to HA peer no longer needed.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:36 info &lt;/TD&gt;&lt;TD&gt;vpn&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;keymgr- 0&amp;nbsp; KEYMGR sync all IPSec SA to HA peer no longer needed.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:35 info &lt;/TD&gt;&lt;TD&gt;ras&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;rasmgr- 0&amp;nbsp; RASMGR daemon sync all user info to HA peer no longer needed.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:34 critical ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;connect 0&amp;nbsp; HA Group 1: All HA1 connections down&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2014/06/25 08:53:34 critical ha&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;connect 0&amp;nbsp; HA Group 1: HA1 connection down&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(that's a backwards view - the oldest event is at the bottom). The standby (normally passive) device has similar entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trouble is, I 100% *know* the links didn't go down - there is nobody available to physically remove them (the devices are in a locked cabinet in another building which only two people are authorised to access, and both of them are sitting in the office right now), and both devices show uptimes which exceed 70 days&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone shed some light on what may have caused this? From memory, this isn't the first time I've noticed this, but on the last occasion I wrote it off as some environmental thing - maybe I should have chased it earlier.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any input appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jun 2014 23:11:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16908#M12318</guid>
      <dc:creator>darren_g</dc:creator>
      <dc:date>2014-06-24T23:11:28Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability weirdness</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16909#M12319</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We had a similar issue a while ago with an older PANOS Version, I think it was 5.0.7. Which PANOS Version are you running ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jun 2014 13:13:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16909#M12319</guid>
      <dc:creator>gafrol</dc:creator>
      <dc:date>2014-06-25T13:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability weirdness</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16910#M12320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The devices in question are on 5.0.12. I don't want to update them to the version 6 software because they're only 2020's, and I have concerns about their load if I do.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jun 2014 23:42:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16910#M12320</guid>
      <dc:creator>darren_g</dc:creator>
      <dc:date>2014-06-25T23:42:28Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability weirdness</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16911#M12321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;While your cables may not have been pulled, clearly the communication link overall failed between the nodes.&amp;nbsp; So this probably means there is an interface or system issue on one of the nodes of the cluster.&amp;nbsp; I think you might have a hardware issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would pull a full tech support from both and open a case for investigation of the root cause.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2014 01:10:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16911#M12321</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2014-06-26T01:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability weirdness</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16912#M12322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;#1&lt;/P&gt;&lt;P&gt;How is dataplane load going?&lt;/P&gt;&lt;P&gt;You can check by 'show running resource-monitor'&lt;/P&gt;&lt;P&gt;If it looks high average or 100% in max, it might stops traffic via HA1 port.&lt;/P&gt;&lt;P&gt;To avoid this situation, you can enable heartbeat backup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#2&lt;/P&gt;&lt;P&gt;You can check if some kind of process was restarted.&lt;/P&gt;&lt;P&gt;'show system files' shows you core-dump if generated.&lt;/P&gt;&lt;P&gt;If you can find any output, then you can export it, open the case, then TAC will investigate it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2014 01:11:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16912#M12322</guid>
      <dc:creator>emr_1</dc:creator>
      <dc:date>2014-06-26T01:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability weirdness</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16913#M12323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;#1 The dataplane load rarely if ever gets above about 17-20%. The *management* plane routinely runs at 60-70% with a known issue on the 2020's (one reason I'm looking to upgrade them).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#2 No recent core dumps or crashinfo files exist&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the suggestions, though. I'll log a case and see if PA TAC can find an answer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2014 01:16:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16913#M12323</guid>
      <dc:creator>darren_g</dc:creator>
      <dc:date>2014-06-26T01:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability weirdness</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16914#M12324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will log a case and see what happens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your input&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2014 01:17:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/high-availability-weirdness/m-p/16914#M12324</guid>
      <dc:creator>darren_g</dc:creator>
      <dc:date>2014-06-26T01:17:21Z</dc:date>
    </item>
  </channel>
</rss>

