cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Static vs DHCP WAN

Highlighted
Conversationalist

Static vs DHCP WAN

I am in the process if switching all of my asa's with Meraki mx and was attempting a test at my main location and it doesn't seem to like me.  Here is what I have tried as far as settings for the MX84 at my main location.

 

I have a static IP from the ISP and entered that in the management portion of the device and it will not connect anywhere and I have left the settings alone on the device with exception of assigning the LAN IP.  If I let the the device pick up DHCP it get a weird IP but it does connect to Meraki Cloud and does update and all that but will not provide an internet connect to the rest of the devices hooked to the switch.  I am new to Meraki and figure this is an easy fix for some of you that are experience.

Thanks

Allen Brown

 

 

6 REPLIES 6
Highlighted
Getting noticed

Re: Static vs DHCP WAN

Depending on your MX version, MX 13.x allows  you to assign a static IP address via Uplink tab.

 

In previous version, you connect via management port or directly and use a web browser to http://mx.meraki.com/

 

In there, you choose Configure tab, enter username and password as setup in Network General setting (or if you haven't connect to the cloud yet, device serial number and blank password). You can set a static IP address for the Uplink ports afterwards.


Find my post helpful? Please give me a kudo!
CCNP Certified and Meraki Operator
Highlighted
Conversationalist

Re: Static vs DHCP WAN

I had to plug into management port to make the changes, but when I do and put in Static WAN IP it won't connect to Meraki cloud or give internet.  When I switch back to DHCP it will connect to Meraki Cloud but not give internet to rest of network.

Highlighted
Getting noticed

Re: Static vs DHCP WAN

Sounds like your static IP addressing is incomplete, make sure you have the correct addressing, subnet mask, gateway and dns.

 

Secondly, when on DHCP mode, your internal network is not accessing the internet. Make sure your MX is set to NAT mode, and that the connection does not drop traffic that you need, since MX will drop untagged traffic by default.


Find my post helpful? Please give me a kudo!
CCNP Certified and Meraki Operator
Highlighted
Kind of a big deal
Kind of a big deal

Re: Static vs DHCP WAN

for test: plug in a laptop and set the given static ip. can you reach the internet and ping 8.8.8.8?

Highlighted
Kind of a big deal

Re: Static vs DHCP WAN

Did the existing ASA use a static configuration?

 

When statically configuring the MX are you also assigning DNS servers (which is critical, and the ASA may not have had this before)?

 

When statically configured, you can look at the local status page and it should say what the problem is.  What problem does it report?

https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_M...

Highlighted
Here to help

Re: Static vs DHCP WAN

Does your ISP require you to register the MAC address with them for the Static address to work ?

Also after setting the static in your MX device - reboot your ISP modem to clear out the old cache etc for the old ASA and have the MX request the static IP from the modem.

Ive had to do both before to get MX working with static IP.

 

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.