<?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 recommended stable code for 5585x fw ? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/recommended-stable-code-for-5585x-fw/m-p/2148908#M359734</link>
    <description>&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Hello&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0.0001pt;"&gt;Looking for a recommended code on the ASA 5585x firewall. We ran into a bug (CSCtr24705) on version 8.4.2 where it rebooted the primary firewall. The bug has to do with modifying an existing ACL that's part of a custom policy-map inside a service-policy. If we upgrade to 8.4.5 (which has the previous bug fix in it), there is another major bug (CSCud70273) where if you use the packet-tracer input command on an inside interface it causes problems too.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;I don't understand why packet-tracer input would have a bug associated with it when it's been around for a long time and we use it on a daily basis for troubleshooting. Is there stable code for the 5585x to upgrade to without running into possibly a major bug? This is our core firewall so there are no VPN tunnels on it. It's setup in active/standby failover in routed mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Thanks in advance! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-John&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 01:17:29 GMT</pubDate>
    <dc:creator>johng231</dc:creator>
    <dc:date>2019-03-12T01:17:29Z</dc:date>
    <item>
      <title>recommended stable code for 5585x fw ?</title>
      <link>https://community.cisco.com/t5/network-security/recommended-stable-code-for-5585x-fw/m-p/2148908#M359734</link>
      <description>&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Hello&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0.0001pt;"&gt;Looking for a recommended code on the ASA 5585x firewall. We ran into a bug (CSCtr24705) on version 8.4.2 where it rebooted the primary firewall. The bug has to do with modifying an existing ACL that's part of a custom policy-map inside a service-policy. If we upgrade to 8.4.5 (which has the previous bug fix in it), there is another major bug (CSCud70273) where if you use the packet-tracer input command on an inside interface it causes problems too.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;I don't understand why packet-tracer input would have a bug associated with it when it's been around for a long time and we use it on a daily basis for troubleshooting. Is there stable code for the 5585x to upgrade to without running into possibly a major bug? This is our core firewall so there are no VPN tunnels on it. It's setup in active/standby failover in routed mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Thanks in advance! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-John&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:17:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/recommended-stable-code-for-5585x-fw/m-p/2148908#M359734</guid>
      <dc:creator>johng231</dc:creator>
      <dc:date>2019-03-12T01:17:29Z</dc:date>
    </item>
    <item>
      <title>Re: recommended stable code for 5585x fw ?</title>
      <link>https://community.cisco.com/t5/network-security/recommended-stable-code-for-5585x-fw/m-p/2148909#M359735</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello John,&lt;/P&gt;&lt;P&gt;i would use 9.1.x ASA code, it is the latest ASA software, so it has fixed most (if not all) of the known bugs.&lt;/P&gt;&lt;P&gt;However, i advise you to check the release notes of the version you plan to deploy, and verify the fixed bugs , and the open caveats (if exisiting), and make sure that you pick 9.1.x version that targets the 5585X platform which SMP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mashal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 20:53:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/recommended-stable-code-for-5585x-fw/m-p/2148909#M359735</guid>
      <dc:creator>malshbou</dc:creator>
      <dc:date>2013-03-21T20:53:11Z</dc:date>
    </item>
  </channel>
</rss>

