Where can you drop off your LIC policy

Smart Licensing - Guidelines for Catalyst Switching Platforms

introduction

This document describes the Smart Licensing feature using the Catalyst Switching Platform Guidelines and the various supported delivery mechanisms from the Cisco IOS®-XE 17.3.2 version and future versions.

purpose

Starting with 17.3.2 and 17.4.1, all Catalyst switching platforms in the product family for Cat9k support a new licensing model for Smart Licensing Using Policy. This document explains the various supported implementation and deployment models of Smart Licensing using guidelines, primarily for greenfield deployments.

Smart licensing with guidelines

With Smart Licensing using Policy, all licenses are used immediately in the device. The earlier concepts, evaluation mode, registration and reservation are carried over with Smart Licensing using Policy. Smart Licensing using Policy is all about reporting licenses and their usage. The licenses are not yet enforced and the licensing levels remain unchanged. There are no export-driven license levels for the Catalyst Switch platforms. Smart Licensing Using Policy only changes the infrastructure for reporting license usage and tracking. This section describes in detail the terminology, the benefits of the changes, the new components that include Smart Licensing using Policy, CSLU - Cisco Smart Licensing Utility, the product ordering process.

terminology

  • CSSM or SSM - Cisco Smart Software Manager
  • SA - Smart Account
  • VA - Virtual Account
  • SL = Smart Licensing
  • PLR = Permanent License Reservation
  • SLR = Smart License Reservation
  • PIDs - Product IDs
  • SCH - Smart Call Home
  • PI = product instances
  • CSLU = Cisco Smart Licensing Utility
  • RUM = Resource Utilization Measurement
  • ACK - confirmation
  • UDI = Unique Device Identification - PID + SN
  • SLP - Smart Licensing with Guidelines

Why this change?

With the introduction of the Smart Licensing model for Trustworthiness and verification Cisco has supported various delivery mechanisms for tracking and reporting license usage with CSSM. However, it has not been easy to adapt to the needs of all deployments. Feedback and requirements were given on site in order to use Smart Licensing for a better introduction. Some of the challenges are: With SL registration: Devices must always be connected to the internet in order to achieve CSSM. This is a deployment issue. On-site satellite servers cause higher deployment and maintenance costs. SLR only supports air gap networks. Deployments that do not support either of these models must have their devices in the Status "Not Registered / Expired" even after licenses have been purchased.

To simplify various such inquiries from the field, Smart Licensing with Policy is introduced. With Smart Licensing using Policy, you do not need to register the product with CSSM. All license levels purchased are instantly in use. This removes the friction from day 0 that was present on the device. Smart Licensing Using Policy also minimizes the license delivery workflow and reduces the number of points of contact. The device must be connected to the CSSM around the clock. Smart Licensing using Policy also enables the use of licenses in the disconnected network, offline reporting of license usage and reporting of licenses at intervals determined by customer policies

The new components

Directive

The policy defines which standard behavior must be set for the PI. It contains information about the attributes for the reporting requirements related to licenses for different license levels and terms. The policy also specifies whether the ACK message must be sent back to PI for every report sent to CSSM. The policy also includes the name of the policy and when the policy will be installed. The Cisco standard policy is common and standard for all Catalyst products. However, the custom policies are also allowed if you want to have different reporting interval, ACK response omission.

The policy can be installed on a PI on several occasions.

  • Standard policy available in the software
  • Policies installed by Cisco Manufacturing
  • Policy is installed by ACK response
  • Manual installation of the policy through the CLI
  • The policy is forwarded with Yang Request.

This output shows what a standard policy looks like.

Policy:

Policy in use: Merged from multiple sources.
Reporting ACK required: yes (CISCO default)
Unforced / Non-Export Perpetual Attributes:
First report requirement (days): 365 (CISCO default)
Reporting frequency (days): 0 (CISCO default)
Report on change (days): 90 (CISCO default)
Unforced / Non-Export Subscription Attributes:
First report requirement (days): 90 (CISCO default)
Reporting frequency (days): 90 (CISCO default)
Report on change (days): 90 (CISCO default)
Enforced (Perpetual / Subscription) License Attributes:
First report requirement (days): 0 (CISCO default)
Reporting frequency (days): 0 (CISCO default)
Report on change (days): 0 (CISCO default)
Export (Perpetual / Subscription) License Attributes:
First report requirement (days): 0 (CISCO default)
Reporting frequency (days): 0 (CISCO default)
Report on change (days): 0 (CISCO default)

