<?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: HOSTNAME CHANGE ON ISE 2.3 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427630#M519654</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is correct. We usually do this for the FQDN of the VIP defined in a load balancer, for example. Of course, this static FQDN needs to be resolvable by the endpoints to IP address and it also needs matched by certificates used for the web portal.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Nov 2017 18:45:00 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2017-11-21T18:45:00Z</dc:date>
    <item>
      <title>HOSTNAME CHANGE ON ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427627#M519636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A client requested the hostname on the PSN be changed because of the guest redirect URL which contains the PSN hostname. Unfortunately, the client don't like the URL display name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apart form FQDN and Certificate, I want to know if changing hostname on ISE server won't break anything.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2017 15:43:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427627#M519636</guid>
      <dc:creator>kajibola</dc:creator>
      <dc:date>2017-11-21T15:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: HOSTNAME CHANGE ON ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427628#M519637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you already tried the Static IP/Host name/FQDN in Common Tasks &amp;gt; Web Redirection?&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="113522" alt="Screen Shot 2017-11-21 at 8.53.22 AM.png" class="image-1 jive-image" src="/legacyfs/online/fusion/113522_Screen Shot 2017-11-21 at 8.53.22 AM.png" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;You may change the hostname after de-registering the PSN from the deployment and re-register it back afterwards. Hostname changes would also impact Active Directory if used. Please leave and re-join.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2017 16:55:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427628#M519637</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-11-21T16:55:04Z</dc:date>
    </item>
    <item>
      <title>Re: HOSTNAME CHANGE ON ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427629#M519650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@hslai,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do the static FQDN option means that I can put URL of choice there and that is what the PSN will push to guest endpoints (it will no longer be the PSN hostname) which means the static FQDN will also have to be mapped to the PSN IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will try it out when I get back on site. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2017 18:30:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427629#M519650</guid>
      <dc:creator>kajibola</dc:creator>
      <dc:date>2017-11-21T18:30:37Z</dc:date>
    </item>
    <item>
      <title>Re: HOSTNAME CHANGE ON ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427630#M519654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is correct. We usually do this for the FQDN of the VIP defined in a load balancer, for example. Of course, this static FQDN needs to be resolvable by the endpoints to IP address and it also needs matched by certificates used for the web portal.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2017 18:45:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427630#M519654</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-11-21T18:45:00Z</dc:date>
    </item>
    <item>
      <title>Re: HOSTNAME CHANGE ON ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427631#M519660</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@hslai,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will test and revert tomorrow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2017 19:43:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427631#M519660</guid>
      <dc:creator>kajibola</dc:creator>
      <dc:date>2017-11-21T19:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: HOSTNAME CHANGE ON ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427632#M519667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@hslai,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The static FQDN option worked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Nov 2017 10:36:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3427632#M519667</guid>
      <dc:creator>kajibola</dc:creator>
      <dc:date>2017-11-24T10:36:25Z</dc:date>
    </item>
    <item>
      <title>Re: HOSTNAME CHANGE ON ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3852875#M519676</link>
      <description>&lt;P&gt;How do you maintain persistence on the load balancer when using the vip as redirect ip. As the psn that received the first radius packet needs to be the one that serves the web page&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 05:31:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/hostname-change-on-ise-2-3/m-p/3852875#M519676</guid>
      <dc:creator>x00008037</dc:creator>
      <dc:date>2019-05-09T05:31:00Z</dc:date>
    </item>
  </channel>
</rss>

