Cisco Cisco IPS 4255 Sensor 릴리즈 노트

다운로드
페이지 38
   
6
Release Notes for Cisco Intrusion Prevention System 6.0(4)E2
OL-20146-01
  Before Upgrading to Cisco IPS 6.0(4)E2
Perform These Tasks
Before you upgrade your sensors to Cisco IPS 6.0(4)E2, make sure you perform the following tasks:
To apply the E2 engine update, you must have version 6.0(4)E1 installed on your sensor.
Make sure you have a valid Cisco Service for IPS service contract per sensor so that you can apply 
software upgrades.
Created a backup copy of your configuration.
Saved the output of the show version command.
I f you need to downgrade a signature update, you will know what version you had, and you can then 
apply the configuration you saved when you backed up your configuration. 
For More Information
For more information on Cisco service contracts, see 
.
For the procedure for creating a backup copy of your configuration, see 
.
For the procedure for displaying version information, refer to 
For the procedure for downgrading signature updates on your sensor, refer to 
Backing Up and Restoring the Configuration File Using a Remote Server
Note
We recommend copying the current configuration file to a remote server before upgrading.
Use the copy [/erasesource_url destination_url keyword 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.
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.