Meraki

Dashboard_DJ · ‎Oct 20 2017

@bbayles That doesn't sound like expected behavior to me. Might be worth giving Support a quick ring and having them validate.

Dashboard_DJ · ‎Oct 16 2017

Hi @Philippe. The topology page is populated using LLDP and CDP inputs received on Meraki switches. If you're not seeing the catalyst switch, I'd first double-check that CDP is enabled on it's connected interface. If it is, it might be worth giving Meraki Support a call to see if they have any additional compatibility insight.

Dashboard_DJ · ‎Oct 3 2017

This might be a useful read as well. I put that together as a way of documenting MX warm spare deployment best practices and considerations. https://willette.works/mx-warm-spare/

Dashboard_DJ · ‎Oct 2 2017

I stand corrected! 🙂 Mixing MX wireless with MR isn't ideal for a variety of reasons, so using the dedicated MR32 will serve you well.

Dashboard_DJ · ‎Oct 2 2017

All configuration for the MX65W's wireless configuration must be done under the Security appliance > Wireless settings page. There, you can see that Meraki Authentication is not currently a supported SSID auth method.

Dashboard_DJ · ‎Oct 2 2017

@Senan_Rogers 3rd-party VPN routes are not advertised into the AutoVPN route table and there is no way to do so unfortunately. A common workaround when you need to merge both AutoVPN and 3rd-party VPN route tables is to use two different MX appliances as hubs: 1. DC MX1, that's in your main org and terminates your Meraki AutoVPN domain. 2. DC MX2, which is in a dedicated org you create just for terminating 3rd-party VPN. Then on DC MX1, simply configure a static route for any of the remote, 3rd-pary VPN destinations with a next hop of the inside IP of MX2. The same can be done in reverse on MX2, with a default route pointing towards your MX1 or your DC core.

Dashboard_DJ · ‎Oct 2 2017

The next hop IP should not be the MX84 IP address. It should be the IP address of the "next hop" towards your internal LAN. Essentially the IP address of the device you have the MX connected to on the LAN-side. Most likely a L3 switch interface or router.

Dashboard_DJ · ‎Oct 1 2017

Assuming your DC MX84 is in NAT mode, then you would need to add a static route for b.b.b.b/32 on your MX84 appliance under Addressing & VLANs with a next hop of a router/switch connected to one of the local, internal subnets. Make sure you select "in VPN, yes". That will inject the route into the AutoVPN global route table and tell the MX64 peer to send all traffic destined for b.b.b.b tunneled to the MX84 first.

Dashboard_DJ · ‎Oct 1 2017

@AnythingHosted If I'm tracking with what you're trying to get to, then this should be a fairly simple fix but depends on the AutoVPN posture of your DC MX84. If you go to Dashboard > Select your MX84 Network > Security appliance > Addressing & VLANs, are you running in NAT mode or concentrator? Both are supported AutoVPN roles for a DC deployment, but the way routes are injected into the AutoVPN table for remote MX peers is different. Knowing if it's NAT mode or concentrator should help us guide you towards a solution.

Dashboard_DJ · ‎Sep 27 2017

The fans on the MS225s are moderately noisy. I don't have dbA info, but they're one of the loudest access-layer switches in the lineup. If noise is a significant concern, then the new MS120 or MS250 platforms are much quieter.

Dashboard_DJ · ‎Sep 27 2017

They pushed an MX template enhancement last week that allows child MX networks' uplink bandwidth sliders to override the template uplink settings. This unlocks the ability to optimize the WAN bandwidth settings on a per-site basis. That might solve most of your issue.

Meraki

Community

About Dashboard_DJ

Dashboard_DJ

Community Record

Badges

Re: MX65 wireless drops when saving firewall rules

Re: topologie not reflecting reality

Re: Meraki MX100 Active and Passive Configuration and Setup

Re: MX65W access control with meraki authentication when MR32 also present

Re: MX65W access control with meraki authentication when MR32 also present

Re: s2s vpn between Meraki and Non Meraki

Re: Exit Hub for specific IP

Re: Exit Hub for specific IP

Re: Exit Hub for specific IP

Re: Looking for info regarding switch fan noises

Re: MX Templates and Traffic Shaping

Re: MX65W access control with meraki authentication when MR32 also present

Re: s2s vpn between Meraki and Non Meraki

Re: Looking for info regarding switch fan noises

Re: Looking for info regarding switch fan noises

Re: Exit Hub for specific IP

Re: topologie not reflecting reality

Re: Meraki MX100 Active and Passive Configuration and Setup

Re: s2s vpn between Meraki and Non Meraki