This section provides the list of SLP-related system messages you may encounter, possible reasons for failure (in case it is a failure message), and recommended action (if action is required).

For all error messages, if you are not able to solve the problem, contact your Cisco technical support representative with the following information:

• The message, exactly as it appears on the console or in the system log.

• The output from the show license tech support and show license history message commands.

SLP-related system messages:

• %LICMGR-3-LOG_SMART_LIC_POLICY_INSTALL_FAILED

• %LICMGR-3-LOG_SMART_LIC_AUTHORIZATION_INSTALL_FAILED

• %LICMGR-3-LOG_SMART_LIC_COMM_FAILED

• %LICMGR-3-LOG_SMART_LIC_COMM_RESTORED

• %LICMGR-3-LOG_SMART_LIC_POLICY_REMOVED

• %LICMGR-3-LOG_SMART_LIC_TRUST_CODE_INSTALL_FAILED

• %LICMGR-4-LOG_SMART_LIC_REPORTING_NOT_SUPPORTED

• %LICMGR-6-LOG_SMART_LIC_POLICY_INSTALL_SUCCESS

• %LICMGR-6-LOG_SMART_LIC_AUTHORIZATION_INSTALL_SUCCESS

• %LICMGR-6-LOG_SMART_LIC_AUTHORIZATION_REMOVED

• %LICMGR-6-LOG_SMART_LIC_REPORTING_REQUIRED

• %LICMGR-6-LOG_SMART_LIC_TRUST_CODE_INSTALL_SUCCESS

%LICMGR-3-LOG_SMART_LIC_POLICY_INSTALL_FAILED: The installation of a new licensing policy has failed: [chars].

Explanation: A policy was installed, but an error was detected while parsing the policy code, and installation failed. [chars] is the error string with details of the failure.

Possible reasons for failure include:

• A signature mismatch: This means that the system clock is not accurate.

• A timestamp mismatch: This means the system clock on the product instance is not synchronized with CSSM.

Recommended Action:

For both possible failure reasons, ensure that the system clock is accurate and synchronized with CSSM. Configure the ntp server command in global configuration mode. For example:

Device(config)# ntp server 198.51.100.100 version 2 prefer

If the above does not work and policy installation still fails, contact your Cisco technical support representative.

%LICMGR-3-LOG_SMART_LIC_AUTHORIZATION_INSTALL_FAILED: The install of a new licensing authorization code has failed on [chars]: [chars].

This message is not applicable to Cisco Nexus Switches, because there are no enforced or export-controlled licenses on these product instances.

%LICMGR-3-LOG_SMART_LIC_COMM_FAILED: Communications failure with the [chars] : [chars]

Explanation: Smart Licensing communication either with CSSM or with CSLU failed. The first [chars] is the currently configured transport type, and the second [chars] is the error string with details of the failure. This message appears for every communication attempt that fails.

Possible reasons for failure include:

• CSSM or CSLU is not reachable: This means that there is a network reachability problem.

• 404 host not found: This means that the CSSM server is down.

For topologies where the product instance initiates the sending of RUM reports (Connected to CSSM Through CSLU: Product Instance-Initiated Communication, Connected Directly to CSSM, and CSLU Disconnected from CSSM: Product Instance-Initiated Communication) if this communication failure message coincides with scheduled reporting (license smart usage interval interval_in_days global configuration command), the product instance attempts to send out the RUM report for up to four hours after the scheduled time has expired. If it is still unable to send out the report (because the communication failure persists), the system resets the interval to 15 minutes. Once the communication failure is resolved, the system reverts the reporting interval to the value that you last configured.

Recommended Action:

1. Check if the smart URL is configured correctly. Use the show license status command in privileged EXEC mode, to check if the URL is exactly as follows: https://smartreceiver.cisco.com/licservice/license. If it is not, reconfigure the license smart url smart smart_URL command in global configuration mode.

2. Check DNS resolution. Verify that the product instance can ping smartreceiver.cisco.com or the nslookup translated IP. The following example shows how to ping the translated IP:

   Device# ping 171.70.168.183 Type escape sequence to abort.
   Sending 5, 100-byte ICMP Echos to 171.70.168.183, timeout is 2 seconds:
   !!!!!
   Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms

If CSSM is not reachable and the configured transport type is callhome :

1. Check if the URL is entered correctly. Use the show license status command in privileged EXEC mode, to check if the URL is exactly as follows: https://tools.cisco.com/its/service/oddce/services/DDCEService.

2. Check if Call Home profile CiscoTAC-1 is active and destination URL is correct. Use the show call-home profile all command in privileged EXEC mode:

   Current smart-licensing transport settings: Smart-license messages: enabled
   Profile: CiscoTAC-1 (status: ACTIVE)
   Destination  URL(s): https://tools.cisco.com/its/service/oddce/services/DDCEService

