03-15-2022 09:00 AM
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?
03-15-2022 09:16 AM
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
03-15-2022 09:24 AM
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
03-15-2022 10:55 AM
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.
03-15-2022 09:35 AM
03-15-2022 03:19 PM
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