<?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: Cisco ISE not support IOT device in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5304917#M597057</link>
    <description>&lt;P&gt;What software?&lt;/P&gt;</description>
    <pubDate>Wed, 02 Jul 2025 15:30:00 GMT</pubDate>
    <dc:creator>Aref Alsouqi</dc:creator>
    <dc:date>2025-07-02T15:30:00Z</dc:date>
    <item>
      <title>Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286489#M596157</link>
      <description>&lt;P&gt;Dear Cisco lover,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We would like to seek your support on case not functional IoT device when we perform Closed Mode on cisco ise such the MAC addresss can't be learn on switch port.&amp;nbsp;&lt;BR /&gt;Once we configure on switch with Low Impact mode, the&amp;nbsp; IoT device is able to perform without any interruption.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It would be great if someone experienced this case and share the fix solution.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Cisco ISE v3.1&lt;BR /&gt;Thank you,&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 06:51:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286489#M596157</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2025-04-30T06:51:05Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286494#M596158</link>
      <description>&lt;P&gt;You will have to supply some more details. How is the device authenticating to the network? Are there any clues in the session details for the device?&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 07:31:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286494#M596158</guid>
      <dc:creator>Torbjørn</dc:creator>
      <dc:date>2025-04-30T07:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286502#M596159</link>
      <description>&lt;P&gt;Sure things &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/964504"&gt;@Torbjørn&lt;/a&gt;&amp;nbsp;, I have shared you in posting.&amp;nbsp;&lt;BR /&gt;First, we have low impact mode, IoT device we build profile and authentication through MAB.&amp;nbsp;&lt;BR /&gt;Then, when we commit the command of Closed mode, the switch port will be disconnected and no any MAC address learn on switch.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;There is impact only kindly of access door/UPS.&amp;nbsp;&lt;BR /&gt;Fortunately, printer/camera ... can work perfectly on closed mode.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 08:10:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286502#M596159</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2025-04-30T08:10:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286528#M596160</link>
      <description>&lt;P&gt;It true not all device work good with close mode' some need low impact mode since it need to get IP and/or some info before it fully work and start send Frame which make SW learn it MAC.&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 09:42:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286528#M596160</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-04-30T09:42:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286533#M596161</link>
      <description>&lt;P&gt;Any workaround solution&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1065752"&gt;@MHM Cisco World&lt;/a&gt;&amp;nbsp;and how to ensure the right product to support with closed mode?&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 10:05:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286533#M596161</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2025-04-30T10:05:49Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286536#M596162</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;When you enable closed mode on the interfaces used by&amp;nbsp;&lt;SPAN&gt;access door/UPS devices, have you tried bouncing the port? Perhaps these devices aren't transmitting packets as regularly as your printers (that do pass MAB in closed mode0&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;hth&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 10:25:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5286536#M596162</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2025-04-30T10:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5287071#M596191</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/255857"&gt;@andrewswanson&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Just some of IoT device only.&lt;BR /&gt;We can not bounce the port once it disconnected status.&amp;nbsp;&lt;BR /&gt;If we bounce the port, the device will be resulted disconnected.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 May 2025 04:39:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5287071#M596191</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2025-05-02T04:39:33Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5287084#M596192</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/82347"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/284594"&gt;@Aref Alsouqi&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/388087"&gt;@Greg Gibbs&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Do you experience this such an issue?&amp;nbsp;&lt;BR /&gt;Thank you for your idea.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 May 2025 06:21:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5287084#M596192</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2025-05-02T06:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5292532#M596402</link>
      <description>&lt;P&gt;Probably you already resolved this issue by now? one of the main differences between low-impact and closed mode is that with the low-impact mode you would have a default access list applied to the port where some traffic will be allowed. In closed mode anything will be denied on the switch port with the exception for EAPoL traffic until the authentication and authorization are completed. Another main difference in low-impact mode is that the traffic on the switch port will still be passing even if ISE returns an access reject and it will be subject to the switch port access list.&lt;/P&gt;
