User manual

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

78-12569-16

Caveats

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.

Resolved Caveats in Release 1.2(1)

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

• CSCdt30757

Server-to-server FTP data connections do not work in passive (PASV) mode.

Workaround: Do not use PASV mode for server-to-server data connections.

• CSCdt42091

Intensive Telnet/FTP probing may cause a device that is being probed to stop responding.

(Generally, intensive probing represents a fault in the device being probed.)

Workaround: Probe the device at a slower rate and increase the probe interval value.

• CSCdt42937

If the CSM is forwarding traffic while the CSM is being configured, error messages may appear on

the screen.

Workaround: This message is for information only and may be ignored.

• CSCdt44655

Booting the CSM with a large number of virtual servers configured (over 2000) causes the CSM to

go offline.

Workaround: Reduce the number of virtual servers and reboot the CSM.

• CSCdt45461

HTTP GET probes may fail when probing using large HTML pages.

Workaround: Probe using smaller web pages, or probe using a HEAD request instead of a GET

request.

• CSCdt64850, CSCdt75262, CSC77827, CSCdt79110, CSCdt80328

In configurations approaching the CSM’s maximum limits, the CSM may reboot when a maximum

load that contains certain traffic mixes and large amounts of invalid traffic is applied.

Workaround: None.

• CSCdt72948

IDENT protocol causes slow Telnet connections to the CSM.

Workaround: Do not use the IDENT protocol to communicate with the CSM.

• CSCdt73069

When the MAC address corresponding to a real server IP address changes, it may take 5 to 6 minutes

before probes to that real server are successful.

Workaround: None.