Error "Smart Licence Authorization Expired" in FMC

[kostasthedelegate]

Hello, 

I have this error in FMC 

"Smart Licence Authorization Expired" in the message center. 

When I try to sync manually i get the below 

Error

Failed to send the message to the server. Please verify the DNS Server/HTTP Proxy settings.

Though when I connect to the FMC from CLI I can telnet www.tools.cisco.com. 

Any ideas?

[Marvin Rhoads]

Does your Smart licensing portal at software.cisco.com show a license is available?

Telnet isn't the best test since the registration and re-authorization takes place over https. Can you curl to the cisco.com page? that will uncover proxy issues (if there are any).

admin@Firepower:~
sudo curl -vvk https://tools.cisco.com

[kostasthedelegate]

Yes the license is available in the portal.

I even build a new token just in case, but no luck!

[Marvin Rhoads]

So did curl from the FMC cli work?

[kostasthedelegate]

Yes, it worked!!

maybe it is just a bug, which I have not found yet.

[Marvin Rhoads]

It sounds like all of the required connectivity and licenses are in place.

I'd suggest opening a TAC case at this point.

[seckka21]

Hi 

I have the same issue.The FMC 6.4.0 can telnet tools.cisco.com the curl work but every time i try to register it it fails by showing the same error.

[kostasthedelegate]

Ok 

Thanks for your support!

[Daniel Hamilton]

Did you ever get a resolution from TAC on this? I am having the exact same issues and have done everything except for TAC case so far.

[kostasthedelegate]

Hello,

No i did not get it resolved.
I did not open a TAC case

[abattia]

Dear,

I had the same issue and it got resolved after I did a reload for the FMC then I used the below URL to define the SSM server:

https://<SSM_Server_IP_Address>:443/Transportgateway/services/DeviceRequestHandler

Usually, this issue happened when you do de-register from the SSM server, then trying to do a new registration for another/or even the same server again.

I tried to restart the sla service on the FMC and then tested again but this didn't fix the issue.

Thanks,