User manual

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

78-12569-16

Caveats

–

Multiple routes on the CSM to the same destination are supported, but all such routes need to

go through gateways on the same VLAN. Ensure that all routes to any particular destination go

through the same VLAN. For example, the following configuration is invalid because it is

possible for traffic from a remote source to arrive on both VLAN 10 and VLAN 20:

Router(config)# module csm 4

Router(config-module-csm)# vlan 10 client

Router(config-slb-vlan-client)# gateway 1.1.1.1

Router(config-module-csm)# vlan 20 client

Router(config-slb-vlan-client)# gateway 2.2.2.2

To make this configuration valid, delete the gateway command from either VLAN 10 or

VLAN 20.

Note NOTE: Do not use the gateway command in more than one VLAN.

–

Traffic into the CSM from an IP address must arrive on the same VLAN that the CSM uses to

send to that IP address. Ensure that all traffic received by the CSM from a specific destination

address arrives on the same VLAN that the CSM uses to reach that destination if the CSM is

configured with a route as follows:

Router(config)# module csm 4

Router(config-module-csm)# vlan 10 client

Router(config-slb-vlan-client)# route 10.0.0.0 255.255.255.0 gateway 1.1.1.1

For load balancing to function properly, all traffic arriving from the 10.0.0.0/24 subnet must

reach the CSM through VLAN 10.

Resolved Caveats in Release 2.2(5)

This section describes caveats that have been resolved in CSM software release 2.2(5).

• CSCdy58105

The web browser will send more data than is specified in the Content Length field of the HTTP

request to the email site. If this traffic needs to be load-balanced through the CSM and if the

persistent rebalance option is enabled, the CSM will drop these requests.

Workaround: Disable the persistent rebalance option for virtual server.

• CSCdy57918

The CSM leaks resources when an SYN and an RST are close to together in certain traffic patterns.

This problem only occurs with Layer 4 load-balancing and only if the CSM receives an RST before

it makes the load-balancing decision for that connection.

Workaround: None

• CSCdy54018

The service RTSP option for load-balancing streaming media traffic has memory leaks, causing the

CSM to slowly run out of resources for the new RTSP flows. When resources are not available, the

CSM will not load-balance any additional streaming media connections.

Workaround: Use IP sticky to match the RTSP control and data flows instead of using the service

RTSP option.