cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
360
Views
0
Helpful
3
Replies

Registering CUBE (IOS-XE 16.12.7) with CSSM via proxy

shibin.kumar.ic
Level 1
Level 1

Hi Team,

I am trying to register my CUBE (IOS XE 16.12.7) with CSSM via proxy server. I have added all the required configuration however getting below error. 

 

000429: Sep 7 01:57:36.910 BST: CALL-HOME-SL-TRACE: smart_license_req_http_send[156], Sending smart license request to url list "https://tools.cisco.com/its/service/oddce/services/DDCEService"
000430: Sep 7 01:58:17.027 BST: CALL-HOME-SL-ERROR: smart_license_req_http_send[165], Failed to send request to all URLs.
000431: Sep 7 00:58:17.027: %CALL_HOME-5-SL_MESSAGE_FAILED: Fail to send out Smart Licensing message to: https://tools.cisco.com/its/service/oddce/services/DDCEService (ERR 205 : Request Aborted)
000432: Sep 7 01:58:17.027 BST: CALL-HOME-SL-TRACE: call_home_smart_license_stats_update[629], Update smart license stats entry, subtype REGISTRATION,stats_type 2
000433: Sep 7 00:58:17.027: %SMART_LIC-3-AGENT_REG_FAILED: Smart Agent for Licensing Registration with the Cisco Smart Software Manager (CSSM) failed: Fail to send out Call Home HTTP message.
000434: Sep 7 00:58:17.027: %SMART_LIC-3-COMM_FAILED: Communications failure with the Cisco Smart Software Manager (CSSM) : Fail to send out Call Home HTTP message.

Below are the configuration I have added in the device

Service call-home
Call-home
  profile “CiscoTAC-1”
  active
  destination transport-method http
http-proxy proxy name port 8080
no destination transport-method email
!
ip http client source interface loopback 1
 
ip http client proxy-server proxy name proxy-port 8080

Could you please suggest what can be done to fix . I have only enabled the firewall rule to allow port 8080 between CUBE and proxy server and in proxy we have allowed the communication from CUBE loopback 1 to https://tools.cisco.com/its/service/oddce/services/DDCEService.

3 Replies 3

Can you try with Smart Transport communication instead of the legacy Call Home communication method?



Response Signature


OK, its a production device so can try this during the next change . I tried the same configuration in our lab and it worked with call-home.

As the SL communication isn’t working I assume that it would not really affect anything to change the configuration. Or am I missing something? Also if it worked in your lab environment, but not in production, there is quite likely something that is different between the two.



Response Signature