Note: A policy cannot be deleted by deleting / changing a system configuration, clearing the NVRAM, or formatting the flash memory: file system. The policy is set to Cisco Standard, "License Smart Factory Reset".

RUM reports

Resource usage measurement includes usage reports that are generated and stored by the PI. The ISO19770-4 standard RUM reports are completed for Smart Licensing using guidelines. RUM reports save any license usage changes made in the PI as report files. Usage data for each license level is stored in separate rum reports. RUM report measurements are collected at regular intervals and stored in PI. If the PI's license usage changes or usage reports have been generated or the maximum size / sample has been reached, new rum reports are generated for all license levels. In other cases, the existing rum reports can be overwritten with a new example and an updated timestamp. The default measurement of the rum report is every 15 minutes. Drum reports are sent to the Cisco CSSM at each reporting interval.


All rum reports are signed by the PI and verified by the CSSM. When the CSSM receives the rum report data from PI, it validates the report, reviews the modified license usage timeline, and updates the CSSM data accordingly. CSSM then confirms back to the PI via the ACK response message.

RUM reports can be sent to the CSSM in a number of ways.

  • PI sends rum reports directly to CSSM over the reporting interval
  • PI forwards the rum report to CSLU.
  • CSLU Pulls Rum reports from PI at regular intervals about RESTAPI and YANG models.
  • Rum reports are manually saved on the PI via the CLI and manually uploaded to the CSSM.

Note: RUM reports cannot be deleted by deleting / changing a system configuration, deleting the nvram, or formatting the flash memory: file system. All rum reports can be removed from PI under "License Smart Factory Reset".

Note: The default reporting interval is 30 days.

Manufacturing process for greenfield deployment case

As soon as a new product order is placed in Cisco CCW, the PI goes through the workflow of the manufacturing team. This is to facilitate the secure process of signing rum reports and to remove the tension of Day-0 when registering the PI. After placing the order, all existing SA / VA or newly created SA / VA are linked to the product. The Cisco Manufacturing Team takes care of these processes before the product is shipped to you.

  • Install the trust code on the device. The trust code signature is installed based on the device UDI. Installed on every product.
  • Installation Code: Information about the license levels that are purchased with the product. Installed on every product.
  • SLAC - Smart License Auth Code - Does not apply to Catalyst platforms.
  • Installation Policy - Standard or Custom Policy based on your input.
  • Report the license usage to CSSM - SA / VA.

Note: {From 3/17/2/17/4/1 the trust code will not be installed by the manufacturing team.}

CSLU

Smart Licensing using Policy provides a new, simple, and powerful tool, Cisco Smart Licensing Utility (CSLU). CSLU is a GUI-based tool that runs on Windows 10. CSLU, which can run on your local private network, is responsible for collecting the RUM ports from the PIs associated with CSSM. The CSLU must be provided in such a way that rum reports are recorded via PIs in the local network and the rum report is regularly forwarded to the CSSM via the Internet. UDI CSLU is a simple tool that only shows the details of the UDI of the deployed devices. All license usage data for PIs, purchased licenses, unused licenses in the pool are only displayed in SA / VA from CSSM, which you can review. It's powerful because it can collect usage reports of up to 10,000 PIs. CSLU is also responsible for getting the ACK messages from the CSSM back to PI.

Note: A detailed configuration and the supported operating modes of CSLU can be found in the section CSLU-based topology.

Smart Licensing Policy - Direct Connect

For a product shipped from the factory, the default transport mode is configured to CSLU. If you want to use the Direct Connect method, you need to change the transport mode to Call Home (Call Home) or SMART (SMART) as required. The basic requirement for the Direct Connect topology method is the availability of CSSM through an internet connection. In addition, it must be ensured that the L3 configurations, DNS and domain configurations required for the connection to the CSSM are available in the device.

