Revised April 17, 2008
December 10, 2003
NOTICE:
THIS FIELD NOTICE HAS BEEN EXPIRED AND IS NO LONGER MAINTAINED OR UPDATED BY CISCO.
THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE, WARRANTY OR SUPPORT. USE OF THE INFORMATION ON THIS FIELD NOTICE OR MATERIALS LINKED FROM THIS FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
Products Affected
|
Product |
|---|
|
CSS11501 |
|
CSS11501S-K9 |
|
CSS11503-AC |
|
CSS11506-2AC |
|
CSS11506-2DC |
Problem Description
If two Adaptive Session Redundancy (ASR) redundant Content Services Switches (CSS) peers run WebNS versions, where one includes the fix for defect CSCdy19162 (registered customers only) , and one does not, the backup box would not see any dormant flows, therefore, during a failover all of the ASR flows would fail.
Background
A fix for defect CSCdy19162 (registered customers only) was introduced into 7.10.3.05 and 7.20.1.04, which broke ASR communication between systems running WebNS prior to these versions. The ASR backup CSS is no longer able to receive and interpret the messages about the dormant flows, which causes ASR to fail.
Problem Symptoms
If two CSSs in a redundant ASR scenario run different versions, where one is prior to 7.10.3.05 or 7.20.1.04 and the other is running 7.10.3.05 or higher or 7.20.1.04 or higher, then in the case of a failover, the ASR will fail. The dormant flows will not get setup on the backup CSS and therefore all sessions will be lost on failover.
Workaround/Solution
If you would like to use the ASR feature, then have both CSSs run WebNS 7.10.3.05 or higher or 7.20.1.04 or higher.
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 |
|---|---|
|
sticky entries dont get updated when doing persistent requests |
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.