get-organization-licenses state field value description

[Manish2]

Hi Team,

 I am looking for any documentation on possible values of state and their descriptions

https://developer.cisco.com/meraki/api-v1/#!get-organization-licenses 

{baseUrl}}/organizations/:organizationId/licenses

{ "id": "1234", "licenseType": "MX64-ENT", "licenseKey": "Z21234567890", "orderNumber": "4C1234567", "deviceSerial": "Q234-ABCD-5678", "networkId": "N_24329156", "state": "active", "seatCount": null, ...}

state :

'active',   --- description ???

'expired',--- description ???

'expiring',--- description ???

'unused',--- description ???

'unusedActive'--- description ???

or 'recentlyQueued'--- description ???

Regards

Manish Kumar

[RomanMD]

This is my guess, because I don't use PDL licensing:

"claimDate": "2019-08-29T12:40:10Z",

"activationDate": "2019-09-01T15:01:46Z",

"expirationDate": "2020-10-30T15:01:46Z"

state :

'active',   --- description ??? -> the license is assigned to a device. This is expected state of the license in the org.

'expired',--- description ??? -> the license is expired. expirationDate is in the past.

'expiring',--- description ??? -> the license expirationDate is less than 30 days from now.

'unused',--- description ??? -> License was claimed in the Organization but was not assigned to any device. 90 days have not passed yet, so activationDate has not yet started.

'unusedActive'--- description ??? -> License is not assigned to any device but activationDate is in the past.

or 'recentlyQueued'--- description ??? -> can't imagine what this could be.

[Inderdeep]

RecentlyQueued - A license that is being assigned to a device that already has an existing license. It will take 7 days for the license to merge. The license will not be queued if the device did not previously have a license.

Hope it clears @Manish2 @RomanMD 

Regards
Inderdeep Singh

[Manish2]

Thanks Roman and Inderdeep.

I also found a documentation at 

https://documentation.meraki.com/General_Administration/Licensing/Meraki_Per-Device_Licensing_Overvi...

Let me try and map the api response to the ones from the documentation, please validate if this looks correct.

1.'active',   --- the license is assigned to a device. This is expected state of the license in the org.

Burn/Active - The license has started to tick and time remaining starts to decrement.

Active & Associated - A license has been associated to a device and is burning. A license in this state can only be reassigned to a device that is either unlicensed or a device that has an expired license. An active & associated device cannot be used to extend time on a device with an active license. 

2.'expired',----> the license is expired. expirationDate is in the past.

3.'expiring',----> the license expirationDate is less than 30 days from now.

4.'unused',----> License was claimed in the Organization but was not assigned to any device. 90 days have not passed yet, so activationDate has not yet started.

Inactive & Unassociated - A license is not associated to a device and has not started to burn. The license is within the defined pre-activation period.

5.'unusedActive'----> License is not assigned to any device but activationDate is in the past.

Active & Unassociated/Unused active - A license has not been associated to a device, but has started to burn. This typically happens when the pre-activation period is over, but the license has yet to be associated to a device. In this state, the license can only be applied to a device that does not have an active license (e.g. a new device).

Burn/Active - The license has started to tick and time remaining starts to decrement.

6.'recentlyQueued'----> can't imagine what this could be.

Queued - A license that is being assigned to a device that already has an existing license. It will take 7 days for the license to merge. The license will not be queued if the device did not previously have a license.

7. ??? API state? : Dont know if this is returned by the api ???

Inactive & Associated - A license is assigned to a device, but it has not started to burn. This typically happens in the case where a customer adds an additional license to a device that already has an active license (renewal). This license will become active when the first device’s time expires.

NOTE: This state can only happen with a license that has not already been active (started to burn).

Thanks

[Inderdeep]

@Manish2 Sure buddy hope you got what you were looking for 😊