MX-100 updated to Firmware MX 16.16 I encounter DHCP Problem on all switches.

[D2Flores]

After I updated MX-100 updated to Firmware MX 16.16 I encounter DHCP Problem on all switches only after 12 hours. Do you also have these issues?  

[cmr]

Are the switch management interface IPs via DHCP, or is the problem with client in VLANs not getting IPs from the MX DHCP server?  We have an MX64 dishing out switch management and client IP addresses that was upgraded two days ago and that is still working.  We upgraded from 16.15 

[ww]

Is it a warm spare setup?

What was the previous  firmware version?

[D2Flores]

All switches have a specific VLAN and all DHCP stopped working.  The previous firmware is MX 15.44 updated to MX 16.16..

[PhilipDAth]

I've had zero issues on 16.16.

Anything interesting in the MX event log?

Anything interesting in the MS event log?

What does the MS local status page say when it is not working?

If you plug a notebook into the same VLAN can it get a DHCP address?

Does the MX DHCP scope show it has plenty of spare capacity?

Does a packet capture on the MX for DHCP packets show anything interesting?

[Lefteris]

Hello

After upgrading on 16.16 firmware update, all users lose connectivity to azure app server (ERP program) we receive an error from app that no messages can received on port [8110]. Something changed to default policy.

Problem temporary solved with rollback.

Product model MX100