Meraki

Mloraditch

The schedule upgrades tab current firmware column should show a firmware version matching the version on the device status pages. The overview tab only shows every current version available it does not mean those versions have been applied to your networks. If you are saying the schedule tab and the device status show different versions AND it's not an instance where the device doesn't support the latest version, then there is some sort of GUI bug and you should open a support ticket.

Raul_Umana

I appreciate your comments. Best.

fruanolo

Since I want to introduce myself, but I don't know if I'm ready only with the ECMS that is in Cisco U

Mloraditch

You'd setup a group policy with the appropriate firewall rules to apply to it and apply it to that VLAN on the MX. Whether you want to connect the cable directly to the MX or trunk it to your switch and put an access port there is more a physical design consideration. It only being on the MX does provide a slight bit more security as you can prevent the VLAN from existing on the switches. No matter what the vlan does have to have it's gateway be on the MX for this to work properly. It can't be a static route to a L3 switch for example. Group Policy info: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies

Mloraditch

I'm not sure where that URL is from (perhaps an older version of the api?) but the API to update radius for Wireless is this one: https://developer.cisco.com/meraki/api-v1/update-network-wireless-ssid/ You have to do it per SSID. Org Wide Radius does exist but only for wired devices at this point.

rhbirkelund

I seem to recall, being told that it also shares the PMKID and PTKIDs, for Oppotunistic Key Caching. Unless I'm mistaken?

RWelch

Give your feedback (previously Make a Wish)

cmr

Configure QoS settings in the Teams admin center - Microsoft Teams | Microsoft Learn

BlakeRichardson

@JBOFL Meraki much like other vendors does not publicly release their roadmap

sungod

I use the getOrganizationDevicesAvailabilitiesChangeHistory endpoint, it does work. It has two separate documentation entries, one in Early Access, I'd guess the endpoint is being tweaked. https://developer.cisco.com/meraki/api-v1/get-organization-devices-availabilities-change-history/ https://developer.cisco.com/meraki/api-v1/api-reference-early-access-api-platform-monitor-devices-availabilities-changehistory-get-organization-devices-availabilities-change-history/ Using device availability is the option I'd recommend. You do need to periodically grab the status 'now', then you can use the change history to calculate from that point. This gets current status, updated every 5 minutes... https://developer.cisco.com/meraki/api-v1/get-organization-devices-availabilities/ If you only want to check site reachability [defined as an MX responding], you might find it simplest to just ping your sites every 60 seconds.

annmarie24us

Thank you for sharing this is interesting about the noise level.

Stephen_P

We've been getting weekly random reboots on our MX450 with the 18.211.4 firmware. I wonder if this will fix the issue. We have a case opened with support who are actively troubleshooting the issue. Has anyone else been experiencing the same issue?

Mloraditch

The 9800-40 is an older model for the previous generation of 9800s. 9800-40s are monitorable: https://documentation.meraki.com/Cloud_Monitoring_for_Catalyst/Getting_Started/Cloud_Monitoring_for_Catalyst_Wireless_Requirements The CW9800M is supposed to be monitorable per the Cisco Data Sheet: https://www.cisco.com/c/en/us/products/collateral/networking/wireless/wireless-lan-controllers/catalyst-cw9800m-wireless-controller-ds.html But as best I'm aware that feature is not live yet. You may be able to get info from your account team on an ETA. If you are looking at purchasing, I would definitely get the CW model and then just waiting to onboard to the dashboard once that's available. The 9800-40 has an announced End of Sale date and the CWs are the recommended migration path.

kruso_tech

I wasn't expecting a solution so soon (<5min after my post). Thanks for your help.

PhilipDAth

Major issues should also be notified here: https://status.meraki.net/ You can also sign up for notifications on this page.

Nova-th

Ok, finally figured it out. The client VPN settings had "Dynamic Client Routing" setup. Somehow that was breaking it. Once disabled the client's SQL application worked as expected. It just goes to show you, challenge your assumptions! Thanks for everyone's help. Cheers, Mike

Ryan2024

Personally? I'm just trying to reduce the extra traffic caused by broadcasting a (seemingly) superfluous SSID.

pematthe

Thanks for the replies. As I suspected. For info for others, we are going with the dedicated local API accounts and converting actual dashboard users to SAML/SSO I had already come up against the issue with changing the "username" attribute after converting our first user to SSO. Very useful to know.

ScottMcD

The only code support for 9500 series is 17.12.3. Even then it keeps dropping the connection to the dashboard, which I have an open ticket with support. was hoping this is getting resolved in the next beta . Or an update on when the 9500 will be able to upgrade their IOS to a higher level supported by Meraki Dashboard would be nice.

MerUser874

I would love to get another backup ISP but this one took a year, even with multiple hiccups with our current ISP. I think I will try moving the Primary uplink to WAN2 initially and then after testing possibly physically move this to WAN1 when our current circuit is disconnected. Thanks!

GIdenJoe

I believe the true Meraki lingo has always been: Virtual stacking = just putting all the ports on one page (great feature, but nothing to do with the switches itself) Physical stacking = backplane stacking with two cables Flexible stacking = having switches transform regular ports into stacking ports which in Cisco classic is actually called virtual stacking 😜 Lovely confusion there.

Mloraditch

A quick google says this usually means the shared secret is mistyped somewhere whether in the Dashboard or on NPS. As you only type it once on the dashboard for all devices (per policy/ssid) and you say some authentications are working I'd check your NPS clients in NPS.

Dunky

It looks as though MS17 introduces RSPAN: New feature highlights Support for MS150 devices DOM (Digital Optical Monitoring) Intelligent Capture RSPAN and VLAN Based SPAN SmartPorts

RWelch

Yes - a better document for your consideration indeed!

BlakeRichardson

The easier option might be to enable IP filtering on the printer itself. Just make sure you include your IP so that the device can be managed and you don't lock yourself out.

About Mloraditch

Mloraditch

Matthew Loraditch

Community Record

Badges