<?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 ASA 5580 ssh problem suddenly in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077950#M146487</link>
    <description>&lt;P&gt;Hi, I have an ASA 5580 with configured access through ssh. I've been accessing to it since always, but suddenly (noticed today) I can't access any more. I'm receiving this:&lt;/P&gt;
&lt;P&gt;ssh -l username 192.168.0.44&lt;BR /&gt;Connection closed by 192.168.0.44 port 22&lt;/P&gt;
&lt;P&gt;I have another 3 ASA's and I'm accessing them perfectly...&lt;/P&gt;
&lt;P&gt;what could have changed???&lt;/P&gt;
&lt;P&gt;thanks in advance.&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 08:56:13 GMT</pubDate>
    <dc:creator>gasparmenendez</dc:creator>
    <dc:date>2019-03-12T08:56:13Z</dc:date>
    <item>
      <title>ASA 5580 ssh problem suddenly</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077950#M146487</link>
      <description>&lt;P&gt;Hi, I have an ASA 5580 with configured access through ssh. I've been accessing to it since always, but suddenly (noticed today) I can't access any more. I'm receiving this:&lt;/P&gt;
&lt;P&gt;ssh -l username 192.168.0.44&lt;BR /&gt;Connection closed by 192.168.0.44 port 22&lt;/P&gt;
&lt;P&gt;I have another 3 ASA's and I'm accessing them perfectly...&lt;/P&gt;
&lt;P&gt;what could have changed???&lt;/P&gt;
&lt;P&gt;thanks in advance.&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 08:56:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077950#M146487</guid>
      <dc:creator>gasparmenendez</dc:creator>
      <dc:date>2019-03-12T08:56:13Z</dc:date>
    </item>
    <item>
      <title>It's possible some automated</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077951#M146489</link>
      <description>&lt;P&gt;It's possible some automated system has exhausted the vty lines. You'd have to check that via a console connection.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 02:54:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077951#M146489</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-02-15T02:54:47Z</dc:date>
    </item>
    <item>
      <title>it makes sense...actually I</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077952#M146494</link>
      <description>&lt;P&gt;it makes sense...actually I tried to check vty lines but the command is not the same as in IOS. I think here in ASA is &lt;EM&gt;show ssh sessions&lt;/EM&gt;, is that correct??? but more important: how do I clean vty lines??? in IOS the command is &lt;EM&gt;clear vty line #&lt;/EM&gt;, is the same in here??&lt;/P&gt;
&lt;P&gt;thanks in advance.&lt;/P&gt;
&lt;P&gt;BR.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 15:30:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077952#M146494</guid>
      <dc:creator>gasparmenendez</dc:creator>
      <dc:date>2017-02-15T15:30:36Z</dc:date>
    </item>
    <item>
      <title>There's a nice article at</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077953#M146510</link>
      <description>&lt;P&gt;There's a nice article at tunnelsup.com that explains checking the resources, viewing the sessions (as you surmised) and disconnecting them. ('ssh disconnect &amp;lt;session number&amp;gt;')&lt;/P&gt;
&lt;P&gt;https://www.tunnelsup.com/how-to-show-and-clear-user-sessions-on-a-cisco-asa/&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 16:09:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077953#M146510</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-02-15T16:09:52Z</dc:date>
    </item>
    <item>
      <title>Excellent!!!</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077954#M146515</link>
      <description>&lt;P&gt;Excellent!!!&lt;/P&gt;
