Cisco Cisco IPS 4255 Sensor

Before you upgrade your sensors to Cisco IPS 6.0(3)E.1, make sure you have performed the following 
tasks:

Created a backup copy of your configuration.

Saved the output of the show version command.

I f you need to downgrade a service pack or signature update, you will know what versions you had, 
and you can then apply the configuration you saved when you backed up your configuration.

You cannot use the downgrade command to downgrade from 6.0(3)E.1 to 5.1. You can only 
downgrade from new service packs and signature updates to the previous version of service 
pack or signature update. 

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(3)E.1. 

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(3)E.1 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(3)E.1. If you were using SNMP gets and sets with IPS 5.x (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(3)E.1 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 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 your sensor, refer to 

For the procedure for upgrading the sensor, see 

.

For the procedure for configuring SNMP, for the CLI procedure, refer to 

 For the 

IDM procedure, refer to 

We recommend copying the current configuration file to a remote server before upgrading.

Use the copy [/erase] source_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.