<?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 Device administration deployment - License for devices using Radius protocol in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3777538#M486384</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Will device administration license per PSN take care devices&amp;nbsp;with&amp;nbsp;Radius protocol or separate base license will require for Radius?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Customer has devices with TACACS+ and Radius protocol. Want to confirm license required for device administration deployment.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 11 Jan 2019 08:37:21 GMT</pubDate>
    <dc:creator>dngore</dc:creator>
    <dc:date>2019-01-11T08:37:21Z</dc:date>
    <item>
      <title>Device administration deployment - License for devices using Radius protocol</title>
      <link>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3777538#M486384</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Will device administration license per PSN take care devices&amp;nbsp;with&amp;nbsp;Radius protocol or separate base license will require for Radius?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Customer has devices with TACACS+ and Radius protocol. Want to confirm license required for device administration deployment.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 08:37:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3777538#M486384</guid>
      <dc:creator>dngore</dc:creator>
      <dc:date>2019-01-11T08:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: Device administration deployment - License for devices using Radius protocol</title>
      <link>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3777561#M486385</link>
      <description>Device administration license is required for TACACS authentications only. You will have to have base license at the very least to serve RADIUS authentications. In short, your client needs both those licenses. Base/Plus/Apex/Mobility licenses are endpoint based. i.e., based on the number of end clients (PCs/Mobiles etc) that would be authenticating against ISE. Device Administration licenses is based on the number of ISE nodes which would serve TACACS authentications (rather, on how many nodes you would enable device administration persona) at any given point of time.&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jan 2019 09:10:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3777561#M486385</guid>
      <dc:creator>Surendra</dc:creator>
      <dc:date>2019-01-11T09:10:04Z</dc:date>
    </item>
    <item>
      <title>Re: Device administration deployment - License for devices using Radius protocol</title>
      <link>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3777612#M486386</link>
      <description>&lt;P&gt;Thx for quick reply.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So in summary, if customer has 10,000 devices having combination like 8000 with TACACS+ and 2000 with Radius for device administration solution then we will require 2000 ISE base license.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 10:31:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3777612#M486386</guid>
      <dc:creator>dngore</dc:creator>
      <dc:date>2019-01-11T10:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: Device administration deployment - License for devices using Radius protocol</title>
      <link>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3777622#M486387</link>
      <description>Yes, 2000 base licenses for basic RADIUS functionality and ‘X’ number of device administration licenses where ‘X’ is the number of ISE nodes on which the Device Administration Persona is enabled at a given point of time.&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jan 2019 10:47:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3777622#M486387</guid>
      <dc:creator>Surendra</dc:creator>
      <dc:date>2019-01-11T10:47:04Z</dc:date>
    </item>
    <item>
      <title>Re: Device administration deployment - License for devices using Radius protocol</title>
      <link>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3881577#M486388</link>
      <description>&lt;P&gt;I have an additional question regarding the base licenses for RADIUS .&lt;/P&gt;&lt;P&gt;BASE Licenses are usually assigned to active sessions for RADIUS auth. At least for network authn.&lt;/P&gt;&lt;P&gt;Is the base license for RADIUS (device admin) sticked to number of NADs or number of active sessions?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2019 15:46:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/device-administration-deployment-license-for-devices-using/m-p/3881577#M486388</guid>
      <dc:creator>Cengiz Savas</dc:creator>
      <dc:date>2019-06-28T15:46:22Z</dc:date>
    </item>
  </channel>
</rss>