3. Check DNS Resolution. Verify that the product instance can ping tools.cisco.com, or the nslookup translated IP.

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

   If the above does not work check the following: if the product instance is set, if the product instance IP network is up. To ensure that the network is up, configure the no shutdown command in interface configuration mode.

   Check if the device is subnet that is masked with a subnet IP, and if the DNS IP is configured.

4. Verify that the HTTPs client source interface is correct.

   Use the show ip http client command in privileged EXEC mode to display current configuration. Use ip http client source-interface command in global configuration mode to reconfigure it. In case the above does not work, double-check your routing rules, and firewall settings.

If CSLU is not reachable:

• Check if CSLU discovery works.

  • Zero-touch DNS discovery of cslu-local or DNS discovery of your domain.

    In the show license all command output, check if the Last ACK received: field. If this has a recent timestamp, it means that the product instance has connectivity with CSLU. If it is not, proceed with the following checks:

    Check if the product instance can ping cslu-local . A successful ping confirms that the product instance is reachable.

    If the above does not work, configure the name server with an entry where hostname cslu-local is mapped to the CSLU IP address (the Windows host where you installed CSLU). Configure the ip domain name domain-name and ip name-server server-address commands in global configuration mode. Here the CSLU IP is 192.168.0.1 and name-server creates entry cslu-local.example.com :

    Device(config)# ip domain name example.com 

    Device(config)# ip name-server 192.168.0.1 

  • CSLU URL is configured.

    In the show license all command output, under the Transport: header check the following: The Type: must be cslu and Cslu address: must have the hostname or the IP address of the Windows host where you have installed CSLU. Check if the rest of the address is configured as shown below and check if the port number is 8182.

    Transport:
    Type: cslu
    Cslu address: http://192.168.0.1:8182/cslu/v1/pi

    If it is not, configure the license smart transport cslu and license smart url cslu http://<cslu_ip_or_host>:8182/cslu/v1/pi commands in global configuration mode.

If the above does not work and policy installation still fails, contact your Cisco technical support representative.

%LICMGR-3-LOG_SMART_LIC_COMM_RESTORED: Communications with the [chars] restored. [chars] - depends on the transport type
-  Cisco Smart Software Manager (CSSM)
-  Cisco Smart License utility (CSLU)
Smart Agent communication with either the Cisco Smart Software Manager (CSSM) or the Cisco Smart License
utility (CSLU) has been restored. No action required.

Explanation: Product instance communication with either the CSSM or CSLU is restored.

Recommended Action: No action required.

%LICMGR-3-LOG_SMART_LIC_POLICY_REMOVED: The licensing policy has been removed.

Explanation: A previously installed licensing policy has been removed. The Cisco default policy is then automatically effective. This may cause a change in the behavior of smart licensing.

Possible reasons for failure include:

If you have entered the license smart factory reset command in privileged EXEC mode all licensing information including the policy is removed.

Recommended Action:

If the policy was removed intentionally, then no further action is required.

If the policy was removed inadvertently, you can reapply the policy. Depending on the topology you have implemented, follow the corresponding method to retrieve the policy:

• Connected Directly to CSSM:

  Enter show license status , and check field Trust Code Installed: . If trust is established, then CSSM will automatically return the policy again. The policy is automatically re-installed on product instances of the corresponding Virtual Account.

  If trust has not been established, complete these tasks: See the Generating a New Token for a Trust Code from CSSM and Installing a Trust Code topics in Common Tasks for Configuring Smart Licensing Using Policy. When you have completed these tasks, CSSM will automatically return the policy again. The policy is then automatically installed on all product instances of that Virtual Account.

• Connected to CSSM Through CSLU:

  • For product instance-initiated communication), enter the license smart sync command in privileged EXEC mode. The synchronization request causes CSLU to push the missing information (a policy or authorization code) to the product instance.

• CSLU Disconnected from CSSM:

  • For product instance-initiated communication), enter the license smart sync command in privileged EXEC mode. The synchronization request causes CSLU to push the missing information (a policy or authorization code) to the product instance. Then complete these tasks in the given order: Download All For Cisco (CSLU Interface) > Uploading Usage Data to CSSM and Downloading an ACK > Upload From Cisco (CSLU Interface)See the Uploading Usage Data to CSSM and Downloading an ACK task in Common Tasks for Configuring Smart Licensing Using Policy..

• No Connectivity to CSSM and No CSLU

  If you are in an entirely air-gapped network, from a workstation that has connectivity to the internet and CSSM complete this task: See the Downloading a Policy File from CSSM and Installing a a File on the Switch topics in Common Tasks for Configuring Smart Licensing Using Policy.

%LICMGR-3-LOG_SMART_LIC_TRUST_CODE_INSTALL_FAILED: The install of a new licensing trust code has failed on [chars]: [chars].

Explanation: Trust code installation has failed. The first [chars] is the UDI where trust code installation was attempted. The second [chars] is the error string with details of the failure.

Possible reasons for failure include:

• A trust code is already installed: Trust codes are node-locked to the UDI of the product instance. If the UDI is already registered, and you try to install another one, installation fails.

