Meraki

Adam · ‎Jan 8 2019

What are you trying to accomplish? In most setups the same LAN shares the two WANs load balanced. You can set an internet preference if something LAN side needs to stick to a certain LAN interface.

Adam · ‎Jan 8 2019

I've run speedtests at sites MX64 and 1G burstable circuits and had the 250M limit.

Adam · ‎Jan 8 2019

I only have MX64 and MX65 networks so I'm not sure. The number I provided is based off of this (see page 3) https://meraki.cisco.com/lib/pdf/meraki_whitepaper_mx_sizing_guide.pdf Which is pretty accurate. You may get a little more bandwidth if you have certain stuff turned off.

Adam · ‎Jan 4 2019

MX67 only supports max throughput of 300M with all security enabled. The first device that can support 1G internet is the MX250 which is way to expensive for a small site. This is still painful for me to size at sites that have large pipes available with a minimal number of users.

Adam · ‎Nov 18 2018

We use the 4U version of what @BlakeRichardson recommended.

Adam · ‎Oct 3 2018

Also it looks like that SFP is designed for multi mode fiber. Are you sure that is what is running between your MDF and IDF? Is it possibly single mode?

Adam · ‎Oct 2 2018

You could try 1:1 NAT a phone to basically eliminate the MX as a variable and see if it makes a difference.

Adam · ‎Oct 2 2018

Glad we could make it easy on you this month 😉

Adam · ‎Oct 1 2018

Is it the vonage box or just vonage desk phones?

Adam · ‎Oct 1 2018

I have multiple clients using MX devices, with Vonage, without issues. I'm pretty sure the MX60 is an old model device so sounds like the support reps knowledge is out of date. You may want to try to call them back and talk to someone that is having a better day.

Adam · ‎Sep 28 2018

Thanks that helps. So it looks like your static IPv4 is VLAN 10 and that IPv6 is getting DHCP from VLAN 2? Do you happen to have a topology you can share? Conceptually the trunk port on the switch should have a native VLAN set and then allowed VLANs. As long as the native VLAN isn't 2 you should be fine. Maybe make the native 10 and just have 2 in the allowed? Sorry trying to help the best I can here with limited visibility.

Adam · ‎Sep 28 2018

@CotyMick I saw those but it looked like a metal box. But now that I read the spec it says they are plastic and don't impede the signal so may be fine. Would be interesting to test.

Adam · ‎Sep 28 2018

Would you mind posting a screenshot or two to help explain? I'm not following where this is showing up exactly.

Adam · ‎Sep 28 2018

Agreed I usually go the iproute method but you may want to test routing something small first before the default route.

Adam · ‎Sep 28 2018

Can you give it a static IPv4? For whatever reason, I didn't think Meraki equipment supported IPv6 yet but I probably just didn't see the update.

Adam · ‎Sep 28 2018

On the MX or on the ASA? MX is all GUI.

Adam · ‎Sep 28 2018

Maybe message these guys and see if they have or can make one for a MR42 https://coverandhyde.com/ I feel like some type of stretchy fabric would work well and not impede signal.

Adam · ‎Sep 27 2018

Yes I do this. Just plug my MX into a regular access port. It'll get DHCP and checkin to the dashboard so you can start configuring it. Then my last step is to configure the static IP on the WAN interface before putting it into production.

Adam · ‎Sep 26 2018

So you are changing the IP of the AP? Have you verified the configuration to make sure the VLAN, IP, Gateway are correct?

Adam · ‎Sep 26 2018

@MRCUR comment reminded me of what you are trying to do. You use to be able to setup the management IP the same as the IP on the switch a long time ago. That is no longer supported by Meraki. On many of my switches we don't even need an L3 configuration and just have the primary switch IP as the management IP (no L3 needed) since adding the extra IP was unnecessary.

Adam · ‎Sep 26 2018

Agreed, I have 10 coming my way in the near future. Thankfully I don't have much L3 stuff. @CotyMickThe easiest way to do this from memory is to add the new switch to the same network without removing the old one. You'll get a temporary license nag (disregard). Then do the clone as you did. Reference the old switch for your static IP info and input that into the new switch. Then go to Switch>Routing & DHCP. Select the static routes and select Edit>Move and select the new switch. This will move those routes to the new switch. The new switch may have to be online to do this, I don't recall. This would be much easier than copy/paste or re-type them all.

Adam · ‎Sep 26 2018

My understanding is that the clone feature only copies over the port configurations. No name, address, static IP or route information gets copied over. I agree this is stupid and should be fixed. Or perhaps another option called 'replace' should be made that does copy all of that info.

Adam · ‎Sep 26 2018

I haven't had any issues. Can you post a screenshot or explanation of what is going on? Also I assume you tried a different browser, clearing temp/cookies etc?

Adam · ‎Sep 25 2018

We get some clustering but not quite that bad.

Adam · ‎Sep 25 2018

When I am creating a floor plan I upload the image and then I set it to Satellite mode and Opacity. Then I drag it over top of the actual building to make sure it is scaled the same.

About Adam

Adam

Community Record

Badges