Talos Connectivity Problem

[Ditter]

Hi to all ,

i am getting many messages as the following:

Severity: critical
Module: Talos Communication
Description: 3 modules failed:

• * URLDB- Failed to retrieve beaker inventory
• * LSP- Failed to retrieve beaker inventory

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.

[dpeldo22]

Jumping in on this thread because my ha pair just started doing this too. If you can post a fix from your tac case, I'd appreciate it.

[pncisco216]

I tried a couple more things and managed to fix this, so didn't get around to talking to Cisco TAC.  I switched the HA roles and made the secondary FMC (with the valid certificate) the active one, and the primary FMC (with the expired certificate) the standby one.  Following that I did a roll back and reinstall of the VDB.  Then I reversed the HA roles again, so that the primary was once again the active one.  It was at this point that I noticed that the certificate was now updated on both FMCs in the HA pair.  I didn't check between steps, so I am not sure if the HA failover was sufficient or if the VBD reinstall was required, as well.  Also, following this the Smart licensing was not seeing the base license for some reason on some of the devices, so I had to de-register/register and apply the licenses again.  This is what worked for me, but if you want an official fix then you may want to talk to Cisco TAC.

[Loebmann]

I finally received a new certificate. I only have a single FMC with version 7.7.12.

With the help of Sherlock, I was able to narrow down the problem to the Cisco Security Cloud. Re-registration the day before didn't work. Today, I generated a new tenant during the second cloud registration, and after a short time, a new certificate can now be found under /var/sf/beaker3/. Let's see how the automatic renewal works next year.