User manual

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

78-12569-16

Caveats

This problem occurs only when the CSM is receiving many Layer 7 connections in which the portion

of the traffic to be parsed (typically either the HTTP headers or SSL hello messages) spans multiple

packets, and those connections are terminated before the CSM has received all of the packets that

require parsing.

For example, if a GET request spans two packets, and the connection is terminated after the CSM

receives the first frame but before it receives the second, a Layer 7 connection object is leaked. Once

all those objects are leaked, the CSM suspends indefinitely.

Workaround: None.

• CSCdy22697

The CSM always drops all ISIS frames it receives. It is desirable that when configured in bridged

mode, that the CSM pass ISIS frames from the client-side VLANs to the server-side VLANs and the

reverse. This action allows ISIS communication through the CSM.

Workaround: Prior to software release 2.2(4), the only work around was to not rely upon

communication of ISIS frames through a CSM. This issue is resolved in CSM release 2.2(4).

• CSCdy19222

There is a limit of two configured HSRP routers per CSM. Routes configured with the route or

gateway command in the CSM VLAN submode may point to HSRP routers as the next-hop address.

Because the CSM interoperates with HSRP, the set of all IP addresses configured as next-hops in

route or gateway commands cannot contain more than two HSRP IP addresses. That is, a single

CSM can interoperate with only two HSRP IP addresses at any given time.

Workaround: Do not configure routes on the CSM to point to more than two distinct HSRP

addresses.

• CSCdy09047

A real server on which multiple health probes are configured will be considered healthy when one

probe recovers, regardless of the state of other health probes on that server. This condition is

undesirable, since one or more of these other probes may indicate that the server is still unhealthy.

Instead, the real server should be considered healthy only when all probes on that server are

successful.

Workaround: None.

• CSCdy08254

Configuring an HTTP probe with a Host header field may result in invalid HTTP requests in the

keep-alive probe to the real servers. The CSM incorrectly overwrites the Host header field with the

IP address of the real server. This condition may result in the CSM erroneously determining the

health status of a real server.

Workaround: Do not configure a Host header for an HTTP probe.

• CSCdy06917

The replicated call-setup-retry-period-flag for the show module csm x connection command always

displays false, even when the connection has been replicated to the peer CSM.

Workaround: Disregard this display from previous releases.