<?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 SSH authentication in PIX 515E in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ssh-authentication-in-pix-515e/m-p/2047265#M438577</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mukundh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would say it's because of this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;aaa-server RADIUS deadtime 10&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;"While the command may be configured even without having configured the LOCAL method on any of the three authentication and authorization commands described earlier, it only affects operations when a user has configured two methods. Obviously, at this time, the second method must and be &lt;EM&gt;LOCAL&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1161114" style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12.800000190734863px; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;The command specifies the minutes a particular method should be marked unresponsive and skipped. When a AAA server group has been marked unresponsive, the firewall will immediately perform the authentication or authorization against the next method which will be the local firewall user database. Every server in a group must be marked unresponsive before the entire group will be declared unresponsive.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1161115" style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12.800000190734863px; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;When you configure the deadtime to "0", the AAA server group is never considered unresponsive and all authentication and authorization requests are always attempted against this AAA server group first before using the next method in the method list (for example, falling back to the local user database).&lt;/P&gt;&lt;P&gt; &lt;A name="wp1161116" style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12.800000190734863px; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;The&lt;STRONG&gt; [no]&lt;/STRONG&gt; form of this command restores the&lt;STRONG&gt; aaa-server &lt;/STRONG&gt;command to its default value of 10 minutes.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1161117" style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12.800000190734863px; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;The &lt;EM&gt;deadtime&lt;/EM&gt; begins as soon as the last server in the AAA server group has been marked DOWN. A server is marked down when maximum number of attempts defined in max-attempts has been reached and failed to receive a response. Upon expiration of the deadtime, the AAA server group becomes active and all requests will are submitted once again to the AAA servers in the AAA server group."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in your case you should be able to use the radius authentication method 10 minutes later the radius server went down,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please change it to 1 minute, wait and see how it behaves.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Rate all the helpful posts&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Sep 2012 17:24:27 GMT</pubDate>
    <dc:creator>Julio Carvajal</dc:creator>
    <dc:date>2012-09-06T17:24:27Z</dc:date>
    <item>
      <title>SSH authentication in PIX 515E</title>
      <link>https://community.cisco.com/t5/network-security/ssh-authentication-in-pix-515e/m-p/2047264#M438576</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a PIX 515 Ewhich does authentication for SSH via RADIUS protocol and fails over to the local database if radius server goes offline. But when the radius server comes back online, authentication still takes place through LOCAL and not the radius server. Following are the commands:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;aaa-server RADIUS protocol radius &lt;/P&gt;&lt;P&gt;aaa-server RADIUS max-failed-attempts 3 &lt;/P&gt;&lt;P&gt;aaa-server RADIUS deadtime 10 &lt;/P&gt;&lt;P&gt;aaa-server RADIUS (outside) host 208.86.100.41 vinakom1365 timeout 5&lt;/P&gt;&lt;P&gt;aaa-server LOCAL protocol local &lt;/P&gt;&lt;P&gt;aaa authentication ssh console RADIUS LOCAL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco PIX Firewall Version 6.3(5)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone let me know what the issue is?&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;Mukundh&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:51:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-authentication-in-pix-515e/m-p/2047264#M438576</guid>
      <dc:creator>mukundh86</dc:creator>
      <dc:date>2019-03-11T23:51:00Z</dc:date>
    </item>
    <item>
      <title>SSH authentication in PIX 515E</title>
      <link>https://community.cisco.com/t5/network-security/ssh-authentication-in-pix-515e/m-p/2047265#M438577</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mukundh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would say it's because of this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;aaa-server RADIUS deadtime 10&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;"While the command may be configured even without having configured the LOCAL method on any of the three authentication and authorization commands described earlier, it only affects operations when a user has configured two methods. Obviously, at this time, the second method must and be &lt;EM&gt;LOCAL&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1161114" style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12.800000190734863px; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;The command specifies the minutes a particular method should be marked unresponsive and skipped. When a AAA server group has been marked unresponsive, the firewall will immediately perform the authentication or authorization against the next method which will be the local firewall user database. Every server in a group must be marked unresponsive before the entire group will be declared unresponsive.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1161115" style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12.800000190734863px; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;When you configure the deadtime to "0", the AAA server group is never considered unresponsive and all authentication and authorization requests are always attempted against this AAA server group first before using the next method in the method list (for example, falling back to the local user database).&lt;/P&gt;&lt;P&gt; &lt;A name="wp1161116" style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12.800000190734863px; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;The&lt;STRONG&gt; [no]&lt;/STRONG&gt; form of this command restores the&lt;STRONG&gt; aaa-server &lt;/STRONG&gt;command to its default value of 10 minutes.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1161117" style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12.800000190734863px; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;The &lt;EM&gt;deadtime&lt;/EM&gt; begins as soon as the last server in the AAA server group has been marked DOWN. A server is marked down when maximum number of attempts defined in max-attempts has been reached and failed to receive a response. Upon expiration of the deadtime, the AAA server group becomes active and all requests will are submitted once again to the AAA servers in the AAA server group."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in your case you should be able to use the radius authentication method 10 minutes later the radius server went down,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please change it to 1 minute, wait and see how it behaves.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Rate all the helpful posts&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2012 17:24:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-authentication-in-pix-515e/m-p/2047265#M438577</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-09-06T17:24:27Z</dc:date>
    </item>
    <item>
      <title>SSH authentication in PIX 515E</title>
      <link>https://community.cisco.com/t5/network-security/ssh-authentication-in-pix-515e/m-p/2047266#M438578</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are correct. I had to reduce deadtime to resolve the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mukundh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2012 23:37:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-authentication-in-pix-515e/m-p/2047266#M438578</guid>
      <dc:creator>mukundh86</dc:creator>
      <dc:date>2012-09-06T23:37:16Z</dc:date>
    </item>
    <item>
      <title>SSH authentication in PIX 515E</title>
      <link>https://community.cisco.com/t5/network-security/ssh-authentication-in-pix-515e/m-p/2047267#M438579</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mukundh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My pleasure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2012 23:38:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-authentication-in-pix-515e/m-p/2047267#M438579</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-09-06T23:38:58Z</dc:date>
    </item>
  </channel>
</rss>

