I am trying to connect my new controller to sccm. However when I try it only resolves a ipv6 address and that is not routed through my network.
9800-cl#telnet smartreceiver.cisco.com 443
Trying 2A04:E4C7:FFFE::F, 443 ...
% Destination unreachable; gateway or host down
I found a bug on this and it gave a work around by using call-home as shown below
We have seen a lot of issues for "Smart Transport" on Smart Licensing Using Policy when trying to register to Cisco Smart Software Manager (smartreceiver.cisco.com), the router is receiving AAAA and A entries from their local DNS server and the router prefers the IPv6 even though the router DOESN'T have IPV6 enabled.
This is happening in Autonomous and Controller-managed mode.
For Call-home transport we have the command that achieves this:
Router(config)# call-home
Router(cfg-call-home)# http resolve-hostname ipv4-first
We need a similar command for Smart Transport, "ip http client source-interface" doesn't help.
Smart agent can't never reach CSSM and authorization for licensing doesn't happen.
Conditions:
- Autonomous
- Controller-managed
- Smart Transport configured for licensing
I have attempted that work around but I am still getting the same issue.
Doing a nslookup to the same DNS server I have setup in my controller, and I do resolve it with a ipv4 address but for the life of me I can't get it to resolve that way from my WLC. Does anyone have any suggestions?
- we tried to configure the smart license using direct connection but it did not work.
- as when we try to telnet to smartreceiver it resolves to ipv6.
- we tried to add the ip http client source-interface for both the gig and the vlan interface but same thing.
