Guest

Cisco ACE GSS 4400 Series Global Site Selector Appliances

Field Notice: FN - 62777- GSS 2.0.1.0.1 Code Has Been Removed from CCO Due to DDTS CSCsi22242


April 4, 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

Product

Comments

GSS - GSS-4480-K9

GSS - GSS-4490-K9

GSS - GSS-4491-K9

GSS - GSS-4492R-K9

GSS

Software version 2.0

Problem Description

After an upgrade to 2.0.1.0.1 there are two issues which can be seen:

If a gss disable is followed by a gss enable executed on the SGSSM (standby GSS), the standby gets into a state where it cannot sync with the pGSSM's database.

The secondary issue associated with this defect is - after an upgrade to 2.0.1.0.1, if the configuration on the pGSSM is added and deleted within a certain time window, the configuration does not get synced to the sGSSM.

The steps that will produce either of these issues are:

  1. Load 1.3.2.0.3 on the PGSSM (4490).

  2. Load 1.3.2.0.3 on the SGSSM (4480) (The same issue is seen when you upgrade from the following releases: 1.3.1.0.0 to 2.0.1.0.1 and 1.3.3.0.0 to 2.0.1.0.1).

  3. Establish a GSS network.

  4. Upgrade the network to 2.0.1.0.1.

  5. On standby, execute gss disable ; gss enable .

  6. The following exception is seen: java.util.ConcurrentModificationExceptioning

  7. Also, database validate process fails.

Background

Performing an enable/disable on an SGSSM, or adding and then deleting the configuration within a particular time window after upgrading to GSS 2.0.1.0.1 code can cause configuration sync errors, resulting in loss of config backup functionality on SGSSM.

Problem Symptoms

After the gss disable and gss enable have been issued, the following exception is seen:

java.util.ConcurrentModificationExceptioning .

The database validation also fails. DNS requests will still be served, however you will be unable to make any configuration changes to the standby GSS. This issue does not affect standalone GSS installations where no Secondary GSS role is defined.

Workaround/Solution

Workaround -

- Downgrade both primary and standby to 1.3.2.0.3. Instructions can be found in the Cisco GSS Administration Guide (Software Version 2.0).

- Restore-factory defaults on both GSSs

- Set up GSS network with primary and standby

- Load the gslb-config with 1.3.2.0.3 gslb-config (using script play-config on pGSSM)

- Make sure network is up and running and database is sync with standby.

- Upgrade primary followed by standby to the 2.0.1.0.5 version now posted on CCO. This will bring up the boxes in functional state.

Solution -

Both of these issues are addressed in version 2.0.1.0.5-k9.upg of the GSS code, available on CCO at the Cisco Global Site Selector 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

CSCsi22242 (registered customers only)

sGSSM database does not sync to pGSSM after gss disable/enable executed

Revision History

Revision

Date

Comment

1.0

04-APR-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.