topic Re: Smart Licensing : Tenancy Unknown in Network Security

Smart Licensing : Tenancy Unknown

Jacob Gibb — Tue, 15 Mar 2022 16:00:23 GMT

Hello,

I have a FTD 1010 that is not able to determine what tenancy it should fall within upon registration with Smart Licensing. I can see the device as registered and licensing applied but this error persist. The device is running 7.0.1. I also noticed that updates fail trying to retrieve for VDB and Geolocation although at the CLI I can ping software.cisco.com etc.. using DNS resolution. Anyone experience these issues?

Re: Smart Licensing : Tenancy Unknown

Marvin Rhoads — Tue, 15 Mar 2022 16:16:04 GMT

When you ping did you use "ping system" to ensure you are using the management interface?

Also you can verify connectivity from the FTD expert cli by running the following command as root:

curl -vvk https://tools.cisco.com

Re: Smart Licensing : Tenancy Unknown

Jacob Gibb — Tue, 15 Mar 2022 16:24:02 GMT

Hey, Marvin. I am using the data interface as the default method for mgmt traffic. The mgmt interface is disconnected. From the expert level I get the following trying to curl to tools.cisco.com

root@TN1FPR1010:/home/admin# curl -vvk https://tools.cisco.com
* Rebuilt URL to: https://tools.cisco.com/

get
helo* Could not resolve host: tools.cisco.com
* Closing connection 0
curl: (6) Could not resolve host: tools.cisco.com

Re: Smart Licensing : Tenancy Unknown

AdamStewart0400 — Tue, 15 Mar 2022 16:35:21 GMT

Cisco Firepower 1010 Getting Started Guide - Firepower Threat Defense Deployment with FDM [Cisco Firepower 1000 Series] - Cisco

The note in section 2 refers.

Re: Smart Licensing : Tenancy Unknown

Jacob Gibb — Tue, 15 Mar 2022 17:55:04 GMT

Well I think I found out some of the issues. Apparently if you have DNS groups configured for mgmt and/or data interfaces affects where the system looks to and the coresponing route table to perform the lookup. I created a public DNS group of 1.1.1.1 and 9.9.9.9 and set 'ANY' interface for data and just the group for mgmt. I can now resolve names when sourcing 'system' interface. Hoping now that it has resolution it will clear up the tenancy unknown. Picture attached of the current configuration.

Re: Smart Licensing : Tenancy Unknown

Leo Laohoo — Tue, 15 Mar 2022 22:19:35 GMT

FN - 72332 - Firepower Software: Cisco Talos Security Intelligence Updates Might Fail After March 5, 2022

FN - 72103 - ASA, FXOS and Firepower Software: QuoVadis Root CA 2 Decommission Might Affect Smart Licensing, Smart Call Home, And Other Functionality