None of the 4 other engineers I contacted in support said it could work unless I either do non-splash radius or I get the failover option by getting new firmware. I'm taking their words over yours, because they have actually done packet captures on my network, tested things with me, and you have not.  ... View more

I'll start one more case, mention that you think it's possible, and I'll report back my findings.  ... View more

Support told me why it's not working in my environment--that this will not work with non-splash radius--that in this configuration it doesn't matter what's in slot #2 if slot #1 is down. It just keeps sending packets to the first one and doesn't try the second. I had one of them tell me to submit a feature request.  ... View more

I've started a case with three different people in Meraki support, and every time we were unable to make it work. The most recent call, they said it's because Radius for splash supports failover and standard radius does not. He did a packet capture and found that the packets were not even hitting radius server in slot #2, but still hitting #1 only, even though #1 was down.   "If the list of multiple servers didn't function a list would be pointless to have in the first place"   Oh, I wholeheartedly agree. And yet it's there in the non-splash radius setup.  ... View more

It's actually just an MR32. We have a lot of MR32's with locked firmware on this network(and we don't have the budget to upgrade at the moment), so we're not going to be seeing those newer options for the time being. I think I'm just going to set up a radius proxy server, have Meraki point to that, and do the failover/load-balancing functionality on our side.  ... View more

Interesting, but the Meraki support person I just talked to on the phone said it was the fact that I wasn't running Radius for splash page--that failover only worked in that radius configuration. Not sure who to believe now.  ... View more

Ok, so, I contacted Meraki about it. (a previous attempt with them failed to ascertain the issue) The problem is not on our radius servers as confirmed by them. The problem is if you're using Radius and not using the splash page option, the 3-server order in options is irrelevant. Radius failover functionality in this configuration simply doesn't work. I'm putting in an official request for them to add failover support.    The whole reason I'm exploring the radius server route is to escape the splash page, because the splash page won't always trigger for apple devices, which comprise the majority of our clients. That was the subject of a case with Meraki with many packet captures. The conclusion there by Meraki is that apple doesn't want to share certain information that would aid Cisco in creating a splash page that always triggers for these devices.  ... View more

It's pretty straight-forward that's how it should work. I read the documentation. It just doesn't work that way which is why I'm here.    Like I said, I have two working radius servers. If I put either in the #1 slot, I can connect and authenticate just fine. If I stop the service on #1(to simulate an outage), #2 does NOT take over regardless of which radius server it is. The connection on the client device fails(can't connect to SSID)   "the fallback option" This option is NOT in my options on the Access Control page. It's in the documentation, but I don't see it anywhere including advanced Radius options.  ... View more

I did. There's no documentation that says any options related to failover are found or configured in that section, so I wouldn't know what to change there. Which is why I'm asking here.      ... View more

I'm painfully aware of that fact, lol. In all of my efforts trying to get this to work, I've since learned how to set up apache servers, get certificates working, and a bunch of other interesting stuff. I just can't get this cmx receiver to work with Meraki.    What's weird is there was some bug where Meraki was actually talking to my http server and sending me JSON dat despite it being http. It was basically working, but then it stopped working days later for some reason.  ... View more

I have support, yeah. I've had many cases with them, and I have a multitude of API-related stuff working. For some reason, they won't help with this specific thing.  ... View more

The receiver is configured correctly according to this:   https://developer.cisco.com/meraki/scanning-api/overview/#validator   I receive the validator string that matches the one in the Meraki portal when I navigate to the URL.    There are no errors in the log for the cmx receiver.    I don't know what the below text means, though:   "You can also refer to your endpoint application/service vendor for documentation and troubleshooting assistance."   There is no vendor to talk to or get support from. It's just Meraki(who won't help me with this), me, and this open source cmx receiver that was included in their resources for setting it up.  ... View more

Yeah, I actually learned to do that and got it working on an Apache server, which was cool. Now, I just need to find out how to get the cmx receiver to utilize it.  ... View more

I see I see, ahh ok I get it now. Thanks for your help ... View more

I'm so close to wrapping my head around this, so bear with me if you can. I just want to break this down to the simplest possible components, because I don't know Python(will eventually be in Powershell), and right now just using this: https://developer.cisco.com/meraki/api/#/rest/api-endpoints/clients/get-network-clients So, I make the initial call for 1000 clients per page and I get this header.link <https://n11.meraki.com/api/v0/networks/N_555555555555555/clients?perPage=1000&startingAfter=a000000&timespan=604800>; rel=first, <https://n11.meraki.com/api/v0/networks/N_555555555555555/clients?perPage=1000&startingAfter=ka1710e&timespan=604800>; rel=next Now, I think I get the logic here. I'm supposed to now enter startingAfter=ka1710e in my next query, so that it starts at that page and gives me another, and so on. Problem is, when I do that, here's what I get next in the header.link <https://n11.meraki.com/api/v0/networks/N_55555555555555555/clients?perPage=1000&startingAfter=a000000&timespan=604800>; rel=first, <https://n11.meraki.com/api/v0/networks/N_55555555555555555/clients?perPage=1000&startingAfter=k17db29&timespan=604800>; rel=next This data confuses me. Shouldn't the first link be ka1710e and the second by something much further along than what it is? ... View more

Thanks, this is what I needed and I like it much better than trying to specify multiple time ranges. The 'link' header info had 2 URLs and that contains both pages of the users which I can then put into my function and extract the data from. ... View more