License reports

In the Direct Connect topology, the rum reports are sent directly to CSSM. License reports require that the successful trust code be installed on the device. Cisco Manufacturing installs the trust code on the device prior to shipping. You can also install Trust Code on the device.

The trust code is a token string that is adopted by CSSM on the "Virtual account - general page" page. Trusted code can be installed through the CLI.

Switch # license smart trust idtoken <> all / local

Note:All Options must be used for HA or stacking back systems. A local option can be used for a stand-alone device.

Switch # license smart trust idtoken <> all / local.



On Successful installation of policy, the same can be verified through 'show license status' CLI.

Switch # show license status

Utility:
Status: DISABLED

Smart Licensing Using Policy:
Status: ENABLED

Data Privacy:
Sending host name: yes
Callhome hostname privacy: DISABLED
Smart Licensing hostname privacy: DISABLED
Privacy version: DISABLED

Transport:
Type: Callhome

Policy:
Policy in use: Installed On Nov 07 22:50:04 2020 UTC
Policy name: SLP Policy
Reporting ACK required: yes (Customer Policy)
Unforced / Non-Export Perpetual Attributes:
First report requirement (days): 60 (Customer Policy)
Reporting frequency (days): 60 (Customer Policy)
Report on change (days): 60 (Customer Policy)
Unforced / Non-Export Subscription Attributes:
First report requirement (days): 30 (Customer Policy)
Reporting frequency (days): 30 (Customer Policy)
Report on change (days): 30 (Customer Policy)
Enforced (Perpetual / Subscription) License Attributes:
First report requirement (days): 0 (CISCO default)
Reporting frequency (days): 90 (Customer Policy)
Report on change (days): 90 (Customer Policy)
Export (Perpetual / Subscription) License Attributes:
First report requirement (days): 0 (CISCO default)
Reporting frequency (days): 90 (Customer Policy)
Report on change (days): 90 (Customer Policy)

Miscellaneous:
Custom Id:

Usage reporting:
Last ACK received: Nov 03 12:57:01 2020 UTC
Next ACK deadline: Dec 03 12:57:01 2020 UTC
Reporting push interval: 30 days
Next ACK push check:
Next report push: Nov 07 22:50:35 2020 UTC
Last report push: Nov 03 12:55:57 2020 UTC
Last report file write:

Trust Code Installed:
Active: PID: C9500-24Y4C, SN: CAT2344L4GH
INSTALLED on Nov 07 22:50:04 2020 UTC
Standby: PID: C9500-24Y4C, SN: CAT2344L4GJ
INSTALLED on Nov 07 22:50:04 2020 UTC

As soon as the trust code has been successfully installed, the PI can report its use directly to CSSM. License reports are made under these conditions.

  • If the Trust Code installation is successful.
  • In every standard reporting interval.
  • Reload / boot to device.
  • With switchover.
  • Adding or removing stack elements.
  • When starting the license synchronization manually.

License reports to CSSM can be triggered via the following CLI.

Switch # license smart sync all

The Usage Reports section in License status shows us the schedules for "Last ACK Received", "Next ACK Deadline", "Next Report Push" and "Last Report".

Usage reporting:
Last ACK received: Nov 03 12:57:01 2020 UTC
Next ACK deadline: Dec 03 12:57:01 2020 UTC
Reporting push interval: 30 days
Next ACK push check:
Next report push: Nov 07 22:50:35 2020 UTC
Last report push: Nov 03 12:55:57 2020 UTC
Last report file write:

Direct Connect - Smart Transport

When using SMART Transport, on a Direct Connect or Direct Cloud Access mode topology, the required configurations are in place on the device.

Configure the desired Transport mode using the CLI below.

Switch (config) #license smart transport smart

Running config on Smart Transport Mode:
!
license smart url smart https://smartreceiver.cisco.com/licservice/license
license smart transport smart
!

Direct Connect - Call Home Transport

On a Direct Connect or Direct Cloud Access mode topology, if Call-Home Transport is used, the required configurations on the device are listed below.

