<?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: ISE 3.1 Change FQDN for Deployment Nodes in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755481#M579239</link>
    <description>&lt;P&gt;Thank you for sharing the information As &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/325766"&gt;@Karsten Iwen&lt;/a&gt; suggest DNS may fix the issue, But myself never tried that option, since your certs binded to FQDN.&lt;/P&gt;</description>
    <pubDate>Mon, 16 Jan 2023 16:09:54 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2023-01-16T16:09:54Z</dc:date>
    <item>
      <title>ISE 3.1 Change FQDN for Deployment Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755450#M579235</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I want your help about a domain change in my company, which will affect Cisco ISE&lt;/P&gt;&lt;P&gt;We have already register our Cisco ISE VM's with an FQDN which includes the legacy domain of my company.&lt;/P&gt;&lt;P&gt;Our case is that we want to change from ise1.xxx.gr to ise1.yyy.gr in a 2 Node Deployment , with &lt;SPAN&gt;with primary &amp;amp; secondary administration nodes&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;Can you please help me how to do this and if any downtime will occur?&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jan 2023 15:48:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755450#M579235</guid>
      <dc:creator>michailkopsiaftis</dc:creator>
      <dc:date>2023-01-16T15:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 Change FQDN for Deployment Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755460#M579236</link>
      <description>&lt;P&gt;how big is the deployment.&lt;/P&gt;
&lt;P&gt;if you change the domain, you need to change the certs and also where ever applicable, this required ISE to reboot also.&lt;/P&gt;
&lt;P&gt;check some guide lines OLD thread, still usefull :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/network-access-control/changing-domain-name-in-the-ise/td-p/3069219" target="_blank"&gt;https://community.cisco.com/t5/network-access-control/changing-domain-name-in-the-ise/td-p/3069219&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jan 2023 15:41:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755460#M579236</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-01-16T15:41:56Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 Change FQDN for Deployment Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755465#M579237</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/286878"&gt;@balaji.bandi&lt;/a&gt;&amp;nbsp;thank you for your immediate response!&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our deployment is a&amp;nbsp;&lt;SPAN&gt;2 Node Deployment , with&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;with primary &amp;amp; secondary nodes. We have already import the new certificates in the Nodes.&lt;/SPAN&gt;&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="michailkopsiaftis_0-1673884011593.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/173536iEA7C3409F49BB2FA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="michailkopsiaftis_0-1673884011593.png" alt="michailkopsiaftis_0-1673884011593.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jan 2023 15:48:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755465#M579237</guid>
      <dc:creator>michailkopsiaftis</dc:creator>
      <dc:date>2023-01-16T15:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 Change FQDN for Deployment Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755468#M579238</link>
      <description>&lt;P&gt;Are you aware that your ISE deployment will likely work perfectly even if your real Domain is different from the one used on the ISE? Just your DNS needs to be able to resolve the new domain on the ISE nodes. Probably you don't &lt;EM&gt;need&lt;/EM&gt; to change it.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jan 2023 15:56:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755468#M579238</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2023-01-16T15:56:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 Change FQDN for Deployment Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755481#M579239</link>
      <description>&lt;P&gt;Thank you for sharing the information As &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/325766"&gt;@Karsten Iwen&lt;/a&gt; suggest DNS may fix the issue, But myself never tried that option, since your certs binded to FQDN.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jan 2023 16:09:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755481#M579239</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-01-16T16:09:54Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 Change FQDN for Deployment Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755882#M579248</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/325766"&gt;@Karsten Iwen&lt;/a&gt;&amp;nbsp; thanks for your reply! So you propose to create a cname entry in the dns in order to resolve the new domain. Our problem on this is that as&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/286878"&gt;@balaji.bandi&lt;/a&gt;&amp;nbsp;mention we will use the new certificates(exported from the new CA) on both ISE Nodes and we are going to delete the old ones. Do you think that this is a problem;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2023 09:02:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755882#M579248</guid>
      <dc:creator>michailkopsiaftis</dc:creator>
      <dc:date>2023-01-17T09:02:09Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 Change FQDN for Deployment Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755945#M579252</link>
      <description>&lt;P&gt;The name on the certificate is not really related to the node-name. You can just import the certs and assign its functions. But for the domain name I would probably configure a new zone as you likely will use that for everything that is new.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2023 10:58:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-change-fqdn-for-deployment-nodes/m-p/4755945#M579252</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2023-01-17T10:58:05Z</dc:date>
    </item>
  </channel>
</rss>

