Cisco Smart Software Manager On-Prem (CSSM)

Cisco Smart Software Manager On-Prem (CSSM)

Cisco Smart Licensing includes the Smart Software Manager On-Premise (Cisco SSM On-Premise) license server. It collaborates with Cisco Smart Software Manager to intelligently manage client product licenses, enabling near-real-time visibility and reporting on Cisco licenses purchased and consumed by customers.

CSSM through an On-Prem SSM (satellite)
Fig 1.1- Cisco Smart Software Manager On-Prem (CSSM)

What is Smart Licensing?

Cisco Smart Licensing is a flexible licensing architecture that makes purchasing and managing software across the Cisco portfolio and throughout your organization easier, quicker, and more consistent. It's also safe since you control who has access to what.

Simple Activation: Smart Licensing creates a pool of software licenses that can be utilized throughout the whole organization, eliminating the need for PAKs (Product Activation Keys). 

Unified Management: My Cisco Entitlements (MCE) gives a comprehensive picture of all of your Cisco products and services in a simple platform, ensuring that you always know what you have and what you are using. 

Flexibility of licenses: Because your software is not node-locked to your hardware, you can easily utilize and transfer licenses as needed. 

Advantages of Cisco Smart Software Licensing

  • Visibility of bought and deployed devices and software
  • Real-time monitoring and management of devices, licenses, and use
  • Automatic activation of licences
  • Standard software offerings, licensing platform, and policies simplify the product.
  • Reduced operational expenses

The Cisco Smart Software Manager On-Prem

The Cisco Smart Software Manager On-Prem (Cisco SSM On-Prem) license server is intended to replicate the license workspace experience of Cisco Smart Software Manager by using a shared user interface and similar functionalities. It is intended for service providers and Cisco partners that require the management of many client accounts through a single management interface rather than individual consumers maintaining their own accounts.

To function correctly, the Cisco SSM On-Premise license server must connect with Cisco Smart Software Manager on a regular basis. To ensure that the most current purchases are reflected in their local copy, customers must synchronize their local license usage with the Cisco site. This can be done automatically or manually. 

The synchronizations may be planned on a daily, weekly, or monthly basis; depending on the frequency, the data on the Cisco SSM On-Premise license server can be made as current as the portal on a daily basis. Manual synchronization necessitates a file transfer at least once a year, creating a chasm for high-security service providers and partners.

After installing the Cisco SSM On-Prem license server, the system must be setup in order to access its user interface. Furthermore, the Cisco SSM On-Premises license server must register with Cisco Smart Software Manager in order to link its local account, which represents a client, with a Cisco Smart Manager Virtual Account and manage licenses in it.

 Once registered, Cisco hardware or software items self-report license usage to the Cisco SSM On-Prem license server as if it were a clone of the Cisco Smart Software Manager. Synchronizations with Cisco Smart Software Manager on a regular basis allow the Cisco SSM On-Premise license server to reflect the most current license entitlement and use.

Cisco SSM On-Prem features

  • Each Cisco SSM On-Premise license server has the capacity to scale up to 300,000 product instances (25,000 per local account). Multiple Cisco SSM On-Prem license servers can connect to Cisco Smart Software Manager utilizing multiple Cisco Virtual Accounts if installations exceed 300,000 product instances.
  • Manage user access through two privileged system roles (system administrator and system operator) as well as nonprivileged roles (system users) utilizing targeted license roles (RBAC).
  • The authentication mechanism can be adjusted by a system administrator to LDAP, Active Directory (AD), or ADFS. If no authentication is supplied, it will utilize local authentication.
  • Users are grouped so that procedures like role assignment may be done to a group of users rather than individual users.
  • LDAP users are grouped so that activities like role assignment may be performed on many LDAP users in the group.