<?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 wism module tuning? in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wism-module-tuning/m-p/847084#M97649</link>
    <description>&lt;P&gt;We use the Ciso WISM solution and have a wism ctlr (4.0.217.0) with 57 AP's. During the day we have +/-650 users on this ctrl. (the other has 81 AP;'s and +/-500 users)&lt;/P&gt;&lt;P&gt;Most users are concentrated in classrooms.&lt;/P&gt;&lt;P&gt;In the snmp trap logs we see concentrated in time during the day a lot (+/- 150) of 'AAA Authentication Failure for UserName:xxxxxx User Type: WLAN USER' messages. &lt;/P&gt;&lt;P&gt;There are complains from the users about maintaining the wireless connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also there's sometimes in this busy period a swap from the primary radius srv (Radiator) to the secondary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a best practice for this? In the 'off hours' everything works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 03 Jul 2021 22:03:58 GMT</pubDate>
    <dc:creator>ruud.kruitwagen</dc:creator>
    <dc:date>2021-07-03T22:03:58Z</dc:date>
    <item>
      <title>wism module tuning?</title>
      <link>https://community.cisco.com/t5/wireless/wism-module-tuning/m-p/847084#M97649</link>
      <description>&lt;P&gt;We use the Ciso WISM solution and have a wism ctlr (4.0.217.0) with 57 AP's. During the day we have +/-650 users on this ctrl. (the other has 81 AP;'s and +/-500 users)&lt;/P&gt;&lt;P&gt;Most users are concentrated in classrooms.&lt;/P&gt;&lt;P&gt;In the snmp trap logs we see concentrated in time during the day a lot (+/- 150) of 'AAA Authentication Failure for UserName:xxxxxx User Type: WLAN USER' messages. &lt;/P&gt;&lt;P&gt;There are complains from the users about maintaining the wireless connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also there's sometimes in this busy period a swap from the primary radius srv (Radiator) to the secondary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a best practice for this? In the 'off hours' everything works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 22:03:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism-module-tuning/m-p/847084#M97649</guid>
      <dc:creator>ruud.kruitwagen</dc:creator>
      <dc:date>2021-07-03T22:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: wism module tuning?</title>
      <link>https://community.cisco.com/t5/wireless/wism-module-tuning/m-p/847085#M97650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You might want to check on your EAP timout values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"show advanced eap" from the CLI and consider increasing the timeout values.   &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2007 20:03:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism-module-tuning/m-p/847085#M97650</guid>
      <dc:creator>ddmoe</dc:creator>
      <dc:date>2007-12-06T20:03:56Z</dc:date>
    </item>
    <item>
      <title>Re: wism module tuning?</title>
      <link>https://community.cisco.com/t5/wireless/wism-module-tuning/m-p/847086#M97651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for this information. I found these values. The default values??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(WiSM-slot11-1) &amp;gt;show advanced eap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EAP-Identity-Request Timeout (seconds)........... 1&lt;/P&gt;&lt;P&gt;EAP-Identity-Request Max Retries................. 20&lt;/P&gt;&lt;P&gt;EAP Key-Index for Dynamic WEP.................... 0&lt;/P&gt;&lt;P&gt;EAP Max-Login Ignore Identity Response........... enable&lt;/P&gt;&lt;P&gt;EAP-Request Timeout (seconds).................... 1&lt;/P&gt;&lt;P&gt;EAP-Request Max Retries.......................... 2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any documentation what these parameters do?&lt;/P&gt;&lt;P&gt;EAP-Identity-Request Timeout vs EAP-Request Timeout ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2007 10:25:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism-module-tuning/m-p/847086#M97651</guid>
      <dc:creator>ruud.kruitwagen</dc:creator>
      <dc:date>2007-12-07T10:25:39Z</dc:date>
    </item>
    <item>
      <title>Re: wism module tuning?</title>
      <link>https://community.cisco.com/t5/wireless/wism-module-tuning/m-p/847087#M97652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The defaults are normally sufficient, unless you're using EAP-FAST, in which case you're supposed to up the wait timer from 10seconds, to 20.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2007 12:21:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism-module-tuning/m-p/847087#M97652</guid>
      <dc:creator>Richard Atkin</dc:creator>
      <dc:date>2007-12-07T12:21:06Z</dc:date>
    </item>
  </channel>
</rss>

