<?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 issue logging into sensor (screenshot) in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915038#M55303</link>
    <description>&lt;P&gt;I just recently took over here and was trying to gain access to the two sensors we have in the environment.&amp;nbsp; I was able to log into one, but when I tried to login to the second sensor, it gave me a strange error (see screenshot).&amp;nbsp; Im using the Cisco IME to access the sensors.&amp;nbsp; Any ideas?&amp;nbsp; Thanks&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 12:40:07 GMT</pubDate>
    <dc:creator>lukeprimm</dc:creator>
    <dc:date>2019-03-10T12:40:07Z</dc:date>
    <item>
      <title>issue logging into sensor (screenshot)</title>
      <link>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915038#M55303</link>
      <description>&lt;P&gt;I just recently took over here and was trying to gain access to the two sensors we have in the environment.&amp;nbsp; I was able to log into one, but when I tried to login to the second sensor, it gave me a strange error (see screenshot).&amp;nbsp; Im using the Cisco IME to access the sensors.&amp;nbsp; Any ideas?&amp;nbsp; Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:40:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915038#M55303</guid>
      <dc:creator>lukeprimm</dc:creator>
      <dc:date>2019-03-10T12:40:07Z</dc:date>
    </item>
    <item>
      <title>issue logging into sensor (screenshot)</title>
      <link>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915039#M55304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It looks like the self-signed certificate on the 10.11.19.41 sensor has expired.&amp;nbsp; If you try to SSH to the device with puTTY, you can issue the "show version" command to confirm.&amp;nbsp; At the bottom of the output, you will see a section titled "Host Certificate Valid from:".&amp;nbsp; To regenerate a new key, you can execute the "tls generate-key" command from the CLI.&amp;nbsp; Once completed, go back to IME and open the 10.11.19.41 device settings and then click OK.&amp;nbsp; This will force IME to poll the device for the update certificate.&amp;nbsp; Below is a snippet from one of my lab sensors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MainApp&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; S-2011_NOV_21_16_13_7_1_2_48&amp;nbsp;&amp;nbsp; (Release)&amp;nbsp;&amp;nbsp; 2011-11-21T16:15:59-0600&amp;nbsp;&amp;nbsp; Running&lt;/P&gt;&lt;P&gt;AnalysisEngine&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; S-2011_NOV_21_16_13_7_1_2_48&amp;nbsp;&amp;nbsp; (Release)&amp;nbsp;&amp;nbsp; 2011-11-21T16:15:59-0600&amp;nbsp;&amp;nbsp; Running&lt;/P&gt;&lt;P&gt;CollaborationApp&amp;nbsp;&amp;nbsp; S-2011_NOV_21_16_13_7_1_2_48&amp;nbsp;&amp;nbsp; (Release)&amp;nbsp;&amp;nbsp; 2011-11-21T16:15:59-0600&amp;nbsp;&amp;nbsp; Running&lt;/P&gt;&lt;P&gt;CLI&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; S-2011_NOV_21_16_13_7_1_2_48&amp;nbsp;&amp;nbsp; (Release)&amp;nbsp;&amp;nbsp; 2011-11-21T16:15:59-0600&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Upgrade History:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;* IPS-sig-S625-req-E4&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:25:24 UTC Wed Feb 15 2012&lt;/P&gt;&lt;P&gt;&amp;nbsp; IPS-sig-S625-req-E4.pkg&amp;nbsp;&amp;nbsp; 00:29:25 UTC Wed Feb 15 2012&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recovery Partition Version 1.1 - 7.1(3)E4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Host Certificate Valid from: 16-Mar-2011 to 16-Mar-2013&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;R057-4270-2# tls ?&lt;/P&gt;&lt;P&gt;generate-key&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Regenerate server's self-signed X.509 certificate.&lt;/P&gt;&lt;P&gt;R057-4270-2# tls generate-key&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 May 2012 21:59:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915039#M55304</guid>
      <dc:creator>Todd Pula</dc:creator>
      <dc:date>2012-05-04T21:59:23Z</dc:date>
    </item>
    <item>
      <title>issue logging into sensor (screenshot)</title>
      <link>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915040#M55305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, since this is a production box, I need to know if this command could have any adverse affects on the system?&amp;nbsp; I dont see why it would, but I cant really take any chances without doing my research, thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;lp&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2012 01:18:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915040#M55305</guid>
      <dc:creator>lukeprimm</dc:creator>
      <dc:date>2012-05-08T01:18:53Z</dc:date>
    </item>
    <item>
      <title>issue logging into sensor (screenshot)</title>
      <link>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915041#M55306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If this single instance of IME is the only log collector in your environment, it should be safe to regenerate the certificate on the production sensor.&amp;nbsp; If you had a number of log collectors (ie. IME, MARS, CSM, etc.), you would want to coordinate the effort in order to prevent a DoS of the web server on the sensor due to certificate authentication failures.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2012 13:58:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915041#M55306</guid>
      <dc:creator>Todd Pula</dc:creator>
      <dc:date>2012-05-08T13:58:20Z</dc:date>
    </item>
    <item>
      <title>issue logging into sensor (screenshot)</title>
      <link>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915042#M55307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Fortunately it looks like the guys that installed the sensors (are all gone now) didn't set anything up other than the management IP addresses.&amp;nbsp; I don't think they are doing anything at the moment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2012 14:01:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/issue-logging-into-sensor-screenshot/m-p/1915042#M55307</guid>
      <dc:creator>lukeprimm</dc:creator>
      <dc:date>2012-05-08T14:01:56Z</dc:date>
    </item>
  </channel>
</rss>

