<?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 How to fetch running config using APIC-EM northbound API in Controllers</title>
    <link>https://community.cisco.com/t5/controllers/how-to-fetch-running-config-using-apic-em-northbound-api/m-p/3418753#M997</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to integrate our application with APIC-EM to fetch device inventory and config initially. Though I am able to find and use REST API to get device and host, it doesn't seem to have one to get device running config or any other show command output. Any workaround or is there something in the roadmap to include this API? I am using sandboxapic.cisco.com for my analysis and prototyping.&lt;/P&gt;&lt;P&gt;Our application features are dependent on the device running config and command output, hence the question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Mar 2019 12:42:00 GMT</pubDate>
    <dc:creator>uwankhed</dc:creator>
    <dc:date>2019-03-01T12:42:00Z</dc:date>
    <item>
      <title>How to fetch running config using APIC-EM northbound API</title>
      <link>https://community.cisco.com/t5/controllers/how-to-fetch-running-config-using-apic-em-northbound-api/m-p/3418753#M997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to integrate our application with APIC-EM to fetch device inventory and config initially. Though I am able to find and use REST API to get device and host, it doesn't seem to have one to get device running config or any other show command output. Any workaround or is there something in the roadmap to include this API? I am using sandboxapic.cisco.com for my analysis and prototyping.&lt;/P&gt;&lt;P&gt;Our application features are dependent on the device running config and command output, hence the question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 12:42:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/how-to-fetch-running-config-using-apic-em-northbound-api/m-p/3418753#M997</guid>
      <dc:creator>uwankhed</dc:creator>
      <dc:date>2019-03-01T12:42:00Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch running config using APIC-EM northbound API</title>
      <link>https://community.cisco.com/t5/controllers/how-to-fetch-running-config-using-apic-em-northbound-api/m-p/3418754#M998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Both are supported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one caveat, the /network-device/{network-device-id}/config&amp;nbsp; API will return a sanitised configuration, with sensitive information removed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOTE: {network-device-id} is the 32char UUID for the device you want the configuration for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have documented the "command runner" api in this blog post.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.cisco.com/migration-blogpost/8708"&gt;APIC-EM 1.4 Update  - Part 1 CommandRunner&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Nov 2017 13:11:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/how-to-fetch-running-config-using-apic-em-northbound-api/m-p/3418754#M998</guid>
      <dc:creator>aradford</dc:creator>
      <dc:date>2017-11-30T13:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch running config using APIC-EM northbound API</title>
      <link>https://community.cisco.com/t5/controllers/how-to-fetch-running-config-using-apic-em-northbound-api/m-p/3418755#M999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks so much.&lt;/P&gt;&lt;P&gt;One more thing. I don't see device os name (i.e. ios, nxos) in the device inventory response. I know there are few other inventory attributes that can possibly be used to derive the os name, but still.&lt;/P&gt;&lt;P&gt;The output of &lt;SPAN style="color: #505050; font-family: OpenSans, Helvetica, Arial, sans-serif; font-size: 12px; background-color: #fafafa;"&gt;&lt;A class="jive-link-external-small" href="http://sandboxapic.cisco.com/api/v1/network-device/ip-address/10.2.2.2:" rel="nofollow" target="_blank"&gt;http://sandboxapic.cisco.com/api/v1/network-device/ip-address/10.2.2.2:&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #505050; font-family: OpenSans, Helvetica, Arial, sans-serif; font-size: 12px; background-color: #fafafa;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "response": {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "location": "85b0e2d7-d5c3-4f78-8938-45bd482b2087",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "type": "Cisco 2911 Integrated Services Router G2",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "family": "Routers",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "errorCode": "DEV-UNREACHED",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "serialNumber": "FTX1840ALBY",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "role": "DISTRIBUTION",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "lastUpdateTime": 1512214557465,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "macAddress": "f0:7f:06:bb:dc:81",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "softwareVersion": "15.2(4)M6a",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "inventoryStatusDetail": "&amp;lt;status&amp;gt;&amp;lt;general code=\"DEV_UNREACHED\"/&amp;gt;&amp;lt;/status&amp;gt;",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "upTime": "174 days, 23:49:53.28",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "series": "Cisco 2900 Series Integrated Services Routers G2",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "locationName": "Barcelona",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "tagCount": "1",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "hostname": "Branch-Router2",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "errorDescription": "SNMP timeouts are occurring with this device. Either the SNMP credentials are not correctly provided to controller or the device is responding too slow. Please ensure correct credentials are provided in discovery/global credentials and run discovery again.&amp;nbsp; You can run the new discovery for this device alone using the “range discovery” feature",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "lastUpdated": "2017-12-02 11:35:57",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "roleSource": "MANUAL",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "apManagerInterfaceIp": "",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "bootDateTime": "2016-05-28 00:29:46",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "collectionStatus": "Partial Collection Failure",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "interfaceCount": "7",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "lineCardCount": "1",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "lineCardId": "94da60d6-5fc3-4613-bce7-7bc03e517647",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "managementIpAddress": "10.2.2.2",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "memorySize": "300246160",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "platformId": "CISCO2911/K9",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "reachabilityFailureReason": "SNMP Connectivity Failed",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "reachabilityStatus": "Unreachable",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "snmpContact": "",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "snmpLocation": "",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "tunnelUdpPort": null,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "instanceUuid": "6ce631db-9212-4587-867f-b8f3aed1702d",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "id": "6ce631db-9212-4587-867f-b8f3aed1702d"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; },&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "version": "1.0"&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 Dec 2017 12:01:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/how-to-fetch-running-config-using-apic-em-northbound-api/m-p/3418755#M999</guid>
      <dc:creator>uwankhed</dc:creator>
      <dc:date>2017-12-02T12:01:49Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch running config using APIC-EM northbound API</title>
      <link>https://community.cisco.com/t5/controllers/how-to-fetch-running-config-using-apic-em-northbound-api/m-p/3418756#M1000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeap, that is a good point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It can be inferred from the platform/family/type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is a good candidate for "make a wish".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Dec 2017 03:18:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/how-to-fetch-running-config-using-apic-em-northbound-api/m-p/3418756#M1000</guid>
      <dc:creator>aradford</dc:creator>
      <dc:date>2017-12-03T03:18:29Z</dc:date>
    </item>
  </channel>
</rss>

