Is there checklist to follow for the MX, MS and MR deployment ?

SOLVED
AlanWong
Conversationalist

Is there checklist to follow for the MX, MS and MR deployment ?

Is there checklist to follow for the deployment of MX, MS and MR appliance? I'm new to Meraki deployment, like to deploy MS, MS and MR appliance in the Cisco recommended way and with basic baseline only.

1 ACCEPTED SOLUTION
rhbirkelund
Kind of a big deal

As @MerakiDave says, there is no specific How-To, since every deployment is different.
However, then I'm out deploying a Full Stack Meraki, I usually prioritize getting the MX up and running as the first thing. I even wait before powering and uplinking any device further down, untill the MX is up.
All Meraki devices upon firsttime boot will contact the dashboard, and perform firsttime upgrade. So also before setting the MX up, make sure you've set whatever firmware you wish to be running in the Dashboard.
Then make sure all basic settings are made (Mgmt DHCP), downlink ports an so on.

After the MX is up, I go about uplinking the switches in the chained way that I have designed, and then work my way through the topology. One could connect it all as once, and go get lunch while it's everything is contacting the dashboard, upgrading, rebooting, and so on. But I prefer doing one device at a time.
When all switches are online, I go about the rest. AP's, client facing ports and so on, as part of the comfiguration process.

When all the basics are done, I go about doing all the finetuning, with everything online.

Those are just my 2 cents..
LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.

View solution in original post

2 REPLIES 2
MerakiDave
Meraki Employee
Meraki Employee

Hello @AlanWong there wouldn't be anything specific since every deployment is going to be different for each customer, but generally speaking all of the Meraki equipment will have default settings that allow it to be fairly plug and play and then you can modify whatever settings suit your needs and requirements. 

 

I'd refer to the various best practice documents here https://documentation.meraki.com/Special:Search?q=best+practice and feel free to come back here and post to the Community with any questions or to get some pointers or if you're stuck on something. 

 

There's also places like the Webinars site and Youtube channel which are basically like free training resources.  https://meraki.cisco.com/webinars and https://www.youtube.com/user/milesmeraki and I'l also suggest reviewing/subscribing to the Meraki Blog to catch all the news and announcements, https://meraki.cisco.com/blog/ 

rhbirkelund
Kind of a big deal

As @MerakiDave says, there is no specific How-To, since every deployment is different.
However, then I'm out deploying a Full Stack Meraki, I usually prioritize getting the MX up and running as the first thing. I even wait before powering and uplinking any device further down, untill the MX is up.
All Meraki devices upon firsttime boot will contact the dashboard, and perform firsttime upgrade. So also before setting the MX up, make sure you've set whatever firmware you wish to be running in the Dashboard.
Then make sure all basic settings are made (Mgmt DHCP), downlink ports an so on.

After the MX is up, I go about uplinking the switches in the chained way that I have designed, and then work my way through the topology. One could connect it all as once, and go get lunch while it's everything is contacting the dashboard, upgrading, rebooting, and so on. But I prefer doing one device at a time.
When all switches are online, I go about the rest. AP's, client facing ports and so on, as part of the comfiguration process.

When all the basics are done, I go about doing all the finetuning, with everything online.

Those are just my 2 cents..
LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
Get notified when there are additional replies to this discussion.