Cisco Cisco Content Switching Module with SSL

Pagina di 40
   
20
Release Notes for Catalyst 6500 Series Content Switching Module with SSL Software Release 2.2(x)
OL-14929-06
Open and Resolved Caveats in Software Release 2.2(3)
Resolved Caveats in Software Release 2.2(3) for CSM
Note
For a description of open CSM caveats in CSM-S software release 2.2(3), see the 
This section describes resolved CSM caveats in CSM-S software release 2.2(3):
This section describes resolved caveats in CSM-S software release 4.3(3):
CSCsm33035
When the CSM-S starts to load balance using the default policy, and then a GET request matches a 
URL under a subpolicy, the CSM-S forwards traffic to the real server without modifying the TCP 
acknowledgement number.
Workaround: Disable persistent rebalance.
CSCsq36042
When SSL stickiness is configured on a backup server farm, the CSM-S fails to perform NAT in 
some cases.
Workaround: Disable SSL stickiness on the server farm.
CSCsu39853
In rare cases, the CSM-S will stop responding to the CLI but will continue to pass traffic.
Workaround: None.
CSCso69828
When cookie-insert is configured on the CSM-S and the server sends the FIN/ACK immediately 
after its HTTP 200 OK response, the CSM-S may send some subsequent packets out of order and 
with an incorrect TCP sequence number.
Workaround: None.
CSCsz81041
The CSM-S does not send a reset upon receiving a synchronize acknowledgement (ACK) packet 
sent to a synchronize start (SYN) packet. This condition occurs in Layer 7 mode when the CSM-S 
opens a connection on the backend server, and if the server responds to the SYN with an ACK that 
has an invalid sequence number.
Workaround: None.
CSCsu92969
Configuring multiple server load balancing (SLB) policies in a particular order causes the 
connection counter in a real server in the server farm to erroneously report the default maximum 
connection (MAXCONN) limit of 4294967295 connections. When this condition occurs, the real 
server refuses new connections.
Workaround: Remove multiple SLB policies.
CSCsz81265
When configuring two virtual servers (Layer 3 and Layer 4) with the same virtual IP address, CSM-S 
drops the ICMP request to the virtual IP address. This condition occurs when both virtual servers 
are operational, and when there is no connection to the Layer 3 virtual server.
Workaround: Ensure that the Layer 3 virtual server is configured after the Layer 4 virtual server.