Hello All,
Is it Meraki Ms250-48LP-HW comes along with default DHCP server ? If no then can I create DHCP server on Meraki Ms250-48LP-HW .
Also can anyone help me how to do the stack of these switches.
Thanks in advance
@V_007 : Look below links related to Meraki MS Switch DHCP.
https://documentation.meraki.com/MS/Monitoring_and_Reporting/MS_DHCP_Servers
Hi @V_007
Just to follow on from your second query. Look at the physical stacking section within this document.
https://documentation.meraki.com/MS/Stacking/Switch_Stacks
Also YouTube video to help you on your way
https://m.youtube.com/watch?v=IKDHnZzkJ8I
quick conf guide for the DHCP piece.
Within the dashboard click on Switching > Configure > Routing and DHCP. Click Add New. Select the Switch which you want the dhcp scope to be configured on.
Thank you Ucert for your reply
One query i have, it would be great help if you or anyone help me.
I have to create dhcp server on Switch and related vlan for Lan, Wifi excluding the Management vlan
Ex: Management vlan 192.168.1.0/24
Lan Users 192.168.2.0/24
Wifi Users 192.168.3.0/24.
Query is will create dhcp server for vlan Lan and Wifi users on Switch, So i need to create vlan (Lan and Wifi) on Mx also and assign a ip address on it or only management vlan will work and take all my traffic from lan and wifi users towards internet from MX
Second query is the connecting link from Mx to Switch will be in access vlan of management only or need to do the trunk ?
For your first query the answer is no.
If your MS250 switch is acting as the default gateway of that LAN then you should configure DHCP server on the VLAN Interface on the switch. In this case the MX is not even connected directly to that VLAN because it will be connected to a point to point link and routing to that subnet. Alternatively you can have the switch be a DHCP relay agent, which would mean you need to point it to a DHCP server in an MX or server.
For your second query: it depends what you want to do.
If your MS250 is acting as default gateway for all local VLAN's with a transit network to the MX you can have two scenario's.
1) You have a separate VLAN directly on the MX that severs as management VLAN for the switches. You can either pass that VLAN over the same port to the MS using a trunk link or use a secondary link that only allows the management VLAN.
2) You grow the transit subnet between MX and MS to a /29 and have the MS250 management IP be in the same subnet as the transit IP. then you can have a management VLAN that terminates on the MS250 for downstream switches. This one is a bit weird but is valid.