Cisco Cisco IPS 4255 Sensor

Pagina di 42
   
7
Release Notes for Cisco Intrusion Prevention System 6.0(4a)E1
OL-8872-02
  Before Upgrading to Cisco IPS 6.0(4a)E1
Before Upgrading to Cisco IPS 6.0(4a)E1
This section describes the actions you should take before upgrading to Cisco IPS 6.0(4a)E1. It contains 
the following topics:
Perform These Tasks
Before you upgrade your sensors to Cisco IPS 6.0(4a)E1, make sure you perform the following tasks:
Upgrade all version 4.x or earlier sensors to IPS 5.0(1) before applying the IPS 6.0(4a)E1 service 
pack.
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. 
Upgraded the IDS 4215 BIOS to the most recent version.
If you are using SNMP set and/or get features, you must configure the read-only-community and 
read-write-community parameters before upgrading to IPS 6.0(4a)E1. 
In IPS 5.x, the read-only-community was set to public by default, and the read-write-community 
was set to private by default. In IPS 6.0(4a)E1 these two options do not have default values. If you 
were not using SNMP gets and sets with IPS 5.x (for example, enable-set-get was set to false), there 
is no problem upgrading to IPS 6.0(4a)E1. If you were using SNMP gets and sets with IPS 5.(for 
example, enable-set-get was set to true), you must configure the read-only-community and 
read-write-community parameters to specific values or the IPS 6.0(4a)E1 upgrade fails. You 
receive the following error message:
Error: execUpgradeSoftware : Notification Application “enable-set-get” value set to 
true, but “read-only-community” and/or “read-write-community” are set to null. Upgrade 
may not continue with null values in these fields.
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