<?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 cannot find a network device if it is created by the ERS API in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3895181#M471225</link>
    <description>&lt;P&gt;CSCvq59887&lt;/P&gt;
&lt;P&gt;is recently logged by our TAC on this issue reported by another customer. This defect is not visible externally yet. The workaround section says,&lt;/P&gt;
&lt;PRE&gt;&lt;EM&gt;This can be rectified by two methods:
1. Reload the node and try to re-authenticate. Result = Authentication Successful
2. If we remove "id", "Profile", and "COAPort" from the POST, the newly created NetworkDevice becomes usable instantly.&lt;/EM&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jul 2019 22:34:11 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2019-07-22T22:34:11Z</dc:date>
    <item>
      <title>ISE cannot find a network device if it is created by the ERS API</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3894855#M471219</link>
      <description>&lt;P&gt;Hello everyone, I am running into an issue with ISE and authentication. If I run my script to create a network device it does so and it shows up in ISE, however when I try to have the device authenticate with ISE, in the radius logs, I can see that ISE gives me the following error:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ISE Code:&amp;nbsp;&lt;SPAN&gt;2.4.0.357&lt;/SPAN&gt;&lt;/P&gt;&lt;TABLE border="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Event&lt;/TD&gt;&lt;TD&gt;5405 RADIUS Request dropped&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Failure Reason&lt;/TD&gt;&lt;TD&gt;11007 Could not locate Network Device or AAA Client&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Resolution&lt;/TD&gt;&lt;TD&gt;Verify whether the Network Device or AAA client is configured in: Administration &amp;gt; Network Resources &amp;gt; Network Devices&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Root cause&lt;/TD&gt;&lt;TD&gt;Could not find the network device or the AAA Client while accessing NAS by IP during authentication.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;NAS IPv4 Address&lt;/TD&gt;&lt;TD&gt;10.11.38.253&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The weird part is if I go into the device itself and click, "Save" (Without making any changes, just simply clicking on the IP address then clicking on the white space then save),&amp;nbsp; it will then work.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Has anyone faced any issues like this? In the past two weeks, this is the second bug behavior I have ran into, the other one was with the X-CSRF-TOKEN in post messages to ERS.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Here is my code if anyone is wondering (IP address and UN/PWD omitted):&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;import requests&lt;BR /&gt;import requests.auth&lt;BR /&gt;import json&lt;BR /&gt;from requests.packages.urllib3.exceptions import InsecureRequestWarning&lt;/P&gt;&lt;P&gt;requests.packages.urllib3.disable_warnings(InsecureRequestWarning)&lt;/P&gt;&lt;P&gt;Username = ("x")&lt;BR /&gt;Password = ("x")&lt;/P&gt;&lt;P&gt;headers = {'Content-Type': 'application/json', 'Accept': 'application/json'}&lt;/P&gt;&lt;P&gt;devicename = input("Enter Device Name:")&lt;BR /&gt;deviceid= devicename + "-" + "PyGenerated"&lt;BR /&gt;deviceip = input("Enter Device IP Address:")&lt;BR /&gt;deviceipmask = input("Enter Device IP Mask [0-32]:")&lt;BR /&gt;devicedescription = input("Enter Device Description:")&lt;BR /&gt;devicesecret = input("Enter Device Secret:")&lt;BR /&gt;#devicelocation = input("Enter Device Location:")&lt;BR /&gt;#devicetype = input("Enter Device Type:")&lt;/P&gt;&lt;P&gt;GETDEVICENAME = requests.get("&lt;A href="https://x.x.x.x:9060/ers/config/networkdevice" target="_blank" rel="noopener"&gt;https://x.x.x.x:9060/ers/config/networkdevice&lt;/A&gt;", verify=False, auth=(Username, Password), headers=headers)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ParseName = json.loads(GETDEVICENAME.text)&lt;/P&gt;&lt;P&gt;for STORENAME in ParseName['SearchResult']['resources']:&lt;BR /&gt;CheckNAME = STORENAME["name"]&lt;BR /&gt;if devicename == CheckNAME:&lt;BR /&gt;print("ERROR: A duplicate Device Name has been detected, please re-run the script and use a unique Device Name!")&lt;BR /&gt;exit()&lt;/P&gt;&lt;P&gt;ISEjson= {&lt;BR /&gt;"NetworkDevice" : {&lt;BR /&gt;"id" : deviceid,&lt;BR /&gt;"name" : devicename,&lt;BR /&gt;"description" : devicedescription,&lt;BR /&gt;"authenticationSettings" : {&lt;BR /&gt;"radiusSharedSecret" : devicesecret,&lt;BR /&gt;"enableKeyWrap" : False,&lt;BR /&gt;"dtlsRequired" : False,&lt;BR /&gt;"keyEncryptionKey" : "",&lt;BR /&gt;"messageAuthenticatorCodeKey" : "",&lt;BR /&gt;"keyInputFormat" : "ASCII"&lt;BR /&gt;},&lt;BR /&gt;"profileName" : "Cisco",&lt;BR /&gt;"coaPort" : 1700,&lt;BR /&gt;"dtlsDnsName" : False,&lt;BR /&gt;"NetworkDeviceIPList" : [ {&lt;BR /&gt;"ipaddress" : deviceip,&lt;BR /&gt;"mask" : deviceipmask&lt;BR /&gt;} ],&lt;BR /&gt;"NetworkDeviceGroupList" : [ "Location#All Locations", "Device Type#All Device Types" ]&lt;BR /&gt;}&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;ISE = requests.post("&lt;A href="https://x.x.x.x:9060/ers/config/networkdevice" target="_blank" rel="noopener"&gt;https://x.x.x.x:9060/ers/config/networkdevice&lt;/A&gt;", verify=False, auth=(Username, Password), headers=headers, json=ISEjson)&lt;/P&gt;&lt;P&gt;if ISE.status_code &amp;lt; 400:&lt;BR /&gt;print("SUCCESS: The device has been created and implemented into ISE! Status Code:", ISE.status_code)&lt;BR /&gt;&lt;BR /&gt;if ISE.status_code &amp;gt; 399:&lt;BR /&gt;print("FAILURE: The code has not been pushed to ISE to create the device! Status Code:", ISE.status_code, "\nHere is the error recieved from the API", ISE.text)&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2019 14:54:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3894855#M471219</guid>
      <dc:creator>ArminGradascevic1123</dc:creator>
      <dc:date>2019-07-22T14:54:07Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cannot find a network device if it is created by the ERS API</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3895181#M471225</link>
      <description>&lt;P&gt;CSCvq59887&lt;/P&gt;