Configure the desired Transport mode using the CLI below.

Switch (config) #license smart transport callhome

Running config on Smart Transport Mode:
!
service call home
!
call home
contact-email-addr [email protected]
no http secure server-identity-check
profile "CiscoTAC-1"
active
reporting smart licensing data
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination transport method http
!

Note: By default, the destination address for Call Home is configured to CSSM URL. This can be done in show run all config should be checked.

Smart Licensing using Policy - CSLU

CSLU mode is the default transport mode on factory-shipped devices running 17.3.2 or later. If you are migrating from expired Eval / Eval licenses, the transport mode after switching to Smart Licensing using policies is CSLU. In the CSLU-based topology, the CSLU is located between the PI and the CSSM. CSLU prevents users from having a direct network connection to Cisco Cloud - CSSM. CSLU can run locally on the private network and usage reports can be downloaded from all associated PIs. The usage reports are saved locally on the Windows PC before they are sent to CSSM over the Internet. CSLU is a simple tool. You can only see the list of PIs assigned to it and identify them using UDIs. CSLU cannot display or contain the redundancy information "PI", "License Levels", or "License Usage".

Installation and configuration of CSLU

The CSLU tool is installed and running on a Windows 10 computer. The software is available for download and use free of charge in CCO. After installing the program, you can download the quick start guide / user manual from the Help menu. Navigate to Help> Download Help.

The license agreement must be accepted for the CSLU installation.

It is recommended that you install the application only for the current user and not for all users who will work on the computer.

If an earlier version of CSLU is already available on the PC, it is advisable to uninstall it beforehand. However, the reinstallation takes over the update of the software.

Once installed, sign in to Cisco using the Sign In option in the top right corner of the application. Your CEC credentials were used for this. By logging in, a trustworthiness between CSLU and CSSM is established.

After signing in to Cisco, make sure the SA and VA details are correctly selected in the drop-down menu in the Preferences section of the tool. Make sure the configurations are saved.

CSLU in PUSH mode

By default, CSLU runs in PUSH mode. In PUSH mode, the PI sends the usage reports to CSLU at regular intervals. From the device, you must ensure that the accessibility of the L3 network to CSLU is available. In order for the PI to communicate with the CSLU, the IP address of the Windows computer on which the CSLU is running must be configured.

Switch (config) #license smart url cslu http: //


The same can be verified through 'show license status' CLI

Switch # show license status

Load for five secs: 0% / 0%; one minute: 0%; five minutes: 0%

No time source, 20:59: 25.156 EDT Sat Nov 7 2020




Utility:

Status: DISABLED




Smart Licensing Using Policy:

Status: ENABLED




Data Privacy:

Sending host name: yes

Callhome hostname privacy: DISABLED

Smart Licensing hostname privacy: DISABLED

Privacy version: DISABLED




Transport:

Type: cslu

Cslu address: http: //

Proxy:

Not configured




Policy:

Policy in use: Merged from multiple sources.

Reporting ACK required: yes (CISCO default)

Unforced / Non-Export Perpetual Attributes:

First report requirement (days): 365 (CISCO default)

Reporting frequency (days): 0 (CISCO default)

Report on change (days): 90 (CISCO default)

Unforced / Non-Export Subscription Attributes:

First report requirement (days): 90 (CISCO default)

Reporting frequency (days): 90 (CISCO default)

Report on change (days): 90 (CISCO default)

Enforced (Perpetual / Subscription) License Attributes:

First report requirement (days): 0 (CISCO default)

Reporting frequency (days): 0 (CISCO default)

Report on change (days): 0 (CISCO default)

Export (Perpetual / Subscription) License Attributes:

First report requirement (days): 0 (CISCO default)

Reporting frequency (days): 0 (CISCO default)

Report on change (days): 0 (CISCO default)




Miscellaneous:

Custom Id:




Usage reporting:

Last ACK received:

Next ACK deadline: Feb 05 15:32:51 2021 EDT

Reporting push interval: 30 days

Next ACK push check:

Next report push: Nov 07 15:34:51 2020 EDT

