Anyone observed DHCP Response problems on MS130 Switches with FW 18.1.1 ?

[Holli69]

Hi,

I've updated a few site with MS 18.1.1 Firmware. I have observed that all wireless clients connected to CW9162I didn't get a DHCP addresses from the DHCP Server, but this happens onyl on MS130 Switches. All other MS225, MS250, MS425 with same AP's are working well.

After that I roll back to MS 17.2.2 and all wireless clients can connect without any problems and got a valid IP Address from the DHCP Server.

[PhilipDAth]

Can you share a screenshot of the switch port configuration for the CW9162I?

[RWelch]

I’m running MS 18.1.1 on MS130s with APs but I’ve not experienced any DHCP response issues/problems.  My APs are all running MR 31.1.18.

By chance did you attempt to recycle the port?  I don’t believe the MS130 series has

Perpetual PoE which is what initially came to mind as a possible cause or hiccup.

What firmware are the CW9162Is running?  Are the CW9162Is in gateway or repeater mode?

If you happen to be using SecurePort, all the model switches you referenced are listed in the SecurePort documentation except MS130s (although the dashboard UI indicates SecurePort works on the MS130X series - documentation doesn't list MS130s support SecurePort).

[Holli69]

We are runnig FW 32.1.3 on all Access Points. All AP's are in Gateway mode and we are using SecurePort.

[rhbirkelund]

I would avoid running MR 32.x firmware for now, as there have been many reports of it not working that well. 

At least I've been having lots of roaming and authentication issues with it. 

[RWelch]

I had initially tested MS 18.1.1 with MR 31.1.18 and the MS130s series switches with SecurePort ON but felt performance was intermittent.  Once I toggled OFF SecurePort (because I have other MS120 series switches with PoE and APs), everything worked as expected.  

I did NOT open a support case but did elect to proceed without SecurePort.

[akh223]

We are seeing this on FW18.1.1 but with MS150 switches.  The interesting thing is that it isnt every client.  We see some clients getting DHCP, and some not.  We are using these in stacks, and I wonder if that is some of the issues with the MS150's.

[Holli69]

We have  configured 3 SSID's (VLAN's) for wireless devices. One SSID (VLAN) is working without any problems, clients get DHCP address, but the other two SSID's (VLAN) get "No DHCP response"

Switching back to 17.2.2 solve the problem.

[akh223]

Are you running any stacks?  I opened a case with Meraki this morning, and they confirmed that we were hitting a bug in 18.1.1 where the DHCP offer was not being forwarded to any other switches in the stack.  In our case, if the APs were connected to the switch or switches that contained the uplinks for the stack the traffic would pass normally.  If the AP was on a stack member that did not have an uplink, and was only using the stacking cables to connect to other switches, then the switch would NOT pass the DHCP offer message to these other switches.  Apparently, the bug was shown to be fixed in 17.2.1, but the support engineer I was working with thinks it was never added to 18.1.1 and is thus a regression for that bug.  We are rolling back code to 17.2.2 as we are hitting way to many issues with 18.1.1 code.  We were told to use it by Meraki support to fix another stacking issue we saw, so we are now having to abandon stacks for the time being until they get all this worked out for the MS150 line.

[RaphaelL]

There was a thread about this : https://community.meraki.com/t5/Switching/MS-18-1-1-First-Beta-New-Features-Fixes-Etc/m-p/281026

but it should be fixed under 18.1.1

I suggest you open a case to see if you are hiting the conditions and if you are really running the version.