Meraki

IanMartin · ‎Jun 21 2018

@jdsilva That's one thing we don't have to worry about as we run fixed IP for everything. (something else we inherited!) I disabled DHCP on both interfaces on both MXs before we tried going live. @T-800 I'll take a look at those articles thanks. EDIT Following a call with Meraki Technical sales this morning it is clear we have a non standard/recommend network setup, Meraki do not support two live active MXs on the same network! We will have to make changes to our network setup to get them to work properly and hopefully improve the network in general. In light of this @T-800 I've marked your reply as the solution. Many thanks to all that have contributed to this thread it has been very enlightening and now looks like I have quite a bit of learning and work to do. Ian

T-800 · ‎Jun 20 2018

If each WAN port is getting its own public IP, I don't see why this wouldn't work. Its not truly redundant, but it should work for aggregation. I have a an MX84 that is ultimately doing something theoretically similar, but not for the purpose of aggregation. The MX can do "private IP" routing on the LAN ports (like to an MPLS router for example), so if you don't need inspection and NAT, that could possibly be an option too. To my knowledge the default 0.0.0.0 has to go through the WAN ports though. T-800

PhilipDAth · ‎Jun 19 2018

I would not use Meraki switches for this use case.

dpf · ‎Jun 19 2018

if you don't replace the 400, we might be interested in purchasing the rail mount kit(s).

MRCUR · ‎Jun 19 2018

Have you considered switching to the Meraki hosted guest auth/splash setup? We use this quite successfully across a number of networks and deploy the guest SSID with a PSK and then present a sign in page.

MerakiBeginner · ‎Jun 19 2018

Hello PhilipDAth, you are right, information from Meraki Support: not possible. Regards, MerakiBeginner

CarolineS · ‎Jun 18 2018

Hi @mchartier - Thanks for letting us know; I see you've also posted your question in Off the Stack. We'll use that one as the thread for following up. I'm asking around internally to find the right person to help you. Cheers!

Rudi · ‎Jun 18 2018

I was having a similar issue on my network, with 2 specific devices (laptops, not phones). In my case it was a firmware upgrade that solved the issue, the machines were seeing up to several hundred failed connections per day. I assume the devices are probably updated, so this probably isn't helpful, but thought I'd offer my experience with it.

dlowery · ‎Jun 15 2018

Well, that may be helpful for us, but it will be a pain in the butt to setup lol. Thanks for the reply.

PhilipDAth · ‎Jun 12 2018

@ww and @jdsilva are correct. Create a seperate VLAN for the guest traffic. Bridge the SSID to this new VLAN (using VLAN tagging). Then connect a security device, like a Cisco Meraki MX to that VLAN, and out to the separate Internet circuit.

kevinl · ‎Jun 11 2018

Thanks! Something we can look at doing in future to eliminate the need for ISP routers 🙂

PhilipDAth · ‎Jun 10 2018

You can get a copy of the certificate from the partner portal.

jdsilva · ‎Jun 8 2018

Meraki has the following definitions for those states: Enabled - RSTP will be used when the port is connected Forwarding - RSTP is in use and the port is forwarding traffic https://documentation.meraki.com/MS/Monitoring_and_Reporting/Switch_Port_View#PortView-RSTP I'm not sure why they wouldn't both be forwarding unless LACP hasn't actually bonded the links? Seems not right...

jdsilva · ‎Jun 8 2018

Hey @Mju. No, you cannot do this currently with that set up. That method will only provide failover. You would need this type of topology to do what you are asking: https://documentation.meraki.com/MX-Z/Site-to-site_VPN/Configuring_Site-to-site_VPN_over_MPLS

PhilipDAth · ‎Jun 7 2018

Try viewing them on the "Orgganisation/Overview" page, and check visually they look in their correct places. Often if one is missed it appears in the USA on the global map.

jdsilva · ‎Jun 7 2018

Right. I amended my reply above for a VPLS (or other layer 2 MPLS service). In that case you're right and it's the same layer 2 domain on both sides.

Adam · ‎Jun 6 2018

Good to know it was temporary.

JohnM · ‎Jun 6 2018

@RH6379 wrote: We're installing 12 MS-120 switches in a remote office and the switches are showing a DNS misconfigured error when we use the IP of the mgmt vlan as the DNS Server. That is configured on an MX84. Is your MX84 not configured as a DNS proxy perhaps? If it's not relaying and returning DNS queries and responses for clients, then the switch isn't going to connect either.

Pdriver · ‎Jun 5 2018

Hello On a side note regards LLDP on the MR's , Any reason you guys know why the AP's would log they are directly to a phone even though they are connected to a switchport and the switch's are logging the correct mac of the aps? Its only occurred as far as I can see since the latest firmware upgrade. Example: Ethernet 1 1000 Mbit, full duplex regDN 2080,MITEL 5312 IP / LAN port

Bassman · ‎Jun 4 2018

Many thanks jdsilva 🙂 Yes, I am struggling to see how I can exclude the Guest Wireless traffic from using the Auto VPN. Maybe if the ADSL router has two ports then I can connect the second port directly to the Meraki core switch (vlan 999) and then bypass the MX84 althogether for guest wireless traffic? Port one of the ADSL router will remain connected to the MX and be used for VPN failover.

Adam · ‎Jun 4 2018

Correct, obviously doesn't need to be those ports. Could just as easily be 47/48 or whatever.

GuiCarvalho · ‎Jun 4 2018

Adam, Thanks for your help.

PhilipDAth · ‎Jun 1 2018

The only other option guaranteed to work is to create an SSID only on your MR42 dedicated for the TV and have the TV use that.

Adam · ‎Jun 1 2018

We have dual internet connections with failover, traffic shaping etc on MX64, MX84 and MX100's.

Adam · ‎May 30 2018

Not easy to switch but you'll want to work with your sales rep to get that figured out. To see if the existing license can possibly be returned to purchase the desired license.

About jdsilva

jdsilva

Community Record

Badges