Last report push:

Last report file write:

Trust Code Installed:

Reports are sent from PI to CSLU under these conditions.

  • In every standard reporting interval.
  • Reload / boot to device.
  • With switchover.
  • Adding or removing stack elements.
  • When starting the license synchronization manually.

The "CSLU" (inventory) page lists the devices that are currently assigned to the CSLU. The devices in the list can be identified using the UDI. The devices can be filtered from the list using the PID or SN in order to identify a specific device.

The CSLU Inventory page also has two additional columns:

The gap Last contactwhich shows the current timestamp when the report status has changed.

The Alerts column shows the current reporting status of the PI.

Once the PI sends the report to the CSLU, the CSLU creates the PI record in the CSSM, the TS for the last contact person is updated, and the status for alerts is also updated.

CSSM processes the reports sent by CSLU, adds or updates the product instance on the CSSM depending on the license usage. Once the CSSM process and date are updated, it sends the ACK message back to CSLU. CSLU saves the message and forwards it back to PI.

The ACK message consists of

  • Confirmation of all reports sent.
  • Directive
  • Trustworthy code

If a new policy is available for you in the CSSM, it will now also be updated to the PI. If the policy is unchanged, this will also be forwarded to PI.

Note: If your policy does not require an ACK message message, the ACK message will not be sent.

The Alert column can have one of these statuses.

  • Product instance usage report
  • Usage report is uploaded to Cisco
  • Confirmation from the CSSM
  • Confirmation of the usage report for the product instance.

Note: In CSLU on an HA system, the entry is only displayed for the active's UDI. Only CSSM has all of the UDI for individual devices in the system.

Automatic CSLU detection

Auto-discovery of the SKLU is supported to support deployments with minimal configurations. This means that you do not have to specifically configure the IP address / URL of the CSLU. To do this, you just need to add an entry to your DNS server. This allows the device whose transport mode is "cslu" (the default) to automatically detect cslu and send reports.

There are a few more points to consider here.

  • Create an entry in the DNS server. The IP address of the cslu must match the name cslu-local be assigned.
  • Make sure that the name server and the DNS configurations are available in the device in order to be reachable.


Without additional configuration, the devices on the network can reach CSLU and send drum reports at regular intervals.

CSLU in PULL mode

In PULL mode, the CSLU retrieves the rum reports from the devices. This is where the device details are added to the CSLU, and the CSLU polls the data on all added devices at regular intervals. The CSLU PULL can also be triggered manually. CSLU, in turn, sends the rum report to CSSM, and ACK messages returned by CSSM are sent to PI. PULL mode is supported in three different ways. - RESTAPI, NETCONF and RESTCONF.

PULL mode with RESTAPI

So that the PULL mode can be executed by RESTAPI, the configurations required by the device and CSLU are

Configs on PI:

Ensure the network reachability from PI to CSLU is available and working.

!
ip http server
ip http authentication local
ip http secure server
!
aaa new-model
aaa authentication login default local
aaa authorization exec default local
username admin privilege 15 password 0 lab
!

Note: The user must have access to priv level 15.

CSLU process for the facility

CSLU must be signed in to CSSM in order for reports to be automatically synchronized.

Step 1: Choose Add a single product on the inventory page.

Step 2: Enter the device IP.

Step 3: Select the Connect Method as RESAPI.

Step 4: Select the product instance credentials.

Step 5: Enter the user credentials for the user with Priv 15 access.

Step 6: Save the configurations.

The device is added with a single IP address in the Name field.

Select the device and navigate to Actions for Selected> Collect Usage.

After the usage data has been successfully collected, the Name field is updated to the PI's UDI and the timestamp is also updated. The warning message field shows the current status.

If the device is still available when the ACK message is received from the CSSM, the ACK is sent back to PI. Other ACKs are sent at the next pull interval.

PULL mode with RESTCONF

So that the PULL mode can be executed by RESTCONF, the configurations and steps required by the device from the CSLU are as follows:

Configs on PI:

!
restconf
!
ip http secure server
ip http authentication local
ip http client source interface GigabitEthernet 0/0
!
username admin privilege 15 password 0 lab
!

