<?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 Configuring Radius Exception in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333537#M135266</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry about the confusion, on your radius server (depending on the model) you should be able to centralize these accounts so they hit the radius server for authentication and authorization. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This can be done regardless of model of radius server but the device has to support it, I do not thing IAS or NPS has the abitlity but then again that local database is AD, so you would have to build a service account for these devices to connect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To answer your main question, the answer is no, radius configuration on routers, switches, with the exception of wireless lan controllers will not allow you select which database to use based on the username or the source ip address that the request is coming in from. the only time you failover is if the database that it is accessing at the time experiences a failover.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Aug 2013 20:18:10 GMT</pubDate>
    <dc:creator>Tarik Admani</dc:creator>
    <dc:date>2013-08-21T20:18:10Z</dc:date>
    <item>
      <title>Configuring Radius Exception</title>
      <link>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333530#M135140</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've successfully configured several edge devices to use RADIUS.&amp;nbsp; I have an SNMP server that I would like to be able to use the default local authentication.&amp;nbsp; Is it possible to configure an exception so that when authentication is attempted from a particular machine, the router allows for local authentication?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance,&lt;/P&gt;&lt;P&gt;Ali&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 03:47:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333530#M135140</guid>
      <dc:creator>Ali Razavi</dc:creator>
      <dc:date>2019-03-11T03:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring Radius Exception</title>
      <link>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333531#M135157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I checked ISE and the exception is used for authorization. If authentication fails then you are out of luck, unless you plan on using a identity store sequence.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Aug 2013 05:05:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333531#M135157</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-08-20T05:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring Radius Exception</title>
      <link>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333532#M135164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Ali&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;From the Network Devices list page, you can configure new network devices where SNMP settings can&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;also be configured. The polling interval that you specify here query network access devices at regular&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;intervals. In addition to configuring the SNMP Query probe, you must also configure other SNMP&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;settings in the following location:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;Administration &amp;gt; Network Resources &amp;gt; Network Devices.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;You can turn on and turn off SNMP querying for specific NADs based on the following configurations:&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;• &lt;/STRONG&gt;SNMP Query on Link up and New MAC notification turned on or turned off&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;• &lt;/STRONG&gt;CDP SNMP Query on Link up and New MAC notification turned on or turned off&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;• &lt;/STRONG&gt;SNMP Query timer for once an hour for each switch by default&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Note: &lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;“&lt;/STRONG&gt;When you configure SNMP settings on the network devices, you must ensure that the Cisco Device&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;Protocol (CDP) is enabled (by default) on all the ports of the network devices. If you disable CDP on&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;any of the ports on the network devices, then you may not be able to profile properly as you will miss&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;the CDP information of all the connected endpoints. You must also ensure that the Link Layer Discovery&lt;/P&gt;&lt;P style="text-align: justify;"&gt;Protocol (LLDP) is running on all the ports of the network devices”&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;The SNMP Trap receives information from the specific NADs that support MAC notification, linkup,&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;linkdown, and informs. For SNMP Trap to be fully functional, you must enable SNMP Query also. The&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;SNMP Trap probe receives information from the specific NADs when ports come up or go down and&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;endpoints disconnect or connect to your network. The information received is not sufficient to create&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;endpoints in Cisco ISE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Note: &lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;“&lt;/STRONG&gt;Cisco ISE does not support SNMP Traps that are received from the Wireless LAN Controllers (WLCs)&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;and Access Points (APs).&lt;STRONG&gt;”&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;To configure the SNMP Trap, complete the following steps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Step 1&lt;/STRONG&gt;: Choose Administration &amp;gt; System &amp;gt; Deployment &amp;gt; Deployment Nodes List &amp;gt; Edit Node &amp;gt; Profiling&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;Configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Step 2&lt;/STRONG&gt;: Enable Link Trap Query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Step 3&lt;/STRONG&gt;: Enable Mac Trap Query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Step 4&lt;/STRONG&gt;: Choose the Interface from the drop-down list.&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;For example, GigabitEthernet 0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Step 5&lt;/STRONG&gt;: Enter the Port number.&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;For example, 162.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Step 6&lt;/STRONG&gt;: Enter the description of the SNMP Trap.&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; text-align: justify; line-height: normal;"&gt;For example, SNMP TRAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;STRONG&gt;Step 7&lt;/STRONG&gt;: Click Save.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 05:56:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333532#M135164</guid>
      <dc:creator>Muhammad Munir</dc:creator>
      <dc:date>2013-08-21T05:56:55Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring Radius Exception</title>
      <link>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333533#M135174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Muhammad,&lt;BR /&gt;&lt;BR /&gt;I think the question is regarding pulling configs from a management application that uses snmp to authenticate and pull the configuration. The steps you labeled concern snmp profiling for devices.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 05:59:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333533#M135174</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-08-21T05:59:46Z</dc:date>
    </item>
    <item>
      <title>Configuring Radius Exception</title>
      <link>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333534#M135180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you guys for your responses, but none of this is on-track with my original request.&amp;nbsp; Let's just forget about SNMP.&amp;nbsp; I have configured radius authentication on a router, therefore all SSH sessions to that router will now use radius for authentication.&amp;nbsp; I have some service (not SNMP) or some server that needs to regularly login to the router to retrieve configurations etc.&amp;nbsp; Can I configure the router so that it will allow connections from that one IP address to use the default local authentication database instead of radius while all other connections still use radius for authentication, hence the phrase radius exception?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 14:57:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333534#M135180</guid>
      <dc:creator>Ali Razavi</dc:creator>
      <dc:date>2013-08-21T14:57:06Z</dc:date>
    </item>
    <item>
      <title>Configuring Radius Exception</title>
      <link>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333535#M135198</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With aaa on the router you are unable to allow specific usernames&amp;nbsp; authenticate against radius while others authenticate locally, The local&amp;nbsp; database is only used when the radius server fails. You will have to&amp;nbsp; create an account locally on ISE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 18:24:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333535#M135198</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-08-21T18:24:19Z</dc:date>
    </item>
    <item>
      <title>Configuring Radius Exception</title>
      <link>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333536#M135236</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Tarik.&amp;nbsp; We do not have ISE deployed on out network.&amp;nbsp; So you're telling me that there is no way to create a radius exception from a particular IP address unless we deploy ISE and create a local account on it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 20:13:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333536#M135236</guid>
      <dc:creator>Ali Razavi</dc:creator>
      <dc:date>2013-08-21T20:13:00Z</dc:date>
    </item>
    <item>
      <title>Configuring Radius Exception</title>
      <link>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333537#M135266</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry about the confusion, on your radius server (depending on the model) you should be able to centralize these accounts so they hit the radius server for authentication and authorization. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This can be done regardless of model of radius server but the device has to support it, I do not thing IAS or NPS has the abitlity but then again that local database is AD, so you would have to build a service account for these devices to connect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To answer your main question, the answer is no, radius configuration on routers, switches, with the exception of wireless lan controllers will not allow you select which database to use based on the username or the source ip address that the request is coming in from. the only time you failover is if the database that it is accessing at the time experiences a failover.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 20:18:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/configuring-radius-exception/m-p/2333537#M135266</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-08-21T20:18:10Z</dc:date>
    </item>
  </channel>
</rss>

