<?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: PnP Remote Software Repository in Controllers</title>
    <link>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592758#M868</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes!&amp;nbsp; This is called the remote TFTP server for config and images when you create a PnP project.&amp;nbsp; You'll see a checkbox for it.&amp;nbsp; Check the box, then fill in the remote details.&amp;nbsp; I have used this for a bootstrap app of my own, and it works quite well.&amp;nbsp; This can be any remote TFTP server.&amp;nbsp; However, no pre-validation is done to make sure the config and image files exist there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For your branches, you can create specific projects for them that use the desired remote "stage."&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 Dec 2015 15:33:37 GMT</pubDate>
    <dc:creator>Joe Clarke</dc:creator>
    <dc:date>2015-12-29T15:33:37Z</dc:date>
    <item>
      <title>PnP Remote Software Repository</title>
      <link>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592757#M867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a way to specify a remote server or switch for a new device to download the software image from instead of it always being downloaded from the APIC?&amp;nbsp; This would be similar to Remote Staging in LMS 4.2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As an example, a 3650/3850 IOS-XE image is almost 300MB.&amp;nbsp; A branch site may have several dozen switches that would need to be provisioned and downloading the same image over the WAN seems inefficient, especially for smaller circuit sizes like a T1 or NxT1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would be great to either be able to leverage the ISR at the site as a repository, or even leverage the first 3650 to be upgraded to serve the image to the rest of the switches.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 12:26:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592757#M867</guid>
      <dc:creator>thjonson</dc:creator>
      <dc:date>2019-03-01T12:26:25Z</dc:date>
    </item>
    <item>
      <title>Re: PnP Remote Software Repository</title>
      <link>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592758#M868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes!&amp;nbsp; This is called the remote TFTP server for config and images when you create a PnP project.&amp;nbsp; You'll see a checkbox for it.&amp;nbsp; Check the box, then fill in the remote details.&amp;nbsp; I have used this for a bootstrap app of my own, and it works quite well.&amp;nbsp; This can be any remote TFTP server.&amp;nbsp; However, no pre-validation is done to make sure the config and image files exist there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For your branches, you can create specific projects for them that use the desired remote "stage."&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Dec 2015 15:33:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592758#M868</guid>
      <dc:creator>Joe Clarke</dc:creator>
      <dc:date>2015-12-29T15:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: PnP Remote Software Repository</title>
      <link>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592759#M869</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Joseph, that is great.&amp;nbsp; I don't suppose there is a way to use HTTPS or SCP instead of TFTP so the config files aren't transmitted in clear text?&amp;nbsp; As I understand it the config files when sent from the APIC-EM itself are sent via HTTPS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Dec 2015 02:07:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592759#M869</guid>
      <dc:creator>thjonson</dc:creator>
      <dc:date>2015-12-30T02:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: PnP Remote Software Repository</title>
      <link>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592760#M870</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only remote option is using TFTP.&amp;nbsp; The impact may be mitigated in branch offices since the transmission won't have to cross "untrusted" networks.&amp;nbsp; But being able to specify other protocols and credentials would be a nice enhancement.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Dec 2015 17:42:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592760#M870</guid>
      <dc:creator>Joe Clarke</dc:creator>
      <dc:date>2015-12-31T17:42:16Z</dc:date>
    </item>
    <item>
      <title>Re: PnP Remote Software Repository</title>
      <link>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592761#M871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joseph, thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Dec 2015 18:08:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/pnp-remote-software-repository/m-p/3592761#M871</guid>
      <dc:creator>thjonson</dc:creator>
      <dc:date>2015-12-31T18:08:02Z</dc:date>
    </item>
  </channel>
</rss>

