<?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: PIX reload in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-reload/m-p/907347#M959778</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What PIX model and software version?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Nov 2007 15:11:57 GMT</pubDate>
    <dc:creator>elparis</dc:creator>
    <dc:date>2007-11-29T15:11:57Z</dc:date>
    <item>
      <title>PIX reload</title>
      <link>https://community.cisco.com/t5/network-security/pix-reload/m-p/907344#M959775</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have no experience workign with cisco PIX . we have a pix ont the netwrok that reloded. I want to know required commands to gather information that help to find root cause of problem&lt;/P&gt;&lt;P&gt;thx&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:36:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-reload/m-p/907344#M959775</guid>
      <dc:creator>pooria_koleyni</dc:creator>
      <dc:date>2019-03-11T11:36:39Z</dc:date>
    </item>
    <item>
      <title>Re: PIX reload</title>
      <link>https://community.cisco.com/t5/network-security/pix-reload/m-p/907345#M959776</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once it has reloaded you will not get any information from it. It is erased during the reload process. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can set up syslog to a server on the network if required to have the info if it happens again. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/hw/vpndevc/ps2030/products_tech_note09186a0080094030.shtml" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/hw/vpndevc/ps2030/products_tech_note09186a0080094030.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That URL runs through the syslog setup, I use KIWI for the syslog daemon. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 13:00:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-reload/m-p/907345#M959776</guid>
      <dc:creator>andyjames</dc:creator>
      <dc:date>2007-11-29T13:00:56Z</dc:date>
    </item>
    <item>
      <title>Re: PIX reload</title>
      <link>https://community.cisco.com/t5/network-security/pix-reload/m-p/907346#M959777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Right, one it's reloaded there's not much that can be collected to determine what happened. The "show version" command of the PIX lacks the reload reason, unlike the "show version" command of IOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One thing that I would suggest the original poster to try the "show crashinfo" command - if the PIX reloaded because of a software bug there is a chance a crashinfo file will exist, and the information in that file can be used to determine if the problem is caused by an existing bug (for which there may be a version with the fix) or by a new bug that requires further Cisco engagement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Logging to a syslog server is always a good idea.&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;Cheers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eloy.-&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 15:11:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-reload/m-p/907346#M959777</guid>
      <dc:creator>elparis</dc:creator>
      <dc:date>2007-11-29T15:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: PIX reload</title>
      <link>https://community.cisco.com/t5/network-security/pix-reload/m-p/907347#M959778</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What PIX model and software version?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 15:11:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-reload/m-p/907347#M959778</guid>
      <dc:creator>elparis</dc:creator>
      <dc:date>2007-11-29T15:11:57Z</dc:date>
    </item>
    <item>
      <title>Re: PIX reload</title>
      <link>https://community.cisco.com/t5/network-security/pix-reload/m-p/907348#M959779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;By the way, the "show crashinfo" command was introduced in PIX software version 6.3(1). If the software version is &amp;lt; 6.3.x then the crash info is just dumped to the serial console. If there is no terminal connected to the serial console then this information is lost.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 15:18:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-reload/m-p/907348#M959779</guid>
      <dc:creator>elparis</dc:creator>
      <dc:date>2007-11-29T15:18:16Z</dc:date>
    </item>
  </channel>
</rss>

