03-31-2025 04:58 AM
Hi to all ,
i am getting many messages as the following:
Severity: critical
Module: Talos Communication
Description: 3 modules failed:
My subscription is active (it expires in 2026).
Any ideas about why is this happening? Is it a problem that has to do with Talos?
Please note that this is the first time i get this message.
The only change i did some days ago was to change the "Cached URLs Expire" which was set to never and i changed it to "week" but i do not think that my issue has something to do with it.
Any ideas,
Thanks,
Ditter.
Solved! Go to Solution.
04-26-2025 02:11 AM
04-26-2025 03:58 AM
Yes, I rebooted the FMC, but the certificate is not updated.
04-27-2025 09:14 AM
I restarted the FMC and the next day the error was there again. I then restarted the two processes manually and the error message returned the next day. I did not have a more detailed analysis carried out. The permanent fix will be released with 7.7.1 in July or with 7.6.1 in May.
Best regards
04-28-2025 12:46 AM
sounds good, thx for info
05-28-2025 12:24 AM - edited 05-28-2025 12:39 AM
Since we are approaching the end of May - any news about the 7.6.1 update?
When visiting a client today, I saw this alert again even though the cert is still valid another 11 month after we installed VDB 406 last month.
root@fmcv:/var/sf/beaker3# openssl x509 -text -in securefirewall-dev-prod-01_prod.pem
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 82214246 (0x4e67d66)
Signature Algorithm: sha256WithRSAEncryption
Issuer: C = US, ST = California, L = San Jose, O = Cisco Systems Inc., OU = Security, CN = Keymaster CA 2
Validity
Not Before: Apr 7 07:33:53 2025 GMT
Not After : Apr 6 07:33:53 2026 GMT
A restart of the following two processes seems to have fixed it temporarly.
root@fmcv:/var/sf/beaker3# pmtool restartbyid talosAgent
root@fmcv:/var/sf/beaker3# pmtool restartbyid beaker3
Thanks
/Chess
05-28-2025 09:00 AM
7.6.1 should be released any time now, although 7.2.10 was in that state for a while and got pushed back a number of times before it finally came out.
05-28-2025 09:12 AM
@Chess Norris I am told that 7.6.1 is in final QA sign off and is still expected out in the next couple of days.
06-03-2025 05:26 AM
FYI 7.6.1 was released yesterday (2 June 2025).
It does say it fixes the bug: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwo63951
06-03-2025 11:21 AM
Unfortunately, same issue persist in 7.6.1
06-03-2025 08:40 PM
@Artezys79 make sure you have the "Customer Success Network" integration enabled under Cloud Services. I upgraded several FMCs in the past day and it fixed the issue for the ones that were manifesting it.
06-05-2025 04:34 AM - edited 06-05-2025 05:38 AM
Did the upgrade at a customer site today. After the upgrade I noticed another alert - "Smart Agent communication error with Smart Licensing Cloud".
Customer Success Network integration was already enabled. Anyone else got the same error?
/Chess
Edit. Seems like this alert comes a bit randomly. No more alerts on the last 3 checks. Will keep monitor it for a while.
07-04-2025 07:21 AM
This TALOS thing drives most of us crazy.
I upgraded to FMC 7.7.0.91 (from 7.6) and the problems with all these messages came back on (every 5 minutes but not all day , some specific time periods) .
Health Monitor Alert from fmc
Time: Thu Jul 3 06:35:08 UTC 2025 UTC
Severity: critical
Module: Talos Communication
Description: 1 modules failed:
As we speak no messages such as these, are coming in but no warranty that they will not restart ...
And currenty i run VDB version: build 408 ( 2025-04-29 08:56:28 )
Just for Information.
Ditter
07-04-2025 09:24 AM - edited 07-04-2025 09:26 AM
- @Ditter FYI : (corrections)
https://www.cisco.com/c/en/us/support/docs/field-notices/742/fn74284.html
https://www.cisco.com/c/en/us/support/docs/field-notices/742/fn74272.html
M.
07-07-2025 12:33 AM - edited 07-07-2025 12:35 AM
After I had the same issue even upgrading a customers FMC to the suposed fixed version 7.6.1, I opened a TAC case. TAC then told me to run the following command from expert mode - start_beaker_process.sh beaker3
It's now been two weeks with any alerts. Not sure what's the difference between this script and restarting the breaker process (that I also tried before but that only helped temporary). Might be worth giving this command a shoot for those still struggling with this alert.
/Chess
07-07-2025 06:36 AM
Ι recall to have done this stop/start process in the past but the messages kept randomly coming back. I will give it a new try. Thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide