<?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: IBNS 2.0 with ISE for dot1x in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358856#M599448</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/59620"&gt;@harryraju&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;What's confusing me is that the following commands under gi1/0/1 enable dot1x&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;no, they don't!&lt;/P&gt;</description>
    <pubDate>Sat, 03 Jan 2026 21:59:15 GMT</pubDate>
    <dc:creator>Karsten Iwen</dc:creator>
    <dc:date>2026-01-03T21:59:15Z</dc:date>
    <item>
      <title>IBNS 2.0 with ISE for dot1x</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358768#M599442</link>
      <description>&lt;DIV&gt;Hi all&lt;/DIV&gt;
&lt;DIV&gt;Hope someone can answer the below for me.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Is a policy-map mandatory for dot1x to work when using IBNS 2.0 with ISE ? &amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I have two ports on a switch configured for dot1x. Out of the two, one is configured without any policy map and the other has a basic policy map attached.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;The port with policy-map attached is working as expected but the port that’s not using a template or policy map is not authenticating.&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;show access-session&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;Interface &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;MAC Address &amp;nbsp; &amp;nbsp;Method &amp;nbsp;Domain &amp;nbsp;Status Fg &amp;nbsp;Session ID&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;--------------------------------------------------------------------------------------------&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;Gi1/0/2 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Mac address &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;dot1x &amp;nbsp; VOICE &amp;nbsp; Auth &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;040DA8C00000004D804E276C&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;Gi1/0/1 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Mac address &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; N/A &amp;nbsp; &amp;nbsp; UNKNOWN Unauth &amp;nbsp; &amp;nbsp; &amp;nbsp;040DA8C000000053806D94FC&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;Gi1/0/1 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Mac address &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; N/A &amp;nbsp; &amp;nbsp; UNKNOWN Unauth &amp;nbsp; &amp;nbsp; &amp;nbsp;040DA8C000000052806D8DC4&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I’m testing with the following setup:&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;ISE version 3.3.0.430&lt;/DIV&gt;
&lt;DIV&gt;Switch - Cat9200-24P on IOS-XE 17.15.03&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I have port 1 on the switch configured as below without any template or policy map attached:&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;interface GigabitEthernet1/0/1&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;description Corporate Data [VLAN xxxx] / Voice [VLAN yyyy]&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;switchport access vlan xxxx&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;switchport mode access&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;switchport voice vlan yyyy&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;device-tracking attach-policy MERAKI_ACCESS_TRACK&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;ip flow monitor MERAKI_TA1_V4_IN input&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;ip flow monitor MERAKI_TA2_IPV4 input&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;ip flow monitor MERAKI_TA1_V4_OUT output&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;ip flow monitor MERAKI_TA2_IPV4 output&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;authentication periodic&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;authentication timer reauthenticate server&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;access-session host-mode multi-domain&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;access-session control-direction in&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;access-session port-control auto&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;mab&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;dot1x pae authenticator&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;dot1x timeout tx-period 7&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;dot1x timeout supp-timeout 7&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;dot1x max-req 3&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;dot1x max-reauth-req 3&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;storm-control broadcast level 10.00&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;storm-control multicast level 10.00&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;storm-control action shutdown&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;storm-control action trap&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;spanning-tree portfast&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;spanning-tree guard root&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;end&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;port 2 on the switch is configured via template with has a policy map attached:&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;interface GigabitEthernet1/0/2&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;device-tracking attach-policy MERAKI_ACCESS_TRACK&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;ip flow monitor MERAKI_TA1_V4_IN input&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;ip flow monitor MERAKI_TA2_IPV4 input&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;ip flow monitor MERAKI_TA1_V4_OUT output&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;ip flow monitor MERAKI_TA2_IPV4 output&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;source template &lt;/I&gt;&lt;SPAN&gt;&lt;I&gt;wired-dot1x-closed&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;spanning-tree portfast&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;end&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;!&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;template &lt;/I&gt;&lt;SPAN&gt;&lt;I&gt;wired-dot1x-closed&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;dot1x pae authenticator&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;dot1x timeout supp-timeout 7&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;dot1x max-req 3&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;storm-control broadcast level 10.00&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;storm-control multicast level 10.00&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;storm-control action shutdown&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;storm-control action trap&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;spanning-tree portfast&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;spanning-tree guard root&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;switchport access vlan xxxx&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;switchport mode access&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;switchport voice vlan yyyy&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;mab&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;access-session host-mode multi-domain&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;access-session control-direction in&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;access-session closed&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;access-session port-control auto&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;authentication periodic&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;authentication timer reauthenticate server&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;service-policy type control subscriber &lt;/I&gt;&lt;SPAN&gt;&lt;I&gt;test_Wired_dot1x_MAB&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;description Corporate Data [VLAN xxxx] / Voice [VLAN yyyy]&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;!&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;policy-map type control subscriber &lt;/I&gt;&lt;SPAN&gt;&lt;I&gt;test_Wired_dot1x_MAB&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp;event session-started match-all&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp; 10 class always do-until-failure&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;&amp;nbsp; &amp;nbsp;10 authenticate using dot1x retries 2 retry-time 0 priority 10&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;I&gt;!&lt;/I&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;So it seems that with a policy map, the switch port doesn’t try to authenticate as I don’t see any logs on ISE for it. &amp;nbsp;Is this by design or have a completely missed something simple here?&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Fri, 02 Jan 2026 21:05:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358768#M599442</guid>
      <dc:creator>harryraju</dc:creator>
      <dc:date>2026-01-02T21:05:11Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 with ISE for dot1x</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358771#M599443</link>
      <description>&lt;P&gt;sorry had a typo in the end ... it should have been... "&amp;nbsp;&lt;SPAN&gt;So it seems that &lt;FONT color="#FF0000"&gt;without&lt;/FONT&gt; a policy map, the switch port doesn’t try to authenticate as I don’t see any logs on ISE for it. &amp;nbsp;Is this by design or have a completely missed something simple here?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jan 2026 21:10:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358771#M599443</guid>
      <dc:creator>harryraju</dc:creator>
      <dc:date>2026-01-02T21:10:14Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 with ISE for dot1x</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358772#M599444</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/59620"&gt;@harryraju&lt;/a&gt;&amp;nbsp;yes, you need a policy-map and relevant class-maps when using IBNS 2.0&lt;/P&gt;
