CSC-SSM Module Problem

Unanswered Question
Sep 3rd, 2009

Hi, I installed a CSC-SSM module on ASA 5510. After policy services have been enabled, services works well for a few minutes, after that the cpu usage's module rise to 100% and all http traffic is wholy blocked, till the cpu usage go down.

This happens very frequently and traffic stay blocked for such a long time that it makes the csc-ssm module unusable. It's disabled right now.

ASA version is 8.0(4)and CSC-Module version is 6.3.1172.0.

Please, can you give me any suggestion?

thank you in advance



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Kureli Sankar Sat, 09/05/2009 - 19:29

Pls. double check and make sure you are not logging http in debug level under the Trend GUI. This may cause cpu spikes.

You are running the latest code.

Also, make sure http inspection is not enabled. (sh run policy-map)

ANGELO DE MASI Sun, 09/06/2009 - 12:12

Hi, Thank you for your post.

I checked http debug level and http inspection but both are not enabled.

Any other suggestion?

thanks in advance.



ANGELO DE MASI Mon, 09/07/2009 - 00:45


only just disabling global policy service matching traffic diverted to module,high CPU usage doesn't happen.

Do you mean reimaging to dowgrade to previous release 6.2.1599.6 ???



Kureli Sankar Tue, 09/08/2009 - 11:25

Removing the service-policy doesn't send any traffic to the CSC to be scanned at all.

Pls. try to re-image the module to 6.2.1599.0.bin and then upgrade to 6.2.1599.6.pkg (from the GUI) and see the problem goes away.

ANGELO DE MASI Tue, 09/08/2009 - 22:29

Yes, I've reimaged the module to 6.2.1599.6 version and the problem does't appear anymore. It means the new version is bugeg. Isn't it?

Many thanks



Kureli Sankar Wed, 09/09/2009 - 04:31

Very glad to hear that. There are a few known issues in the new code. I have not run into high CPU issue with the new code personally. Pls. stay at 6.2.1599.6.pkg for now until you see another release in the 6.3.11xx code.

tmobrien Thu, 07/15/2010 - 14:00

We are having a similar issue with 6.3.1172.0 running to 100% CPU.

Do you have a current link to the downgrade procedure?


This Discussion