<?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 WCS reports Radius server port 1813 up and down. in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/wcs-reports-radius-server-port-1813-up-and-down/m-p/1529302#M296999</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;Help me on this, please. I use Radius server 172.20.104.253 and .254 port 1812 to authenticate some wireless clients. However, the .254 keep failling, deactivate on port 1813 (this is from the log); resulting some clients can't authenticate. How do I approach this? Why port 1813 fail effect the authentication which is on port 1812 ?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 00:28:35 GMT</pubDate>
    <dc:creator>xuanhuymai</dc:creator>
    <dc:date>2019-03-11T00:28:35Z</dc:date>
    <item>
      <title>WCS reports Radius server port 1813 up and down.</title>
      <link>https://community.cisco.com/t5/network-access-control/wcs-reports-radius-server-port-1813-up-and-down/m-p/1529302#M296999</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;Help me on this, please. I use Radius server 172.20.104.253 and .254 port 1812 to authenticate some wireless clients. However, the .254 keep failling, deactivate on port 1813 (this is from the log); resulting some clients can't authenticate. How do I approach this? Why port 1813 fail effect the authentication which is on port 1812 ?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 00:28:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/wcs-reports-radius-server-port-1813-up-and-down/m-p/1529302#M296999</guid>
      <dc:creator>xuanhuymai</dc:creator>
      <dc:date>2019-03-11T00:28:35Z</dc:date>
    </item>
    <item>
      <title>Re: WCS reports Radius server port 1813 up and down.</title>
      <link>https://community.cisco.com/t5/network-access-control/wcs-reports-radius-server-port-1813-up-and-down/m-p/1529303#M297002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; What RADIUS sever are you using?&amp;nbsp; Generally I would make sure that your RADIUS server isn't becomming unavailable either due to network problems or service problems on the RADIUS server itself.&amp;nbsp; When you see these errors on your Wireless Controllers can you confirm whether or not the RADIUS server is available at that time?&amp;nbsp; Also the RADIUS timeout on the WLCs are by default 2 seconds, is it possible the requests are taking longer then 2 seconds to be responded to by that server?&lt;/P&gt;&lt;P&gt;--Jesse&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Oct 2010 19:49:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/wcs-reports-radius-server-port-1813-up-and-down/m-p/1529303#M297002</guid>
      <dc:creator>jedubois</dc:creator>
      <dc:date>2010-10-07T19:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: WCS reports Radius server port 1813 up and down.</title>
      <link>https://community.cisco.com/t5/network-access-control/wcs-reports-radius-server-port-1813-up-and-down/m-p/1529304#M297004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;jedubois!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use Cisco ACS as my radius. For laptops, instead using pre-shared key, I use radius to authenticated the laptop. I create user/password on AD (username is laptop name). On laptop under Intel Proset/Wireless utility, I create a profile with this username. Upon startup, the Proset/Wireless utility authenticates this user this radius server; then gives the laptop wireless connectivity; no pre-shared key needed.&lt;/P&gt;&lt;P&gt;On the WCS event view; radius server is timeout (activated and deactivated) every 2 seconds (like you said; it is default). But is on port 1813 and I config radius server on WCS on port 1812.&lt;/P&gt;&lt;P&gt;My questions are what is ideal timeout on each radius server? and why radius server report timeout on port 1813 instead of 1812?&lt;/P&gt;&lt;P&gt;FYI, I ping -t both of my radius servers. And radius servers are available all the time.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Oct 2010 12:24:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/wcs-reports-radius-server-port-1813-up-and-down/m-p/1529304#M297004</guid>
      <dc:creator>xuanhuymai</dc:creator>
      <dc:date>2010-10-12T12:24:51Z</dc:date>
    </item>
    <item>
      <title>Re: WCS reports Radius server port 1813 up and down.</title>
      <link>https://community.cisco.com/t5/network-access-control/wcs-reports-radius-server-port-1813-up-and-down/m-p/1529305#M297006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Port 1813 is the RADIUS Accounting port, the accounting servers and authentications servers on the WCS/WLC are configured seperately with a place to put RADIUS shared secrets in both locations.&amp;nbsp; Check your RADIUS Accounting servers and ensure that the correct IP and shared secret are used in that configuration.&lt;/P&gt;&lt;P&gt;--Jesse&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Oct 2010 12:30:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/wcs-reports-radius-server-port-1813-up-and-down/m-p/1529305#M297006</guid>
      <dc:creator>jedubois</dc:creator>
      <dc:date>2010-10-12T12:30:49Z</dc:date>
    </item>
  </channel>
</rss>

