About NolanHerring

NolanHerring

That is correct WAN 1 goes down, WAN 2 auto kicks in.

NolanHerring

Turn off loadbalancing. that slower DSL sounds like the purpose is for redundancy. I would only use load-balance if you have two good/fast pipes

NolanHerring

Here are some links to get you going: https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Meraki_Cloud_Architecture https://documentation.meraki.com/zGeneral_Administration/Other_Topics/Firewall_Rules_for_Cloud_Connectivity https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Behavior_during_Connection_Loss_to_Cisco_Meraki_Cloud

NolanHerring

I'm like 99% certain that the LAN ports on the MX will respect/observe/maintain/not-mess-with the QoS markings for any packet coming/going. As far as remarking them, I was always under the impression that it was something would only apply to the WAN interfaces (for VPN/MPLS tunnels etc.). There is a good blog on it here you can review as well: https://www.willette.works/mx-qos-and-traffic-shaping/

NolanHerring

I didn't see anything. Might have just been the shard your utilizing, but only support would be able to tell you that. I have seen a blip or two in the past and once I realize its the cloud and not me, I just shrug it under the rug since 'things happen'.

NolanHerring

I know on the wireless Access Control page they provide a TEST button on the right side. Is there one for this? Can't tell if you simply cut it off or not in the screenshot.

NolanHerring

Also I'm going to take a wild guess and say that if there are any issues, support probably won't be able to officially assist if using those.

NolanHerring

Technically it looks like it should work, but I would probably advise against using an extension (if possible) as it will introduce some loss and another device in line that could fail etc.

NolanHerring

Contact support for an RMA is probably your best bet at this point.

NolanHerring

Quick google yields only wireshark related results. I can't help but wonder if this new MDP was supposed to be announced yet or if someone let it slip lol. Whatever it is.

NolanHerring

If you remove the native VLAN 10 from the switch port, then you should be able to assign VLAN 10 onto the SSID. If you leave native VLAN 10, then you don't need to specifiy it on the SSID. I personally am not a fan of this approach. I use the native VLAN on trunk ports for the access points so that it places them on the VLAN (management), and then the actual VLANs I use for end-users (data vlans etc) are different.

NolanHerring

FYI Seems to be defaulted to Enabled, since I never messed with it before and all my sites have it set this way. I just randomly ran across this setting under Network Wide>General https://documentation.meraki.com/MR/Other_Topics/Multicast-Unicast_Conversion

NolanHerring

14.39 is currently Stable release candidate, so I think you'll be safe going to that one.

NolanHerring

I would suggest running the latest 24.X firmware for MR16's personally. You have to contact support to do this. I never had any luck with them on 25.X

NolanHerring

Ok, well I honestly don't know how the /16 vs /19 will work (if it actually impacts anything), so lets assume its not that. Can you validate the Access Control setting for the 'office' SSID is set correctly. Also, can you show the switch port configuration for where the AP connects to. Its possible the switch port is not allowing VLAN 10 for example etc.

NolanHerring

What version firmware are your MX devices running?

NolanHerring

Is your MX the one supplying DHCP (acting as the server) or is that another server somewhere else? Also, is your scope size accurate? I see you showing it as a /16 If your MX is doing DHCP I believe from recent discussions that doing a /16 is too large for it to process locally. If it is not doing DHCP, you need to make sure you have a relay setup for the actual DHCP server (possibly).

NolanHerring

What do those two columns represent? I don't see an option in my view to show 2.4GHz only, and 5GHz only columns. I would suggest rebooting the AP. the 2.4GHz radio might be 'stuck' and not accepting clients. Seen this plenty of times (although usually on the 5GHz radio).

NolanHerring

Way to go guys! I could have sworn @BrechtSchamp was going to kill it as #1 lol

NolanHerring

@Aaron_Wilson Was there a solution/fix for that issue you are referencing?

NolanHerring

Good idea ! I'll look into doing that. thanks for the idea

NolanHerring

Hey guys, Looking for a way to disable a port and re-enable it after a minute or two, on weekly basis, to reboot an access point. I was hoping to find a way to do this via port scheduling but it looks like they only allow 30 minute intervals at the smallest time frame. I don't want the AP down for 30 minutes, just need to reboot it automatically and this was the only clever way I could come up with. Any ideas?

NolanHerring

I had about 30 old MR16 that I finally got rid of about 6 months ago. They all acted like christmas tree lights on 25.X code, just rebooting randomly throughout the day, all of them. For certain contact support to investigate. They can see more details behind the scenes that what we can, to determine issue etc. My suggestion would be to ask support to put them on latest 24.X code (as mine were somewhat stable on this version) and see if they are more stable. Or upgrade them because they are indeed old.

NolanHerring

He also sent me a message, but I replied and now he wants me to give him only $500 USD and I can help him to finally unlock his family fortune that has been held up with court documents, and he promised me 5 Billion in return. I mean....how can I pass up on that kind of an offer!!!

NolanHerring

Does the old network use two /24 or one /23 ? The MX will hand out IP Addresses from its DHCP range, first come first serve. The DHCP reservation you have above is basically blocking out all of your IP Addresses, so it will require DHCP static reservations either on the MX or client side.

NolanHerring

Nolan Herring

Community Record

Badges