Note: These configurations are used for local authentication. Remote authentication can also be used.

CSLU - Procedure for Establishment

CSLU must be signed in to CSSM in order for reports to be automatically synchronized. The CSLU facility is the same as RESTAPI for creating and reporting rum reports.

Step 1: Choose Add a single product on the inventory page.

Step 2: Enter the device IP

Step 3: Select the Connect method as RESTCONF.

Step 4: Select the product instance credentials.

Step 5: Enter the user credentials for the user with Priv 15 access.

Step 6: Save the configurations.

Step 7: Collect usage data for the selected device

PULL mode with NETCONF

So that the PULL mode can be executed via NETCONF, the configurations required by the device and the steps from the CSLU are as follows:

Configs on PI:

!
ip ssh version
!
netconf-yang
netconf ssh
netconf-yang feature candidate-datastore
!
username admin privilege 15 password 0 lab
!

To ensure yang process is running, execute the command:

Switch # show platform software yang-management process
confd: Running
nesd: Running
syncfd: Running
ncsshd: Running
dmiauthd: Running
nginx: Running
ndbmand: Running
pubd: Running
gnmib: Not Running

Note: These configurations are used for local authentication. Remote authentication can also be used.

CSLU - Procedure for Establishment

CSLU must be signed in to CSSM in order for reports to be automatically synchronized. The CSLU facility is the same as RESTAPI for creating and reporting rum reports.

Step 1: Choose Add a single product on the inventory page.

Step 2: Enter the device IP.

Step 3: Select the Connect Method as NETCONF.

Step 4: Select the product instance credentials.

Step 5: Enter the user credentials for the user with Priv 15 access.

Step 6: Save the configurations.

Step 7: Collect usage data for the selected device

Note: With all models, NETCONF, RESTCONF and RESTAPI, the device list can be added in bulk.

To perform the bulk upload, navigate to the Menu bar to Product Instance> Upload Product Instance Listas shown in this picture.

A new pop-up window will open. The template file can be downloaded from here. In the CSV format file, fill in the device details of the device list and upload it to CSLU to add multiple devices.

Note: For all types of CSLU PULL mode, it is recommended that the transport setting be set to Off for the PI. This can be done through the CLI.

Switch (config) #license smart transport off

CSLU in disconnected mode

CSLU can be operated in separate mode from CSSM. This applies to all deployments where the CSLU cannot connect to the Internet. In disconnected mode, reports from all devices are manually downloaded from CSLU and uploaded to CSSM. ACK messages, in turn, are downloaded from CSSM and uploaded to CSLU. CSLU continues the PULL / PUSH usage date of PIs and continues to send the ACK message back to PI.

Step 1: uncheck on the CSLU preference-Page the option Cisco Connectivity. This confirms that Cisco is not available.

Step 2: Save the settings.

Step 3: Click in the Menu bar on Product Instances> Download All for Cisco. This creates a tar.gz-File downloaded to the CSLU.

Step 4: Upload the file to CSSM. On the CSSM Smart Account page, navigate to Report> Usage Data Files> Upload Usage Data.

Load the file in the pop-up window tar.gz high.

Step 5: After the data has been processed, the confirmation is generated. Download the ACK file and upload it to CSLU.

Step 6: In the CSLU, import the ACK file from the menu bar and navigate to Product Instances> Upload from Cisco (Product Instances> Upload From Cisco) as shown in this picture.

Step 7: After uploading the ACK, the message is sent to the PIs. The same can also be checked in the "Warnings" column.

Smart Licensing Policy - Offline Mode

Smart Licensing using Policy can also be run in offline mode. This is especially true for air-gap networks that do not prefer an internet connection and also do not want to use a CSLU connection. In offline mode the transport is on Out set.

Switch (config) #license smart transport off

Same can be verified through, 'show license status'

Switch # show license status

Utility:
Status: DISABLED

Smart Licensing Using Policy:
Status: ENABLED

Data Privacy:
Sending host name: yes
Callhome hostname privacy: DISABLED
Smart Licensing hostname privacy: DISABLED
Privacy version: DISABLED

