Networks & templates per device type vs combined

Solved
eye
Here to help

Networks & templates per device type vs combined

Are there advantages in having separate networks for each device type (MR, MS, MX) for each location bound to separate templates for each device type rather than single combined networks per location with a combined template? 

1 Accepted Solution
Ryan_Miles
Meraki Employee
Meraki Employee

There's no difference in functionality between those two scenarios. Templates by nature will enforce most settings with only a limited amount of overridable changes at the network level. Whether you have them as separate templates or a combined template doesn't change the functionality. 

 

If templates make sense for your environment then I would choose combined templates and combined networks as it provides a more cohesive look and feel versus jumping around between templates and network types. Plus, it allows for one spot (per network) to specify thing like timezone or to view client details rather than jumping between a MR, MS, MX network all to view the same wireless client that traverses the entire stack. There's a reason templates and networks by default are set to combined 😉

 

Whether or not to use templates in general is a different question and needs to be made based on your requirements. They work great for some and for others impose limitations that can be problematic.

Ryan

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.

View solution in original post

4 Replies 4
DOC_Meraki
Getting noticed

I’ve always stayed away from Templates due to the amount of issues highlighted in posts in the forum.

 

Run a quick search….

alemabrahao
Kind of a big deal
Kind of a big deal

I particularly use templates to manage my clients' environment and I can assure you that it works very well, not to mention that it makes it much easier to manage. As mentioned by @DOC_Meraki  problems can occur but usually, it's when the networks are not well planned, if you have a well planned network design you will hardly have any problems.


But each case is different and depends on your needs.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Ryan_Miles
Meraki Employee
Meraki Employee

There's no difference in functionality between those two scenarios. Templates by nature will enforce most settings with only a limited amount of overridable changes at the network level. Whether you have them as separate templates or a combined template doesn't change the functionality. 

 

If templates make sense for your environment then I would choose combined templates and combined networks as it provides a more cohesive look and feel versus jumping around between templates and network types. Plus, it allows for one spot (per network) to specify thing like timezone or to view client details rather than jumping between a MR, MS, MX network all to view the same wireless client that traverses the entire stack. There's a reason templates and networks by default are set to combined 😉

 

Whether or not to use templates in general is a different question and needs to be made based on your requirements. They work great for some and for others impose limitations that can be problematic.

Ryan

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.