Meraki

Ryan_Miles · ‎Jun 13 2023

The BLE in MV is only for communicating with Meraki MT Sensors. For BLE communications with third party tags you'd want to look at using Meraki MR Access Points https://documentation.meraki.com/MR/Bluetooth/Bluetooth_Low_Energy_(BLE)

Ryan_Miles · ‎Jun 12 2023

I see the same thing when I check your org. I would recommend opening a Support case so they can confirm the issue and get Engineering eyes on it. By the way I don't have the same problem in my own org with a 9164 or other orgs. So, it might be something specific to your org/config.

Ryan_Miles · ‎Jun 9 2023

I have 2 gateways and 3 repeaters (and 2 offline APs). When I test RADIUS it shows 5 passes and 2 fails for the offline APs. So it is showing test results for repeaters. Perhaps you have something else going on. Have you opened a Support case?

Ryan_Miles · ‎Jun 8 2023

I can confirm RADIUS testing works from mesh repeaters. Repeaters don't have IPs themselves so they will use the IP of the gateway AP they're connected to.

Ryan_Miles · ‎Jun 8 2023

It's the client's mDNS hostname and dashboard prefers that over other potentially seen names via NetBIOS or DHCP. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Rename_a_Client's_Hostname

Ryan_Miles · ‎Jun 7 2023

Same experience. There was at least 1 question that had no correct answer when I took it.

Ryan_Miles · ‎Jun 7 2023

I'd suggest opening a Support case. But I have a hunch it might be the USB modem in your Oval HQ MX causing the alert. If possible you could disconnect it and see if the error clears. I don't think it's actually connected to the cell network from what I can tell.

Ryan_Miles · ‎Jun 6 2023

Pretty sure this is due to the recent bifurcation of the switch firmware into the MS & CS lines. It now shows up on orgs with 0 switches. Probably some validation process no longer catches it as the underlying code trains have changed. I'd open a Support case so they can log it as a UI bug.

Ryan_Miles · ‎Jun 2 2023

If the serial number isn't showing for org admins on the inventory page then it sounds like it's not claimed into the correct org. Hard to say without seeing it myself. If you want to PM the serial number of the switch I could give more guidance. Or, engage Meraki Support.

Ryan_Miles · ‎Jun 2 2023

Can you give more detail on what you mean about the switch showing on your side but not theirs? A device can only live in one org/dashboard.

Ryan_Miles · ‎Jun 1 2023

One approach would be add a column and use a formula like =B2- (7/24). In this example it changes the time to my local timezone which is UTC -7. When the result causes a date change it appears it would need some additional formula work to get it functioning.

Ryan_Miles · ‎May 31 2023

In my lab the MX is concentrator mode. So not a interface dropdown, but rather an open field to type a non default/native VLAN ID. But I don't think the behavior would be any different. In my usual setup I have the tunneled SSID drop clients into VLAN 600 (a DMZ subnet). In my testing this morning I added VLAN 90 to the switchport connected to my MX. Then for the IPSK and RADIUS tests I set VLAN 90 as the VLAN tag (IPSK) /Tunnel-Private-Group-ID attribute (RADIUS). For the RADIUS config you of course need to enable the toggle for RADIUS override for the VLAN tagging to work.

Ryan_Miles · ‎May 31 2023

Just tested using JumpCloud RADIUS and the VLAN attribute is also honored/working.

Ryan_Miles · ‎May 31 2023

Andrew I can answer the IPSK question. I just tested and the client does indeed honor the VLAN sent in the Group Policy when using IPSK. I would imagine a VLAN sent via RADIUS would also work fine.

Ryan_Miles · ‎May 26 2023

Nope. For example MR34 came out in 2013 and was 802.11ac wave 1. MR74 came out 4 years later and was 802.11ac wave 2.

Ryan_Miles · ‎May 26 2023

The 4 models of outdoor APs we sell today are the MR70, 78, 76, 86. The MR70/78 are basically outdoor versions of the entry level indoor MR20/28. The MR76 is basically an outdoor MR36 with various external antenna options. The MR86 would be roughly equivalent to the indoor MR46 again with various external antenna options. The entire AP family datasheet can help with all the info you need

Ryan_Miles · ‎May 19 2023

Maybe try upgrading the MX84 firmware. I see you're on 18.106. In 18.107 there was this fix "Fixed an issue that could result in DHCP leases not being provided by MX84 or MX100 appliances after upgrading to MX 18.1.05 or MX 18.1.06." And all your other MXs appear to be on other/older firmware versions than your MX84.

Ryan_Miles · ‎May 18 2023

Open a Support case and they will help you

Ryan_Miles · ‎May 16 2023

Correct, no EoX announcements for the MR70. However, if product longevity is your goal you should consider the MR78.

Ryan_Miles · ‎May 15 2023

I believe this is a known issue/limitation of the mobile app with SSO and network only camera admins. I suggest opening a Support case for confirmation and issue tracking.

Ryan_Miles · ‎May 13 2023

Only the MX85/95/105 have a PoE WAN port https://meraki.cisco.com/product-collateral/mx-family-datasheet/?file

Ryan_Miles · ‎May 12 2023

If they have static WAN IPs you'll need to account for that with a local status page config (unless it can get DHCP from the subnet then be changed to statics).

Ryan_Miles · ‎May 12 2023

Exactly as Brash stated. The PoE budget values are all listed in this doc. https://meraki.cisco.com/product-collateral/ms-family-datasheet/?file

Ryan_Miles · ‎May 12 2023

Claim the new MX serials into your org Disable HA which removes the spare from the network Enable HA and select the new spare serial Bring it online, let if update config and firmware and settle Force HA switchover from primary to spare using the swap button Disable HA again which would remove the old primary serial from the network Enable HA and choose the serial for what will be the new primary MX Bring it online, let if update config and firmware and settle Last, force HA swap again Enabling HA does cause a soft reset on both MXs and will interrupt traffic. So, you'll still want to do this all in a maintenance window.

Ryan_Miles · ‎May 12 2023

Meshing between MX and MR wireless is not supported. You can advertise the same SSID from a MX and MR, but it will not be mesh nor provide a coordinated roam/handoff.

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges