About NolanHerring

NolanHerring

I'm sure some have. I have migrated some small sites before myself. Do you have any specific questions regarding if someone has done so?

NolanHerring

The 3rd radio is the one that should be used for packet captures like that. I would open a case with support as this seems like a bug, with the MR45/55 being new models on beta code, also try 26.5 to see if that helps.

NolanHerring

@pjc wrote: Same here, issue with MR16 and a specific vendor's network card. Spent months working with support, and they indentified the problem being introduced in firmware 25.x. Doesn't affect any other model of AP or other nic vendor for us Could have told you that lol Latest 24.X code had MR16s working fine. 25.X introduced some issue. The easy fix for Meraki is to allow clients that still have MR16 (possibly MR18 too) to be able to still run that latest 24.X code. Same principle applies for cisco WLCs, there is a 'latest code' for specific hardware version, not sure why Meraki doesn't follow the same process.

NolanHerring

Upgraded my lab to 26.5 just now and there she blows !

NolanHerring

Dropping this here for others to find: https://documentation.meraki.com/MR/Access_Control/IPSK_with_RADIUS_Authentication

NolanHerring

https://documentation.meraki.com/MR/Access_Control/IPSK_with_RADIUS_Authentication

NolanHerring

You'll want to use the 'Make a Wish' button within your dashboard as well. 😃

NolanHerring

Not sure if you can but this is the only command that I know of: https://api.meraki.com/api/v0/networks/:networkId/ssids I'd have to test it, because I'm not sure if it even shows you the PSK or not But if you do a GET to get all your networks, then parse out the networks, then run that command above to get all the SSID's for each network

NolanHerring

There currently is not an easy way to do this. You have to go to Network-Wide>Clients and you can see them there. Either filter by their subnet, or look for the following ICONs: (connected or not connected).

NolanHerring

Basically you choose which VLAN's are 'allowed' across the trunk. Make both sides of the trunk match the allowed vlan settings.

NolanHerring

I meant you could change it to 1 day, it will force everyone to change their passwords, and then after, change it back to whatever you had before. 90 days or longer or disabled etc.

NolanHerring

Round about way would be to go to Organization>Settings>Security Change Password Expiration to 1 day

NolanHerring

There isn't any option that I am aware of to delete a current lease, you'll just have to wait for it to expire naturally. As for OPTION 66, you should have the ability to change it from IP or TEXT, depending on your needs, on the DHCP options for the subnet in question.

NolanHerring

You'll have limited ability to see this information, but this is what your looking for I believe: https://documentation.meraki.com/MR/Monitoring_and_Reporting/Hostname_Visibility As for access to LAN and blocking WAN, is this for a single client? Or an entire subnet? All clients? You can use Group Policies to lock down what clients can access (or not), or you can simply use VLAN Pruning on the TRUNK uplink, so say on a switch you have VLAN 500 created only on the switch, and you don't allow that through the trunk uplink to your MX for example. That would give you layer 2 for devices on VLAN 500 (basically just local switching like any other switch).

NolanHerring

Well that design seems flawed, so I would look to fix how you have it setup so you do not have to worry about this in the future. Cloud connectivity shouldn't have any impact on production (from the LAN perspective). You just won't be able to configure things. That being said, I think if you access the local status page you'll be able to do what you want I believe: https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page

NolanHerring

Where do you see that also cause i can't find release notes showing the month of September =(

NolanHerring

Well that depends, are you relying on the auto radius testing to be a monitoring tool for your radius server? Then I would agree 😃

NolanHerring

Here is the process for the radius requests: https://documentation.meraki.com/MR/Encryption_and_Authentication/RADIUS_Issue_Resolution_Guide This is specifically saying for MR, but I have a feeling it also applies for MS: https://documentation.meraki.com/MR/MR_Splash_Page/RADIUS_Failover_and_Retry_Details

NolanHerring

If you change it from 'wpa-eap' to just 'wpa' does it work? Either they changed the value on the back end or you are right, its broked.

NolanHerring

You don't need to worry about the license for the spare/HA model as once you set it or buy it as HA SKU. The new controllers support SmartLicensing or something (have not messed with Cisco in like 3 years now so I am rusty) Either way, its not a cost you have to pay for, its part of the HA setup that it will automatically support the max number of AP's the controller supports for the HA unit

NolanHerring

Cisco WLC HA does not require licenses, since its role is HA However, pricing will depend on the model of WLC your looking at, but I've found pricing for Cisco to usually be more expensive, sometimes by a large amount, when compared to a 5 year setup with Meraki.

NolanHerring

I would confirm each AP is working correctly, you'll need to check each port that every AP is connected to, in order to confirm each port is correctly configured. Its possible one port doesn't have a VLAN allowed or something strange like that, which would be preventing 'some' clients from working and other not. Take a peek at the wireless health tab, do you see anything there standing out?

NolanHerring

If you have different organizations I believe you have to put that in for each one.

NolanHerring

Look underneath the CLIENTS section: https://api.meraki.com/api/v0/networks/:networkId/clients/provision { "mac": "00:11:22:33:44:55", "name": "Miles's phone", "devicePolicy": "Group policy", "groupPolicyId": "101" }

NolanHerring

Your 3750 (or any non-meraki device really, even cisco gear) is not managed or manageable through the dashboard. Your best bet is to replace that cisco switch with a meraki switch if you want that.

NolanHerring

Nolan Herring

Community Record

Badges