Symptom
File copy via the Secure Copy Protocol (SCP) fails with the error "no such file or directory".
This symptom is observed when copying a file to (to-the-box) or from the firewall (from-the-box).
firewall# copy scp://user@192.0.2.1/tmp/file disk0:
Address or name of remote host [192.0.2.1]?
Source username [user]?
Source filename [tmp/file]?
Destination filename [file]?
no such file or directory: disk0:/file <=======
The debugs for the Secure Shell (debug ssh 255) show the "filesys check: no flashdir mapping found" error:
KSEC-FPR2100-4# copy scp://user@192.0.2.1/tmp/file disk0:
path: scp://user@192.0.2.1/tmp/file
prefix: scp
username: user
password:
location: 192.0.2.1
port:
directory: tmp/
filename: file
path: disk0:/file
prefix: disk0
username:
password:
location:
port:
directory: /
filename: file
Remote Addr: 192.0.2.1
filesys checks entry: mode: sink path: disk0:/file
path: disk0:/file
prefix: disk0
username:
password:
location:
port:
directory: /
filename: file
filesys check: no flashdir mapping found <=======
Conditions
First seen when all of the conditions are in place:
1. Firepower 2100 running Adaptive Security Appliance application (ASA) in platform mode (only).
2. The ciscossh stack is enabled:
ciscoasa(config)# show run ssh
ssh stack ciscossh
...
Workaround
Disable the ciscossh stack:
ciscoasa(config)# no ssh stack ciscossh
Further Problem Description
1. Before disabling ciscossh, users are advised to check the documentation and the command reference to understand the impact. the ciscossh stack provides new features that are unsupported in the classic ASA stack.
2. The symptoms of this defect are not observed in Firepower 2100 running ASA in appliance mode, or other platforms running ASA or FTD, even if the ciscossh stack is enabled.
