<?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: WLC Blocking in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564834#M239243</link>
    <description>&lt;P&gt;The main function of a traditional &lt;A href="https://ciscocentral.blogspot.com/p/300-730-cisco-implementing-secure.html" target="_self"&gt;wireless LAN controller (WLC)&lt;/A&gt; is to configure wireless access points (AP) that connect to it locally.&lt;/P&gt;</description>
    <pubDate>Sat, 19 Mar 2022 06:25:29 GMT</pubDate>
    <dc:creator>alirafaleiro</dc:creator>
    <dc:date>2022-03-19T06:25:29Z</dc:date>
    <item>
      <title>WLC Blocking</title>
      <link>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564564#M239225</link>
      <description>&lt;P&gt;Hi All,&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can I know which 3rd party device is causing the blocking in WLC, there is a description here that it is blockedbyFS.&lt;/P&gt;&lt;P&gt;Is there a way that I can know which FS is causing this? I am assuming this is a forescout because there was an integration made between forescout and WLC via snmpv3. I just want to be sure if a 3rd party is capable of doing it. Please see screenshot below&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIA,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tim&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Forescout blocking.jpg" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/145395i36E808DCEBCBE3E4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Forescout blocking.jpg" alt="Forescout blocking.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 05 Mar 2022 11:34:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564564#M239225</guid>
      <dc:creator>workmen</dc:creator>
      <dc:date>2022-03-05T11:34:01Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Blocking</title>
      <link>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564574#M239226</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;gt;...&amp;nbsp;I am assuming this is a forescout because&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;- The status &lt;FONT color="#FF0000"&gt;Blockby&lt;STRONG&gt;FS&lt;/STRONG&gt;&lt;/FONT&gt; seems rather descriptive indeed (FS=forescout) , are you using FS as a NAC-policy service (network access control). Or ISE or other ? If FS are NAC-policies correct ? If Radius is used , check for authenticating details on the radius server too&amp;nbsp; ? Normally this is not related to SNMP(v3)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Use , for instance an open-SSID as test to verify that basic wireless can work (&lt;STRONG&gt;e.g.&lt;/STRONG&gt;)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;M.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 05 Mar 2022 12:54:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564574#M239226</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-03-05T12:54:52Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Blocking</title>
      <link>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564606#M239227</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;Follow&lt;/P&gt;</description>
      <pubDate>Sat, 05 Mar 2022 14:55:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564606#M239227</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2022-03-05T14:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Blocking</title>
      <link>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564673#M239230</link>
      <description>&lt;P&gt;Yes, Provided that you give SNMP write access to ForceScout NAC it can add MAC addresses to Cisco WLC's. I remember this was working only in AierOS WLC's. Forcescount will perform something similar to ISE profiling (compliance check) and if it fails NAC will automatically add the MAC address to disabled clients.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But for the newer 9800's they required a different level of access, as I remember they wanted an user account in the WLC with CLI access to add the MAC addresses to block list.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 05 Mar 2022 18:57:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564673#M239230</guid>
      <dc:creator>Arshad Safrulla</dc:creator>
      <dc:date>2022-03-05T18:57:50Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Blocking</title>
      <link>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564765#M239238</link>
      <description>&lt;P&gt;yes FS is used as NAC. I will verify it with my team&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you very much&lt;/P&gt;</description>
      <pubDate>Sun, 06 Mar 2022 03:39:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564765#M239238</guid>
      <dc:creator>workmen</dc:creator>
      <dc:date>2022-03-06T03:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Blocking</title>
      <link>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564767#M239239</link>
      <description>&lt;P&gt;yes, the currently deployed APs are Cisco AP 3600 and 3700, we have a 9120 ax ap but it runs on vwlc as of now because the 9800 is under VA Scan.&lt;/P&gt;&lt;P&gt;Thank You very much&lt;/P&gt;</description>
      <pubDate>Sun, 06 Mar 2022 03:41:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564767#M239239</guid>
      <dc:creator>workmen</dc:creator>
      <dc:date>2022-03-06T03:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Blocking</title>
      <link>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564834#M239243</link>
      <description>&lt;P&gt;The main function of a traditional &lt;A href="https://ciscocentral.blogspot.com/p/300-730-cisco-implementing-secure.html" target="_self"&gt;wireless LAN controller (WLC)&lt;/A&gt; is to configure wireless access points (AP) that connect to it locally.&lt;/P&gt;</description>
      <pubDate>Sat, 19 Mar 2022 06:25:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4564834#M239243</guid>
      <dc:creator>alirafaleiro</dc:creator>
      <dc:date>2022-03-19T06:25:29Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Blocking</title>
      <link>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4565117#M239263</link>
      <description>&lt;P&gt;So I believe you have your answer then. Just heard from our security team that when you integrate 9800’s with forcescout you need write access to CLI. SNMP write access will not work with 9800’s.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Mar 2022 03:43:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-blocking/m-p/4565117#M239263</guid>
      <dc:creator>Arshad Safrulla</dc:creator>
      <dc:date>2022-03-07T03:43:56Z</dc:date>
    </item>
  </channel>
</rss>

