- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Question regarding to network design
Hi all,
just have a question regarding to my network design for a new site...
Will have a stack of two coreswitches (aggregationswitch), a few access switches and a several accesspoints.
In the past, I made a network and put all devices into the same network.
Now I´m thinking of making two networks... One for the corestack, the other for all switches and accesspoints.
How do you guys do it or is there a best practice?
Thinking of updating firmwares... in the network where I have all in one, I can only update everything... It may make sense to only (or step by step) update accessswitches (first).
Thanks for your tips.
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One Network - and use Staged Upgrades: https://documentation.meraki.com/MS/Firmware/MS_Firmware_Upgrades#:~:text=Staged%20Upgrades%20allows....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One Network - and use Staged Upgrades: https://documentation.meraki.com/MS/Firmware/MS_Firmware_Upgrades#:~:text=Staged%20Upgrades%20allows....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ah nice, didn´t notice staged updates till now. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @GreenMan ,
got a further question on this...
Nearly the same question as above, but this time there is already a network running and now another building is coming in with its own corestack, switches and accesspoints.
Existing network/building and new building are connected to each other. The new Corestack will get its uplink through the existing corestack.
Is there a best practise for this?
All in one Network or a new network for the new building?
It may be more clearer if I have to networks, but as it is at the exact same address and even connected between each other I´m not sure what the best way is.
Thanks, regards
Marc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'd be tempted to do these as one network still. How many switches are we talking about, it total?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
33 Switches (couple of stacks) , 150 Accesspoints.
But regarding to your posts, decided to put all in one network 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes one network, if you split them into multiple networks the dashboard will not be able to draw the topology and it could make viewing network clients a pain.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @BlakeRichardson ,
got a further question on this...
Nearly the same question as above, but this time there is already a network running and now another building is coming in with its own corestack, switches and accesspoints.
Existing network/building and new building are connected to each other. The new Corestack will get its uplink through the existing corestack.
Is there a best practise for this?
All in one Network or a new network for the new building?
It may be more clearer if I have to networks, but as it is at the exact same address and even connected between each other I´m not sure what the best way is.
Thanks, regards
Marc
