On-Prem Licensing

CML supports Cisco On-prem licensing. This licensing method is best suited when the CML server does not have connectivity beyond your corporate network and your organization already uses On-Prem licensing for other Cisco products.

On-Prem Licensing is only supported on non-personal product offerings, such as CML-Enterprise and CML-Education.

Prerequisites:

  1. Access to your organization’s On-Prem account

  2. CML communicates to On-Prem using port 8443, make sure the port is open.

Note

Before proceeding make sure that the available CML licenses are available in the On-Prem account. If you see the licenses in the CSSM account, but not in the On-Prem account, try synchronizing your On-Prem account. If the CML licenses are still missing in your On-Prem account after synchronization, please open a case with Cisco GLO Licensing team.

Procedure (CML-Enterprise and CML-Education only)

Connect to the CML server by navigating to its assigned IP address, which is shown in the VM’s console window.

Open https://nnn.nnn.nnn.nnn in your web browser.

Log in using the initial user credentials defined during initial deployment or any application account with administrator privileges.

After successful login, the Dashboard page is shown.

Click the Tools ‣ Licensing (available only for an application account with administrator privileges) in the menu bar at the top of the Dashboard page.

The Smart Software Licensing page will open.

Click the View/Edit associated with Product Configuration in Smart Software Licensing Status section. Select Enterprise License CML-ENT-BASE Or Education Institution License CML-EDU-BASE (whichever is applicable) and click Save.

Open a new browser tab and open On-Prem licensing web page.

Open https://192.168.10.10:8443/#/mainview/ replace the IP address with your On-Prem IP address or DNS name.

Click Smart licensing ‣ Inventory ‣ General.

Click the Smart Call Home Registration URL in Product Instance Registration Tokens section and copy the URL.

https://nnn-nnn-nnnn.company.com/Transportgateway/services/DeviceRequestHandler

Note

The URL may use either the IP address or DNS name of the On-Prem Server.

Go back to CML UI ‣ Tools ‣ Licensing.

Click the View/Edit associated with Transport Settings in Smart Software Licensing Status section.

A pop-up will open and display the various options for the VM to communicate with Cisco.

Select the Transport Gateway option, paste the URL in the URL field and click Save.

Go back to On-Prem Webpage ‣ Smart Licensing ‣ Inventory ‣ General ‣ New Token.

A pop-up will open to enter the parameters for the token.

Enter a relevant description for the token, enter the max number of uses for the token and click Create Token.

The newly created token will be displayed under Inventory ‣ General tab

Click the white arrow button next to newly created token.

The token will be copied to the clipboard.

Go to CML UI Licensing page and click the blue Register button, paste the token and click Register.

The Registration Status will change to Registered. The Authorization Status will change to Authorized.

For Enterprise Licenses: if you additionally purchased CML – Expansion Node licenses along with your CML – Enterprise License click the Choose Licenses > Increase the count of CML – Expansion Node License to match the available license count in your On-Prem account.

For Education Institution Licenses: If you additionally purchased CML- Higher Education User licenses along with your CML- Higher Education Base License click the Choose Licenses > Increase the count of CML – Higher Education User License to match the available license count in your On-Prem account.

Troubleshooting

  1. Verify that CML has connectivity to On-Prem server over port 8443.

Open CML Cockpit Webpage > Terminal > Enter the below command, replace On-PremIP to the IP address or DNS name of your On-Prem server

$ nc -vz On-PremIP 8443

  1. Use http instead of https in the transport gateway URL.

  2. Use ip address of the On-Prem server instead of DNS name of the On-Prem server in the transport gateway URL and vice-versa.