<?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 Weird Behavior from New Code in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/weird-behavior-from-new-code/m-p/1860524#M496891</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; We rolled back to 8.2.5.19 and all is good.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Jan 2012 00:49:29 GMT</pubDate>
    <dc:creator>Patrick McHenry</dc:creator>
    <dc:date>2012-01-27T00:49:29Z</dc:date>
    <item>
      <title>Weird Behavior from New Code</title>
      <link>https://community.cisco.com/t5/network-security/weird-behavior-from-new-code/m-p/1860522#M496887</link>
      <description>&lt;P&gt;&lt;BR /&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We just upgraded from 8.2.4 to 8.2.5.20 on each firewall. The Primary and Secondary work when they are standalone but, when we connect the fail over link from the Primary to the Secondary, invariably, one of them will go into a constant boot cycle and one will be active but, external users will be intermittently dropped. As soon as we unplug the fail over, the firewall that stays up behaves normally. Has anyone seen this with the 8.2.5.20 code or any other code for that matter?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, Pat.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:14:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/weird-behavior-from-new-code/m-p/1860522#M496887</guid>
      <dc:creator>Patrick McHenry</dc:creator>
      <dc:date>2019-03-11T22:14:39Z</dc:date>
    </item>
    <item>
      <title>Weird Behavior from New Code</title>
      <link>https://community.cisco.com/t5/network-security/weird-behavior-from-new-code/m-p/1860523#M496889</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pat,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on your description I would suspect this is caused by CSCtx03464, which only affects 8.2.5.20. However, please open a TAC case to confirm for sure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jan 2012 18:13:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/weird-behavior-from-new-code/m-p/1860523#M496889</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2012-01-20T18:13:29Z</dc:date>
    </item>
    <item>
      <title>Weird Behavior from New Code</title>
      <link>https://community.cisco.com/t5/network-security/weird-behavior-from-new-code/m-p/1860524#M496891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; We rolled back to 8.2.5.19 and all is good.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jan 2012 00:49:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/weird-behavior-from-new-code/m-p/1860524#M496891</guid>
      <dc:creator>Patrick McHenry</dc:creator>
      <dc:date>2012-01-27T00:49:29Z</dc:date>
    </item>
  </channel>
</rss>

