<?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 Pix Firewall | Migration Help in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-firewall-migration-help/m-p/1603212#M559082</link>
    <description>&lt;P&gt;We have a dozen odd pix 515e, 525 and 535's in our organization with v6.1 software.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Per cisco these models are EOL/EOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also the latest Pix Software for these appear to be EOL as well&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/pix/pix80/release/notes/pixrn804.html" target="_blank"&gt;&lt;SPAN style="font-family: Calibri; color: #800080; font-size: 12pt;"&gt;http://www.cisco.com/en/US/docs/security/pix/pix80/release/notes/pixrn804.html&lt;/SPAN&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is can the software on these pix boxes be upgraded ?or are the softwares for the PIX boxes EOL/EOS as well ?&lt;/P&gt;&lt;P&gt;In which case migrating over to ASA's the only option ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also is there a number or person we can reach out in Cisco to get some suggestions ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Harsha &lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 20:13:20 GMT</pubDate>
    <dc:creator>harshavardhanhr-hr</dc:creator>
    <dc:date>2019-03-11T20:13:20Z</dc:date>
    <item>
      <title>Pix Firewall | Migration Help</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-migration-help/m-p/1603212#M559082</link>
      <description>&lt;P&gt;We have a dozen odd pix 515e, 525 and 535's in our organization with v6.1 software.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Per cisco these models are EOL/EOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also the latest Pix Software for these appear to be EOL as well&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/pix/pix80/release/notes/pixrn804.html" target="_blank"&gt;&lt;SPAN style="font-family: Calibri; color: #800080; font-size: 12pt;"&gt;http://www.cisco.com/en/US/docs/security/pix/pix80/release/notes/pixrn804.html&lt;/SPAN&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is can the software on these pix boxes be upgraded ?or are the softwares for the PIX boxes EOL/EOS as well ?&lt;/P&gt;&lt;P&gt;In which case migrating over to ASA's the only option ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also is there a number or person we can reach out in Cisco to get some suggestions ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Harsha &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:13:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-migration-help/m-p/1603212#M559082</guid>
      <dc:creator>harshavardhanhr-hr</dc:creator>
      <dc:date>2019-03-11T20:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Firewall | Migration Help</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-migration-help/m-p/1603213#M559083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There was an upgrade kit for version 7.X for those models which allowed you to increase the RAM on those models and then upgrade to version 7.x.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my personal opinion it would be a good idea to start thinking on migrating to ASAs since support for the PIX models will end soon. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could contact a Local Cisco Parter so that they can help you with the right ASA models and with the price of it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 27 Mar 2011 13:01:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-migration-help/m-p/1603213#M559083</guid>
      <dc:creator>PAUL GILBERT ARIAS</dc:creator>
      <dc:date>2011-03-27T13:01:49Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Firewall | Migration Help</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-migration-help/m-p/1603214#M559084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Don't bother upgrading those devices.&amp;nbsp; You are better off rewriting the policies for new ASAs and cleaning up the configs while you are at it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6.x is very old now.&amp;nbsp; I hope you don't have conduit statements but if you do there is a tool to convert them to access-lists at least.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Mar 2011 00:04:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-migration-help/m-p/1603214#M559084</guid>
      <dc:creator>Matthew Warrick</dc:creator>
      <dc:date>2011-03-28T00:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Firewall | Migration Help</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-migration-help/m-p/1603215#M559085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks guys!&lt;/P&gt;&lt;P&gt;have reached out to cisco tac and hopefully shall get some ans.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Harsha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2011 14:08:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-migration-help/m-p/1603215#M559085</guid>
      <dc:creator>harshavardhanhr-hr</dc:creator>
      <dc:date>2011-03-30T14:08:42Z</dc:date>
    </item>
  </channel>
</rss>

