<?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 Updating credentials for multiple devices in Controllers</title>
    <link>https://community.cisco.com/t5/controllers/updating-credentials-for-multiple-devices/m-p/3470944#M663</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Out of my 2k devices in APIC-EM there are now about 200 devices that has CLI-AUTH-ERROR or DEV-UNREACHED status.&lt;BR /&gt;To fix this I intend to take out the inventory with the API and sort on the devices that needs to be rediscovered with the correct credentials and push jobs to the Discovery.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After we upgraded to 1.6.1 it seems like the discovery service is not working correctly. Whenever we create a new discovery job we get an error saying that a job with that name already exists no matter what we set as a name for the job. The job is created, but it never starts and is just stuck. Has anyone else had this issue with the discovery?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Mar 2019 12:43:17 GMT</pubDate>
    <dc:creator>daniel.sunde1</dc:creator>
    <dc:date>2019-03-01T12:43:17Z</dc:date>
    <item>
      <title>Updating credentials for multiple devices</title>
      <link>https://community.cisco.com/t5/controllers/updating-credentials-for-multiple-devices/m-p/3470944#M663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Out of my 2k devices in APIC-EM there are now about 200 devices that has CLI-AUTH-ERROR or DEV-UNREACHED status.&lt;BR /&gt;To fix this I intend to take out the inventory with the API and sort on the devices that needs to be rediscovered with the correct credentials and push jobs to the Discovery.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After we upgraded to 1.6.1 it seems like the discovery service is not working correctly. Whenever we create a new discovery job we get an error saying that a job with that name already exists no matter what we set as a name for the job. The job is created, but it never starts and is just stuck. Has anyone else had this issue with the discovery?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 12:43:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/updating-credentials-for-multiple-devices/m-p/3470944#M663</guid>
      <dc:creator>daniel.sunde1</dc:creator>
      <dc:date>2019-03-01T12:43:17Z</dc:date>
    </item>
  </channel>
</rss>

