Hello, is there a solution for this for Windows 10 22H2 version? Seems the update on the link provide is not working on my side. Thanks ... View more

Hi @Marsrock2021 , May be we can use the idea of filtering the VLAN at the switch port page (there are various parameter)   Switch -> Switch Ports ... View more

Chris it has to be 10gb. We have failover resilent connections on single IP with 10gb connections so need a 10gb switch ... View more

@cmr you are correct in that Meraki switches will physically accept standard QSFP transceivers in the rear stacking ports (since mechanically that’s all they are), but my understanding is it’s not supported, and in most cases won’t work - you’re pretty much restricted to the cables Meraki specify as ‘stacking cables’. With the Flexible Stacking on the MS425, Meraki fully support all the transceivers supported in the MS425 for stacking, so you can do long distance stacking if you want.   I’ve never tried to long distance stack anything other than a MS425 (which works fine), and above is consistently what I’ve been told by our local Meraki CSE team. ... View more

Thanks guys.   Exactly as I thought myself.   Will have to by qsfps so.   👍👍👍 ... View more

Thanks for that.   The print to pdf is just screenshots of each page and would have to include too many pages to cover one device.   It has to be something official from within the system not a script that the data would have to be verified on.   Really weird that there is no report or export of configurations (understand backup restore isn't part of their thing) but not able to get some sort of a device config report is a bit of a flaw like the vpn client situation.   ... View more

We've had Cisco all day long and an architecture which made it possible to update every single component with little to none downtime. And we were able to have specific devices to update to see how things went. In the office all is replaced by Meraki.  Seems ok but i really do miss some enterprise worthy things;  - Changing configs on vlans without interrupting other vlan traffic (On MS for example) - Changing ospf config without the possibility to determine the moment of clearing the proces by yourself. - No LACP on MX's - being able to update 1 or 2 devices without having to "clone" the network to specific subsets - being in control of which version you exactly want. You only have stable, release candidate and beta and no choices in between. - Advanced logging from the gui so you don't have to contact support to have some logs which you would normally see yourself (Like the exact reason why a failover was triggered on the MX)   - etc etc   So for beginner network admins or system admins things seem sufficient and graphically logic, but I am more flexible with Cisco.     ... View more

Just to add to what Bruce said: make sure you configure the Ping-checks on both ends. Both sides must use the p2p link *or* the s2s-vpn. Otherwise you get asymetric routing and the traffic will be dropped. Another possibility: If your internal switches support these connectivity-checks or a dynamic routing-protocol *and* you don't need any filtering between the sites, then you can terminate the L2-link on an internal switch. ... View more

There is a setting at the organization level to adjust the idle timeout.   Organization => Settings => Idle timeout     If you uncheck the checkmark you probably will stay logged in (need also to test it).      hope this helps roger   ... View more

Thanks for that.    Had a radius setup before so must see about setting that up.    The AD setup in meraki seems a bit pointless.  ... View more

I switched them over at lunch time.    Only dropped 2 pings.    Dropped a zoom call for 5 seconds which was great.    Thanks everyone.    Ye all so helpful.      ... View more

LACP does not work well with number of uplinks different than 2, 4 or 8. So basically you need to figure out depending on the application needs how much the oversubscription ratio should be for every stack. Normally in Cisco design documentation the normal approach was to have an oversubscription of 20 : 1 from access layer switching to distribution (or in your case collapsed core).  This means for every 20x  1GB access port you need at least 1GB uplink.   So if you don't expect much traffic on your network you can round down: So for a 48 port switch, account for 40 ports and you would need 2x 1GB uplink.  However stacking changes that so in a stack of two switches you should go for at least 4x 1GB and beyond that start accounting for 10GB uplinks. So if you can afford two 10GB uplinks per stack you should be able to stack up to the full 8 switches per stack.  I'm not sure if the cpu on the lower end switches do nicely with a large stack.  I remember in the catalyst world that stack over 5 2960x switches meant a slower responding CLI. And like Philip and Bruce alluded to: for access switch stacks, keep your stack inside one closet.  ... View more

Remember that the config you apply is applied 'to the dashboard', which then pushes it down to the device, once the two have trusted comms.   You will indeed need to make sure that whatever is upstream of the MX, by way of NAT (your 5G router) and firewall rules enables / allows those comms.   Dashboard advises you what you need to permit, under Help > Firewall info.   If you're uplink comes via a mobile network, beware of the use of carrier grade NAT, by your mobile network provider, if you need to get VPN working to your MX. ... View more