• Smart Account-Virtual Account mismatch: This means the Smart Account or Virtual Account (for which the token ID was generated) does not include the product instance on which you installed the trust code. The token generated in CSSM, applies at the Smart Account or Virtual Account level, and applies only to all product instances in that account.

• A signature mismatch: This means that the system clock is not accurate.

• Timestamp mismatch: This means the product instance time is not synchronized with CSSM and can cause installation to fail.

Recommended Action:

• A trust code is already installed: If you want to install a trust code despite an existing trust code on the product instance, re-configure the license smart trust idtoken id_token_value{local|all}[force] command in privileged EXEC mode, and be sure to include the force keyword this time. Entering the force keyword sets a force flag in the message sent to CSSM to create a new trust code even if one exists.

• Smart Account-Virtual Account mismatch: Log in to the CSSM Web UI at https://software.cisco.com/software/smart-licensing/alerts and click Smart Software Licensing > Inventory > Product Instances.

• Check if the product instance on which you want to generate the token is listed in the selected Virtual Account. If it is, proceed to the next step. If not, check and select the correct Smart Account and Virtual Account. Then complete these tasks again: See the Generating a New Token for a Trust Code from CSSM and Installing a Trust Code topics in Common Tasks for Configuring Smart Licensing Using Policy.

• Timestamp mismatch and signature mismatch: Configure the ntp server command in global configuration mode. For example:

  Device(config)# ntp server 198.51.100.100 version 2 prefer

%LICMGR-4-LOG_SMART_LIC_REPORTING_NOT_SUPPORTED: The CSSM OnPrem that this product instance is connected to is down rev and does not support the enhanced policy and usage reporting mode.

Explanation: Cisco Smart Software Manager On-Prem (formerly known as Cisco Smart Software Manager satellite) is not supported in the SLP environment. The product instance behaves as follows:

• Stop sending registration renewals and authorization renewals.

• Start recording usage and saving RUM reports locally.

Recommended Action: Refer to and implement one of the supported topologies instead. See: Supported Deployment Models and Topologies.

%LICMGR-6-LOG_SMART_LIC_POLICY_INSTALL_SUCCESS: A new licensing policy was successfully installed.

Explanation: A policy was installed in the following way:

• As part of an ACK response.

Recommended Action: No action is required. If you want to know which policy is applied (the policy in-use) and its reporting requirements, enter the show license all command in privileged EXEC mode.

Error Message %LICMGR-6-LOG_SMART_LIC_AUTHORIZATION_INSTALL_SUCCESS: A new licensing authorization code was successfully installed on: [chars].

This message is not applicable to Cisco Nexus Switches, because there are no enforced or export-controlled licenses on these product instances.

%LICMGR-6-LOG_SMART_LIC_AUTHORIZATION_REMOVED: A licensing authorization code has been removed from [chars]

Explanation: [chars] is the UDI where the authorization code was installed. The authorization code has been removed. This removes the licenses from the product instance and may cause change in the behavior of smart licensing and the features using licenses.

Recommended Action: No action is required. If you want to see the current state of the license, enter the show license all command in privileged EXEC mode.

%LICMGR-6-LOG_SMART_LIC_REPORTING_REQUIRED: A Usage report acknowledgement will be required in [dec] days.

Explanation: This is an alert which means that RUM reporting to Cisco is required. [dec] is the amount of time (in days) left to meet this reporting requirements.

Recommended Action: Ensure that RUM reports are sent within the requested time.

• If the product instance is directly connected to CSSM, or to CSLU and the product instance is configured to initiate communication complete this step on the product instance, the product instance will automatically send usage information at the scheduled time.

• If it is not sent at the scheduled time, because of technical difficulties, you can license smart sync command in privileged EXEC mode. For syntax details, see the license smart (privileged EXEC) in the Command Reference.

• If the product instance is connected to CSLU, but CSLU is disconnected from CSSM, complete these tasks: Download All For Cisco (CSLU Interface), Uploading Usage Data to CSSM and Downloading an ACK, and Upload From Cisco (CSLU Interface). See the Uploading Usage Data to CSSM and Downloading an ACK task in Common Tasks for Configuring Smart Licensing Using Policy.

• If the product instance is disconnected from CSSM and you are not using CSLU either, enter the license smart save usage command in privileged EXEC mode, to save the required usage information in a file. Then, from a workstation where you have connectivity to CSSM, complete these tasks: First perform the Uploading Usage Data to CSSM and Downloading an ACK task and then perform the Installing a File on the Product Instance task from Common Tasks for Configuring Smart Licensing Using Policy..

%LICMGR-6-LOG_SMART_LIC_TRUST_CODE_INSTALL_SUCCESS: A new licensing trust code was successfully installed on [chars].

Explanation: [chars] is the UDI where the trust code was successfully installed.

Recommended Action: No action is required. If you want to verify that the trust code is installed, enter the show license status command in privileged EXEC mode. Look for the updated timestamp under header Trust Code Installed: in the output.