DEFAULT ROUTE FOR CISCO MERAKI MS350

Censystems-Prev
Comes here often

DEFAULT ROUTE FOR CISCO MERAKI MS350

I have a management network where a Cisco MX device acts as the default gateway for my networks and is connected via a trunk port to a Cisco MS switch. When I manage the MS using DHCP from the MX, everything works fine. However, when I switch to a static IP configuration on the MS, I lose administrative connectivity.

 

I have already made adjustments to the VLANs and configured static routes pointing to the MX, but the issue persists. Does anyone know what could be causing this problem?

 

I’d appreciate your help!

7 Replies 7
ww
Kind of a big deal
Kind of a big deal

Are you assinging a ip in a switch L3 vlan?

 

Its recommended to have a switch management ip in the vlan on the mx. So that the switch doesnt need to route its own management traffic. 

 

Does the mx have routes to the switch vlans?

Censystems-Prev
Comes here often

Hello thank you for your answers

 

My situation is there:

 

 

My MX have default gateway for my vlans and DHCP only for Specific segments, i have a management vlan 90 and i have the following address

 

192.168.90.1/28 Default Gateway for MX

192.168.90.5/28 for MS but this address its with DHCP from MX 

 

i have a interface trunk between MX and MS with native vlan 90, when i remove the DHCP in MX and put the address 192.168.90.2/28 for my MS a lost the administration from dashboard. I put a interface L3 but not resolve the issue.

 

If i use a catalyst swicth the configuration its resolve with command ip default-gateway but in Meraki i dont know what happen.

ww
Kind of a big deal
Kind of a big deal

So u configure this, and then you lose connectivity?  .2 is not in use already?

 

1000053687.jpg

Censystems-Prev
Comes here often

Its correct when i put this configuration and remove DHCP from MX i Lost the MS

Censystems-Prev
Comes here often

MS

CensystemsPrev_0-1736903732763.png 

 

MX

CensystemsPrev_1-1736903816114.png

 

TRUNK

 

CensystemsPrev_2-1736903860269.png

 

DHCP From MX

 

CensystemsPrev_3-1736903902564.png

 

 

this is currently

ww
Kind of a big deal
Kind of a big deal

DarrenOC
Kind of a big deal
Kind of a big deal

Agree with @ww - the switch can’t have its Management L3 VLAN interface on itself.  So in your case the Management VLAN interface will reside on the MX

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
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.
Labels