<?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 Re: Wireless anchor issues in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211848#M276777</link>
    <description>&lt;P&gt;Ive changed the RADIUS IP on both the local and the anchor controller.&lt;/P&gt;&lt;P&gt;There is a route to the whole 192.168.20.x range and the new RADIUS IP is just the next IP in the subnet&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 21 Oct 2024 03:49:43 GMT</pubDate>
    <dc:creator>salamislimy</dc:creator>
    <dc:date>2024-10-21T03:49:43Z</dc:date>
    <item>
      <title>Wireless anchor issues</title>
      <link>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211840#M276774</link>
      <description>&lt;P&gt;My Current scenario is Wireless controller &amp;gt; Anchor Controller &amp;gt; Radius&lt;/P&gt;&lt;P&gt;we are in the process of changing the RADIUS server&lt;/P&gt;&lt;P&gt;In current setup traffic flows as WC&amp;gt;Anchor&amp;gt;RADIUS&lt;/P&gt;&lt;P&gt;But when I change the IP of RADIUS to new RADIUS server, it goes WC&amp;gt;RADIUS, doesnt talk to the anchor.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What am I missing? I have a mobility tunnel to the anchors and the mobility anchors are configured on the SSID&lt;/P&gt;&lt;P&gt;New RADIUS servers are configured on the SSID under AAA servers as well.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 03:16:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211840#M276774</guid>
      <dc:creator>salamislimy</dc:creator>
      <dc:date>2024-10-21T03:16:47Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless anchor issues</title>
      <link>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211847#M276776</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/126378"&gt;@salamislimy&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Where are you changing the Radius IP address, on the foreign or on the anchor wlc?&lt;/P&gt;
&lt;P&gt;Does the anchor have connectivity with the new radius?&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 03:43:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211847#M276776</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2024-10-21T03:43:35Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless anchor issues</title>
      <link>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211848#M276777</link>
      <description>&lt;P&gt;Ive changed the RADIUS IP on both the local and the anchor controller.&lt;/P&gt;&lt;P&gt;There is a route to the whole 192.168.20.x range and the new RADIUS IP is just the next IP in the subnet&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 03:49:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211848#M276777</guid>
      <dc:creator>salamislimy</dc:creator>
      <dc:date>2024-10-21T03:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless anchor issues</title>
      <link>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211849#M276778</link>
      <description>&lt;P&gt;From the anchor, use the following command to test connectivity&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;STRONG&gt;test aaa radius username&amp;nbsp;admin password cisco123 wlan-id 1 apgroup default-group server-index 2&lt;/STRONG&gt;&lt;/PRE&gt;
&lt;P&gt;Just chance the parameters accordingly&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 03:53:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211849#M276778</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2024-10-21T03:53:33Z</dc:date>
    </item>
    <item>
      <title>Re: Wireless anchor issues</title>
      <link>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211851#M276779</link>
      <description>&lt;P&gt;Ensure the mobility tunnels are up&lt;/P&gt;&lt;P&gt;ensure the radius config matches between the foregn and anchor wlcs&lt;/P&gt;&lt;P&gt;ensure routing and firewall rules allow the RADIUS traffic from Anchor to RADIUS&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 04:03:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wireless-anchor-issues/m-p/5211851#M276779</guid>
      <dc:creator>Haydn Andrews</dc:creator>
      <dc:date>2024-10-21T04:03:44Z</dc:date>
    </item>
  </channel>
</rss>

