Skip to main content
Cisco Meraki Documentation

MT Template Best Practices

Overview

MT sensors do not have any configuration other than Alert Profiles. However, since MT devices rely on either MV or MR for connectivity, there’s limited support for templates when using MR as a gateway. This article will walk you through options to add sensor support to a template configuration.

Note: MVs do not support templates, so this article mainly focuses on having sensor support with MRs in template-bound networks.

Appending MT Networks to Existing Templates

Existing templates will not have an environmental section, nor is there an option to add it. It is strongly recommended to create new templates when adding new product lines because newly created templates will have the environmental section included. The most common scenario is when you need to add a sensor to a network that is currently bound to a template. 

If your existing templates do not have the environmental product available, this walk-through will guide you on adding the environmental product to an existing template in your organization.

clipboard_e24273d9a6d05dac6e61148112e44b72b.png clipboard_e2c0c43b84307ed6dd9472900665cf379.png
This "Old Combined Template" lacks environmental options. Newly created templates have environmental settings available.

This process involves splitting a newly created template and combining the environmental (MT) portion with your existing template. Your existing template will not be split, so it will have an environmental option. 

Warning: The appending process of existing templates is recommended to be done during a maintenance window as it could affect configurations of your existing networks bound to the template. 

  1. Go to Organization > Monitor > Configuration Templates and view the list of existing templates in your organization.

  2. Create a new template that will be used to split the environmental (MT) portion and save your changes.

Split_this.png

  1. Select the new template, click on Split, then OK to confirm. This will create templates of specific network types.

clipboard_ecbc65a04082575d8e75b2b3d52d209db.png

  1. Select the environmental template that was split from the previous step and select the existing template you wish to combine it with.

    • In this example, Split this new Template - environmental and Old Combined Template are selected to be combined.

clipboard_e5fbed0ea109d27ab4dc1817f6e54c46f.png

  1. Select Combine and fill in the new network name of the template.

    • In this example, the "Template Network" name remains “Old Combined Template.”

clipboard_e8d8171cf1130d405aab683dcb488b5b5.png

  1. Once the template networks are combined, the environmental configuration should be available in the Old Combined Template. Your existing settings from the old template should remain.

clipboard_e616daaa787422e7e21a2f7be24184c7d.png

  1. (Optional) Clean up the empty template networks that were split.

    1. Under Organization > Monitor > Configuration Templates select the templates that you wish to delete.

    2. Click on Delete at the top and confirm on the following section.

      clipboard_eceadb427d1ff3a84ae251584843bb5d0.png

Template Support

Currently, no configuration for MT devices can be done through templates. The purpose of adding support is solely to allow users to add sensors to a network with MR bound to templates.

Please refer to the documentation to create or assign Alert Profiles.

Adding Sensors to Wireless-Only Templates

In the example below, there is a WirelessOnlyNetwork that is bound to a WirelessOnlyTemplate. If you attempt to add a sensor to the WirelessOnlyNetwork, you may see the following error:

clipboard_ef1c5981f23253afb02cfec6c81181f5f.png

Please follow the steps below to resolve this.

Step 1 - Change a wireless-only template to a combined template
  1. Create a new combined template.
    • For example, the name used below is NewCombinedTemplate
       
  2. Select the new combined template, click on Split, then OK to confirm. This will create templates of specific network types.clipboard_e193bc19a026dd06a2197426472d3f247.png
  3. Check the box next to all the newly split templates, except NewCombinedTemplate - wireless and an existing wireless-only template, in this example, WirelessOnlyTemplate.
    clipboard_ed052715ec0713854b6776603adef6fdf.png

  4. Select Combine at the top and fill in the new network name of the template. 

    • In this example, the template network name was changed to CombinedEnvTemplate
      clipboard_e44199f6a25cacd8a820f231a7b0e78ac.png

  5. (Optional) Clean up the empty template networks that were split.

    1. Under Organization > Monitor > Configuration Templates select the templates you wish to delete.

    2. Click on Delete at the top and confirm on the following screen.

Step 2 - Create a new Combined Network
  1. Create a new network with the combined hardware network type. 
  2. Bind the new combined network to the CombinedEnvTemplate template.

clipboard_e0f18105f9cf95efd7e4226c2b5f6c5b4.png

Step 3 - Combining the Networks
  1. Split the NewCombinedNetwork from Overview Page.

    clipboard_e55d3c822cd715f7ff8cf7b5e543f9d83.png
     
  2. Check the boxes next to NewCombinedNetwork - environmental and WirelessOnlyNetwork.
    clipboard_eb7b5cf866accfa30335eb1fc7e223775.png
  3. Click on Combine and give it the same name as the original network and click on the blue combine button.
    • In this example, the network name was kept the same and remains WirelessOnlyNetwork 
    • (Optional) Enter a network enrollment string if you are using System Manager, otherwise, you can leave this blank
      clipboard_ef524a53aaf133bd92cf7ebeb5279447d.png
  4. You can now add the sensor to the original network. For further help on adding devices, refer to the Adding and Removing Devices from Dashboard Networks document.
  • Was this article helpful?