cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Welcome to the Smart Call Home Community!

Our online forum for Smart Call Home customers to share, learn, and collaborate on Smart Call Home related topics. We encourage you to ask questions of Cisco experts, start a discussion, or share ideas and insight.

Smart Call Home enabled devices perform proactive diagnostics on their own components to provide real-time alerts and remediation advice when an issue is detected. An embedded support feature available on a broad range of Cisco products, it is provided at no additional cost with an active Smart Net Total Care Service, SP Base, Unified Computing Support Service, or Mission Critical Support Service contract for the designated products.

This Community will provide you with an overview about Cisco Smart Call Home features and how these features are embedded in a wide range of Cisco products to help your network. Smart Call Home provides higher network availability and support service quality.

1573
Views
0
Helpful
3
Replies
Beginner

Smart Call Home https url resolution yields an IPv6 address

  I have a couple of Catalyst 9300 Stacks licensed DNA/Network Essentials.  One has managed to register and one is having difficulty logging the error "Fail to send out Call Home HTTP message"  

  When I configure a nameserver on this stack telnet resolves tools.cisco.com 443 to and IPv6 address however using the same nameserver ping yields the IPv4 address and finally telnet to the IP address resolved by ping indicates an open socket.  We currently are not routing IPv6.  

  Is there a way to force this system to yield an IPv4 address or will I need to change the call home address to and IP?   I'm worried that if I do this the IP will change one day and these switches will go unregistered with our Smartnet Account.

 

Cisco IOS Software [Fuji] (CAT9K_IOSXE), Version 16.9.2

SW#telnet tools.cisco.com 443 /source-interface vlan 44
Trying 2001:420:1201:5::A, 443 ...
% Destination unreachable; gateway or host down

SW#ping tools.cisco.com source vlan 44
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 173.37.145.8, timeout is 2 seconds:
!!!!!

SW#telnet 173.37.145.8 443 /source-interface vlan 44
Trying 173.37.145.8, 443 ... Open

 

 

 

Everyone's tags (1)
3 REPLIES 3
Beginner

Re: Smart Call Home https url resolution yields an IPv6 address

Well go figure it resolved itself.  Even though my telnet to the url still fails.  This may have had something to do with our Radius authentication and the fact that prior to this Smart Net call home program our management vlan was not allowed to speak to the internet.  I'm sure we will have to come up with a better way of managing this either through a web proxy or SMTP.

 

SW#telnet tools.cisco.com 443 /source-interface vlan 44
Trying 2001:420:1201:5::A, 443 ...
% Destination unreachable; gateway or host down
Beginner

Re: Smart Call Home https url resolution yields an IPv6 address

This is still very much a problem for us.  We are running version 16.06.02 on our CSR1000 routers in AWS and call-home is trying to use ipv6 for smart licensing.   The only way I have found to work around the issue is to hardcode the ip address in the call-home destination. Changing the default "destination address http http://tools.cisco.com/its/service/oddce/services/DDCEService" to use an IP that it resolves too....  "destination address http http://72.163.4.38/its/service/oddce/services/DDCEService" but we CANNOT stay running like that with a hardcoded ip.

 

The router resolves the URL fine and pinging the url works; however, telnet using the name fails.   See below.

 

CSR-ROUTER#ping tools.cisco.com
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 72.163.4.38, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 46/46/47 ms


CSR-ROUTER#telnet tools.cisco.com
Trying 2001:420:1201:5::A ...
% Destination unreachable; gateway or host down

 

CSR-ROUTER#telnet 72.163.4.38 80
Trying 72.163.4.38, 80 ... Open

 

 

Highlighted
Beginner

Re: Smart Call Home https url resolution yields an IPv6 address

Having the exact same problem on Azure with CSR1000v and smart call-home..
CreatePlease to create content
Content for Community-Ad
FusionCharts will render here