Cisco Smart Licensing setup using Specific License Reservation (SLR)

[BenBautista8672]

In a Cisco Smart Licensing setup using Specific License Reservation (SLR), is it correct that an engineer cannot simply create a new Smart Account and generate SLR codes independently?

My understanding is that SLR must first be enabled by Cisco Licensing for the Smart Account that actually owns the devices, and that the routers must already appear under that account in Cisco Smart Software Manager (CSSM) before a valid SLR authorization code can be generated.

This has caused some confusion in my workplace, as someone suggested creating a new Smart Account and generating the SLR directly from the device. However, my understanding is that the original Smart Account owner must either enable SLR on that account or formally transfer the devices to the new Smart Account before SLR can be used.

Could someone please confirm the correct procedure for associating devices and request SLR authorization codes within the proper Smart Account?

[M02@rt37]

Hello @BenBautista8672 

Yes exactly. SLR must be explicitly enabled by cisco for the smart acount that owns the devices. Devices must appear in CSSM under that account before authorization codes can be generated.
-- see the Cisco Smart Licensing Using Policy deployment guide.

[Roger Kallberg · Accepted solution]

This is well described in this document, Specific License Reservation 

This part outlines the basic of how this operates.

”Specific License Reservation (SLR) allows reservation of specific licenses, including add-on licenses. Begin by requesting license reservation for your Smart Account. After you have received a response from the licensing support team, you can proceed with the next steps, as outlined below.

To reserve specific licenses for a device, generate a request code from the device. Enter the request code in Cisco SSM along with the required licenses and their quantity, and generate an authorization code. Enter the authorization code on the device to map the license to the Unique Device Identifier (UDI).”