Kiến thức

# Meraki Co-Termination Licensing Overview

All current Cisco Meraki products require valid licensing to operate. This article describes how Cisco Meraki Co-Termination licensing operates and applies to an Organization. All licensing related operations can be performed from the Organization > Configure > License Info page.

## Co-Termination

The Cisco Meraki Co-Termination licensing model works on the basis of Co-termination. This means that for any given Organization, regardless of how many licenses were applied or when they were applied, the license expiration date for all licenses claimed to that Organization will be exactly the same. This is accomplished by averaging all active licenses together and dividing by the License Limit count of devices in the Organization.

For example, suppose an Organization had 2 separate Enterprise AP licenses, one license for 2x APs spanning 1-year (365 days) and another for 1x AP spanning 5-years (1825 days). The Co-termination value would be calculated as ((1825*1)+(365*2))/3= 851 days total for all 3 APs. So assuming all 3 licenses were applied on the same day, the Organization would have a Co-term date of 851 days from the start date of the licenses.

If the licenses were not applied at the same time, for example if the 5 year license was applied half-way through the 1 year license, the Co-term calculation will take that into affect. In this case the calculation would be ((1825*1)+(182*2))/3=730 days total for all 3 APs.

Note: The Organization Co-termination date does not depend on the current device count, but rather the license limit. Removing devices from a Network or Organization will not impact the Co-termination date.

To calculate how licenses impact each other in an Organization, check out the

. To see a more detailed explanation and the exact calculations that are used to determine Co-term dates, please refer to our detailed

Co-term Explanation

page.

Licenses in the co-termination model start consuming time from the date purchased, not the date they are added to an Organization.

Note: Waiting to activate a license in Dashboard does not delay its activation date. There is no time benefit gained from delaying an activation.

## Device types

Licenses are sold based on the specific model of device, so for example an MS220-24 will require a separate license from an MS220-8. This applies even to PoE vs non-PoE versions of devices and Wireless vs non-Wireless versions for MX devices. For example, an MS220-8 will require a different license than an MS220-8P, and an MX64 license will not work for an MX64W.

## Organization-wide Licensing

Cisco Meraki licensing is applied on an Organization-wide basis. This means that a license isn’t purchased for a specific serial number or device, rather each license added to the Organization increases the number of a specific device type (the License Limit) that can be added to Networks within the Organization.

## The 30 day Grace Period

The number of devices in an Organization can not exceed the License Limits, if this occurs the Organization will enter a 30 day Grace Period during which the Organization must be brought back in compliance. Should the Organization not be brought back into Compliance it will be

shut down until proper licensing is applied to the Organization

Note: During the Grace Period network clients will notice no difference.

Should an Organization enter the 30 day Grace Period because of exceeding device License Limits it can be brought back into compliance either by removing devices from Networks within the Organization or through purchasing additional licensing. The only other time an Organization will enter this 30 day Grace Period would be if it’s licensing has expired by passing the Co-term date. If this occurs the only way to bring it back into licensing compliance is through the purchase of additional licensing.

article.

## License Limit and Current Device Count

The image below shows an example License Limit and Current Device Count table for an Organization. Notice how each hardware model has it’s own individual License Limit and Current Device Count. Each column is explained in more detail below.

The License Limit is defined by the sum of the device count for all currently active licenses applied to an Organization. Licenses that have been Invalidated or were applied prior to the most recent Renewal operation will not be counted when calculating the License Limit. For example, if an Organization has three active licenses, one license for 1x MX65, one license for 2x MR devices, and one license for 1x MS220-8P and 1x MR device, the total License Limit for that Organization would be 1x MX65, 1x MS220-8P, and 3x MR devices.

### Current Device Count

The Current Device Count column lists the total number of each type of device that is currently added to any network inside the Organization. Devices that are claimed to the Organization Inventory but not added to any Networks will not count towards the Current Device Count. For example, if one network has 1x MX65 and 2x MR33, and a second network has 1x MS220-8P and 1x MR52, the Current Device Count for that Organization would be 1x MX65, 1x MS220-8P, and 3x APs.

Note: All MR and MV series devices are grouped under the same respective licensing group. So an MR18 will require the same license as an MR72 and both will count equally toward the total device count of MR devices.

The Current Device Count does not impact the Co-Term date of an Organization, the Co-term date is instead calculated based on the License Limit of the Organization. Because of this, adding or removing devices from networks will not affect the Co-term date of the Organization except in situations where adding a device will put the Organization outside of its License Limit and invoke the 30 day Grace Period. In this situation, either removing the device(s) from the Network(s) or adding the required licensing prior to the end of the 30 day Grace Period will put the Organization back into compliance. If new licensing is added, the Co-term date will be updated to reflect this change. If no new licensing is added then the Co-term date should remain unchanged.

