User manual

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

78-12569-16

Caveats

• CSCdu54735

If the version of software running on the CSM does not correspond to the version of Cisco IOS

software running on the Catalyst switch, a spurious memory access message may be displayed when

the CSM is inserted into a Catalyst 6500 Series chassis.

Workaround: If the versions of software do not correspond, either the Cisco IOS or the CSM

software must be upgraded for the module to function.

Open Caveats in Release 1.2(2)

This section describes known limitations that exist in the CSM software release 1.2(2).

• CSCdw47284

Client access lists for the CSM are specified in one of two ways:

–

If the list is assigned directly to the virtual server using the client command in the vserver

submode, the client mask will be changed to 255.255.255.255 during a configuration reload,

which occurs when the configuration is first sent to the module on startup.

–

When using the clear ip slb linecard-config command.

You can determine that the mask has been changed by comparing the virtual server output for the

show running command with the output from the show ip slb vserver detail command.

Workaround: Create a Cisco IOS standard IP access list, assign it to an slb policy, and assign the

policy to the virtual server.

• CSCdv78416

When using the no ip slb map command (or no map in the module CSM submode) in Cisco IOS

software for the CSM, the memory allocated for match rules is not deallocated. This condition is not

usually a problem since the amount of memory required is small. Additionally, calling the no

url-map, no cookie-map, or no header-map command from SLB policy submode can cause the

specified map to be associated with the policy, rather than disassociated, if the policy is not currently

associated with a map of that type.

Workaround: Do not call the command for a policy that is not configured with a map of the given

type.

• CSCdv73302

When serverfarms for the CSM have been configured with health probes and no real servers at the

time the module comes online, the probe configuration for the serverfarm is never sent to the

module, even when the real servers are later added to the serverfarm.

Workaround: Configure real servers before configuring probes in ip slb serverfarm submode.

• CSCdu04990

If the CSM parses a cookie to make a connection when the connection is closed, the connection will

be listed as being current. If the client makes a connection again after the sticky timer expires, then

one more connection goes into a closing state, thereby incrementing the counter by one.

Workaround: None.