yes that worked only just managed to check as in the office so could console on ... View more

Hi, interest with this using MR46, we will have plan to implementation MR46 at small office about 7x7 m, and will try  using this device, as your experience its better place on ceil or on wall to get better performance (throughput) and also how tall you install this device.   Thank you  ... View more

Also check if there are no dfs issues involved. https://documentation.meraki.com/MR/Radio_Settings/Dynamic_Frequency_Selection_(DFS)#Verifying_DFS_Events ... View more

Also think of Meraki ACL's as VACL's, not RACL's as one would expect.  You also have a 128 ACE hard limit so you'll have to be quite coarse in your rules.   This hard limit is a reason to consider mixed environments where you have a Catalyst distribution pair of switches to allow for complexer ACL's and VRF support and keep the access switch Meraki to take advantage of the dashboard. ... View more

That makes perfect sense now 😉 ... View more

Hi @GIdenJoe ,   I am not clearly sure about firmware bug. I'm running version 18.107.2 in my organization, in this scenario if my MX lost connectivity to Meraki cloud and the Internet port on MX is unplug, this issue won't happen but if WAN is still plugin with the Internet port in MX, it will revert to the previous configuration after losing connectivity to the cloud more than 7 days. ... View more

100% agree. I would also review the STP Guard settings on all the ports to make sure it is intended and in alignment with Meraki documentation and best practices. And as always, remember that MX firewalls do not participate in STP.   Configuration: https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Configuring_Spanning_Tree_on_Meraki_Switches_(MS) https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Spanning_Tree_Protocol_(STP)_Overview <- this links to a basic eLearning module that might be helpful, esp. if there are other switches in your network   Design docs: https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MS_Switching/General_MS_Best_Practices https://documentation.meraki.com/MS/Meraki_Campus_LAN%3B_Planning%2C_Design_Guidelines_and_Best_Practices   ... View more

Good luck to all of you, there are some real experts out there... ... View more

Hi,   Thanks for all insight and link that provide, little clear about my curious about antenna.   Regards, ... View more

There is a MS250 in play here, and a spare MX68CW, so after looking around I found this: https://community.meraki.com/t5/Security-SD-WAN/How-to-turn-MS120-into-WAN-breakout-for-2-ISPs-and-2-MX250s-in/td-p/186160/jump-to/first-unread-message Looks like I'll just do this. Thanks for the help. ... View more

On the Aruba switches you can verify your VLAN config as follows: - show vlans ports <portnumber> detail (then you will see ALL VLAN's on that port) However if you are using comware based HPE switches you can do: - display interface <interface number> (usually gigabitethernet 1/0/1 format a bit like a Catalyst)   Also on Aruba switches you can define a vlan as voice and that should also be visible in that first command.   So if you are sure each port only uses 1 data vlan and 1 tagged voice vlan you can use an Access port on Meraki with a voice VLAN.  If not then you need to use a trunk port with all necessary VLAN's allowed. ... View more

You don't have any direct interfaces on the LAN side of an MX.  However defining a VLAN and having that VLAN on an access port on the firewall or as native and only VLAN on a port is basically the same as defining an "interface" on the other types of firewalls.   Do mind that indeed some needed features are missing like the spanning-tree support and port-channel/LACP support as alemabrahao mentioned. ... View more

@networkingat20the Meraki official stacking cables come in 50cm,1 meter and 3 meter variants. I have found that the 50 cm stacking cables can be connected between two switches on the back ports if you have no more than 4U between them. So if you for example have a rack with a few switches and each switch is no more than 4U apart you can stack them by using 50cm between each switch.  In case of maximum 8U you can use the 1 meter cables.  However you still need to complete the loop by connecting the bottom switch with the top one again and usually you need a 3 meter cable for this. ... View more

On the wireless front we have only seen new models being supported with both persona's. I believe both development teams need input in the hardware to create a fully compatible model with software support. ... View more

Thanks so much again everyone! Be sure to check out our other Wireless Fundamental Implementation courses on the learning hub about Deploying, Building, and Securing (coming soon!) your wireless networks.  ... View more

Same question here.  We were planning on mandating Meraki at client locations, but given this news, I'm actually having to back-track and investigate alternatives to present to clients who want VMWare virtualized firewalls.  Kind of sucks since it was nice to have everything in one dashboard, but this really is a deal-breaker for exclusivity since it limits flexibility so much. ... View more

Interestingly, it looks like the devices will still work (without management or monitoring) after the 30 day grace period when there is no active subscription:   After the 30-day grace period and the subscription is inactive all networks bound to that subscription will come to a disable management state. Disable Management Expected Behavior The following is a description of the expected behavior for the devices on networks that experience a disable management event. Devices in the network will preserve their last known license-compliant configuration prior to getting into a disabled state Administrators will lose the ability to configure the devices via Dashboard (GUI or API) Configuration data will not be displayed via Dashboard (GUI or API) Monitoring and health information  will not be displayed via Dashboard (GUI or API) Devices will not have access to customer-initiated firmware updates from Dashboard (GUI or API) Customers will not receive support for devices ... View more

For MX68's, since not very long you can see what client is connected to what MX68 port in the Clients overview. ... View more

Looks like a false positive then.  Perhaps it can be that the MX does not reach dashboard fully via WAN2 but the rest of the internet works fine causing the VPN traffic to work too. ... View more

A device behind an MX will be NAT'ed unless it is in concentrator mode.  In that last case you will not be able to support it.  Otherwise in the normal routed mode your ESP endpoint will just encapsulate ESP inside UDP port 4500.   The MX itself when making IPsec VPN's will always use ESP for encapsulation. AutoVPN is proprietary and does not use standards based IPsec. ... View more

or, just flick the allow all any any to deny and see what breaks The story of my life. 🙂 I actually did look up this subject before I asked again hoping that they had added it to the API and I just couldn't find it. I'd bet you it is there but is expensive to execute so they just don't document it. ... View more

the output you see is taken from the API response in the Postman application. ... View more

Have you tried change the ip setting in the starlink  webpage?  change it from default  to "Private IP"     ... View more

It likely is allowed as the 6 GHz radio is default disabled and will be enabled only based on regulatory availability. For ETSI, I would likely still choose the MR86, although the CW 9163E is fascinating. But in the EU, the device will likely go through the next refresh cycle before the EU approves it ... ... View more