Cisco Cisco Content Switching Module with SSL

For a description of open caveats in CSM software release 2.2(4), see the 

.

This section describes resolved caveats in CSM software release 4.3(4):

CSCtd31622

The default expiration date of the cookies inserted by the CSM is Friday, 1 Jan 2010, 01:01:50 GMT.  
After this time, the cookie-insert sticky will not work as expected.

Workaround: The default cookie expiration date can be changed by setting the 
COOKIE_INSERT_EXPIRATION_DATE environment variable on the CSM. For example, you can 
move the expiration date to May 25, 2020, by using the following commands:

Router# config t

Router(config)# mod csm 8

Router(config-module-csm# variable COOKIE_INSERT_EXPIRATION_DATE "Mon, 25 May 2020 

Make sure to change the slot number. The new expiration date changes in the inserted cookies 
immediately as this change does not require a reboot of the CSM.  This change will not affect the 
production traffic.

CSCtc25780

In rare cases, when CSM fault tolerant (FT) synchronization is performed with the hw-module csm 
mod standby config-sync command and FT VLAN is intermittently down, the standby CSM may 
send out an ARP packet towards the Layer 2 adjacent nodes using its physical MAC-address, instead 
of its virtual MAC-address. This causes an outage until the ARP table cache is either cleared or times 
out.

Workaround: To prevent rapid failover in the standby CSM2 node, increase the failover timer to 
120 seconds on both CSM nodes (active and standby).

For a description of SSL caveats resolved in CSM-S software release 2.2(4), see the 

.

This section describes the open SSL caveats in CSM-S software release 2.2(4):

There are no open caveats for SSL.

For a description of open SSL caveats in CSM-S software release 2.2(4), see the

This section describes the SSL caveats resolved in CSM-S software release 2.2(4):