Meraki

KH · ‎Oct 16 2024

Hey @AKANKWASA Can you verify if the cloud ports/IPs are being allowed upstream, those IP addresses can be seen under Help>Firewall info in the top right corner of the dashboard. Otherwise you can have someone browse to the local status page of the APs and download the SDB bundle from the device and upload that to a support case so that we can tell you what's going on. https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Out-of-Band_Log_Fetching

KH · ‎Oct 16 2024

Hey @CraigP Sticky MAC isn't supported on port profiles. Port Profiles are meant for bulk configurations and something like a unique MAC allow list per port is kind of counter-intuitive to a bulk configuration

KH · ‎Oct 16 2024

Hey @FlyingFrames Here is the most recent update:

KH · ‎Sep 4 2024

Hey @Richcarr It is stored up to a month, if its been past a month you won't be able to see it anymore, filtering by the last month on your switches, or the last month on the connectivity graph on the AP, or the last month on your clients page with the LLDP filter, should all be ways to see what was connected previously.

KH · ‎Aug 30 2024

Hey @AxL1971 The fact that it says not running configured version means that it failed to upgrade. You can expect the MS to try and upgrade at a later time. When switches upgrade they set a random backoff timer on them to reduce the chance of upgrading at the same time otherwise one might fail upgrading while the other one goes offline to upgrade as well. Its possible that they had similar backoff timers, or something else caused the switch to fail to upgrade.

KH · ‎Aug 30 2024

Hey @gabriel-ribba Content Filtering and Threat protection features will apply to Anyconnect/Client VPN Users. The Threat protection page mentions the following: In both IDS and IPS modes the following is inspected: all traffic between LAN and the Internet all traffic between VLANs

KH · ‎Aug 30 2024

Hey @Heino1 You will need to walk around with a spectrum analyzer to pinpoint it exactly. However, checking for common causes of 2.4 interference is probably easier. Look out for microwaves , cordless phones, and Bluetooth devices as a start.

KH · ‎Aug 29 2024

Hey @MisG We pull the information from the HTTP user-agent string, explained here: https://documentation.meraki.com/MR/Group_Policies_and_Block_Lists/Applying_Policies_by_Device_Type#Client_Identification Have the devices send an HTTP Get first and if it doesn't auto-resolve you can take a PCAP to see what they are reporting in that field

KH · ‎Aug 29 2024

Hey @RaphaelL Sometimes its just a matter of bringing things up. I have reached out to our Product team and they agree this should no longer show Beta and are now working internally to get this removed. As far as a timelime though, I don't really have one to share. Thanks for bringing this to our attention!

KH · ‎Aug 28 2024

Hey @252_Masked_Nett If you are referring to the Z3 itself ,a factory reset will clear leases off of the device. Otherwise, you can edit the DHCP scope from a /24 to a /23 for example, just ensure that the config changes were pushed to the device and the Z3 is up to date before changing it back, typically waiting 5 minutes between changes should suffice.

KH · ‎Aug 28 2024

Hey @wick Devices that end in -M come in Meraki Managed mode by default. You would have to migrate them first to DNA/CLI mode and then configure them as a monitor-only switch separately. Support can assist with Migrating to DNA/CLI mode. https://documentation.meraki.com/MS/Deployment_Guides/Getting_started%3A_Cisco_Catalyst_9300_Management_with_Meraki_Dashboard#Migrating_to_DNA_or_CLI_managed_mode

KH · ‎Aug 28 2024

Hey @Jahir_xmartek The MX does support hairpin routing: Documented here: https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_MX#Hairpin_Routing

KH · ‎Aug 28 2024

Hey Fernie, It would take some more information typically to troubleshoot via the Community page and it might be best to open a support case. That being said, error code 17 is an IEEE 802.11 error code which means: Association denied because AP is unable to handle additional associated stations This will typically happen in Meraki devices when client balancing is enabled and the AP tries to steer it to another AP but perhaps it fails to roam or doesn't support 802.11v . What happens if you disable Client Balancing under the Wireless>Configure>Radio Settings page as a test.

KH · ‎Aug 28 2024

Hey @Fanny Meraki's SASE solution, Secure Connect, can only be used within the Dashboard and is only compatible with Meraki. Cisco has another product called Secure Access which is more suitable for your use case: https://www.cisco.com/site/us/en/products/security/secure-access/index.html

KH · ‎Aug 28 2024

Hey @Rachel1 If you pushed the profile as removeable then you can remove it from the device and then try to reinstall it without the need to Factory reset. If you pushed a non-removable profile then a Factory Reset is likely needed here

KH · ‎Aug 28 2024

Hey @Thiandanai Per our documentation: Clients list data is aggregated over time and therefore the information is not ‘live’, thus there will be a slight delay to a client’s online/offline status. This data is automatically refreshed every few minutes. Wired clients that had transferred data in the past 5 minutes should appear online. Verify that the “Last seen” timestamp is within the last 5 minutes to ensure the client reflects the proper status. Are you seeing them offline for longer than 5 minutes?

KH · ‎Aug 28 2024

Hey @Lalana I am curious how/what method is used to run these calls. Meraki uses the API key for authentication and not any kind of certificate so it sounds like whatever application you are using is the problem. Can you run the same API call using Postman or in the browser?

KH · ‎Aug 27 2024

Hey @dhayes89 If you see it in the MAC table but not the ARP table it doesn't sound like the static IP address might have been taken by the MX or it might have been factory reset and doesn't have an IP. Are you able to double check the local status page to confirm the static IP exists. If it does, are your 9500-40X devices capable of taking packet captures, we would want to see what kind of packets MX2 is generating.

KH · ‎Aug 27 2024

Hey @Riser Is there any reason we can't use the switches and have a pruned VLAN(s) for the ISPs between both buildings to provide WAN 2 to both MXes from both ISPs?

KH · ‎Aug 27 2024

Hello Holli, We would need more information on your setup, was the MS250 migrated to the c9300 with the same exact configuration? Does the MS250 when working, use the same config as the C9300? Can you share the output of your Addressing & VLANs page from the MX as well as the Routing & DHCP page for your switches?

KH · ‎Aug 27 2024

Hey @zack3 If you need these on specific networks you can use the camera-only sensor admin section. Otherwise, to configure this Org-Wide you can configure a Org-wide camera admin:

KH · ‎Aug 27 2024

Hey @LeoAri Meraki AutoVPN does not require a Static Public IP if that is what you are referring to, obviously you will need a public IP on the ISP side to route out to the internet. As long as your MXes are online they can form a full mesh tunnel with each other via AutoVPN

KH · ‎Aug 27 2024

Hey @zack3 Did you set them up as network-wide admins or organization admins perhaps? Ideally you would want to configure them as Camera/sensor only admins which can be done through here: https://documentation.meraki.com/MT/MT_General_Articles/Camera_and_sensor-only_admin_(IoT_Admin)

KH · ‎Aug 26 2024

Hey @GIdenJoe The MS family datasheet specifies the different "routing capabilities" that each model has and mentions the DHCP relay for said models. Other models add static routes, DHCP server capabilities, dynamic routing, or VRRP. https://meraki.cisco.com/product-collateral/ms-family-datasheet/?file

KH · ‎Aug 26 2024

Hey @PhilipDAth To close the loop here, I have updated the KB with screenshots of the different states/errors to make it more clear when it has kicked in.

About KH

KH

Kamal Haidar

Community Record

Badges