<?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: Positioning of ISE and WLC in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914844#M583760</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;We plan to use the Local PSN at each site for authenticating both wireless and wired users using methods such as 802.1x, MAB, and Guest Captive Portal. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Additionally, we intend to use TACACS+ authentication for our network devices. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;It's important to note that we have Active Directory (servers, applications, databases, and more at each site.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Our proposed setup is connecting the ISE and WLC directly to the access switch, which will have an uplink to the Core Switch. We will allocate separate VLANs for ISE, WLC, and AP, without implementing a firewall between them.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;We're considering whether there are any advantages to placing ISE behind a firewall. For the guest network, we plan to establish a separate VLAN with its Layer 2 gateway on the Perimeter Firewall&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 30 Aug 2023 19:50:39 GMT</pubDate>
    <dc:creator>techno.it</dc:creator>
    <dc:date>2023-08-30T19:50:39Z</dc:date>
    <item>
      <title>Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914736#M583752</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are currently in discussions with our vendor regarding the installation of Cisco WLCs and ISE in our organisation. We've got a multi-site setup with a mix of corporate and guest access needs.&lt;BR /&gt;&lt;BR /&gt;Before finalizing the deployment, I'd like to tap into the collective wisdom here to ensure we're on the right track with our design.&lt;/P&gt;&lt;P&gt;At HQ:&lt;BR /&gt;&lt;BR /&gt;ISE - distributed deployment with 2x PSN for HQ, 2x MNT and 2xPAN.&lt;/P&gt;&lt;P&gt;Users- 20, 000&lt;/P&gt;&lt;P&gt;Remote Sites (3 in total): Each remote site has 2x PSN for ISE.&lt;/P&gt;&lt;P&gt;Users- 10,000 at each site&lt;/P&gt;&lt;P&gt;WLC:&lt;BR /&gt;2x WLCs at each remote site for corporate wireless and guest access.&lt;BR /&gt;&lt;BR /&gt;We've chosen to deploy WLC and AP as FlexConnect for both corporate wireless and Guest access with captive portal&lt;/P&gt;&lt;P&gt;My question to the community is: Based on similar requirements and setups, where do you recommend positioning the WLC and ISE within the network?&lt;/P&gt;&lt;P&gt;For those interested in the details, I've shared our current design in this link.&lt;/P&gt;&lt;P&gt;HQ - &lt;A href="https://imgur.com/a/NUtoeL7" target="_blank" rel="noopener"&gt;https://imgur.com/a/NUtoeL7&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Remote - &lt;A href="https://imgur.com/a/2vZ5mLf" target="_blank" rel="noopener"&gt;https://imgur.com/a/2vZ5mLf&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 16:39:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914736#M583752</guid>
      <dc:creator>techno.it</dc:creator>
      <dc:date>2023-08-30T16:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914737#M583753</link>
      <description>&lt;P&gt;what WLC and AP you looking to deploy ? is the network SD-Access ?&lt;/P&gt;
&lt;P&gt;some guide lines where to place WLC&amp;nbsp; placement :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;for ISE deployment i go below presentation and where to place :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.ciscolive.com/c/dam/r/ciscolive/us/docs/2020/pdf/DGTL-BRKSEC-3432-reference.pdf" target="_blank" rel="noopener"&gt;https://www.ciscolive.com/c/dam/r/ciscolive/us/docs/2020/pdf/DGTL-BRKSEC-3432-reference.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Note : some how not able to open that URL may be restrictions my side i guess.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 16:48:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914737#M583753</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-08-30T16:48:59Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914740#M583754</link>
      <description>&lt;P&gt;Hmm&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 16:49:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914740#M583754</guid>
      <dc:creator>jadromepso</dc:creator>
      <dc:date>2023-08-30T16:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914743#M583755</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/286878"&gt;@balaji.bandi&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Without SD-Access&lt;/P&gt;&lt;P&gt;WLC-9800&lt;/P&gt;&lt;P&gt;AP- 9120 and 9115&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have attached the network designs&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 17:00:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914743#M583755</guid>
      <dc:creator>techno.it</dc:creator>
      <dc:date>2023-08-30T17:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914838#M583759</link>
      <description>&lt;P&gt;Why have local PSNs at all?&amp;nbsp; Is the plan to do AAA configuration for local 802.1X from the AP to the PSN?&amp;nbsp; Do you also have local Active Directory?&amp;nbsp; Or any local compute?&amp;nbsp; Even if the users are able to join the network would they actually be able to do anything&lt;/P&gt;
