ProxySG/ ASG/ SG VA is hitting the max default size for the SSL Session Cache.
If you have found that due to the amount of SSL traffic you have passing via the ProxySG / ASG / SG VA you may hit the max value of the SSL Session Cache. The impact of this is that you will see an increase in the CPU usage due to the SSL traffic.
In SGOS 6.6.5.11 and above you can now increase the SSL Session Cache to a maximum value of 1000000. To do this you will need to run the command below in the CLI:
# enable
# config t
#(config)ssl
#(config ssl)set-session-cache_size <new_size>
Notes -
To set back to default size.
#config t
Enter configuration commands, one per line. End with CTRL-Z.
#(config)ssl
#(config ssl)set-session-cache_size auto
#(config ssl)view set-session-cache_size
auto
And when its changed from default size
#(config ssl)set-session-cache_size 200000
#(config ssl)view set-session-cache_size
200000
Also note that when SSL session cache size is changed , existing cache is flushed and subsequent sessions (new connections) will perform full handshakes. Because of this if session cache size is changed during peak time of the day , SG may exhibit high CPU in SSL & Crypto until session cache rebuilt is done. It is recommended to perform this change during off peak hours.
To find the default SSL session cache size for your SG or ASG, please reference the following document:
Default SSL Session Cache Size of A ProxySG, ASG and SWG VA
https://knowledge.broadcom.com/external/article/169903