License Renewal - Cotermination Model

SVR
New here

License Renewal - Cotermination Model

Hi

We have a oraganztion with 140 devices including switches, Access apoints. The license is in a Cotermination model and by 2025 Oct 3, it will be expired. Client would like to renew the license upto maximum 2029 ( Oct 3) only.

 

My question is here that using Cotermination model can I renew the license for around 80 devices for 5 years and get the license of the organisation extended up to 4 years which is Oct 3, 2029.

 

6 Replies 6
cmr
Kind of a big deal
Kind of a big deal

With co termination renewals you have to renew everything that you want to keep working.  Any devices not renewed will stop working.  If the client only wants 4 years then buy a five year license as more than one year is free (compared to the one year licenses), or buy 3 now and another 1 later on.

If my answer solves your problem please click Accept as Solution so others can benefit from it.
cmr
Kind of a big deal
Kind of a big deal

If you change to subscription licensing you can have a more flexible renewal date.

Meraki Subscription Licensing Overview - Cisco Meraki Documentation

 

From the link above:

 

Flexible Terms

Customers can choose their licensing terms from 12 months up to 120 months, including customer determined start and end dates. This allows them to align their licensing needs with their network growth and planning strategies. 

If my answer solves your problem please click Accept as Solution so others can benefit from it.
SVR
New here

Hi

If we purchase renewal license for only 80 access points for 5 years, how it will be reflected in the organisation dashboard, what would be the status of other non renewed devices.

 

As per my understanding with Cotermination the entire organisation has single subscription end date.

 

cmr
Kind of a big deal
Kind of a big deal

You would only be licensed for 80 APs and all the other devices would become unlicensed and stop working.  The end date would be existing + 5 years.  It's not the same as adding a device where a single AP with 5 years would just add a few days across everything else.

If my answer solves your problem please click Accept as Solution so others can benefit from it.
GreenMan
Meraki Employee
Meraki Employee

cmr is right;   you can't trade quantity of devices for time, nor vice versa.

If you want 4 years, you could create two orders - one for 3 years and one for 1 year, but both would need to be for the full 140 APs - if you have 140 working APs.   You would then use both keys, one after the other, using the 'Renew my Dashboard license' operation.   This would leave you with 140 APs licensed and stack the 1 year and the 3 year on top of each other, to make the co-termination date 4 years in the future.

This assumes that you only have Meraki access points in that Organization (?)

 

https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_-_License_More_De...)

GreenMan
Meraki Employee
Meraki Employee

Actually - referring back now to your first point; your Organization does include more Meraki gear (you mentioned switches as well as APs, which I'd missed).   Any time you apply a renewal, the key needs to include licensing for all the devices you need to keep working.   So in my example above, you could still do two separate orders, 3 years and 1 year, but both of those orders would also need to also include the switches and all the APs (and any other Meraki devices you want to keep working).

In co-termination, everything is encompassed by one date - you can't part-renew.

 

Remember too that an Organization is either compliant or not.   If it's non-compliant, it will enter a 30 day grace period (where admins get lots of warnings to fix it).   If you let that expire, without fixing, ALL the devices will stop carrying traffic.   This is clearly not what anyone wants.   Maybe look to catch up with your Meraki account team to go through the detail?    As mentioned briefly above, a shift to Subscription licensing might be a good option.

Get notified when there are additional replies to this discussion.