&lt;P&gt;What do you mean by "&lt;SPAN&gt;Based on similar requirements and setups, where do you recommend positioning the WLC and ISE within the network?"&amp;nbsp; I would just deploy wherever you deploy all of your other server footprint.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 19:34:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914838#M583759</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-08-30T19:34:19Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914844#M583760</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;We plan to use the Local PSN at each site for authenticating both wireless and wired users using methods such as 802.1x, MAB, and Guest Captive Portal. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Additionally, we intend to use TACACS+ authentication for our network devices. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;It's important to note that we have Active Directory (servers, applications, databases, and more at each site.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Our proposed setup is connecting the ISE and WLC directly to the access switch, which will have an uplink to the Core Switch. We will allocate separate VLANs for ISE, WLC, and AP, without implementing a firewall between them.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;We're considering whether there are any advantages to placing ISE behind a firewall. For the guest network, we plan to establish a separate VLAN with its Layer 2 gateway on the Perimeter Firewall&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 19:50:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4914844#M583760</guid>
      <dc:creator>techno.it</dc:creator>
      <dc:date>2023-08-30T19:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915322#M583784</link>
      <description>&lt;P&gt;Why not plug ISE and the WLC into the core?&amp;nbsp; What happens if that access switch fails?&amp;nbsp; Do you plan on redundancy here at the local level?&amp;nbsp; Are you buying SNS appliances?&amp;nbsp; Or are these VMs?&lt;/P&gt;
&lt;P&gt;For the guest network yes, protect ISE properly with a firewall.&amp;nbsp; For the internal network, I don't see the firewall as a requirement.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 11:03:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915322#M583784</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-08-31T11:03:09Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915341#M583789</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have SNS appliances. Redundancy is paramount. I can't connect ISE appliance to Core because ISE don't have SFP+ fiber ports on 3655 and 3615 appliances.&lt;/P&gt;&lt;P&gt;I believe ISE is only required to protect from Guest Access Portal. For that&amp;nbsp;we would pop a hole in the firewall to allow traffic from the Guest VLAN to reach ISE on TCP/8443 (or whatever port number you use for the guest portal). I guess it's simple and more secure than bridging the firewall with a 2nd interface from the ISE node.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 12:47:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915341#M583789</guid>
      <dc:creator>techno.it</dc:creator>
      <dc:date>2023-08-31T12:47:30Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915454#M583794</link>
      <description>So what happens if that access switch fails?  Do you have proper redundancy at the access layer?  You could always purchase copper SFPs for the core.&lt;BR /&gt;Either approach is acceptable from the firewall policy, depending on your security requirements/policy.&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Aug 2023 13:03:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915454#M583794</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-08-31T13:03:32Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915459#M583795</link>
      <description>&lt;P&gt;Catalyst 9300 access switch is configured as a Stack with uplinks to Primary and Secondary Core.&lt;/P&gt;&lt;P&gt;We are planning to use a service switch Catalyst 9300 to connect ISE and WLC controllers on it.&lt;/P&gt;&lt;P&gt;I have a concern what about&amp;nbsp;&lt;SPAN&gt;the MAC table size when connecting the WLC controllers to 9300. Does the trunk port connecting to the WLC learn all the MAC addresses of devices associated with an AP when the SSID is configured as Flex Connect?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 13:14:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915459#M583795</guid>
      <dc:creator>techno.it</dc:creator>
      <dc:date>2023-08-31T13:14:32Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915467#M583796</link>
      <description>No, the MAC addresses are learned by the local switch the AP is plugged into.  If the SSID has FlexConnect local switching enabled.&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Aug 2023 13:27:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915467#M583796</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-08-31T13:27:32Z</dc:date>
    </item>
    <item>
      <title>Re: Positioning of ISE and WLC</title>
      <link>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915471#M583797</link>
      <description>&lt;P&gt;&lt;SPAN&gt;In that case, I think the Cisco 9300 should suffice for our requirements, as it will be used to connect 2 ISE Nodes, 2 WLCs, and a cluster of 3 DNACs.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 13:32:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/positioning-of-ise-and-wlc/m-p/4915471#M583797</guid>
      <dc:creator>techno.it</dc:creator>
      <dc:date>2023-08-31T13:32:23Z</dc:date>
    </item>
  </channel>
</rss>

