User manual

Release Notes for Catalyst 6500 Series Content Switching Module Software Release 2.2(8)

78-12569-16

Caveats

• CSCdy87767

CSM TCP health probes are using an incorrect Maximum Segment Size (MSS) value of 1480. The

correct default MSS option value should be 1460. Most of the servers ignore the high MSS value

from the health probe messages.

Workaround: None.

• CSCdy80475

Connection replication does not work after removing and adding a fault-tolerant VLAN. After

removing the fault-tolerant VLAN between two CSMs, both fault-tolerant modules become active

as expected. When you reconfigure the fault-tolerant VLAN, one CSM becomes active and the other

becomes the standby module. The active CSM will not replicate the connections to the standby

module.

Workaround: Reboot the standby CSM to resolve the problem.

• CSCdy76100

Changing the redirect-vserver protocol through the SSL port command in some cases does not take

effect. The redirect protocol (HTTP, HTTPS, FTP, etc.) would stay at the previously configured

value.

Workaround: Take the real server out of service, and then return it to in-service to force the CSM

to take the new value.

• CSCdy71021

When configuring the NAT client command for a serverfarm with the FTP service, the CSM stops

forwarding the FTP traffic after 8000 connections are made. There is a resource leak in the CSM

with the client NAT and FTP service.

Workaround: None.

• CSCdy76748

Under packet processing stress (high packet-per-second load), the NAT module on the CSM sends

out a corrupted frame, which crashes the CSM resulting in a core dump and reboot.

Workaround: None.

• CSCdy54047

The CSM sends multiple GET requests of the same HTTP 1.1 persistent connection to the same

server, even though this server has failed in between the GET requests. Thus, the subsequence GET

will fail when the server fails.

Workaround: None

• CSCdy44301

The CSM is now generating the syslog and SNMP traps when taking the real server out of service.

There is no syslog generated when putting the real server in service again.

Workaround: None.

• CSCdy33708

The CSM now supports client NAT with the FTP service in the “passive” mode.

Workaround: Remove the client NAT option from the serverfarm.