<?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: Flex connect issue in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194322#M275601</link>
    <description>&lt;P&gt;IOS-XE 17.3 is effectively end of life:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-17/ios-xe-17-3-x-eol.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-17/ios-xe-17-3-x-eol.html&lt;/A&gt;&lt;BR /&gt;Upgrade as per the TAC recommended link below.&lt;/P&gt;
&lt;P&gt;If the WLAN is using local switching, authentication, association and DHCP then it should continue operating in standalone mode.&amp;nbsp; You should have:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no central association&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no central authentication&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no central dhcp&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no central switching&lt;/FONT&gt;&lt;BR /&gt;configured in the wireless profile policy for the WLAN.&lt;/P&gt;
&lt;P&gt;What type of authentication are you using on the WLAN?&lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2024 13:08:03 GMT</pubDate>
    <dc:creator>Rich R</dc:creator>
    <dc:date>2024-09-13T13:08:03Z</dc:date>
    <item>
      <title>Flex connect issue</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194154#M275579</link>
      <description>&lt;P&gt;Hello Experts ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have an AP that's operating in Flex mode and registered to 9800 WLC ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After complaining from clients that random disconnections happening to wifi , i took debugs for one of the clients at the disconnection time and found that client has been disconnected due to AP was unregistered from WLC due to a connectivity issue , now my question if AP operating in Flex mode and SSID policy also in Flex mode , hence even if ap disconnected from wlc , client should continuo operating normally as per my understanding to how FLEX mode works , is that correct ?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 08:15:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194154#M275579</guid>
      <dc:creator>qsosan20</dc:creator>
      <dc:date>2024-09-13T08:15:30Z</dc:date>
    </item>
    <item>
      <title>Re: Flex connect issue</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194156#M275580</link>
      <description>&lt;P&gt;Reboot the AP.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If problem persists, reboot the controller.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It could be&amp;nbsp;&lt;A href="https://quickview.cloudapps.cisco.com/quickview/bug/CSCvx56223" target="_blank" rel="noopener"&gt;CSCvx56223&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 08:25:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194156#M275580</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-09-13T08:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: Flex connect issue</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194159#M275582</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1684277"&gt;@qsosan20&lt;/a&gt;&amp;nbsp;yes your assumption is right, clients should keep connected to a Flexconnect AP even when the AP is disconnected from WLC, but new clients won't be able to connect unless you have configured local-authentication in the Flex profile.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 08:31:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194159#M275582</guid>
      <dc:creator>JPavonM</dc:creator>
      <dc:date>2024-09-13T08:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: Flex connect issue</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194160#M275583</link>
      <description>&lt;P&gt;Hi Leo ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your reply ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I will reboot the AP for now and see ,&lt;/P&gt;
&lt;P&gt;For the bug its affecting 17.3.3 and earlier , however my AP is&amp;nbsp;&lt;/P&gt;
&lt;DIV class="row form-group"&gt;
&lt;DIV class="col-sm-4"&gt;&lt;SPAN class="label ng-binding"&gt;17.3.5.43,&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 08:31:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194160#M275583</guid>
      <dc:creator>qsosan20</dc:creator>
      <dc:date>2024-09-13T08:31:02Z</dc:date>
    </item>
    <item>
      <title>Re: Flex connect issue</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194162#M275585</link>
      <description>&lt;P&gt;Thanks for your conformation&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/324840"&gt;@JPavonM&lt;/a&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 08:32:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194162#M275585</guid>
      <dc:creator>qsosan20</dc:creator>
      <dc:date>2024-09-13T08:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: Flex connect issue</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194166#M275586</link>
      <description>&lt;P&gt;Always assume the bug affects all version.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 08:34:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194166#M275586</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-09-13T08:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: Flex connect issue</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194168#M275587</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#008000"&gt;&lt;U&gt;&amp;nbsp; - Yes ,&lt;/U&gt;&lt;/FONT&gt; client should be able to continue working on a flexconnect based AP&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;Check controller software version installed and consider &lt;FONT color="#008000"&gt;&lt;STRONG&gt;17.12.3&lt;/STRONG&gt;&lt;/FONT&gt; as latest advisory version&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;especially if you are on an older release currently&lt;/P&gt;
&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;&amp;nbsp; + Always useful :&lt;/STRONG&gt;&lt;/U&gt;&amp;nbsp;&amp;nbsp;-&amp;nbsp; Have an overall checkup of the&amp;nbsp;&amp;nbsp;9800&amp;nbsp; WLC controller's configuration with the CLI command&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;FONT color="#008000"&gt;show tech wireless&lt;/FONT&gt;&lt;/STRONG&gt;&amp;nbsp;and feed the output from that into&amp;nbsp;&lt;A href="https://cway.cisco.com/wireless-config-analyzer/" target="_blank"&gt;Wireless Config Analyzer&lt;/A&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; use the &lt;STRONG&gt;&lt;U&gt;full &lt;/U&gt;&lt;/STRONG&gt;command as denoted in green , do not use a simple&lt;EM&gt;&amp;nbsp;&lt;FONT color="#FF0000"&gt;show tech&lt;/FONT&gt;&lt;/EM&gt;&lt;FONT color="#FF0000"&gt;&amp;nbsp;&lt;/FONT&gt;as input for this procedure&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;EM&gt;(Actually you may consider the above &lt;STRONG&gt;mandatory&lt;/STRONG&gt; when working with 9800 controllers)&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 08:34:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194168#M275587</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-09-13T08:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: Flex connect issue</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194322#M275601</link>
      <description>&lt;P&gt;IOS-XE 17.3 is effectively end of life:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-17/ios-xe-17-3-x-eol.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-17/ios-xe-17-3-x-eol.html&lt;/A&gt;&lt;BR /&gt;Upgrade as per the TAC recommended link below.&lt;/P&gt;
&lt;P&gt;If the WLAN is using local switching, authentication, association and DHCP then it should continue operating in standalone mode.&amp;nbsp; You should have:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no central association&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no central authentication&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no central dhcp&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;no central switching&lt;/FONT&gt;&lt;BR /&gt;configured in the wireless profile policy for the WLAN.&lt;/P&gt;
&lt;P&gt;What type of authentication are you using on the WLAN?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 13:08:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-issue/m-p/5194322#M275601</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2024-09-13T13:08:03Z</dc:date>
    </item>
  </channel>
</rss>

