User manual

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

78-12569-16

Caveats

Resolved Caveats in Release 1.2(2)

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

• CSCdw24071

In CSM software versions 1.1(1), 1.2(1), and 1.2(1) or earlier, the CSM may fail if it receives a TCP

RST frame on a connection at an inappropriate time. This condition may be triggered if an RST

frame arrives immediately following a valid data frame on the same connection. This scenario

occurs rarely yet is prevalent when many packet drops or errors occur in the network due to

congested or defective servers or due to overloaded transmission links. This defect is fixed in

versions 2.1(2), and versions later than 2.1(2).

• CSCdw41620

The CSM may classify incoming frames incorrectly, causing those frames to be dropped. Such

packet loss results in intermittent connectivity to virtual servers configured on the CSM. This

problem occurs only if 128 or more virtual servers have been configured on the device since bootup.

(This number includes virtual servers that have been configured and subsequently removed from the

configuration.) In most production scenarios, virtual servers are configured only when the device

boots.

This defect is present in CSM software releases 1.1(1), 1.2(1), 2.1(1), 2.1(2). This defect is fixed in

version 1.2(1).

• CSCdw24384

When connections arrive that are configured to a CSM through a redundant router pair running

HSRP, those connections may be from the standby HSRP peer. When returning traffic through that

redundant router pair, the CSM must send the traffic to the HSRP virtual MAC address shared by

the two routers. In CSM software versions 1.2(1) and 2.1(1), the CSM incorrectly forwards such

traffic to the real MAC address of the standby router.

Open Caveats in Release 1.2(1)

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

• 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.

• CSCdu05559

During heavy traffic conditions, in a fault-tolerant configuration, the primary CSM may not be able

to send heartbeat messages to the secondary CSM. This condition causes both the primary and

secondary CSMs to become active, creating a bridge loop in the network.

Workaround: Reboot the primary CSM.

• CSCdu33696

While the CSM is balancing traffic and you configure the CSM with both a DFP agent and a

manager, the following may occur:

–

All the counters in the show ip slb stats command are reset to 0.

–

The show command returns No ICC Response intermittently.