## Licensing Options

### MR Licensing Options

The MR Access Points only have one license type, a general “wireless AP” license. This license can apply to any Meraki access point, so long as there is one license for every AP in the account. For example, a network containing 2x MR18s and 1xMR32 will require licensing for 3x APs.

### MS Licensing Options

Classic MS Switches have licenses on a per-model basis, so every MS model has a corresponding license. Please note that these licenses are non-transferrable between switch models. For example, an MS220-48 switch will not be covered by an MS320-48 license; it will require an MS220-48 license.

#### MS390 Licensing Options

MS390 license structure includes two feature tiers:  Enterprise and Advanced. The MS390 also introduces a new and simpler license to hardware mapping, specifically 24-port or 48-port licenses. As with all MS, every MS390 license is available in 1, 3, 5, 7, and 10 year terms.

 MS390 License Structure 24-Port Model 48-port Model Advanced Features LIC-MS390-24A LIC-MS390-48A Enterprise Features LIC-MS390-24E LIC-MS390-48E

The features available with advanced licensing are:

• Greater than 1,000 routes for OSPF

* Available in a future software release

In the Co-term licensing model (most existing Organizations), an Organization must either have all MS390 Enterprise or all MS390 Advanced licenses – they cannot be mixed. In the Per-device licensing model, a mix of Enterprise and Advanced can be added to a single Organization, but certain features may require all devices in a Network to have Advanced licenses, e.g. Adaptive Policy.

Meraki Licensing Models article

.

### MX Licensing Options

The MX Security Appliances have licenses on a per-model basis, so every MX model has a corresponding license. Please note that these licenses are non-transferrable between appliance models. For example, an MX64 will not be covered by an MX84 license; it will require an MX64 license.

The MX Security Appliance has multiple license editions: Enterprise, Advanced Security, and Secure SD-WAN Plus. Please note that the MX licensing edition is uniform across the Organization. For example, you can have all 25 appliances using Enterprise Edition or Advanced Security Edition or Secure SD-WAN Plus Edition, but you cannot have 20 appliances using one edition and 5 using the other edition. If you wish to use Enterprise Edition for some appliances and Advanced Security Edition for other appliances, you need to create two Organizations, one for your appliances with the Enterprise Edition, and another for the appliances with the Advanced Security Edition. Similar concept appliance for Secure SD-WAN Plus Edition as well.

Note: Advanced Security and Secure SD-WAN Plus licensing and features are currently only available on MX devices, not on Z-Series devices, or any other Meraki series of devices.

Note: For Advanced Security features available in China mainland, please refer to the following article for the detail.

MX Security and SD-WAN Licensing

article.

### SM Licensing Options

Meraki Systems Manager has only one license type, which is used for all managed clients in SM, regardless of operating system type. Licenses need to be available for devices to enroll into your network.

Systems Manager Licensing

.

From the Organization > Configure > License Info page, the ‘Add another license‘ link allows Organization Administrators to add additional licensing to their Organization. This can be done to either increase the total number of devices licensed to the Organization or to renew the existing licensing for all devices in the Organization. Adding additional licensing to an Organization is a simple 5 step process, outlined below.

3. Enter the 12 digit license key you would like to claim

Note: Claiming a new license with the claim type of ‘License more devices‘ will simply add the new license count to the existing License Limit of the Organization and alter the Co-term date appropriately.

Warning: Claiming a new license with the claim type of ‘Renew my Dashboard license‘ will invalidate any previous License Limit counts and force the Organization License Limit to match only licenses applied during or after the most recent Renewal action, in addition to altering the Co-term date for the Organization.

When a license key is applied using the ‘Renew my Dashboard license‘ operation the Organization’s licensing state updates to exactly match the device count of that license key, and any remaining time from previous licenses is kept and added to the new Co-term date. For example, if an Organization with licensing for 5x APs were to have a 2x AP, 3 year license applied as a renewal, that Organization would only be licensed for 2x APs for 3 years plus the remaining time from prior to the renewal. In this instance, the Organization would be 3x APs over the license limit, and therefore out-of-compliance.

Note: The recommended practice for applying a Renewal is to purchase a single license key that covers all devices currently in the Organization for X number of years. Applying that license key as a Renewal will then extend the Organization’s Co-term date by that many years while keeping the same License Limit for devices.

Even if the Organization is still compliance, (Co-term date has not passed and the Organization has not yet expired or been shut down,) the Renewal license should still be applied immediately because the time on the license starts counting down from the date purchased.

Warning: Holding onto a license does not delay its activation date. There is no time benefit gained from delaying a Renewal.