&lt;P&gt;You must convert the IBNS 1.0 configuration to IBNS 2.0 syntax using the command -&amp;nbsp;&lt;STRONG&gt;authentication display new-style.&amp;nbsp;&lt;/STRONG&gt;I don't believe you can run both IBNS 1.0 and 2.0 concurrently.&amp;nbsp;Refer to the wired prescriptive guide for implementaton -&amp;nbsp;&lt;A href="https://community.cisco.com/t5/security-knowledge-base/ise-secure-wired-access-prescriptive-deployment-guide/ta-p/3641515" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/security-knowledge-base/ise-secure-wired-access-prescriptive-deployment-guide/ta-p/3641515&lt;/A&gt;&amp;nbsp;and&amp;nbsp;&lt;A href="https://www.ciscolive.com/c/dam/r/ciscolive/emea/docs/2025/pdf/BRKOPS-2584.pdf" target="_blank"&gt;https://www.ciscolive.com/c/dam/r/ciscolive/emea/docs/2025/pdf/BRKOPS-2584.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jan 2026 21:41:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358772#M599444</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2026-01-02T21:41:28Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 with ISE for dot1x</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358836#M599445</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;already told you that you need it. For some more understanding: On your interface Gig1/0/1, you have a couple of commands that tell the interface what needs to be done *if* 802.1X is used. But you are missing the part where 802.1X is finally enabled, as that is controlled in the policy-map.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jan 2026 16:58:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358836#M599445</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2026-01-03T16:58:04Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 with ISE for dot1x</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358839#M599446</link>
      <description>&lt;P&gt;Thanks Rob. The prescriptive deployment guide is what I used for my deployment and is really good. And the following Cisco live session is also a good deep dive into IBNS 2.0.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2025/pdf/BRKCRT-3002.pdf" target="_blank"&gt;https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2025/pdf/BRKCRT-3002.pdf&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;And I understand that we can't run IBNS 1.0 and 2.0 on the same switch but in my setup, both ports are using IBNS 2.0 commands. So the derived config of gi1/0/2 and run config of gi1/0/1 is identical except for the service-policy that's attached to gi1/0/2.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What's confusing me is that the following commands under gi1/0/1 enable dot1x so why is a service-policy required (assuming I'm not after backup solution for the ISE servers being not available) ?&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;I&gt;interface GigabitEthernet1/0/1&lt;/I&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;...&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;device-tracking attach-policy MERAKI_ACCESS_TRACK&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;authentication periodic&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;authentication timer reauthenticate server&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;access-session host-mode multi-domain&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;access-session control-direction in&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;access-session port-control auto&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;mab&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;dot1x pae authenticator&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;dot1x timeout tx-period 7&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;dot1x timeout supp-timeout 7&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;dot1x max-req 3&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;dot1x max-reauth-req 3&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;...&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jan 2026 17:48:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358839#M599446</guid>
      <dc:creator>harryraju</dc:creator>
      <dc:date>2026-01-03T17:48:10Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 with ISE for dot1x</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358840#M599447</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/325766"&gt;@Karsten Iwen&lt;/a&gt;&amp;nbsp;. Please see my reply to Rob.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jan 2026 17:48:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358840#M599447</guid>
      <dc:creator>harryraju</dc:creator>
      <dc:date>2026-01-03T17:48:48Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 with ISE for dot1x</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358856#M599448</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/59620"&gt;@harryraju&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;What's confusing me is that the following commands under gi1/0/1 enable dot1x&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;no, they don't!&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jan 2026 21:59:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-with-ise-for-dot1x/m-p/5358856#M599448</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2026-01-03T21:59:15Z</dc:date>
    </item>
  </channel>
</rss>

