I'm having an issue with the Smart License registration on a 9200 Stack running Version 16.09.04. Altough in both the Core Switch (an old 4500) and the access switch I'm trying to register (9200) I have configured the same name servers, on the 9200 it's resolving the IPv6 address for Cisco, and thus, is unable to ping to it.
Below you can see how the core switch (rigth side) resolves IPv4 addresses, but the 9200 is resolving Cisco or Facebook with IPv6. I can ping all the IPv4 addresses from the 9200, but I'm unable to ping to the names if they are resolved with IPv6
I've disabled "ipv6 unicast-routing" and also entered "ip host cisco.com 188.8.131.52" on the 9200 but still no luck.
Any ideas would be welcomed
Thanks in advance
just to be sure, do you have the 'ip name-server' configured, as outlined in step 2 of the link below ?
Its configured. I'v tried both the internal name server and 184.108.40.206. Also, they both resolve cisco.com, so the issue shouldn't be there.
Now it pings cisco resolving with IPv4, but when I try to register, this is what appears:
Status: REGISTERING - REGISTRATION IN PROGRESS
Export-Controlled Functionality: NOT ALLOWED
Initial Registration: FAILED on Apr 20 07:49:14 2020 CEST
Failure reason: Fail to send out Call Home HTTP message.
Next Registration Attempt: Apr 20 08:53:27 2020 CEST
I followed this https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9500-series-switches/214484-cisco-smart-licensing-troubleshooting.html#anc26 and when I telnet to tools.cisco.com on port 443, I see it is responding again via IPv6 (please refer to previous post)
Vlan 1 is the only SVI, so all is sourced from that interface. I can ping external IP addresses. If you go to the first post you´ll see those tests.
I don´t know why even with Ipv6 disabled, the switch keeps resolving IPv6 for some things, like the telnet test, and probably the Smart License registration.
Just for the sake of trying, I edited the call-home profile, and it does't register with either https or http
After each editing of the profile I entered the comand
license smart register idtoken <token>
I think the issue is not related with the Smart Call Home configuration, I think the problem is with the IPv6 resolution of the address.
I am starting to think that the problem might be with the portal itself. You could try and contact GLO at the numbers below: