Cisco Cisco IPS 4255 Sensor

Seite von 44
 
10
Release Notes for Cisco Intrusion Prevention System 6.2(2)E4
OL-21670-01
  Before Upgrading to Cisco IPS 6.2(2)E4
Options
The following options apply:
/erase—Erases the destination file before copying. 
This keyword only applies to the current-config; the backup-config is always overwritten. If this 
keyword is specified for destination current-config, the source configuration is applied to the system 
default configuration. If it is not specified for the destination current-config, the source 
configuration is merged with the current-config.
source_url—The location of the source file to be copied. It can be a URL or keyword.
destination_url—The location of the destination file to be copied. It can be a URL or a keyword.
current-config—The current running configuration. The configuration becomes persistent as the 
commands are entered.
backup-config—The storage location for the configuration backup. 
The exact format of the source and destination URLs varies according to the file. Here are the valid 
types:
ftp:—Source or destination URL for an FTP network server. The syntax for this prefix is:
ftp:[//[username@] location]/relativeDirectory]/filename
ftp:[//[username@]location]//absoluteDirectory]/filename
scp:—Source or destination URL for the SCP network server. The syntax for this prefix is:
scp:[//[username@] location]/relativeDirectory]/filename
scp:[//[username@] location]//absoluteDirectory]/filename
Note
If you use FTP or SCP protocol, you are prompted for a password. If you use SCP protocol, 
you must also add the remote host to the SSH known hosts list.
http:—Source URL for the web server. The syntax for this prefix is:
http:[[/[username@]location]/directory]/filename
https:—Source URL for the web server. The syntax for this prefix is:
https:[[/[username@]location]/directory]/filename
Note
HTTP and HTTPS prompt for a password if a username is required to access the website. If 
you use HTTPS protocol, the remote host must be a TLS trusted host.
Caution
Copying a configuration file from another sensor may result in errors if the sensing interfaces and virtual 
sensors are not configured the same.
Backing Up the Current Configuration to a Remote Server
To back up your current configuration to a remote server, follow these steps:
Step 1
Log in to the CLI using an account with administrator privileges.
Step 2
Back up the current configuration to the remote server.
sensor# copy current-config scp://user@192.0.2.0//configuration/cfg current-config