Smart Licensing Using Policy

1. What is Smart Licensing Using Policy?

   The Smart Licensing Using Policy is an evolved version of the Smart Licensing.

   The Smart Licensing Using Policy simplifies the day-0 operations for customers. The product will not boot in evaluation-mode, per product software registration is not required, and ongoing communication every 30 days with the Cisco Cloud is not required. However, license use compliance does require software reporting. Reporting is and can be done:

   • From Cisco factory. when all new purchases include a Smart Account on an order

   • Smart Software Manager (SSM) On-Prem (Version XXXX)

   • Cisco Smart Licensing Utility (CSLU) lite-windows application

   • Via APIs / CLIs for any 3rd party system

   • Directly to a Smart Account

2. Which platform and software release supports Smart Licensing Using Policy?

   Smart Licensing Using Policy Release 10.2(3t) supports Cisco Nexus 3550-T platform switches. Enforced and Export licenses are not supported on Cisco Nexus 3550-T platform switches.

3. How often is reporting required?

   • Report is required within 90 days only when there is a change in software use.

   • Ongoing reporting frequency: 365 days.

   • Unenforced/Non-Export, first report is required within 90 days.

4. What are the supported topologies for connecting to Cisco Smart Software Manager (CSSM)?

   The following are the supported topologies.

   Topology 1: Connected to CSSM Through CSLU

   Topology 2: Connected Directly to CSSM

   Topology 3: Connected to CSSM Through SSM On-Prem

   Topology 4: CSLU Disconnected from CSSM

   Topology 5: No Connectivity to CSSM and No CSLU

   Topology 6: SSM On-Prem Disconnected from CSSM

5. How do customers Report software use?

   Cisco Smart Licensing Using Policy provides various reporting options using online and offline modes to report software use.

   • From the switch in off-line or direct connect mode.

   • Cisco Smart License Utility (CSLU) Lite-Windows application

   • SSM On-Prem

   • Direct to CSSM via APIs

6. Does the customer require to install a trust token?

   No, unless customer is using a direct connection to CSSM then a one-time trust exchange is established.

7. Will the Smart Account/Virtual Account migrate to Smart Licensing Using Policy by default, or does it must be requested?

   Smart Account/Virtual Account will be enabled with Smart Licensing Using Policy functionality. No migration of Smart Account is necessary.

8. Are all Virtual Accounts inside a Smart Account enabled for Smart Licensing Using Policy?

   Yes.

9. Can a Smart Licensing Using Policy-enabled SA/VA handle non-Smart Licensing Using Policy Images?

   Yes.

10. Can a non-Smart Licensing Using Policy connect to a Smart Licensing Using Policy SA/VA?

    Yes.

11. Does anything change with the existing software subscription tiers?

    No. The software subscription tier remains the same.

12. Does Release 10.2(3t) support only Smart Licensing Using Policy?

    Starting with Release 10.2(3t) devices will only support Smart Licensing Using Policy.

13. After migrating to Smart Licensing Using Policy, what’s the maximum amount of time I get before I send the first report.

    A report is required within 90 days.

14. Who determines the policy and how many policies can be applied on a single device?

    CSSM determines the policy that is applied to a product. Only one policy is in use at a given point in time.

15. Is the Policy a hard requirement?

    The policy is a requirement from Cisco. It is a soft requirement on device and not an enforcement.

16. What is Cisco Smart Licensing Utility (CSLU)?

    Cisco Smart Licensing Utility (CSLU) is a Windows application that is used to automate receiving or pulling software use reports from a Cisco product and report the software use to a Smart Account on Cisco Smart Software Manager (CSSM).

17. What are the minimum Windows system requirements to install CSLU?

    Component	Minimum	Recommended
    Hard disk	100 GB	200 GB
    RAM	8 GB	8 GB
    CPU	x86 Dual Core	x86 Quad Core
    Ethernet NIC	1	1

18. What are the key features of CSLU?

    • Collect license usage reports from the product instances in either a push or pull modes.

    • Store and forward usage reports to CSSM for billing and analytics.

    • Obtain and distribute policy and authorization codes from CSSM.

    • It can be deployed as standalone micro service:

      • Windows host (up to 10,000 Product Instances (PI))

    • It can also be integrated as software component with controller-based products.

    • Regardless how the micro service is deployed, it is able to deliver an on-line or off-line connectivity model for the license data.

19. What is the report format in CSLU?

    The CSLU report format is based on ISO 19770-4 standard RUM report format. It is delivered in JSON format and is signed per trust model.

20. What are the various tools to collect software use report?

    Customers can use various sets of APIs that are available on NX-OS.

21. Which data does Cisco care about?

    Below are the required data fields for software reconciliation for each Cisco product that supports Smart Licensing Using Policy.

    UDI	HardwareProduct serial number
    SN	Software Unique ID Serial Number
    Software Package and Reg ID	Software product package and entitlement tag
    Count	Software use count per license entitlement
    Time and date stamp	Per license entitlement change and use

    Below are optional data fields for software reconciliation for each Cisco product that support Smart Licensing Using Policy.

    SA-VA Level 1	example, Entity (map to a SA)
    SA-VA Level 2	example, GEO (map to a SA)
    SA-VA Level 3	example, department (map to a SA)
    SA-VA Level 4	example, building (map to a SA)
    SA-VA Level 5	example, room (map to a SA)
    Free form	Data does not go back to Cisco
    Free form	Data does not go back to Cisco

    (SA = Smart Account, VA = Virtual Account)

22. How does Smart Licensing Using Policy work with device replacement (RMA)?

    This can be realized through Cisco TAC.

23. What are Licenses Enforcement types?

    The enforcement type indicates if the license requires authorization before use. Following are the two types of license enforcement.

    • Unenforced - Unenforced licenses do not require authorization before use in connected networks. The terms of use for such licenses are as per the End User License Agreement (EULA)

    • Enforced - Licenses that belong to this enforcement type require authorization before use. The required authorization is in the form of an authorization code, which must be installed in the corresponding product instance.

    Note	Only unenforced licenses are supported in Release 10.2(3t).