About Adam

Adam

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

Adam · ‎11-08-2018

Interesting, didn't see anything directly related in the 25.13 firmware notes. The closest thing I see is this Fixed an issue where the BLE radio would stop beaconing and scanning (MR30H/MR33/MR74)

Adam · ‎11-08-2018

I couldn’t find anything in the wireless section on this issue. Here is some information and resources. https://www.bleepingcomputer.com/news/security/new-bleedingbit-vulnerabilities-affect-widely-used-bluetooth-chips/ and https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20181101-ap

Adam · ‎10-19-2018

I got a new job in a non Meraki environment so I probably won't be here as much as I usually am. I still do consulting on the side and I primarily recommend Meraki equipment so I won't be a complete stranger. This community has been a great resource and I hope to checkin from time to time. On to new challenges and bigger projects.

Adam · ‎10-07-2018

Your best bet for this type of config is to setup the switch port going to the router as access vlan X. Use a VLAN you don't use for other stuff. Then setup the port going to the MX as access with that same VLAN you used above. Then you should be good.

Adam · ‎10-07-2018

Did you try rebooting the MX?

Adam · ‎10-03-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 · ‎10-02-2018

I've never tested this but my guess is the VPN tunnel would establish through one of the WAN links and hold its session open there.

Adam · ‎10-02-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 · ‎10-02-2018

Glad we could make it easy on you this month ;)

Adam · ‎10-01-2018

Is it the vonage box or just vonage desk phones?

Adam · ‎10-01-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 · ‎10-01-2018

When relying on meshing I got the 5G directional antennas for my AP's and pointed them toward each other so they have a stronger mesh.

Adam · ‎09-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 · ‎09-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 · ‎09-28-2018

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

Adam · ‎09-28-2018

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

Adam · ‎09-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 · ‎09-28-2018

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

Adam · ‎09-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 · ‎09-28-2018

Tried that @PhilipDAth and I don't think it is entirely accurate. I believe that may only trigger on devices that are alerting for connectivity reasons. See below screenshots. Network-wide overview search of alerting devices is 0. But clearly, some are alerting.

Adam · ‎09-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 · ‎09-27-2018

Do you guys know of anyway, using the dashboard or APIs, to get a summary of alerting devices? I just happen to stumble into one of my networks in the switch section and noticed it said. "Unable to fetch configuration. This device is unable to fetch its configuration from the Meraki cloud. Please contact Meraki Support." I called support and I guess it failed its internal NTP check and likely just needs an after-hours reboot. But this got me to thinking that I don't really have a way to proactively review any alerting devices. Even if I go to Organization>Overview and select the 'Devices' tab it wouldn't show that device as alerting there. Another element that would be useful to have a report or dashboard would be any ports with high CRC errors. Any input or feedback is appreciated and kudo'd.

Adam · ‎09-27-2018

I don't even have that enable client privacy button. I'm kind of confused as to why the difference here.

Adam · ‎09-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

Community Record

Badges