<?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 If you have two in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-secondary-licensing/m-p/2475320#M87150</link>
    <description>&lt;P&gt;&lt;SPAN style="color: Black; font-style: normal; font-weight: normal"&gt;If you have two Administration nodes deployed in a high-availability pair, you can obtain a license based on the hardware IDs of both the primary and secondary Administration nodes. After you obtain the license, add it only to the primary Administration node. The license gets replicated to the secondary Administration node.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: Black; font-style: normal; font-weight: normal"&gt;Refer&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/user_guide/ise_user_guide/ise_man_license.html&lt;/P&gt;</description>
    <pubDate>Wed, 19 Mar 2014 09:39:36 GMT</pubDate>
    <dc:creator>Saurav Lodh</dc:creator>
    <dc:date>2014-03-19T09:39:36Z</dc:date>
    <item>
      <title>ISE Secondary licensing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-secondary-licensing/m-p/2475319#M87148</link>
      <description>There used to be a facility to add the secondary ISE admin node to the licensing so that there weren't problems when the primary fell over.
I licensed a primary and secondary yesterday for base in this way. When I filled out the advanced license in the same way it failed and suggested I raise a TAC case.
TAC telling me that only the primary is licensed. Has this changed?
I did ask if this was only for advanced, but got the same answer back "ISE is only licensed on the primary".

Thanks.</description>
      <pubDate>Mon, 11 Mar 2019 04:33:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-secondary-licensing/m-p/2475319#M87148</guid>
      <dc:creator>bikespace</dc:creator>
      <dc:date>2019-03-11T04:33:28Z</dc:date>
    </item>
    <item>
      <title>If you have two</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-secondary-licensing/m-p/2475320#M87150</link>
      <description>&lt;P&gt;&lt;SPAN style="color: Black; font-style: normal; font-weight: normal"&gt;If you have two Administration nodes deployed in a high-availability pair, you can obtain a license based on the hardware IDs of both the primary and secondary Administration nodes. After you obtain the license, add it only to the primary Administration node. The license gets replicated to the secondary Administration node.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: Black; font-style: normal; font-weight: normal"&gt;Refer&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/user_guide/ise_user_guide/ise_man_license.html&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2014 09:39:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-secondary-licensing/m-p/2475320#M87150</guid>
      <dc:creator>Saurav Lodh</dc:creator>
      <dc:date>2014-03-19T09:39:36Z</dc:date>
    </item>
    <item>
      <title>I should have replied an</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-secondary-licensing/m-p/2475321#M87153</link>
      <description>&lt;P&gt;I should have replied an update. Licensing department were mistaken. I showed them documentation and they processed the primary and secondary as initially requested.&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2014 10:03:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-secondary-licensing/m-p/2475321#M87153</guid>
      <dc:creator>bikespace</dc:creator>
      <dc:date>2014-05-29T10:03:33Z</dc:date>
    </item>
  </channel>
</rss>