&lt;P&gt;I'll check it.&lt;/P&gt;
&lt;P&gt;BR.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 16:15:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077954#M146515</guid>
      <dc:creator>gasparmenendez</dc:creator>
      <dc:date>2017-02-15T16:15:40Z</dc:date>
    </item>
    <item>
      <title>Hi Marvin, I connected to the</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077955#M146517</link>
      <description>&lt;P&gt;Hi Marvin, I connected to the ASA via console and did run a couple of commands but shows nothing:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;ASA5580# show resource usage resource ssH&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Resource&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; Current&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Peak&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Limit&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Denied Context&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;ASA5580#&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;ASA5580# show ssh sessions&lt;BR /&gt;ASA5580#&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;what could be happening???&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 19:24:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077955#M146517</guid>
      <dc:creator>gasparmenendez</dc:creator>
      <dc:date>2017-02-15T19:24:50Z</dc:date>
    </item>
    <item>
      <title>Do you have multiple contexts</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077956#M146519</link>
      <description>&lt;P&gt;Do you have multiple contexts?&lt;/P&gt;
&lt;P&gt;Which ASA software version is running on the 5580?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 02:07:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077956#M146519</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-02-16T02:07:39Z</dc:date>
    </item>
    <item>
      <title>Cisco Adaptive Security</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077957#M146521</link>
      <description>&lt;P&gt;&lt;BR /&gt;Cisco Adaptive Security Appliance Software Version 8.4(5)&lt;BR /&gt;Device Manager Version 7.1(1)52&lt;BR /&gt;&lt;BR /&gt;Compiled on Mon 29-Oct-12 10:51 by builders&lt;BR /&gt;System image file is "disk0:/asa845-smp-k8.bin"&lt;BR /&gt;Config file at boot was "startup-config"&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 15:01:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077957#M146521</guid>
      <dc:creator>gasparmenendez</dc:creator>
      <dc:date>2017-02-16T15:01:08Z</dc:date>
    </item>
    <item>
      <title>There was a bug in ASA 8.3(2</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077958#M146523</link>
      <description>&lt;P&gt;There was a bug in ASA 8.3(2.8) where there were orphaned ssh sessions. But that shouldn't affect your release.&lt;/P&gt;
&lt;P&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtq84364/?referring_site=bugquickviewredir&lt;/P&gt;
&lt;P&gt;The bug notes do suggest checking for the session using:&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;show process | include ssh&lt;/PRE&gt;
&lt;P&gt;I have also seen this sometimes be remedied with a simple reload. Are you able to shcedule that?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 15:20:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077958#M146523</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-02-16T15:20:53Z</dc:date>
    </item>
    <item>
      <title>ASA5580# show processes | i</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077959#M146525</link>
      <description>&lt;P&gt;ASA5580# show processes | i ssh&lt;BR /&gt;Mwe 0x0000000001346b80 0x00007ffe73d1f528 0x00007ffe73cf5828&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3 0x00007ffe73d17860 30752/32768 listen/ssh&lt;BR /&gt;Mwe 0x00000000012eaddd 0x00007ffe73d3a438 0x00000000040ea310&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3 0x00007ffe73d325e0 30200/32768 ssh/timer&lt;BR /&gt;ASA5580#&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;reload the appliance would be my last resource...besides, what if it happens again??? I can't be reloading the ASA every time...&lt;/P&gt;
&lt;P&gt;it's very disappointing...&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 15:41:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077959#M146525</guid>
      <dc:creator>gasparmenendez</dc:creator>
      <dc:date>2017-02-16T15:41:19Z</dc:date>
    </item>
    <item>
      <title>Understood. Perhaps the TAC</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077960#M146526</link>
      <description>&lt;P&gt;Understood. Perhaps the TAC would be able to advise further. Are you able to open a TAC case?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2017 02:44:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077960#M146526</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-02-17T02:44:59Z</dc:date>
    </item>
    <item>
      <title>Hi Marvin,</title>
      <link>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077961#M146527</link>
      <description>&lt;P&gt;Hi Marvin,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;reload did the job...now is working fine!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;but I would like to know what happened....&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;BR.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2017 15:20:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5580-ssh-problem-suddenly/m-p/3077961#M146527</guid>
      <dc:creator>gasparmenendez</dc:creator>
      <dc:date>2017-02-17T15:20:31Z</dc:date>
    </item>
  </channel>
</rss>

