Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About EBow
EBow
Comes here often
Member since Mar 23, 2020
Apr 27 2020
Community Record
8
Posts
0
Kudos
0
Solutions
Badges
Mar 31 2020
12:55 PM
It is the weirdest thing. We changed the IP to a non production address to test then setup a packet capture on the our firewall. After a few minutes we could see the MX-250 arp entry on the firewall. Still, we couldn't ping it. We could see it reaching out to 8.8.8.8 over ICMP and a few other addresses via UDP. Then 20 to 30 minutes later poof it shows up in our Meraki dashboard and then we could ping it from the firewall. Why we couldn't ping it from the start is annoying. That is the most basic connectivity test. Why did we have to wait for it to check in and do what ever it was doing is beyond me. Especially when non technical people are deploying these in a data center and you are going behind them and verifying the connectivity and get a false negative because you didn't wait long enough for something to happen.
... View more
Mar 31 2020
4:59 AM
This device has never reached the cloud because the IP is not working.
... View more
Mar 31 2020
4:50 AM
Let me be clear are you saying I need to configure rules on the MX-250 to allow ping replies? That would imply it was attached to the cloud and operational. Which it isn't. I am on the local web interface to the device. We configured an IP and it doesn't respond to the configured ip or try to reach out to the cloud.
... View more
Mar 31 2020
4:43 AM
This is a new install, since when do you have to configure rules to allow pings? I say that because for our pilot we configured a MX-65W and it didn't require rules to allow us to ping the configured WAN uplink interface.
... View more
Mar 31 2020
3:32 AM
So we got a new MX-250 shipped to a data center. I sent the install guy the Meraki document on how to configure a static IP in the device. I can't ping the MX-250. I can see a MAC addresses on the WAN uplinks. So L1 and L2 is working. I am using the existing address of a working Meraki. I shut interfaces and clear the ARP entries for that address prior to bringing this one online. So there are no duplicate IP addressing going on. It simply isn't responding to the configured IP. Anyone know if there is a step missing in the documentation. Steps 1-5 below are completed and still no L3 connectivity or response. Connecting to WAN All Meraki MX devices must have an IP address. This section describes how to configure your local area network before you deploy it. A local management web service, running on the appliance, is accessed through a browser running on a client PC. This web service is used for configuring and monitoring basic ISP/WAN connectivity. Setting up a Static IP Address To ensure that the client PC is redirected to the local web service in the following step, you must disable all other network services (ex: wi-fi) on your client machine. Do the following to configure basic connectivity and other networking parameters: Using a client machine such as a laptop, connect to the management port of the MX. Using a browser on the client machine, access the appliance's built-in web service by browsing to http://setup.meraki.com. (You do not have to be connected to the Internet to reach this address) Click Uplink configuration under the Local status tab. The default credentials use the device serial number as the username, with a blank password field. Choose Static for the IP Assignment option. Enter the IP address, subnet mask, default gateway IP and DNS server information.
... View more
© 2024 Cisco Systems, Inc.
