<?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 Server status:   FAILED in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701992#M557240</link>
    <description>&lt;P&gt;Hello Folks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when i issue the command the sh aaa-server MYACS,I Noted the below msg for server status,how to troubleshoot and fix this issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Server Group:&amp;nbsp;&amp;nbsp;&amp;nbsp; MYACS&lt;BR /&gt;Server Protocol: radius&lt;BR /&gt;Server Address:&amp;nbsp; 192.168.100.100&lt;BR /&gt;Server port:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1645(authentication), 1646(accounting)&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt;Server status:&amp;nbsp;&amp;nbsp; FAILED&lt;/SPAN&gt;, Server disabled at&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 20:24:48 GMT</pubDate>
    <dc:creator>Ibrahim Jamil</dc:creator>
    <dc:date>2019-03-11T20:24:48Z</dc:date>
    <item>
      <title>Server status:   FAILED</title>
      <link>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701992#M557240</link>
      <description>&lt;P&gt;Hello Folks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when i issue the command the sh aaa-server MYACS,I Noted the below msg for server status,how to troubleshoot and fix this issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Server Group:&amp;nbsp;&amp;nbsp;&amp;nbsp; MYACS&lt;BR /&gt;Server Protocol: radius&lt;BR /&gt;Server Address:&amp;nbsp; 192.168.100.100&lt;BR /&gt;Server port:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1645(authentication), 1646(accounting)&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt;Server status:&amp;nbsp;&amp;nbsp; FAILED&lt;/SPAN&gt;, Server disabled at&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:24:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701992#M557240</guid>
      <dc:creator>Ibrahim Jamil</dc:creator>
      <dc:date>2019-03-11T20:24:48Z</dc:date>
    </item>
    <item>
      <title>Re: Server status:   FAILED</title>
      <link>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701993#M557241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX/ASA lost connectivity to radius server. Make sure network path is available and the ASA IP/name and node key correctly configured on Radius server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can test the server authentication from ASA using command - test aaa-server authentication &lt;GROUPNAME&gt;. Also, you can try enabling debug aaa-server see where the issue is.&lt;/GROUPNAME&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hth&lt;/P&gt;&lt;P&gt;MS&lt;/P&gt;&lt;P&gt;&lt;SPAN style=": ; color: #000000; font-color: #000000; "&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 01:26:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701993#M557241</guid>
      <dc:creator>mvsheik123</dc:creator>
      <dc:date>2011-04-22T01:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: Server status:   FAILED</title>
      <link>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701994#M557242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When the AAA server is in FAILED state, you can check to ensure that you have connectivity to the AAA server by trying to ping it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once confirm that connectivity between the ASA and the AAA server is up, you can re-activate the server with the following command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;aaa-server active host 192.168.100.100&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you check the status again:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;show aaa-server MYACS host 192.168.100.100&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it should say it's ACTIVE now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 01:30:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701994#M557242</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-04-22T01:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: Server status:   FAILED</title>
      <link>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701995#M557244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have 3 acs in the group MYACS,both r okay but the third one gave the failed status so when you use this command &lt;STRONG&gt;aaa-server active host 192.168.100.100 ,&lt;/STRONG&gt;r u sure this dosnt affect the first acs(192.168.100.101) who is active and serve the vpn users&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 08:44:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701995#M557244</guid>
      <dc:creator>Ibrahim Jamil</dc:creator>
      <dc:date>2011-04-22T08:44:08Z</dc:date>
    </item>
    <item>
      <title>Re: Server status:   FAILED</title>
      <link>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701996#M557245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The default aaa-server reactivation mechanism is depletion. This means that failed servers only reactivate after all of the servers in the group are inactive. The command given to you will manually reactivate the sever, but it will not affect existing servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Command Reference link:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/command/reference/a1.html#wp1558160"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/command/reference/a1.html#wp1558160&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Brendan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 14:52:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701996#M557245</guid>
      <dc:creator>brquinn</dc:creator>
      <dc:date>2011-04-22T14:52:57Z</dc:date>
    </item>
    <item>
      <title>Re: Server status:   FAILED</title>
      <link>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701997#M557246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With reference to postring about 3 servers in the group.. just a note , on ASA you do not need to add all the 3 servers if they are Master/replica. The master is enough and ASA will get all the info from the master and will look for replica/backup incase Master is not available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;&lt;P&gt;MS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: I mentioned this as I added all the servers on my prod ASA and later realised that was not required. Everything works great with all the servers status 'OK'.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Apr 2011 15:03:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/server-status-failed/m-p/1701997#M557246</guid>
      <dc:creator>mvsheik123</dc:creator>
      <dc:date>2011-04-22T15:03:16Z</dc:date>
    </item>
  </channel>
</rss>

