INTERNAL: Licensing FAQ

Meraki MX/Z Security and SD-WAN Licensing FAQs

Things to consider while selling/ renewing the SDW license: 

• Selling SDW: 

  • If a customer is buying both MI + SDW (MI for Z3/c series), please make sure to:

    • Separate the order to different keys (MI + Z series in one, SDW licenses in the other).

    • Apply the MI license prior to the SDW license (This is due to a bug - Dashboard does not allow MI licenses to be added on top of SDW).

      • A mule has been opened and will be resolved,

  • Z series will currently get automatically upgraded with MI licenses. This is a bug and it will be fixed soon.

  • Z3/C devices currently allow smart VPN exclusions.  This is a bug and it will be fixed soon.

• Trialing SDW:

  • PDL vs Co-Term:

    • No special considerations, create the trial as usual.

  • How can I trial the SD-WAN Plus license if I have MI 

    • If no MI licenses prior to upgrade- no worries there.

    • If MI licenses exist in the org prior to trial- 

      • Once the trial starts the MI license will be removed from the org.

      • Upon trial termination, the MI licenses will automatically be re-assigned to the org.

  • How can I trial the SD-WAN Plus license if I have Z1/Z3 in the organization?

    • As usual, no specific considerations when it comes to Z3 in the organization.

• Upgrading to SDW:

  • PDL:

    • There is a bug effectively assigning the SDW functionality to all MX devices in the org (vs just licensed devices).

    • Please assign the new SKU for each network so customers have the correct licensing structure to meet capabilities, as the customer would do in all PDL situations.
       

  • Co-term

    • Option 1: Add a single SKU to flip org-

      • Please do not use this method as it gives customers ‘free’ days in co-term and ‘free’ functionality in PDL that lead to loss of revenue.
        We are working on fixing this behaviour, but until we do, please use option 2. 

• Option 2: Support to convert and Calculate remaining days: 

  • This is the proper way to upgrade orgs to SDW+, and the co-term is calculated correctly.

  • To calculate (estimated) term reduction please use the following sheet: https://docs.google.com/spreadsheets/d/183-MX1MOTHhtjWVxqkOUAJU908XOAYCRfQYbSwoWC-U/edit#gid=0

    • Note that non-MX devices also affect co-term date and so exact term date calculation is out of scope at this point.

• SDW During Renewals:

  • If Z and EoL devices exist in the org, please do the following: 

    • Create two orders: The first will have anything that can be SDW, the second would have Z and EoL devices.

      • For the second order, (Z, EoS) order the highest applicable license 

    • ​​Open a case on the Support home page before renewing the license- they will alter the SDW order to add the SEC renewals to it so that the customer can successfully claim it

• SDW Configuration Considerations:

  • If EoL devices exist in the network and templates are in use- two templates are needed: One for SDW supporting devices, one for non-supporting devices.

Managing License Reminder Emails: Configuration

License Reminder emails are sent to Dashboard administrators per the configuration on the Administration -> Manage alerts section on the Organization -> Settings page.

However, recipients can still opt out of receiving these emails on a per-organization basis, despite the configuration on the Organization -> Settings page, via the link at the bottom of the reminder emails:
If you wish to no longer receive license warning emails for this network, click here.

Once they have opted out, they will no longer receive License reminder emails for that org.
Users can opt back in to receiving the emails via their My profile page (found on the Menu at the top of Dashboard).

Policy Update on PDL Conversions and Licensing Options

In general, PDL conversions will no longer be accepted or approved. We recommend customers explore alternative licensing options, such as co-term or subscription licensing.
Conversions to PDL require special approval from Licensing PM. Support Ops will not honor requests for conversion that do not contain PM approval.

Notification Policy for Per-Device Licensing Model and Support Operations Assistance

Due to complications with the per-device licensing model, organizations following this model are not being strictly enforced. Devices that fall out of compliance are not being shut down. For this reason, notification emails are not being sent to administrators. For assistance with such questions, please refer customers to Support Operations by Assigning Cases to Support Ops.

Licensing and Feature Availability for Meraki Insight and Secure SD-WAN Plus

OLD:Will new features under Meraki Insight be restricted to the Secure SD-WAN Plus license only?
No. Any new features that released as a part of MI will also be available under separate MI licenses.

If I have the Advanced Security license + MI or Enterprise + MI, do I essentially have the new Secure SD-WAN functionality?
No, you will miss out on the new features (present and future) coming under the SD-WAN Plus license. However, you will have more flexibility in being able to move the MI license around between devices.

How to do a License Transfer in Cotermination FAQs

Will the customer license moves show up in the changelog?
Yes, in the source org.

Can SAML users move license keys?
Yes, this is stated in the public documentation.

Is there an example org where the move was done so we can look at it?
Please refer to the demo video that was included in the announcement to Support from the L&D team. 

What should we do if a customer says the tool doesn't work for them?
Confirm that the move should have worked (not expected behavior). If YES, submit a Mule.

Which customers can we potentially offer license generation for (with Licensing PM's approval)?
Anybody whose organization is negatively impacted, regardless of support score.

Is there anything in place to stop people from gaming the system?
Yes, PM has a script to track customers who are likely culprits of gaming the system to confront, nothing Support has to worry about. 

How are we planning on fixing negatively impacted organizations (once we receive approval from Licensing PM)?
Follow the below process after getting approval from the Licensing PM team:  
1. Use the custom query to identify the organization expiration date before the license move: https://n1.meraki.com/manage/queries...dit_mode=false. Fill the Org_id and Run it only on the shard Id where the org is hosted. For e.g. Org id = 74904; Shard id: n24(can be seen in the URL) for the org: https://n24.meraki.com/o/vahwMc/mana.../license_info# 
2. Generate the count of licenses pre-move that can be found on the license history page( this is an internal-only page, please don't share with the customers). Open the License_info page of the org and modify the URL to https:**this will remain same**/manage/dashboard/license_history 
3. Invalidate the key from the destination org and generate the key that aligns with the count calculated from step#2 and the license term to be close to the expiration pre-move calculated in step#1. 

Who should SOPS reach out to regarding questions about the tool or one-off situations?
SOPS Managers. Only reach out to Licensing PMs regarding permissions to help negatively impacted organizations. 

How were the customers chosen for the beta testing?
It was based on customers who were requesting license transfers often.

Will customers also be able to move (unclaim to reclaim) trial licensing?
No.

What SFDC case component should be assigned to cases opened about this tool?
"License move".