<?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: System Certificates Backup/Restore in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/system-certificates-backup-restore/m-p/3448865#M509005</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes they are.&lt;/P&gt;&lt;P&gt;You can only restore a config backup on a standalone node.&amp;nbsp; Once restored, you'll have the appropriate system cert that matches the hostname.&amp;nbsp; Let's say your old pan was ise01 and you had a system cert for that.&amp;nbsp; If int he deployment you also had ise02, ise03 with their own system certs, and if you restored the backup onto one of them, then I think ISE is clever enough to apply the appropriate system cert to the standalone node.&lt;/P&gt;&lt;P&gt;However, when you register additional nodes back into the deployment then those standalone nodes will know nothing about the PAN.&amp;nbsp; You'll have to prep each standalone with your PKI Trusted Certs and then the node's system certs prior to registering it with the PAN.&amp;nbsp;&amp;nbsp; You could cheat and use self-signed certs but that's not cool.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Jun 2018 02:50:57 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2018-06-15T02:50:57Z</dc:date>
    <item>
      <title>System Certificates Backup/Restore</title>
      <link>https://community.cisco.com/t5/network-access-control/system-certificates-backup-restore/m-p/3448864#M509004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are system certificates included in a configuration backup of ISE?&amp;nbsp; If so, what happens during a restore?&amp;nbsp; Are the existing system certificates on the target system deleted and replaced with the system certificates from the backup?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2018 21:43:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/system-certificates-backup-restore/m-p/3448864#M509004</guid>
      <dc:creator>matthen</dc:creator>
      <dc:date>2018-06-14T21:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: System Certificates Backup/Restore</title>
      <link>https://community.cisco.com/t5/network-access-control/system-certificates-backup-restore/m-p/3448865#M509005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes they are.&lt;/P&gt;&lt;P&gt;You can only restore a config backup on a standalone node.&amp;nbsp; Once restored, you'll have the appropriate system cert that matches the hostname.&amp;nbsp; Let's say your old pan was ise01 and you had a system cert for that.&amp;nbsp; If int he deployment you also had ise02, ise03 with their own system certs, and if you restored the backup onto one of them, then I think ISE is clever enough to apply the appropriate system cert to the standalone node.&lt;/P&gt;&lt;P&gt;However, when you register additional nodes back into the deployment then those standalone nodes will know nothing about the PAN.&amp;nbsp; You'll have to prep each standalone with your PKI Trusted Certs and then the node's system certs prior to registering it with the PAN.&amp;nbsp;&amp;nbsp; You could cheat and use self-signed certs but that's not cool.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2018 02:50:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/system-certificates-backup-restore/m-p/3448865#M509005</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2018-06-15T02:50:57Z</dc:date>
    </item>
  </channel>
</rss>

