@skendric band steering is exactly that, it tries to get the client to use the 5GHz band, but ultimately the client makes the decision.  With regard to the DHCP bug you mention, we have quite a number of MR32s and haven't seen this.  What is your DHCP server for those APs? ... View more

@Emre666 thanks, I was looking there and it was so obvious that I completely missed it!  We actually have it enabled at the site I was at yesterday where everything is working well, so I'm not sure that can be the issue, but still worth trying as we did have to disable it in the past to improve client roaming. ... View more

@Sapkota_A best is to log a support ticket, they should be able to tell you. ... View more

@Emre666 we have Windows laptops, iOS devices and IoT devices with pretty much no Mac laptops, so you might have something there.  Also I'm pretty sure we disabled load balancing years ago, but I can't find the settings right now to confirm! ... View more

Just to reassure you on the reboot loop, we have over 50 MR42s running release 28.4 and we don't have the reboot issue. ... View more

@Sapkota_A it can be a connectivity issue, or it can be that the MX is busy, so drops (most commonly repeated) events.  I appreciate your frustration and we send events to a syslog server to attempt to cover this. ... View more

Looks like setting a limit of 150Mbps worked!       ... View more

@Jimbo1 why do you need any address space from the ISP?  Most LANs these days run on private addressing (10.n.n.n, 172.n.n.n. or 192.168.n.n) and simply translate it when talking to the outside world.   I've not seen a LAN using public IP addresses in over 20 years! ... View more

@Network_user55I'd disable the port on switch 1 for MX2 and the port on switch 2 for MX1.  That way you keep switch and MX redundancy without risking spanning tree not working when the units reboot.  I have had too many issues with reboots causing issues when double connected to risk leaving them all enabled...   It might make no difference and if your ports connecting to the MXs on the switches are set in trunk mode then you might be okay without making this change, but it's worth a try, even if you re-enable the ports after the upgrade. ... View more

Thanks @Network_user55 it looks like you have an HA pair of MXs, can you please clarify, is each MX connected to two switches, or is one MX connected to one stacked switch and the other MX being connected to a separate switch in the same stack?   If the former then please disconnect one cable from each MX and try again, if the latter then that isn't the problem. ... View more

Not sure how I missed that! 🤦‍♂️. Giving it a try now... ... View more

@Network_user55 we have 9 switches behind MXs running 15.43 (and were running 15.42 before then).  Our switches that are behind the 15.43 MXs are running 14.22 (eight 120, 210, 220, 225 models) and 14.27 (a 120) that was just upgraded from 14.26 today.  These switches are all L2 only, but we had L3 switches (MS210s) behind MXs running 15.42 before those MXs were upgraded to 16.11   What switch models are you using How are they interconnected How is the management traffic routed and is the IP dynamically or statically assigned What license do you have on the MXs Are the MXs dual connected to the switches and if so try disabling one of the connections ... View more

@KarstenI I'd give you mode Kudos if I could, it is high time that a better 8 port switch came along and a 355 would get an A* from me 😎 ... View more

@RW2 if you have Cisco IOS switches in a stack then you should cross connect as has been suggested to you and this will mitigate switch or cable failure causing the MXs to go into dual master mode.    If you have Meraki switches in a stack then you should single connect as otherwise when you reboot the stack, both connections to each MX will come up unblocking leading to failure.  You could set STP loop protection on those ports to avoid this, but will need your management to use a different uplink in order to do that.   I'm not sure with separate non stacked switches, but I'd bet the same is true.   And if you want to know how I know, the answer is being bitten more than once..! ... View more

@SopheakMang any chance that you can terminate the two ISPs on the MX, perhaps alongside the existing device, as opposed to behind it?  Then both IPs would be registered all the time.   You'll need each ISP to give you at least a /29 which may or may not be easy, depending on where you are in the world. ... View more

@Dunky to add to option 2 of using Meraki switches, you might want to put them in two separate networks that are not the main site network.  This would ensure that when you upgrade them, they don't both reboot at once...   You don't need to do this, as when you schedule a switch firmware upgrade, you can now go back in and change the times for individual switches, but you might forget on one occasion!   If I were going to follow that route I'd have one network for all the switches connected to provider A at all sites, and another for all switches connected to provider B.  That way you'll also get some overall provider reporting 😇   ... View more

@Dunky I think your option 2 will work, remember to put the MX to ISP connections in their own VLAN without an interface.   We use Cisco Small Business SG110D-05 switches in that role, cheap as chips and in over 2 years we've never had one cause a problem. ... View more

@watdee you may get errors if you reboot the stack, or you.may be lucky.  I'd definitely get a second cable! ... View more

Click on Security & SD-WAN / Addressing & VLANs     Scroll down to Routing and click on Single LAN settings, you will get a box as below, choose a new MX IP and matching Subnet, the press Update     ... View more