<?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: Adding a windows-based SFTP server for DNA Automation Backup failed in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/adding-a-windows-based-sftp-server-for-dna-automation-backup/m-p/4085911#M652</link>
    <description>So you are correct.  The GUI backup configuration must use either nfs or a linux based repo.  That information as you stated is mentioned in Cisco docs.  Note that even if you properly setup a Windows based SFTP host and attempt to use it it will fail.  This is because one of the steps DNAC takes to determine/verify that the remote host is a linux host upon username/pass verification is that it will run a uname check.  Once the uname check fails you see this specific error in the DNAC gui:&lt;BR /&gt;'Remote server is not supported: Error running uname on remote server'&lt;BR /&gt;&lt;BR /&gt;We have experienced remote backup issues in early versions of code so the workaround was to configure and run the backup locally to a DNAC node in the cluster on a partition with enough space.  Then ssh to the node, tar up that directory, and move it off of the host.  I am not recommending this, but sharing a workaround from my experience.  I strongly suggest setting up a remote repo and ensuring it works as expected.  &lt;BR /&gt;&lt;BR /&gt;Lastly, for anything that may not be included in the sw release you are running that you feel would be a nice feature request please utilize the 'make-a-wish' utility in the DNAC gui.  I use this all the time and Cisco is pretty responsive.  Good luck &amp;amp; HTH!&lt;BR /&gt;</description>
    <pubDate>Thu, 14 May 2020 15:33:24 GMT</pubDate>
    <dc:creator>Mike.Cifelli</dc:creator>
    <dc:date>2020-05-14T15:33:24Z</dc:date>
    <item>
      <title>Adding a windows-based SFTP server for DNA Automation Backup failed</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/adding-a-windows-based-sftp-server-for-dna-automation-backup/m-p/3952327#M329</link>
      <description>&lt;P&gt;Adding a windows-based SFTP host to DNAC failed.&amp;nbsp; "No Permission..." warning at UI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In contrast a SFTP session could be established from the maglev CLI to the SFTP host successfully.&lt;/P&gt;&lt;P&gt;Whats different between DNA App and CLI behavior for SFTP connections ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As stated in the DNAC admin guide only linux-based SFTP hosts are supported.&lt;/P&gt;&lt;P&gt;Any reason for this limitation for SFTP service ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please share your experience / feedback !&lt;/P&gt;</description>
      <pubDate>Sun, 03 Nov 2019 16:53:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/adding-a-windows-based-sftp-server-for-dna-automation-backup/m-p/3952327#M329</guid>
      <dc:creator>holger.moersfelder@global.ntt</dc:creator>
      <dc:date>2019-11-03T16:53:32Z</dc:date>
    </item>
    <item>
      <title>Re: Adding a windows-based SFTP server for DNA Automation Backup failed</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/adding-a-windows-based-sftp-server-for-dna-automation-backup/m-p/4085911#M652</link>
      <description>So you are correct.  The GUI backup configuration must use either nfs or a linux based repo.  That information as you stated is mentioned in Cisco docs.  Note that even if you properly setup a Windows based SFTP host and attempt to use it it will fail.  This is because one of the steps DNAC takes to determine/verify that the remote host is a linux host upon username/pass verification is that it will run a uname check.  Once the uname check fails you see this specific error in the DNAC gui:&lt;BR /&gt;'Remote server is not supported: Error running uname on remote server'&lt;BR /&gt;&lt;BR /&gt;We have experienced remote backup issues in early versions of code so the workaround was to configure and run the backup locally to a DNAC node in the cluster on a partition with enough space.  Then ssh to the node, tar up that directory, and move it off of the host.  I am not recommending this, but sharing a workaround from my experience.  I strongly suggest setting up a remote repo and ensuring it works as expected.  &lt;BR /&gt;&lt;BR /&gt;Lastly, for anything that may not be included in the sw release you are running that you feel would be a nice feature request please utilize the 'make-a-wish' utility in the DNAC gui.  I use this all the time and Cisco is pretty responsive.  Good luck &amp;amp; HTH!&lt;BR /&gt;</description>
      <pubDate>Thu, 14 May 2020 15:33:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/adding-a-windows-based-sftp-server-for-dna-automation-backup/m-p/4085911#M652</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2020-05-14T15:33:24Z</dc:date>
    </item>
  </channel>
</rss>