Transport:
Type: Transport Off

Policy:
Policy in use: Merged from multiple sources.
Reporting ACK required: yes (CISCO default)
Unforced / Non-Export Perpetual Attributes:
First report requirement (days): 365 (CISCO default)
Reporting frequency (days): 0 (CISCO default)
Report on change (days): 90 (CISCO default)
Unforced / Non-Export Subscription Attributes:
First report requirement (days): 90 (CISCO default)
Reporting frequency (days): 90 (CISCO default)
Report on change (days): 90 (CISCO default)
Enforced (Perpetual / Subscription) License Attributes:
First report requirement (days): 0 (CISCO default)
Reporting frequency (days): 0 (CISCO default)
Report on change (days): 0 (CISCO default)
Export (Perpetual / Subscription) License Attributes:
First report requirement (days): 0 (CISCO default)
Reporting frequency (days): 0 (CISCO default)
Report on change (days): 0 (CISCO default)



Miscellaneous:
Custom Id:

Usage reporting:
Last ACK received: Nov 11 15:41:10 2020 EDT
Next ACK deadline: Dec 11 15:41:10 2020 EDT
Reporting push interval: 30 days
Next ACK push check:
Next report push: Dec 07 21:42:30 2020 EDT
Last report push: Nov 07 21:42:30 2020 EDT
Last report file write:

Trust Code Installed:

If you want to report the usage data to CSSM, the usage reports must be downloaded as a file and manually uploaded to CSSM. In an HA system, Active tracks usage for standby / member devices.

To download the usage data from PI -

Switch # license smart save usage unreported file bootflash:

Above option 'unreported' is recommended to use. This downloads only the files that are yet to be reported
and discard old usage reports that were acknowledged.


However, there are other options available for the amount of data that needs to be reported.
For downloading all the available report use option all,
# of daya can be specified


Switch # license smart save usage?
all Save all reports
days Save reports from last n days
rum-Id Save an individual RUM report
unreported Save all previously un reported reports


This report must now be uploaded manually to CSSM.

Export the storage usage data from PI to Desktop.

On the CSSM Smart Account page, navigate to Report> Usage Data Files> Upload Usage Data. In the pop-up window, select the usage report and click Upload.

After the file is uploaded, you will need to select the correct VA that the device is associated with.

After the data is fully processed and the confirmation is ready, download the file and upload it to PI.

To import the ACK to PI,
Switch # license smart import bootflash:
Import data successful

Switch #
Nov 11 20: 23: 06.783:% SMART_LIC-6-POLICY_INSTALL_SUCCESS: A new licensing policy was successfully installed
Switch #

Policy Installed syslog is displayed on console if successful.

Also, the same can be verified using CLI, 'show license all'. The field 'Last ACK received' tells the
last TimeStamp when ACK message was received.


Switch # show license all
Load for five secs: 0% / 0%; one minute: 1%; five minutes: 0%
No time source, 16: 23: 22.294 EDT Wed Nov 11 2020

Smart Licensing Status
======================

Smart Licensing is ENABLED

Export Authorization Key:
Features Authorized:
<none>

Utility:
Status: DISABLED

Smart Licensing Using Policy:
Status: ENABLED

Data Privacy:
Sending host name: yes
Callhome hostname privacy: DISABLED
Smart Licensing hostname privacy: DISABLED
Privacy version: DISABLED

Transport:
Type: Transport Off

Miscellaneous:
Custom Id:

Policy:
Policy in use: Installed On Nov 11 16:23:06 2020 EDT
Policy name: SLP Policy
Reporting ACK required: yes (Customer Policy)
Unforced / Non-Export Perpetual Attributes:
First report requirement (days): 60 (Customer Policy)
Reporting frequency (days): 60 (Customer Policy)
Report on change (days): 60 (Customer Policy)
Unforced / Non-Export Subscription Attributes:
First report requirement (days): 30 (Customer Policy)
Reporting frequency (days): 30 (Customer Policy)
Report on change (days): 30 (Customer Policy)
Enforced (Perpetual / Subscription) License Attributes:
First report requirement (days): 0 (CISCO default)
Reporting frequency (days): 90 (Customer Policy)
Report on change (days): 90 (Customer Policy)
Export (Perpetual / Subscription) License Attributes:
First report requirement (days): 0 (CISCO default)
Reporting frequency (days): 90 (Customer Policy)
Report on change (days): 90 (Customer Policy)