&lt;P&gt;Now for the IoT or whichever dummy devices to start the authentication process they need to send at least one frame to the switch before the switch relay that info to ISE and based on the response back from ISE the authentication will be accepted or rejected. The devices do not need any IP addressing during this process, and the main detail that will be taken from the frame received from the devices to the switch port is their MAC addresses. Those MAC addresses will be used as their credentials for authentication and also authorization.&lt;/P&gt;
&lt;P&gt;Assuming the authentication has passed, the authorization process would start, and the returned attributes from ISE will be applied to the port, whether to fully open the port or apply specific attributes.&lt;/P&gt;
&lt;P&gt;This process should not change if the port is in low-impact or closed mode. As long as the IoT device sends a frame the switch will take it and relay it to ISE for authentication and subsequently for authorization. If the IoT device does not send any frame this whole process will not be triggered.&lt;/P&gt;
&lt;P&gt;Rebouncing the port usually helps as the connected devices to the switch ports might send some frames, however, other devices might not. Also, some devices might send frames periodically which means that you would need to wait for some time before those devices start talking to the switch by sending some frames.&lt;/P&gt;
&lt;P&gt;Were you getting anything on ISE logs for those devices?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 May 2025 08:33:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5292532#M596402</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-05-21T08:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5292910#M596423</link>
      <description>&lt;P&gt;I am a Cisco ISE lover. Also some IOT network stacks are very poorly implemented. Make sure the firmware is up to date. If that doesn't work you may need to exclude that particular port from authentication.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/identity-service-engine-software-3-1-3-2.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/identity-service-engine-software-3-1-3-2.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 12:11:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5292910#M596423</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-05-22T12:11:39Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5300972#M596855</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/284594"&gt;@Aref Alsouqi&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Not yet resolved, the issue when we unplug cable, this IoT device can't connect or even no MAC address detect on switch.&amp;nbsp;&lt;BR /&gt;Workaround solution just revert to low-impact mode to get device connected, then apply command closed mode one by one.&lt;BR /&gt;&lt;BR /&gt;We don't accept this workaround solution, open with TAC they just capture the switch log but not solution yet.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jun 2025 03:44:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5300972#M596855</guid>
      <dc:creator>oum-odom</dc:creator>
      <dc:date>2025-06-20T03:44:31Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5301056#M596860</link>
      <description>&lt;P&gt;Thanks for the update. What switch model and release are you running on this/these switches out of interest?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jun 2025 10:30:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5301056#M596860</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-06-20T10:30:47Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5304671#M597044</link>
      <description>&lt;P&gt;9200L&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 02:15:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5304671#M597044</guid>
      <dc:creator>oum-odom</dc:creator>
      <dc:date>2025-07-02T02:15:05Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5304917#M597057</link>
      <description>&lt;P&gt;What software?&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 15:30:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5304917#M597057</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-07-02T15:30:00Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306364#M597117</link>
      <description>&lt;P&gt;Hello Aref&amp;nbsp; here the switch software&amp;nbsp;&lt;SPAN&gt;IOSXE.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jul 2025 08:00:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306364#M597117</guid>
      <dc:creator>oum-odom</dc:creator>
      <dc:date>2025-07-07T08:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306414#M597123</link>
      <description>&lt;P&gt;Sorry what I meant, what software release is running on the switch because the issue could be caused by a software bug in that specific release. In the past I saw similar issues that have been fixed with software upgrades.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jul 2025 10:33:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306414#M597123</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-07-07T10:33:49Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306748#M597144</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/284594"&gt;@Aref Alsouqi&lt;/a&gt;&amp;nbsp; could you please share the workable software on switch, since we are running the latest software already.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 01:53:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306748#M597144</guid>
      <dc:creator>oum-odom</dc:creator>
      <dc:date>2025-07-08T01:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306855#M597147</link>
      <description>&lt;P&gt;It depends, I would look at the open caveat/bugs of the release you are running and see if there is anything reported in there.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 09:12:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306855#M597147</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2025-07-08T09:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306863#M597148</link>
      <description>&lt;P&gt;I will send you later today what I think solution for your issue&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 09:35:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5306863#M597148</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-07-08T09:35:57Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE not support IOT device</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5314631#M597484</link>
      <description>&lt;P&gt;Please share&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jul 2025 06:13:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-not-support-iot-device/m-p/5314631#M597484</guid>
      <dc:creator>oum-odom</dc:creator>
      <dc:date>2025-07-28T06:13:08Z</dc:date>
    </item>
  </channel>
</rss>

