<?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 802.1x A_While timer in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/802-1x-a-while-timer/m-p/345752#M432788</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have done some testing with 802.1x on IOS 12.1(13)EA1c on Cisco 3550 switches.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the switch does not get an answer from a radius server, then it will retry after some period.&lt;/P&gt;&lt;P&gt;There seems to be a timer in the switch that has some influence on this behaviour.&lt;/P&gt;&lt;P&gt;This timer can not be changed in this IOS version. It can be seen with the &amp;#147;debug dot1x core&amp;#148; command.&lt;/P&gt;&lt;P&gt;Output: dot1x-core(Fa0/1): timer A_WHILE expired&lt;/P&gt;&lt;P&gt;This A_WHILE timer expires every 30 seconds if there is no answer from the RADIUS servers. &lt;/P&gt;&lt;P&gt;The switch will abort the first EAP conversation with the supplicant and start a second EAP conversation with &lt;/P&gt;&lt;P&gt;an &amp;#147;EAP request identity&amp;#148;. The port will not become HELD.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know why this timer exists ?&lt;/P&gt;&lt;P&gt;And can it be modified ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     Regards, Gerard van Bon&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 20:59:33 GMT</pubDate>
    <dc:creator>vanbon</dc:creator>
    <dc:date>2019-03-10T20:59:33Z</dc:date>
    <item>
      <title>802.1x A_While timer</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-a-while-timer/m-p/345752#M432788</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have done some testing with 802.1x on IOS 12.1(13)EA1c on Cisco 3550 switches.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the switch does not get an answer from a radius server, then it will retry after some period.&lt;/P&gt;&lt;P&gt;There seems to be a timer in the switch that has some influence on this behaviour.&lt;/P&gt;&lt;P&gt;This timer can not be changed in this IOS version. It can be seen with the &amp;#147;debug dot1x core&amp;#148; command.&lt;/P&gt;&lt;P&gt;Output: dot1x-core(Fa0/1): timer A_WHILE expired&lt;/P&gt;&lt;P&gt;This A_WHILE timer expires every 30 seconds if there is no answer from the RADIUS servers. &lt;/P&gt;&lt;P&gt;The switch will abort the first EAP conversation with the supplicant and start a second EAP conversation with &lt;/P&gt;&lt;P&gt;an &amp;#147;EAP request identity&amp;#148;. The port will not become HELD.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know why this timer exists ?&lt;/P&gt;&lt;P&gt;And can it be modified ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     Regards, Gerard van Bon&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 20:59:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-a-while-timer/m-p/345752#M432788</guid>
      <dc:creator>vanbon</dc:creator>
      <dc:date>2019-03-10T20:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x A_While timer</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-a-while-timer/m-p/345753#M432789</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think the best solution is to upgrade to IOS &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Feb 2005 14:55:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-a-while-timer/m-p/345753#M432789</guid>
      <dc:creator>umedryk</dc:creator>
      <dc:date>2005-02-03T14:55:17Z</dc:date>
    </item>
  </channel>
</rss>

