Copying The Capture File To An Scp Server - Acopia Adaptive Resource Switch Cli Maintenance Manual

Copying the Capture File to an SCP Server

bstnA6k(cfg)# exit
bstnA6k# copy capture clientCap.cap scp://juser@rh1.wwmed.com:clientCap.cap
Password: jpasswd
bstnA6k# ...
CLI Maintenance Guide
For secure sites, you can upload with the Secure Copy (SCP) protocol. The URL has a
different syntax for SCP transfers:
copy capture capture-file scp://username@server:file
[accept-host-key]
where
capture-file identifies the capture file to copy,
username@ is a valid username at the remote host,
server identifies the SCP server with an IP address or FQDN (for example,
"172.16.100.18" or "deb1.mynet.com"), and
file is the chosen file name. Lead with a slash (scp-server:/file) if the file
path is absolute. Without the slash, the path is presumed to start in the home
directory for username.
accept-host-key (optional) tells the CLI to accept an unknown host key if
offered by the SCP server. The host key authenticates the server; if the key is
unknown, it is possible that an attacker has taken the server's hostname
and/or IP address. Note that any SCP server is "unknown" if the switch has
not had an SCP exchange with it since the switch's last reboot.
The CLI prompts for the username's password. Enter a password that is valid at the
remote site.
For example, the following command exits from cfg mode to priv-exec mode, then
sends the "clientCap.cap" file to juser's home directory on rh1.wwmed.com:
Troubleshooting Network Connections
Capturing IP Traffic in a File
7-27