Table Of Contents
Working With Configuration Files
Displaying the Current Configuration
Displaying the Current Submode Configuration
Filtering the Current Configuration Output
Filtering the Current Submode Configuration Output
Displaying the Contents of a Logical File
Copying and Restoring the Configuration File Using a Remote Server
Creating and Using a Backup Configuration File
Erasing the Configuration File
Working With Configuration Files
This chapter describes how to use commands that show, copy, and erase the configuration file. It contains the following sections:
•Displaying the Current Configuration
•Displaying the Current Submode Configuration
•Filtering the Current Configuration Output
•Filtering the Current Submode Configuration Output
•Displaying the Contents of a Logical File
•Copying and Restoring the Configuration File Using a Remote Server
•Creating and Using a Backup Configuration File
•Erasing the Configuration File
Displaying the Current Configuration
Use the show configuration or the more current-config command to display the contents of the current configuration.
To display the contents of the current configuration, follow these steps:
Step 1 Log in to the CLI.
Step 2 Display the current configuration:
sensor# show configuration
! ------------------------------
! Current configuration last modified Fri Dec 17 21:38:23 2004
! ------------------------------
! ------------------------------
! ------------------------------
service event-action-rules rules0
! ------------------------------
host-ip 10.89.130.108/23,10.89.130.1
standard-time-zone-name UTC
! ------------------------------
! ------------------------------
! ------------------------------
! ------------------------------
! ------------------------------
service signature-definition sig0
specify-payload-source yes
event-action produce-alert|produce-verbose-alert|deny-attacker-inline|deny-conne
ction-inline|deny-packet-inline|log-attacker-packets|log-pair-packets|log-victim
-packets|request-block-connection|request-block-host|request-snmp-trap|reset-tcp
-connection|modify-packet-inline
event-action produce-alert|produce-verbose-alert|deny-attacker-inline|deny-conne
ction-inline|deny-packet-inline|log-attacker-packets|log-pair-packets|log-victim
-packets|request-block-connection|request-block-host|request-snmp-trap|reset-tcp
-connection|modify-packet-inline
edit-default-sigs-only default-signatures-only
specify-syn-flood-max-embrionic yes
! ------------------------------
! ------------------------------
service trusted-certificates
trusted-certificates 10.89.130.108 certificate MIICJDCCAY0CCPbSkgXUchJIMA0GCSqGS
Ib3DQEBBQUAMFcxCzAJBgNVBAYTAlVTMRwwGgYDVQQKExNDaXNjbyBTeXN0ZW1zLCBJbmMuMRIwEAYDV
QQLEwlTU00tSVBTMjAxFjAUBgNVBAMTDTEwLjg5LjEzMC4xMDgwHhcNMDMwMTAzMDE1MjEwWhcNMDUwM
TAzMDE1MjEwWjBXMQswCQYDVQQGEwJVUzEcMBoGA1UEChMTQ2lzY28gU3lzdGVtcywgSW5jLjESMBAGA
1UECxMJU1NNLUlQUzIwMRYwFAYDVQQDEw0xMC44OS4xMzAuMTA4MIGfMA0GCSqGSIb3DQEBAQUAA4GNA
DCBiQKBgQCzldqLFG4MT4bfgh3mJfP/DCilnnaLfzHK9FdnhmWI4FY+9MVvAI7MOhAcuV6HYfyp6n6cY
vH+Eswzl9uv7H5nouID9St9GI3YrSUtlIQAJ4QVL2DwWP230x6KdHrYqcj+Nmhc7AnnPypjidwGSfF+V
etIJLEeRFh/mI2JcmwF2QIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAAUI2PLANTOehxvCfwd6UAFXvy8ui
fbjqKMC1jrrF+f9KGkxmR+XZvUaGOS83FYDXlXJvB5Xyxms+Y01wGjzKKpxegBoan8OB8o193Ueszdpv
z2xYmiEgywCDyVJRsw3hAFMXWMS5XsBUiHtw0btHH0j7ElFZxUjZv12fGz8hlnY
! ------------------------------
Displaying the Current Submode Configuration
Use the show settings command in a submode to display the current configuration of that submode.
To display the current configuration of a submode, follow these steps:
Step 1 Log in to the CLI.
Step 2 Display the current configuration of the service analysis engine submode:
sensor# configure terminal
sensor(config)# service analysis-engine
sensor(config-ana)# show settings
-----------------------------------------------
-----------------------------------------------
max-open-iplog-files: 20 <defaulted>
-----------------------------------------------
-----------------------------------------------
virtual-sensor (min: 1, max: 255, current: 1)
-----------------------------------------------
-----------------------------------------------
description: default virtual sensor <defaulted>
signature-definition: sig0 <protected>
event-action-rules: rules0 <protected>
physical-interface (min: 0, max: 999999999, current: 0)
-----------------------------------------------
-----------------------------------------------
logical-interface (min: 0, max: 999999999, current: 0)
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
Step 3 Display the current configuration of the service authentication submode:
sensor# configure terminal
sensor(config)# service authentication
sensor(config-aut)# show settings
attemptLimit: 0 <defaulted>
Step 4 Display the current configuration of the service event-action-rules submode:
sensor# configure terminal
sensor(config)# service event-action-rules rules0
sensor(config-rul)# show settings
variables (min: 0, max: 256, current: 0)
-----------------------------------------------
-----------------------------------------------
overrides (min: 0, max: 12, current: 0)
-----------------------------------------------
-----------------------------------------------
filters (min: 0, max: 4096, current: 0 - 0 active, 0 inactive)
-----------------------------------------------
-----------------------------------------------
global-overrides-status: Enabled <defaulted>
global-filters-status: Enabled <defaulted>
global-summarization-status: Enabled <defaulted>
global-metaevent-status: Enabled <defaulted>
global-deny-timeout: 3600 <defaulted>
global-block-timeout: 30 <defaulted>
max-denied-attackers: 10000 <defaulted>
-----------------------------------------------
target-value (min: 0, max: 5, current: 0)
-----------------------------------------------
-----------------------------------------------
Step 5 Display the current configuration of the service host submode:
sensor# configure terminal
sensor(config)# service host
sensor(config-hos)# show settings
-----------------------------------------------
host-ip: 10.89.130.108/23,10.89.130.1 default: 10.1.9.201/24,10.1.9.1
host-name: sensor default: sensor
telnet-option: enabled default: disabled
access-list (min: 0, max: 512, current: 1)
-----------------------------------------------
network-address: 0.0.0.0/0
-----------------------------------------------
-----------------------------------------------
ftp-timeout: 300 seconds <defaulted>
login-banner-text: <defaulted>
-----------------------------------------------
-----------------------------------------------
offset: 0 minutes default: 0
standard-time-zone-name: UTC default: UTC
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
Step 6 Display the current configuration of the service interface submode:
sensor# configure terminal
sensor(config)# service interface
sensor(config-int)# show settings
physical-interfaces (min: 0, max: 999999999, current: 2)
-----------------------------------------------
-----------------------------------------------
media-type: backplane <protected>
admin-state: enabled <protected>
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
media-type: tx <protected>
admin-state: disabled <protected>
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
command-control: GigabitEthernet0/0 <protected>
bypass-mode: auto <defaulted>
-----------------------------------------------
missed-percentage-threshold: 0 percent <defaulted>
notification-interval: 30 seconds <defaulted>
idle-interface-delay: 30 seconds <defaulted>
-----------------------------------------------
Step 7 Display the current configuration for the service logger submode:
sensor# configure terminal
sensor(config)# service logger
sensor(config-log)# show settings
-----------------------------------------------
enable-debug: false <defaulted>
individual-zone-control: false <defaulted>
-----------------------------------------------
zone-control (min: 0, max: 999999999, current: 14)
-----------------------------------------------
severity: debug <defaulted>
zone-name: AuthenticationApp
severity: warning <defaulted>
severity: warning <defaulted>
severity: warning <defaulted>
zone-name: ctlTransSource
severity: warning <defaulted>
severity: warning <defaulted>
severity: warning <defaulted>
severity: warning <defaulted>
severity: warning <defaulted>
severity: warning <defaulted>
severity: warning <defaulted>
severity: warning <defaulted>
severity: warning <defaulted>
severity: warning <defaulted>
-----------------------------------------------
Step 8 Display the current configuration for the service network access submode:
sensor# configure terminal
sensor(config)# service network-access
sensor(config-net)# show settings
-----------------------------------------------
log-all-block-events-and-errors: true <defaulted>
enable-nvram-write: false <defaulted>
enable-acl-logging: false <defaulted>
allow-sensor-block: false <defaulted>
block-enable: true <defaulted>
block-max-entries: 250 <defaulted>
max-interfaces: 250 <defaulted>
master-blocking-sensors (min: 0, max: 100, current: 0)
-----------------------------------------------
-----------------------------------------------
never-block-hosts (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
never-block-networks (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
block-hosts (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
block-networks (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
user-profiles (min: 0, max: 250, current: 1)
-----------------------------------------------
-----------------------------------------------
enable-password: <hidden>
-----------------------------------------------
-----------------------------------------------
cat6k-devices (min: 0, max: 250, current: 1)
-----------------------------------------------
-----------------------------------------------
communication: ssh-3des default: ssh-3des
nat-address: 0.0.0.0 <defaulted>
block-vlans (min: 0, max: 100, current: 1)
-----------------------------------------------
-----------------------------------------------
pre-vacl-name: aaaa default:
post-vacl-name: bbbb default:
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
router-devices (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
firewall-devices (min: 0, max: 250, current: 0)
-----------------------------------------------
-----------------------------------------------
Step 9 Display the current configuration for the notification submode:
sensor# configure terminal
sensor(config)# service notification
sensor(config-not)# show settings
trap-destinations (min: 0, max: 10, current: 0)
-----------------------------------------------
-----------------------------------------------
error-filter: error|fatal <defaulted>
enable-detail-traps: false <defaulted>
enable-notifications: false <defaulted>
enable-set-get: false <defaulted>
snmp-agent-port: 161 <defaulted>
snmp-agent-protocol: udp <defaulted>
read-only-community: public <defaulted>
read-write-community: private <defaulted>
trap-community-name: public <defaulted>
system-location: Unknown <defaulted>
system-contact: Unknown <defaulted>
Step 10 Display the current configuration for the signature definitions submode:
sensor# configure terminal
sensor(config)# service signature-definition sig0
sensor(config-sig)# show settings
variables (min: 0, max: 256, current: 1)
-----------------------------------------------
-----------------------------------------------
web-ports: 80-80,3128-3128,8000-8000,8010-8010,8080-8080,8888-8888,2432
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
http-enable: false <defaulted>
max-outstanding-http-requests-per-connection: 10 <defaulted>
aic-web-ports: 80-80,3128-3128,8000-8000,8010-8010,8080-8080,8888-8888,
-----------------------------------------------
ftp-enable: false <defaulted>
-----------------------------------------------
-----------------------------------------------
ip-reassemble-mode: nt <defaulted>
-----------------------------------------------
-----------------------------------------------
Step 11 Display the current configuration for the SSH known hosts submode:
sensor# configure terminal
sensor(config)# service ssh-known-hosts
sensor(config-ssh)# show settings
rsa1-keys (min: 0, max: 500, current: 0)
-----------------------------------------------
-----------------------------------------------
Step 12 Display the current configuration for the trusted certificates submode:
sensor# configure terminal
sensor(config)# service trusted-certificate
sensor(config-tru)# show settings
trusted-certificates (min: 0, max: 500, current: 1)
-----------------------------------------------
common-name: 10.89.130.108
certificate: MIICJDCCAY0CCPbSkgXUchJIMA0GCSqGSIb3DQEBBQUAMFcxCzAJBgNVBAYTA
lVTMRwwGgYDVQQKExNDaXNjbyBTeXN0ZW1zLCBJbmMuMRIwEAYDVQQLEwlTU00tSVBTMjAxFjAUBgNVB
AMTDTEwLjg5LjEzMC4xMDgwHhcNMDMwMTAzMDE1MjEwWhcNMDUwMTAzMDE1MjEwWjBXMQswCQYDVQQGE
wJVUzEcMBoGA1UEChMTQ2lzY28gU3lzdGVtcywgSW5jLjESMBAGA1UECxMJU1NNLUlQUzIwMRYwFAYDV
QQDEw0xMC44OS4xMzAuMTA4MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzldqLFG4MT4bfgh3mJ
fP/DCilnnaLfzHK9FdnhmWI4FY+9MVvAI7MOhAcuV6HYfyp6n6cYvH+Eswzl9uv7H5nouID9St9GI3Yr
SUtlIQAJ4QVL2DwWP230x6KdHrYqcj+Nmhc7AnnPypjidwGSfF+VetIJLEeRFh/mI2JcmwF2QIDAQABM
A0GCSqGSIb3DQEBBQUAA4GBAAUI2PLANTOehxvCfwd6UAFXvy8uifbjqKMC1jrrF+f9KGkxmR+XZvUaG
OS83FYDXlXJvB5Xyxms+Y01wGjzKKpxegBoan8OB8o193Ueszdpvz2xYmiEgywCDyVJRsw3hAFMXWMS5
XsBUiHtw0btHH0j7ElFZxUjZv12fGz8hlnY
-----------------------------------------------
Step 13 Display the current configuration for the web server submode:
sensor# configure terminal
sensor(config)# service web-server
sensor(config-web)# show settings
enable-tls: true <defaulted>
server-id: HTTP/1.1 compliant <defaulted>
Filtering the Current Configuration Output
Use the show configuration | [begin | exclude | include] regular-expression command to search or filter the output of the contents of the current configuration.
Note Users with operator or viewer privileges can search or filter the current-config only.
The following options apply:
•|—The pipe symbol indicates that an output processing specification follows.
•begin—Begins unfiltered output of the show configuration command with the first line that contains the regular expression specified.
•exclude—Excludes lines in the output of the show configuration command that contain a particular regular expression.
•include—Includes only the lines in the output of the show configuration command that contain the regular expression you specify.
•regular-expression—Any regular expression found in the show configuration command output.
Note The regular-expression option is case sensitive and allows for complex matching requirements.
To search or filter the output of the contents of the current configuration, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
Step 2 Search the configuration output beginning with the regular expression "ssh," for example
Note The show configuration | begin regular-expression command begins unfiltered output of the show command with the first line that contains the specified regular expression.
sensor# show configuration | begin ssh
! ------------------------------
! ------------------------------
service signature-definition sig0
specify-payload-source yes
Note Press Ctrl-C to stop the output and return to the CLI prompt.
Step 3 Filter the current configuration so that you exclude lines that contain a regular expression, for example, "service":
sensor# show configuration | exclude service
! ------------------------------
! Current configuration last modified Fri Dec 17 21:38:23 2004
! ------------------------------
! ------------------------------
! ------------------------------
! ------------------------------
host-ip 10.89.130.108/23,10.89.130.1
standard-time-zone-name UTC
! ------------------------------
! ------------------------------
Note Press Ctrl-C to stop the output and return to the CLI prompt.
Step 4 Filter the current configuration so that you include lines that contain a regular expression, for example, "service":
sensor# show configuration | include service
service event-action-rules rules0
service signature-definition sig0
service trusted-certificates
Filtering the Current Submode Configuration Output
Use the show settings | [begin | exclude | include] keyword command in the submode you are interested in to search or filter the output of the contents of the submode configuration.
The following options apply:
•|—The pipe symbol indicates that an output processing specification follows.
•begin—Begins unfiltered output of the show settings command with the first line that contains the regular expression specified.
•exclude—Excludes lines in the output of the show settings command that contain a particular regular expression.
•include—Includes only the lines in the output of the show settings command that contain the regular expression you specify.
•regular-expression—Any regular expression found in the show settings command output.
Note The regular-expression option is case sensitive and allows for complex matching requirements.
To search or filter the output of the contents of the submode configuration, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
Step 2 Search the output of the event action rules settings for the regular expression, "filters," for example:
sensor# configure terminal
sensor(config)# service event-action-rules
sensor(config-rul)# show settings | begin filters
filters (min: 0, max: 4096, current: 0 - 0 active, 0 inactive)
-----------------------------------------------
-----------------------------------------------
global-overrides-status: Enabled <defaulted>
global-filters-status: Enabled <defaulted>
global-summarization-status: Enabled <defaulted>
global-metaevent-status: Enabled <defaulted>
global-deny-timeout: 3600 <defaulted>
global-block-timeout: 15 default: 30
max-denied-attackers: 10000 <defaulted>
-----------------------------------------------
target-value (min: 0, max: 5, current: 0)
-----------------------------------------------
-----------------------------------------------
Step 3 Filter the output of the network access settings to exclude the regular expression:
sensor# configure terminal
sensor(config)# service network-access
sensor(config-net)# show settings | exclude false
-----------------------------------------------
log-all-block-events-and-errors: true default: true
block-enable: true default: true
block-max-entries: 11 default: 250
max-interfaces: 13 default: 250
master-blocking-sensors (min: 0, max: 100, current: 1)
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
-----------------------------------------------
never-block-hosts (min: 0, max: 250, current: 1)
-----------------------------------------------
ip-address: 10.89.146.112
-----------------------------------------------
-----------------------------------------------
never-block-networks (min: 0, max: 250, current: 1)
-----------------------------------------------
ip-address: 88.88.88.0/24
Step 4 Filter the output of the host settings to include the regular expression "ip":
sensor# configure terminal
sensor(config)# service host
sensor(config-hos)# show settings | include ip
host-ip: 10.89.149.185/25,10.89.149.254 default: 10.1.9.201/24,10.1.9.1
Displaying the Contents of a Logical File
Use the more keyword command to display the contents of a logical file, such as the current system configuration or the saved backup system configuration.
The following options apply:
•keyword—Either the current-config or the backup-config.
–current-config—The current running configuration. This configuration becomes persistent as the commands are entered.
–backup-config—The storage location for the configuration backup file.
Note Operators and viewers can only display the current configuration. Only administrators can view hidden fields such as passwords.
You can disable the more prompt in more current-config or more backup-config by setting the terminal length to zero using the terminal length 0 command. The more command then displays the entire file content without pausing. For the procedure for using the terminal command, see Modifying Terminal Properties.
To display the contents of a logical file, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
Step 2 Display the contents of the current configuration file:
sensor# more current-config
Generating current config:
The current configuration is displayed.
! ------------------------------
! Current configuration last modified Fri Dec 17 21:38:23 2004
! ------------------------------
! ------------------------------
! ------------------------------
service event-action-rules rules0
! ------------------------------
host-ip 10.89.130.108/23,10.89.130.1
standard-time-zone-name UTC
! ------------------------------
! ------------------------------
! ------------------------------
! ------------------------------
! ------------------------------
service signature-definition sig0
specify-payload-source yes
event-action produce-alert|produce-verbose-alert|deny-attacker-inline|deny-conne
ction-inline|deny-packet-inline|log-attacker-packets|log-pair-packets|log-victim
-packets|request-block-connection|request-block-host|request-snmp-trap|reset-tcp
-connection|modify-packet-inline
event-action produce-alert|produce-verbose-alert|deny-attacker-inline|deny-conne
ction-inline|deny-packet-inline|log-attacker-packets|log-pair-packets|log-victim
-packets|request-block-connection|request-block-host|request-snmp-trap|reset-tcp
-connection|modify-packet-inline
edit-default-sigs-only default-signatures-only
specify-syn-flood-max-embrionic yes
! ------------------------------
! ------------------------------
service trusted-certificates
trusted-certificates 10.89.130.108 certificate MIICJDCCAY0CCPbSkgXUchJIMA0GCSqGS
Ib3DQEBBQUAMFcxCzAJBgNVBAYTAlVTMRwwGgYDVQQKExNDaXNjbyBTeXN0ZW1zLCBJbmMuMRIwEAYDV
QQLEwlTU00tSVBTMjAxFjAUBgNVBAMTDTEwLjg5LjEzMC4xMDgwHhcNMDMwMTAzMDE1MjEwWhcNMDUwM
TAzMDE1MjEwWjBXMQswCQYDVQQGEwJVUzEcMBoGA1UEChMTQ2lzY28gU3lzdGVtcywgSW5jLjESMBAGA
1UECxMJU1NNLUlQUzIwMRYwFAYDVQQDEw0xMC44OS4xMzAuMTA4MIGfMA0GCSqGSIb3DQEBAQUAA4GNA
DCBiQKBgQCzldqLFG4MT4bfgh3mJfP/DCilnnaLfzHK9FdnhmWI4FY+9MVvAI7MOhAcuV6HYfyp6n6cY
vH+Eswzl9uv7H5nouID9St9GI3YrSUtlIQAJ4QVL2DwWP230x6KdHrYqcj+Nmhc7AnnPypjidwGSfF+V
etIJLEeRFh/mI2JcmwF2QIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAAUI2PLANTOehxvCfwd6UAFXvy8ui
fbjqKMC1jrrF+f9KGkxmR+XZvUaGOS83FYDXlXJvB5Xyxms+Y01wGjzKKpxegBoan8OB8o193Ueszdpv
z2xYmiEgywCDyVJRsw3hAFMXWMS5XsBUiHtw0btHH0j7ElFZxUjZv12fGz8hlnY
! ------------------------------
Copying and Restoring the Configuration File Using a Remote Server
Use the copy [/erase] source-url destination-url keywords command to copy the configuration file to a remote server. You can then restore the current configuration from the remote server. You are prompted to back up the current configuration first.
Note We recommend copying the current configuration file to a remote server before upgrading.
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.
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
•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 If you use FTP or SCP protocol, you are prompted for a password.
The following keywords are used to designate the file location on the sensor:
•current-config—The current running configuration. The configuration becomes persistent as the commands are entered.
•backup-config—The storage location for the configuration backup.
Caution Copying a configuration file from another sensor may result in errors if the sensing interfaces and virtual sensors are not configured the same.
To back up and restore your current configuration, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
Step 2 To back up the current configuration to the remote server:
sensor# copy current-config ftp://qa_user@10.89.146.1//tftpboot/update/qmaster89.cfg
Step 3 To restore the configuration file that you copied to the remote server:
sensor# copy ftp://qa_user@10.89.146.1//tftpboot/update/qmaster89.cfg current-config
Warning: Copying over the current configuration may leave the box in an unstable state.
Would you like to copy current-config to backup-config before proceeding? [yes]:
Step 4 Press Enter to copy the configuration file or type no to stop.
Creating and Using a Backup Configuration File
To protect your configuration, you can back up the current configuration and then display it to confirm that is the configuration you want to save. If you need to restore this configuration, you can merge the backup configuration file with the current configuration or overwrite the current configuration file with the backup configuration file.
To back up your current configuration, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
Step 2 Save the current configuration:
sensor# copy current-config backup-config
The current configuration is saved in a backup file.
Step 3 Display the backup configuration file:
sensor# more backup-config
The backup configuration file is displayed.
Step 4 You can either merge the backup configuration with the current configuration, or you can overwrite the current configuration.
•To merge the backup configuration into the current configuration:
sensor# copy backup-config current-config
•To overwrite the current configuration with the backup configuration:
sensor# copy /erase backup-config current-config
Erasing the Configuration File
Use the erase [backup-config | current-config] command to delete a logical file.
The following options apply:
•current-config—The current running configuration. The configuration becomes persistent as the commands are entered.
•backup-config—The storage location for the configuration backup.
To erase the current configuration and return all settings back to the default, follow these steps:
Step 1 Log in to the CLI using an account with administrator privileges.
sensor# erase current-config
Warning: Removing the current-config file will result in all configuration being reset to
default, including system information such as IP address.
User accounts will not be erased. They must be removed manually using the "no username"
command.
Step 2 Press Enter to continue or type no to stop.