Guest

Cisco Security Manager

Field Notice: FN - 62822 - Cisco Security Manager 3.1 - Software Removed from Cisco.com Due to Upgrade Issue - Updated Software Re-posted


Revised June 12, 2007

May 17, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Products Affected

CS-MANAGER

Problem Description

If activities were pending in the Cisco Security Manager version 3.0.1 database, customers upgrading from version 3.0.1 to version 3.1 may experience database corruption.

This symptom may occur in Cisco Security Manager version 3.1, build number 465. See Help>About Security Manager for version and build number.

Because this is an upgrade issue, if your current installation of Cisco Security Manager version 3.1 is operational, this field notice does not apply.

Background

The upgrade process attempts to prevent problematic conversion by checking a data file. On some systems, this file cannot be read, which allows the upgrade to continue improperly.

Problem Symptoms

Systems that have experienced this failure may exhibit varying behaviors such as:

- Missing policy objects

- Missing devices in the Device View

- Inability to access the Device selector

To conclusively determine if there was database corruption during migration, the user should inspect the migration log:

$CSMROOT\log\Migration_.log

for the following text:

"Found uncommitted Building Blocks (or policies or assignments or nodes) in the database!" .

Also, the user should inspect the installation log:

C:\Ciscoworks_install_.log

for the following text:

"ERROR: Cannot read checkForUncommittedData.out" .

The presence of both of these entries together indicates that the database has been corrupted.

Workaround/Solution

If the Cisco Security Manager version 3.1 database has been corrupted, the user may recover the system as follows:

- Uninstall Cisco Security Manager version 3.1

- Perform a clean install of version 3.0.1

- Restore a clean backup of the version 3.0.1 database

If the failed upgrade was attempted more than once, it is possible that the original Cisco Security Manager version 3.0.1 backup, in the original directory, was over-written.

In this case, a previous backup should be used if one is available. Alternatively, the customer may choose to re-import the configuration from the devices.

Cisco has re-posted version 3.1 on Cisco.com at the following location. The correct version has a build number of 482. See Help>About Security Manager for version and build number.

Cisco Security Manager Software Download (registered customers only) page.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCsi78953 (registered customers only)

Database was corrupted after upgrade. (severe)

Revision History

Revision

Date

Comment

1.3

12-JUN-2007

Bolded the text in the last sentence of the Problem Desciption section. Reworded version build reference in Workaround/Solution section.

1.2

05-JUN-2007

Update Title and Workaround/Solution sections to indicate that updated software has been re-posted. Added link to software download in Workaround/Solution section.

1.1

18-MAY-2007

Corrected install log path and file name in Problem Symptoms section.

1.0

17-MAY-2007

Initial Public Release

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.