<?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 2.7 Patch 1 SFTP Repository SSH issue in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4297049#M565684</link>
    <description>&lt;P&gt;FYSA I also had a similar issue with ISE2.7p2.&amp;nbsp; The fix was re-adding the host key via CLI as&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/624773"&gt;@Colby LeMaire&lt;/a&gt;&amp;nbsp;suggested.&lt;/P&gt;</description>
    <pubDate>Wed, 24 Feb 2021 16:14:05 GMT</pubDate>
    <dc:creator>Mike.Cifelli</dc:creator>
    <dc:date>2021-02-24T16:14:05Z</dc:date>
    <item>
      <title>ISE 2.7 Patch 1 SFTP Repository SSH issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4148357#M562747</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I&amp;nbsp;&lt;/SPAN&gt;have created a new SFTP repository on a ISE 2.7 Patch 1 in GUI.&lt;/P&gt;&lt;P&gt;And I get the error below when I try to validate the repository.&amp;nbsp; What did I miss for the config?&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Repository validation failed due to error - SSH connect error. Verify configuration. In case Backup was restored on different setup, please re-configure the repository passwords (Expected behaviour)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Below the SFTP server's logs (Windows 2K19 OpenSSH works fine with another SFTP Backup for an other app ) :&amp;nbsp;&lt;BR /&gt;13484 2020-09-09 14:15:45.563 debug1: inetd sockets after dupping: 4, 4&lt;BR /&gt;13484 2020-09-09 14:15:45.564 Connection from 10.10.9.13 port 15115 on 10.10.9.4 port 22&lt;BR /&gt;13484 2020-09-09 14:15:45.566 debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1&lt;BR /&gt;13484 2020-09-09 14:15:45.567 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6 PKIX[11.0]&lt;BR /&gt;13484 2020-09-09 14:15:45.567 debug1: match: OpenSSH_7.6 PKIX[11.0] pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002&lt;BR /&gt;13484 2020-09-09 14:15:45.668 debug1: list_hostkey_types: rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.668 debug1: SSH2_MSG_KEXINIT sent [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.668 debug1: SSH2_MSG_KEXINIT received [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.668 debug1: kex: algorithm: curve25519-sha256 [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.668 debug1: kex: host key algorithm: ssh-rsa [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.668 debug1: kex: client-&amp;gt;server cipher: aes128-gcm@openssh.com MAC: &amp;lt;implicit&amp;gt; compression: none [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.668 debug1: kex: server-&amp;gt;client cipher: aes128-gcm@openssh.com MAC: &amp;lt;implicit&amp;gt; compression: none [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.668 debug1: expecting SSH2_MSG_KEX_ECDH_INIT [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.694 debug1: rekey out after 4294967296 blocks [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.694 debug1: SSH2_MSG_NEWKEYS sent [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.694 debug1: Sending SSH2_MSG_EXT_INFO [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.694 debug1: expecting SSH2_MSG_NEWKEYS [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.695 Connection closed by 10.10.9.13 port 15115 [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.696 debug1: do_cleanup [preauth]&lt;BR /&gt;13484 2020-09-09 14:15:45.697 debug1: monitor_read_log: child log fd closed&lt;BR /&gt;13484 2020-09-09 14:15:45.697 debug1: do_cleanup&lt;BR /&gt;13484 2020-09-09 14:15:45.697 debug1: Killing privsep child 11252&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 12:19:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4148357#M562747</guid>
      <dc:creator>Pierre44120</dc:creator>
      <dc:date>2020-09-09T12:19:23Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 Patch 1 SFTP Repository SSH issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4148421#M562748</link>
      <description>&lt;P&gt;Did you add the server host key to the ISE server CLI using the command "crypto host_key add"?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 13:52:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4148421#M562748</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2020-09-09T13:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 Patch 1 SFTP Repository SSH issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4297049#M565684</link>
      <description>&lt;P&gt;FYSA I also had a similar issue with ISE2.7p2.&amp;nbsp; The fix was re-adding the host key via CLI as&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/624773"&gt;@Colby LeMaire&lt;/a&gt;&amp;nbsp;suggested.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 16:14:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4297049#M565684</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2021-02-24T16:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 Patch 1 SFTP Repository SSH issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4448208#M569001</link>
      <description>&lt;P&gt;Hi Mike, I tried your method but it did not work. Is there anything else I can explore?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Ng Turng Hui&lt;/P&gt;</description>
      <pubDate>Thu, 12 Aug 2021 07:09:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4448208#M569001</guid>
      <dc:creator>NgTurngHui7950</dc:creator>
      <dc:date>2021-08-12T07:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 Patch 1 SFTP Repository SSH issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4448211#M569002</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1122385"&gt;@NgTurngHui7950&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Have you executed 'crypto host_key add' on same server you are trying to access it from? In case of multiple ISE nodes, you need to repeat command on all nodes from which you are attempting to read repository.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Milos&lt;/P&gt;</description>
      <pubDate>Thu, 12 Aug 2021 07:29:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4448211#M569002</guid>
      <dc:creator>Milos_Jovanovic</dc:creator>
      <dc:date>2021-08-12T07:29:03Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 Patch 1 SFTP Repository SSH issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4448318#M569005</link>
      <description>&lt;P&gt;Hi Milo,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes i did add Crypto host_key add host &amp;lt;Hostname of SFTP Server&amp;gt; on the exec mode.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This was working fine before I upgrade the Cisco ISE from version 2.3.0 to 2.7.0 . I redo the entire process which is to remove the host_key from the CLI and remove the SFTP Server setting on the GUI, reboot the services, added the SFTP Server settings again and lastly added the host_key.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When i type "show repository &amp;lt;Repository Name&amp;gt;" , I am left with the following error.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;"Repository sftprepo could not be accessed. In case Backup was restored on different setup, please re-configure the repository passwords (Expected behaviour). Failure occurred during request"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am in a pickle here. This is just SFTP and is giving me so much problems. Do you have any idea what may be causing this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Ng Turng Hui&lt;/P&gt;</description>
      <pubDate>Thu, 12 Aug 2021 09:30:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4448318#M569005</guid>
      <dc:creator>NgTurngHui7950</dc:creator>
      <dc:date>2021-08-12T09:30:02Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 Patch 1 SFTP Repository SSH issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4448472#M569014</link>
      <description>&lt;P&gt;You could try to look at logs on the server side, to try to understand something from there, if possible.&lt;/P&gt;&lt;P&gt;It looks you did everything you should. I would contact TAC as next step, as I can't recommend any reasonable troubleshooting step from here.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Milos&lt;/P&gt;</description>
      <pubDate>Thu, 12 Aug 2021 13:38:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4448472#M569014</guid>
      <dc:creator>Milos_Jovanovic</dc:creator>
      <dc:date>2021-08-12T13:38:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 Patch 1 SFTP Repository SSH issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4605177#M574585</link>
      <description>&lt;P&gt;Hi Ng Tung Hui&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a similar problem and I would like to know if you managed to resolve your problem and how if you did?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sydney&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2022 15:48:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4605177#M574585</guid>
      <dc:creator>SydneyMarihoho54099</dc:creator>
      <dc:date>2022-05-05T15:48:23Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 Patch 1 SFTP Repository SSH issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4610121#M574784</link>
      <description>&lt;P&gt;Hi Sydney,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How I resolve the issue is to upgrade the Cisco ISE to Version 2.7 Patch 4. There is a bug is Cisco Ise Version 2.7 which resulted in failure using SFTP. Hope this helps.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Ng Turng Hui&lt;/P&gt;</description>
      <pubDate>Sat, 14 May 2022 05:00:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-patch-1-sftp-repository-ssh-issue/m-p/4610121#M574784</guid>
      <dc:creator>Ng Turng Hui</dc:creator>
      <dc:date>2022-05-14T05:00:07Z</dc:date>
    </item>
  </channel>
</rss>

