User manual

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

78-12569-16

Caveats

• CSCdu82478

In CSM software release 2.x, it is important that packets transmitted from the CSM toward a client

(server) are transmitted on the same VLAN as packets received by the CSM from that same client

(server). This constraint may be satisfied as follows:

–

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 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(1)

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

• CSCdw84018

Release 2.2 does not support RTSP UDP streaming modes when a client NAT is enabled. If this

configuration is set up, the server attempts to open a UDP connection, causing the CSM to drop

packets. Some RTSP clients then fall back on interleaved mode (inline TCP) even though the

connection is sent to fastpath.

Workaround: None

• CSCdw81611

The CSM drops or corrupts UDP fragments. This issue was originally introduce in Release 2.1.1 and

is resolved in Release 2.2.1. Both the drop and the corruption issues are located only in fragments

other than the first fragment. In the affected fragments, the CSM is incorrectly interpreting the

payload of the frame as UDP port information.