Usage reporting:
Last ACK received: Nov 11 4:23:06 PM 2020 EDT
Next ACK deadline: Dec 11 16:23:06 2020 EDT
Reporting push interval: 30 days
Next ACK push check:
Next report push: Dec 07 21:42:30 2020 EDT
Last report push: Nov 07 21:42:30 2020 EDT
Last report file write:

Trust Code Installed:

License Usage
=============

network advantage (C9500 Network Advantage):
Description: network-advantage
Count: 1
Version: 1.0
Status: IN USE
Export status: NOT RESTRICTED
Feature Name: network-advantage
Feature Description: network-advantage
Enforcement type: NOT ENFORCED
License type: Perpetual

dna advantage (C9500 32QC DNA Advantage):
Description: C9500-32QC DNA Advantage
Count: 1
Version: 1.0
Status: IN USE
Export status: NOT RESTRICTED
Feature Name: dna-advantage
Feature Description: C9500-32QC DNA Advantage
Enforcement type: NOT ENFORCED
License type: Subscription

Product information
===================
UDI: PID: C9500-32QC, SN: CAT2148L15K

Agent version
=============
Smart Agent for Licensing: 5.0.6_rel / 47

License Authorizations
======================
Overall status:
Active: PID: C9500-32QC, SN: CAT2148L15K
Status: NOT INSTALLED

Purchased Licenses:
No purchase information available

Troubleshooting

Debug PI

To troubleshoot problems, PI collects the following commands:

show license all
show license tech support
show license eventlog
show license history message


For debugging Trust Installation / Sync -

Switch # show license tech support | s Trust
Trust Establishment:
Attempts: Total = 0, Success = 0, Fail = 0 Ongoing Failure: Overall = 0 Communication = 0
Last Response:
Failure reason:
Last Success Time:
Last Failure Time:
Trust Acknowledgment:
Attempts: Total = 0, Success = 0, Fail = 0 Ongoing Failure: Overall = 0 Communication = 0
Last Response:
Failure reason:
Last Success Time:
Last Failure Time:
Trust Sync:
Attempts: Total = 0, Success = 0, Fail = 0 Ongoing Failure: Overall = 0 Communication = 0
Last Response:
Failure reason:
Last Success Time:
Last Failure Time:
Trusted Store Interface: True
Local Device: No Trust Data
Overall Trust: No ID

For debugging Usage reporting timers / intervals -

Switch # show license tech support | in utility
Utility:
Start Utility Measurements: Nov 11 16:46:09 2020 EDT (7 minutes, 34 seconds remaining)
Send Utility RUM reports: Dec 07 21:42:30 2020 EDT (26 days, 5 hours, 3 minutes, 55 seconds remaining)
Process Utility RUM reports: Nov 12 15:32:51 2020 EDT (22 hours, 54 minutes, 16 seconds remaining)


For collecting all btrace logs for debugging -

Step 1. Switch # request platform software trace rotate all
Step 2.Switch # show logging process iosrp internal start last boot to-file bootflash:


If there are any failues on PULL mode, ensure server SL_HTTP is Acive

Debug CSLU

When debugging a CSLU problem, it is important that the log file from this directory be saved on the PC installed on the CSLU.

C: \ Users \ \ AppData \ Roaming \ CSLU \ var \ logs

More information

  • Migrate to SL using policies - Migrate older SL / SLR / PLR licenses to SL using policies
  • Release Notes: RN-9200, RN-9300, RN-9400, RN-9500, RN-9600
  • Configuration Instructions: Cat9200-CG, Cat9300-CG, Cat9400-CG, Cat9500-CG, Cat9600-CG
  • Command References: Cat9200-CR, Cat9300-CR, Cat9400-CR, Cat9500-CR, Cat9600-CR