Примечания к выпуску для Cisco Cisco Content Switching Module with SSL
23
Release Notes for Catalyst 6500 Series Content Switching Module with SSL Software Release 2.2(x)
OL-14929-06
Open and Resolved Caveats in Software Release 2.2(2)
•
CSCsk43903
A pair of CSM-S configured for a fault-tolerant operation will both enter the active state after 828
days.
days.
Workaround: None.
•
CSCsk29021
When persistent rebalance is configured, the CSM-S will reexamine a persistent GET and remap it
if it matches a different policy. As part of the remapping, the CSM-S will send a reset to the old
connection. If the header insert feature is configured, this reset message has an incorrect sequence
number.
if it matches a different policy. As part of the remapping, the CSM-S will send a reset to the old
connection. If the header insert feature is configured, this reset message has an incorrect sequence
number.
Workaround: None.
•
CSCsk50939
The CSM-S stops responding to CAPP-UDP requests from a Global Site Selector (GSS) after
changing the CAPP-UDP setting from secure to no secure.
changing the CAPP-UDP setting from secure to no secure.
Workaround: Reload the CSM-S.
•
CSCsl23801
HSRP causes CSM-S static ARP entries to be overwritten with all zeros (00-00-00-00-00-00). This
problem is an unintended result of a previous caveat resolution.
problem is an unintended result of a previous caveat resolution.
Workaround: None.
•
CSCsj05855
In rare cases, the CSM-S may reboot and create a core dump due to memory corruption.
Workaround: None.
•
CSCsl59508
When a server farm contains many real servers (for example, 100), the CSM-S may reboot and create
a core dump when you add the predictor leastconns slowstart num command to the server farm.
a core dump when you add the predictor leastconns slowstart num command to the server farm.
Workaround: Do not use the slowstart command option.
•
CSCsk98543
The CSM-S console might lock up when a backup server farm is configured with a threshold and
contains few real servers (for example, when you have fewer than ten real servers).
contains few real servers (for example, when you have fewer than ten real servers).
Workaround: Remove the threshold command.
•
CSCsl07382
When the CSM-S is configured for Global Server Load Balancing (GSLB), the active CSM-S can
exhibit a slow memory leak.
exhibit a slow memory leak.
Workaround: Monitor memory usage regularly by using the venus console. Open a session to the
active CSM-S by entering the session slot x processor 0 command. At the CSM> prompt, enter the
venus command. At the venus# prompt, enter the core_show_usage command. If available memory
is less than 20 percent, schedule a reboot of the CSM-S. Because the memory leak occurs only on
the active CSM-S, the standby CSM-S should be available to take over.
active CSM-S by entering the session slot x processor 0 command. At the CSM> prompt, enter the
venus command. At the venus# prompt, enter the core_show_usage command. If available memory
is less than 20 percent, schedule a reboot of the CSM-S. Because the memory leak occurs only on
the active CSM-S, the standby CSM-S should be available to take over.
•
CSCsi58089
The CSM-S drops SASP server messages larger than 2816 bytes.
Workaround: Reduce the number of servers participating in SASP to reduce the length of the SASP
messages.
messages.
•
CSCsl72371