A Co-term license can be requested to be moved between organizations. Only organization administrators have the permissions to request licenses moves and are required to have access to both organizations.

Moving Co-term licenses can only be done by

Meraki Support

NOTE: Co-term licenses cannot be moved to Per-device licensing (PDL) organizations.

The following list reflects all supported license model conversions by Meraki Support in a Co-Term Org. These License Conversions are not supported in a Per-Device Licensing Org. If you have received a different model device as the result of a device-RMA, we can update the license to reflect that change. Licenses can also be converted if the request is a valid conversion from the list below and the license key is outside the 30-day License-RMA Window.

These are the supported conversions:

• MX80 → MX84

• MX84 → MX80

• MX60/W → MX64/W (MX65 conversions NOT allowed)

• MX64/W → MX60/W
• MX65W/64W/60W → MX65/64/60
• MX65/64/60 → MX65W/64W/60W (MX65 to MX65W, MX64 to MX64W and MX60 to MX60W are only allowed)
• MX64/W → MX67/W
• MX65/W → MX68/W
• Z1 → Z3

NOTE: Keys that fall within the 30-day RMA window MUST be RMA’d and re-purchased. There is no exception to this.

License RMA’s can be submitted at meraki.com/rma in an incognito/private browser window.

## Removing and Undoing License Claims

There are a number of licensing issues that are caused by misapplication of a single license key. If a license has been applied incorrectly, the undo license claim tool can be used to remove the license so it can be re-added correctly.

### Use Cases

There are two common situations where a license application can cause problems on an organization:

• License was applied to the wrong organization.
A license may have accidentally been applied to the incorrect organization. The undo license claim tool will release the license so it can be applied to the correct organization.
When a license key is applied to an organization, there are two options for the license type: Renewal or add devices. Applying a license as the incorrect type will have an undesired effect on the organization’s licensing, and will likely take the organization out of compliance. The undo license claim tool can be used to remove the license, so it can be reapplied correctly.

Licensing Guidelines and Limitations

.

### Using the Undo License Tool

1. Make sure you are a full organization administrator on both organizations. If not, this process will need to be followed by another admin.
2. Contact

Meraki Support via phone

or email

licensing@meraki.com

with the following information:

• Your

support passcodes

for both the source and destination organizations.

• The URL for both organizations License Info pages.
• The license key to be transferred and the device models and the number of devices that need to be moved to the new organization.

The following steps explain how to undo a license application:

1. In Dashboard, navigate to Organization > Configure > License info.
2. Click the undo button next to the license in question:
3. Review the confirmation window that pops up. If you are sure this is the correct license to remove, click Yes:

Upon confirming the change and closing the pop-up, the organization will be reverted to the previous licensing state. The original license will be invalidated, so a replacement key will be generated. The new license key can then be re-applied or added to another organization for the remaining license term. The new license key can also be found under Organization > Change log.

## Out-of-Licensing Compliance Warnings and Solutions

Cisco Meraki devices use the Cisco Meraki cloud for centralized management and control. The Cisco Meraki cloud is licensed on a “per device, per year” basis. Each organization is licensed for a certain number of devices through a termination date. When out of compliance, due to expiration of licenses or insufficient device counts, you will be notified by e-mail.

This e-mail will begin with “Thank you for being a valued Cisco Meraki customer. Our records show that your organization is over the device limit for your Cisco Meraki Cloud license.”

Dashboard

and go to Organization > License info. This page will include information about your licensing status, MX Advanced Security features (if applicable), license expiration date, and details of your current and licensed device counts. Points where you are out of compliance will be indicated in red. To return your organization to a compliant status, you will need to purchase the appropriate licensing.

Licensing FAQ

.

To purchase licensing, contact your Cisco Meraki account executive, or visit

Sales Contacts

.

### Out of Compliance Examples

#### Over Device Limit

In this case, the organization has one additional MX65W device in a network than they are licensed for, and would need to purchase the necessary license in order to achieve compliance.

Since devices that are not in a network do not count towards the device count, the MX65W can be

removed from its network

and left in the

organization inventory

#### Licensing Expired

In this case, licensing for the organization expired on May 11th. The licenses would need to be renewed, or new licenses purchased in order to return to a compliant state.

#### Licensing Expired & Network Shutdown

In this case, licensing for the organization expired and the organization has been shutdown. This will not occur until after the 30 day grace period, and may also occur if the organization has been in excess of the licensed device count.

### Compliant Licensing

In this case, the organization has more device licenses than they have devices and their licensing will expire in 899 days.

in Dashboard to understand how specific licenses will co-terminate.

For more detailed information about how Co-termination is calculated, see the

Co-termination details

article.

.