Meraki

Ryan_Miles · ‎Dec 16 2021

What model(s) AP? What firmware? Happening on all SSIDs or just some? Happening to all clients or just some?

Ryan_Miles · ‎Dec 16 2021

All Meraki EoX info is here. And the MS125 is not EoS/EoL. It's a fairly new product.

Ryan_Miles · ‎Dec 13 2021

Do you have remote device status pages enabled? If so, you should be able to reach the local status webpage via any reachable/route-able LAN IP on your MX. https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#Controlling_Remote_Access_to_the_Local_Status_Page

Ryan_Miles · ‎Dec 9 2021

1 - Understood 😉 2 - Unfortunately uptime is not exposed in dashboard. Please keep submitting feedback that it should be visible! 3 - Support can see the uptime/reboots. So, I'm not sure why/what transpired in the case.

Ryan_Miles · ‎Dec 9 2021

Not sure why it's not coming online. Try the factory reset first. If that doesn't help please open a Support case and they'll be able to get it resolved for you.

Ryan_Miles · ‎Dec 9 2021

Looks like the AP is connected to port 1 of your MS120 switch correct? Do you have physical access to the AP? If so, can you do a factory reset on it? https://documentation.meraki.com/MR/MR_Installation_Guides/MR76_Installation_Guide#Factory_reset_button

Ryan_Miles · ‎Dec 9 2021

Click on my name and click send message

Ryan_Miles · ‎Dec 9 2021

All 8 in the stack did reboot on the 6th. Not sure what the cause was. If you open a Support case they may be able to determine root cause. Also, you should update to the current stable firmware. You're running a beta from over a year ago.

Ryan_Miles · ‎Dec 9 2021

PM the AP serial number and I can take a look

Ryan_Miles · ‎Dec 9 2021

If you do a motion search for that time period does it return the thumbnail results? If so, you should be able to download the screenshot. I just did that for one of my MVs and motion events back from June. The video is no longer available as expected.

Ryan_Miles · ‎Dec 8 2021

If the video has already purged from the camera and you're not using Cloud Archive then it's no longer available

Ryan_Miles · ‎Dec 8 2021

Not tied to font update. There was a bug discovered a few days back and it's being worked on. It will return once resolved.

Ryan_Miles · ‎Dec 6 2021

Details of Connection Monitor here The Connection Monitor timers aren't configurable in dashboard. If you have a Meraki SE that supports you they can help adjust back end timers. Or, contact Support and they should also be able to help. That said if your MX-C is never failing over to cellular that leads me to believe something is going on and this isn't a timer issue. Again, that would be a great opportunity to engage Support.

Ryan_Miles · ‎Dec 6 2021

In the event of a soft failure it can take up to 5 mins to fail the wired link. Have you waited longer than 5 mins to verify it does eventually kick over to cell? If you contact Support they might be able to help shorten the timers for soft failure detection.

Ryan_Miles · ‎Dec 3 2021

Using the Local Status Page yes. They're all set to auto by default.

Ryan_Miles · ‎Dec 1 2021

Gotcha. As you've seen if you just leave a value out when using API it should ignore/not change the current value. You'd probably need to use Runner in Postman and use a source spreadsheet with a column of all the switch serials. I've not tried this specific scenario, but I assume it should work. If you haven't used Runner you'll need to read up on it and do some testing to get the basics down.

Ryan_Miles · ‎Dec 1 2021

As Russ said it's the MDNS name. If a custom name has not been given to a client in dashboard MDNS is the next value to be used if detected. The order dashboard uses to show the client name is here. If you'd rather have DHCP above MDNS (like I would) please click the give feedback button in the lower right corner so Meraki can hear your input.

Ryan_Miles · ‎Dec 1 2021

I assumed you were using static mgmt IPs based on your initial question. If your switches are receiving DHCP IPs then just change the supplied DNS server IPs in your DHCP scope config. What is providing the DHCP?

Ryan_Miles · ‎Nov 30 2021

You'd need to use the API https://developer.cisco.com/meraki/api-v1/#!update-device-management-interface

Ryan_Miles · ‎Nov 30 2021

If you click the Allow more connections link you can enter lines for specific protocol, ports, and remote IPs to allow

Ryan_Miles · ‎Nov 30 2021

That is the recommended way and we have many customers using it.

Ryan_Miles · ‎Nov 30 2021

You don't need no nat feature. In the 1:1 NAT just enter the same IP in the Public and LAN boxes.

Ryan_Miles · ‎Nov 28 2021

Local LAN is a default object for subnets 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16. So you want this set to Allow so clients can access internal resources. If you want to lock things down you can add more explicit rules or do it at the MX.

Ryan_Miles · ‎Nov 28 2021

On page Wireless > Firewall & traffic shaping is the first rule showing as Deny or Allow? It needs to be Allow if this is an internal/employee SSID.

Ryan_Miles · ‎Nov 28 2021

That is tunneling the SSID to your MX. That is typically used for remote teleworker deployments where the AP is remote and tunnels over the internet back to the MX. I wouldn't use that mode in your topology.

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges