30.7 Update Breaks RADIUS

[jpeter]

We just recently upgraded our eligible APs to 30.7 from 30.5. Immediately afterward all 802.11 auth attempts to our RADIUS servers failed. Thus, we rolled back to 30.5. Has anyone else encountered this issue? I see in the 30.7 release notes a reference to a fix for RADIUS requests when if they had exited the primary management interface if an AMI was defined. In our environment we don't have a AMI defined.

[jpeter]

Just read it (pun intended). You have got to be kidding me. Our affected SSID is in slot 9. Now I haven't fully tested it yet, however, if this is the reason, this has to be one of the most absurd bugs encountered in my entire 30 year IT career. I echo the sentiment of another post prior "Doesn't anyone test anything anymore?"

[ChristianHenn]

Our affected SSID is in different templates in different slots...

[JMI]

I now found they actually updated the 30.7 release notes a couple weeks back. Not that it would have made much of a difference to us, we only have three active SSIDs. But at our main site (of course) one of them was in #9, due to the presence of various disabled legacy networks. No RADIUS on that SSID, by the way.

One might be forgiven for thinking Meraki could have issued a warning to accounts where they saw this particular configuration, them having access to global inventories and all.

[Brad39]

So looks to be an update in the "Known Issues".

None of our affected networks are in slot 9 SSID, however they are in Slot 10. Meraki has updated the known issue to now be SSID 10. We are going to look at moving these from that SSID slot to another one in the next week or so and re-test 30.7...

[redsector]

Hello, where can I see the "slot"-number?

[Brad39]

Under the network, Wireless > Configure > SSIDs and then click show all my SSIDs. Left to Right is 1 to 15

[DainBrammage]

No, in GUI left to right it is 0 , 1, 2 ,3

[DainBrammage]

https://developer.cisco.com/meraki/api-v1/get-network-wireless-ssids/

Left to right in GUI is slot 0 , slot 1, slot 2, etc

[Brad39]

Sorry you are correct!

Pulling it via API it’s “Number” 0-14 and via the GUI “Unconfigured SSID” 1-15.

The terminology is prob not the best.

Sorry!

[kenneth.thomson]

we only have 4 ssids and the radius issues is there . we downgraded firmware and used meraki proxy on the MRs but also had to upgrade firmware on the MX

[redsector]

Which MX firmware had you bevore and after upgrading?

[kenneth.thomson]

MX 18.211.2 - 18.211.3

MX - 75

[redsector]

Thank you, very interessting. we will check it here, we also have MX75 and firmware MX 18.211.2

[kenneth.thomson]

it does seem like this had a bearing whereas our mx100 worked without issues.

[JMI]

That's weird, so this bug is moving across the configured SSIDs? In our case it was definitely the 9th SSID that was affected (Default name "Unconfigured SSID 8" as they start counting from zero).