<?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 IPS auto update in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-auto-update/m-p/1241774#M77563</link>
    <description>&lt;P&gt;Hello, Customers having IPS 4215 version 6.0(5)E3 are having their sensor crashing following auto update from an FTP server.&lt;/P&gt;&lt;P&gt;The web interface is no more accessible and the analysis engine stopped( I've attached the show tech-support)&lt;/P&gt;&lt;P&gt;The problem happened with different signatures S383 and S384, please advise&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 11:32:05 GMT</pubDate>
    <dc:creator>k.abillama</dc:creator>
    <dc:date>2019-03-10T11:32:05Z</dc:date>
    <item>
      <title>IPS auto update</title>
      <link>https://community.cisco.com/t5/network-security/ips-auto-update/m-p/1241774#M77563</link>
      <description>&lt;P&gt;Hello, Customers having IPS 4215 version 6.0(5)E3 are having their sensor crashing following auto update from an FTP server.&lt;/P&gt;&lt;P&gt;The web interface is no more accessible and the analysis engine stopped( I've attached the show tech-support)&lt;/P&gt;&lt;P&gt;The problem happened with different signatures S383 and S384, please advise&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:32:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-auto-update/m-p/1241774#M77563</guid>
      <dc:creator>k.abillama</dc:creator>
      <dc:date>2019-03-10T11:32:05Z</dc:date>
    </item>
    <item>
      <title>Re: IPS auto update</title>
      <link>https://community.cisco.com/t5/network-security/ips-auto-update/m-p/1241775#M77575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Having a 4215 sensor crash on a signature update is a very common event.&lt;/P&gt;&lt;P&gt;The 4215 sensors only have 512 MB or RAM (most sensors have 1 or 2 GB), this has caused many problems during the update process. &lt;/P&gt;&lt;P&gt;You can try rebooting the sensor several times, if that doesnt bring it back to life, you can try resetting the signature policy back to default, if that doesn't help you'll need to open a TAC case to modify some of the signature build time memory parmeters.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Mar 2009 16:58:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-auto-update/m-p/1241775#M77575</guid>
      <dc:creator>rhermes</dc:creator>
      <dc:date>2009-03-04T16:58:56Z</dc:date>
    </item>
    <item>
      <title>Re: IPS auto update</title>
      <link>https://community.cisco.com/t5/network-security/ips-auto-update/m-p/1241776#M77580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The problem is indeed being resolved after rebooting the ips, but this is not a solution for the client since it happened twice in one month!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Mar 2009 06:43:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-auto-update/m-p/1241776#M77580</guid>
      <dc:creator>k.abillama</dc:creator>
      <dc:date>2009-03-05T06:43:14Z</dc:date>
    </item>
  </channel>
</rss>

