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.

Smart Call Home Portal Performance

On We are currently experiencing performance issues with accessing and operations of the Small Call Home portal. Users are being dropped from the portal. Our team is working to resolve this issue as quickly as possible. We apologize for any inconvenience this is creating.

2094
Views
5
Helpful
5
Replies

Satellite Server Connection Issues

I have setup a SSM On-Prem satellite server to manage the Smart Licenses on our internal Network. I have been able to get it to publish smart licenses to my firewalls that had no license on them. I am currently attempting to connect my ISR 1100(17.3) Series routers to the server in order to convert their traditional licenses into smart licenses.

 

After following the Configuration Guide for the 1100 Series I am now getting the following error when using the Smart Transport URL:

SMART_LIC-3-COMM_FAILED: Communications failure with the Cisco Smart Software Manager (CSSM) : Received empty response from serv

When I attempt to use the Call-Home URL I get the following Error:

SMART_LIC-3-COMM_FAILED: Communications failure with the Cisco Smart Software Manager (CSSM) : Fail to parse response data from SCH server.

Here is my current Config for it

Snip
no license feature hseck9
license udi pid XXXX sn XXXXX
license smart url https://<On-Prem IP>/SmartTransport
license smart url cslu https://<On-Prem IP>/SmartTransport
license smart url smart https://<On-Prem IP>/SmartTransport
license smart transport smart
Snip
ip http server
ip http authentication local
ip http secure-server
ip http client source-interface GigabitEthernetX/X/X
ip forward-protocol nd
Snip call-home contact-email-addr email@domain.domain no http secure server-identity-check profile "License" reporting smart-licensing-data destination transport-method http destination address http https://<On-Prem IP>/SmartTransport

Any ideas would be super helpful, I've only just started working on Smart Licensing as a whole so I'm still fumbling through it.

1 ACCEPTED SOLUTION

Accepted Solutions

I asked around some more and was informed that SSM On-Prem doesn't support the new CSLU at this time which is most likely causing my issue when using version 17.3.3 IOS XE. I went ahead and backported to 16.12.05 and my device registered on the first try with no configuration changes. I am currently starting the DLC process to convert the license via my Satellite Server.

 

If anyone has any idea on how long it normally takes or if I need to ReSync my Server to complete please let me know. However the original question has been answered so I'll be marking this as the solution.

View solution in original post

5 REPLIES 5
balaji.bandi
VIP Master

check my Blog :

 

https://www.balajibandi.com/?p=1286

 

BB

***** Rate All Helpful Responses *****

How to Ask The Community for Help

If I'm reading this correctly, with this config

crypto pki trustpoint TP-self-signed xx
 enrollment selfsigned
 subject-name cn=IOS-Self-Signed-Certificate xx
 revocation-check none
 rsakeypair TP-self-signed xx
!
crypto pki trustpoint SLA-TrustPoint
 enrollment terminal
 revocation-check none
!
!
crypto pki certificate chain TP-self-signed xx
 certificate self-signed 01
****
        quit
crypto pki certificate chain SLA-TrustPoint
 certificate ca 01
****

You're saying to do

no crypto pki certificate chain SLA-TrustPoint

After doing that It was recreated after issuing the Registration Command. This time without a visible Certificate. 

 

As for the DNS settings I don't  have one configured for this stand alone network. For my Prem server I'm still using an IP for the Hostname.

I asked around some more and was informed that SSM On-Prem doesn't support the new CSLU at this time which is most likely causing my issue when using version 17.3.3 IOS XE. I went ahead and backported to 16.12.05 and my device registered on the first try with no configuration changes. I am currently starting the DLC process to convert the license via my Satellite Server.

 

If anyone has any idea on how long it normally takes or if I need to ReSync my Server to complete please let me know. However the original question has been answered so I'll be marking this as the solution.

View solution in original post

Got the same situation here :

- ISR 1100 17.3.3

- SSM On-Premise v8

--> I tried to use the classical callhome parameter at first : KO

--> then the licensing support told me to upgrade the SSM to the last version so the CSLU transport will be OK : done

--> tried the different transport options :

    - cslu : KO as expected (CSLU and SSM On-Prem are 2 different modes)

    - smart : KO : url is not customizable

    - callhome : the router reaches the SSM On-Prem, but the server response is empty

 

Does anyone know about a future release that allow the use of 17.3+ with SSM On-Prem ? (my customer would prefer a Linux VM rather than the CSLU Windows app, even wit the CentOS 7 end-of-support approaching)

Filip Po
Beginner

same issue here with Cat9500 and 17.3.3 and CSSM On-Prem.

Even documentation for Cat9500 IOS XE 17.3.x is not updated. Using license smart register tokenid command.