&lt;P&gt;is recently logged by our TAC on this issue reported by another customer. This defect is not visible externally yet. The workaround section says,&lt;/P&gt;
&lt;PRE&gt;&lt;EM&gt;This can be rectified by two methods:
1. Reload the node and try to re-authenticate. Result = Authentication Successful
2. If we remove "id", "Profile", and "COAPort" from the POST, the newly created NetworkDevice becomes usable instantly.&lt;/EM&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2019 22:34:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3895181#M471225</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-07-22T22:34:11Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cannot find a network device if it is created by the ERS API</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3895905#M471235</link>
      <description>&lt;P&gt;Hslai,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried both of those and the issue is still present. I tried to view the bug, but I could not. Is there any type of update from Cisco on what is causing this bug to occur?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 17:34:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3895905#M471235</guid>
      <dc:creator>ArminGradascevic1123</dc:creator>
      <dc:date>2019-07-23T17:34:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cannot find a network device if it is created by the ERS API</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3896248#M471239</link>
      <description>&lt;P&gt;Please try it with a simpler body. Below worked for me. I will try yours later when I have more time.&lt;/P&gt;
&lt;PRE class="hljs" style="display: block; overflow-x: auto; padding: 0.5em; background-color: #333333; color: #ffffff;"&gt;{
  &lt;SPAN class="hljs-attr"&gt;"NetworkDevice"&lt;/SPAN&gt; : {
    &lt;SPAN class="hljs-attr"&gt;"name"&lt;/SPAN&gt; : &lt;SPAN class="hljs-string" style="color: #a2fca2;"&gt;"dag"&lt;/SPAN&gt;,
    &lt;SPAN class="hljs-attr"&gt;"authenticationSettings"&lt;/SPAN&gt; : {
      &lt;SPAN class="hljs-attr"&gt;"networkProtocol"&lt;/SPAN&gt; : &lt;SPAN class="hljs-string" style="color: #a2fca2;"&gt;"RADIUS"&lt;/SPAN&gt;,
      &lt;SPAN class="hljs-attr"&gt;"radiusSharedSecret"&lt;/SPAN&gt; : &lt;SPAN class="hljs-string" style="color: #a2fca2;"&gt;"myRadSecret"&lt;/SPAN&gt;
    },
    &lt;SPAN class="hljs-attr"&gt;"NetworkDeviceIPList"&lt;/SPAN&gt; : [
 {
      &lt;SPAN class="hljs-attr"&gt;"ipaddress"&lt;/SPAN&gt; : &lt;SPAN class="hljs-string" style="color: #a2fca2;"&gt;"10.1.100.43"&lt;/SPAN&gt;,
      &lt;SPAN class="hljs-attr"&gt;"mask"&lt;/SPAN&gt; : &lt;SPAN class="hljs-number" style="color: #d36363;"&gt;32&lt;/SPAN&gt;
    } ],
    &lt;SPAN class="hljs-attr"&gt;"NetworkDeviceGroupList"&lt;/SPAN&gt; : [ &lt;SPAN class="hljs-string" style="color: #a2fca2;"&gt;"Location#All Locations"&lt;/SPAN&gt;, &lt;SPAN class="hljs-string" style="color: #a2fca2;"&gt;"IPSEC#Is IPSEC Device#No"&lt;/SPAN&gt; ]
  }
}&amp;nbsp;&amp;nbsp;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2019 01:15:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3896248#M471239</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-07-24T01:15:41Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cannot find a network device if it is created by the ERS API</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3897021#M471296</link>
      <description>&lt;P&gt;Thank you! What worked is adding this in the json code:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"authenticationSettings" : {&lt;BR /&gt;&lt;STRONG&gt;"networkProtocol" : "RADIUS",&lt;/STRONG&gt;&lt;BR /&gt;"radiusSharedSecret" : devicesecret,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was wondering if you guys have any clue as to what causes this bug to occur? We are on 2.4.0.357, thanks for your help mate &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2019 20:19:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cannot-find-a-network-device-if-it-is-created-by-the-ers-api/m-p/3897021#M471296</guid>
      <dc:creator>ArminGradascevic1123</dc:creator>
      <dc:date>2019-07-24T20:19:19Z</dc:date>
    </item>
  </channel>
</rss>

