cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
847
Views
1
Helpful
2
Replies

SNA Stealthwatch SLIC channel down

aradano
Level 1
Level 1

Hi all,

I'm new in the communinty, thanks in advance for any help you'd like to provide me.

My customer is using Secure Network Analytics version 7.4.2, the product have been licensed, also the license for Threat Intelligence is authorized but the alarm for the SLIC channel down is working.

I tried to ping esdhttp.flexnetoperations.com (ping ok) and lancope.flexnetoperations.com (ping ko) but when I tried to browse the last one I get an end of support announcement. May this be the cause of the issue?

You can find the /lancope/var/smc/log/smc-core.log  file attached.

I will appreciate if anyone can give me some support about that.

1 Accepted Solution

Accepted Solutions

JennieZhang
Cisco Employee
Cisco Employee

Hello, aradano ,

I have checked your log and I noticed below error message were happening.

"Caused by: org.bouncycastle.crypto.IllegalKeyException: Attempt to sign/verify with RSA modulus already used for encrypt/decrypt"

Are you still seeing the issue or is it working well now? This error message seems related to a bug which impacts version 7.4.2.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwh17234

If you are still seeing this error message, I suggest you collect and provide diagnostic  log to TAC team, they will confirm if you are hitting that bug. 

View solution in original post

2 Replies 2

JennieZhang
Cisco Employee
Cisco Employee

Hello, aradano ,

I have checked your log and I noticed below error message were happening.

"Caused by: org.bouncycastle.crypto.IllegalKeyException: Attempt to sign/verify with RSA modulus already used for encrypt/decrypt"

Are you still seeing the issue or is it working well now? This error message seems related to a bug which impacts version 7.4.2.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwh17234

If you are still seeing this error message, I suggest you collect and provide diagnostic  log to TAC team, they will confirm if you are hitting that bug. 

Hi Jennie,

I belive you're right: the symptoms of the bug matches with the issue I'm experiencing. I involved the TAC team as you sggested before applying the workaround.

Thanks for your help