<?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 Cisco ISE 1.1 Guest Portal Services in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-1-guest-portal-services/m-p/1992694#M197079</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each Cisco ISE policy services node can run a guest portal also if they run in one deployment.&lt;/P&gt;&lt;P&gt;Depending on the way you mean "separate", your requirement can be met in one deployment or in two stand alone deployments. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending on your approach you need four Cisco ISE machines to build the in "one deployment" option. &lt;/P&gt;&lt;P&gt;2 Admin/Monitoring Nodes (Admin is Active/Standby, Monitoring is Active/Active) and two Policy Services Nodes (RADIUS Servers).&amp;nbsp; Both Policy Services Nodes can run the guestportal. The configuration of the WLC determines which Policy Services Node is being used. ISE use RADIUS URL redirect is used to redirect to it's own guest portal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 16 Jun 2012 20:08:40 GMT</pubDate>
    <dc:creator>jwmolenaar</dc:creator>
    <dc:date>2012-06-16T20:08:40Z</dc:date>
    <item>
      <title>Cisco ISE 1.1 Guest Portal Services</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-1-guest-portal-services/m-p/1992693#M197072</link>
      <description>&lt;P&gt;Do you have to have separate ISE appliances or VM clusters to have have 2 separate "Guest Portal" services?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two sites that have their own equipment (Arizona / Illinois):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Cisco ISE Server&lt;/P&gt;&lt;P&gt;- Cisco Wireless LAN Controller&lt;/P&gt;&lt;P&gt;- Cisco Wireless Anchor Controller&lt;/P&gt;&lt;P&gt;- Cisco ASA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My understanding is that I'd need to have the ISE boxes running in "STAND ALONE" mode in order to have two separate "Guest Networks / Portal".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!!!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:10:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-1-guest-portal-services/m-p/1992693#M197072</guid>
      <dc:creator>tdoyle</dc:creator>
      <dc:date>2019-03-11T02:10:50Z</dc:date>
    </item>
    <item>
      <title>Cisco ISE 1.1 Guest Portal Services</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-1-guest-portal-services/m-p/1992694#M197079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each Cisco ISE policy services node can run a guest portal also if they run in one deployment.&lt;/P&gt;&lt;P&gt;Depending on the way you mean "separate", your requirement can be met in one deployment or in two stand alone deployments. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending on your approach you need four Cisco ISE machines to build the in "one deployment" option. &lt;/P&gt;&lt;P&gt;2 Admin/Monitoring Nodes (Admin is Active/Standby, Monitoring is Active/Active) and two Policy Services Nodes (RADIUS Servers).&amp;nbsp; Both Policy Services Nodes can run the guestportal. The configuration of the WLC determines which Policy Services Node is being used. ISE use RADIUS URL redirect is used to redirect to it's own guest portal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 16 Jun 2012 20:08:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-1-guest-portal-services/m-p/1992694#M197079</guid>
      <dc:creator>jwmolenaar</dc:creator>
      <dc:date>2012-06-16T20:08:40Z</dc:date>
    </item>
    <item>
      <title>Cisco ISE 1.1 Guest Portal Services</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-1-guest-portal-services/m-p/1992695#M197092</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;STRONG&gt; &lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As mentioned above, the Sponsor portal should be allowed to work on any node in a deployment, as long as that node also has Policy Services functionality enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please also check the below link,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/ise/1.1/user_guide/ise_guest_pol.html#wp1126706"&gt;http://www.cisco.com/en/US/docs/security/ise/1.1/user_guide/ise_guest_pol.html#wp1126706&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Sep 2013 05:58:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-1-guest-portal-services/m-p/1992695#M197092</guid>
      <dc:creator>Anas Naqvi</dc:creator>
      <dc:date>2013-09-24T05:58:46Z</dc:date>
    </item>
    <item>
      <title>Cisco ISE 1.1 Guest Portal Services</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-1-guest-portal-services/m-p/1992696#M197107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will depend on Network Design you have and ISE version you are running.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Oct 2013 18:31:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-1-guest-portal-services/m-p/1992696#M197107</guid>
      <dc:creator>sahseth</dc:creator>
      <dc:date>2013-10-03T18:31:19Z</dc:date>
    </item>
  </channel>
</rss>

