On-Prem synchronizes with your Smart Account at a Virtual Account level, and a Local Account must exist or be created on SSM On-Prem, which maps to the Virtual Account in your Smart Account. Therefore, this document explains the process to set up a new Local Account in SSM On-Prem.
Video
The purpose of this content is to share information for educational and/or informational use. You may choose to watch the video or read the content below-both provide the same material, so feel free to engage with whichever format you prefer.
Prerequisites
Before you start, ensure that you have the following:
Active Cisco.com account
Access to SSM On-Prem
A Virtual Account (with no products currently registered to it)
The user accessing License Central must have at least one of the following:
Smart Account Admin
Virtual Account Admin
Steps
Step 1: Open SSM On-Prem Administration Workspace (https://(IP Address):8443/admin/#/mainview).
Note: Where the IP address is the value used during the installation of CSSM On-Prem. If IP-Address is part of an HA cluster, this will be the virtual IP address.
Step 2: Open the Accounts Widget
Step 3: Click on New Account
Step 4: Enter the required information: Local Account Name, Cisco Smart Account, Cisco Virtual Account, and Email for notification. The required fields are labelled with “*“.
Note:
The Cisco Smart Account must exist on Cisco License Central. A Cisco Virtual Account will be created if it does not exist on Cisco License Central. Each Local Account must be associated with a unique Cisco Virtual account. The Cisco Virtual Account must not have a product or another Local Account registered to it.
Smart Account/Virtual Account in the account creation tab should match with Cisco License Central Smart Account/Virtual Account name.
Step 5: Click Submit. (The Account request then is listed on the Account Requests tab in the Accounts Widget, waiting for the System Administrator to approve and register.)
Note:
Users having access to Cisco License Central SA can approve the request.
Once a new Local Account has been requested, the Local Account request will show up in the Administration workspace in the Accounts Widget Account Requests Tab, waiting for the System Administrator to approve and register the Local Account to your Cisco Smart Account
Step 6: Registration could be done in two ways: Manual On-Prem Account Registration or Network registration.
Manual On-Prem Account Registration
Step 6A: In the Administration workspace, for the account requesting approval in the Account Requests tab of the Accounts widget, use the Actions drop-down to click Manual Registratio.
Step 6B: Click Generate Registration File to generate and save the file to your local file directory. Click outside the dialog box or press the Esc key to dismiss the dialog.
Note: After this step, you are required to open a new tab in the browser and log in to Cisco License Central to authorize the registration file.
Internal users should submit a case to the Licensing support team to fix the customer view issue with orders in License Central. There are no checks for internal users with a Cisco support role to prevent unauthorized transactions from the Orders tab.
Troubleshooting
If you experience an issue during the process explained in this document, open a case in Support Case Manager (SCM).
For feedback on the content of this document, please submit here.
For External Customer / Partner Use Only: These instructions are provided to help customers / partners perform the following action themselves to resolve the issue. If the customer / partner runs into issues following the instructions, please have them open a case with licensing support (https://www.cisco.com/go/scm) to help resolve
Revision History
Revision
Publish Date
Comments
1.0
October 28, 2025
Initial Release
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.