SFOS 20.0.0 GA-Build222 DHCP ISSUES

I had the exact same problem and did the same thing.  Went back to SFOS 19.5.3 MR-3-Build652 and everything works fine.  Is this something specific to SFOS 20.0.0 GA-Build222?  I am using 19.5.3 and don't see where to configure this.

Nope, nothing major it was a config thing - "Fine-tuned the DHCP settings with specific interface as it was configured as "all""

Can you give me some detail on how the DHCP was tuned.  I have added interfaces in Network ->DHCP and everything works in 19.2 but doesn't in 20.0.  I am missing where DHCP is configured as all.

Hi OldMtnGoat Can you please share your DHCP congratulations manage page screenshot to review the details? ( i.e. Configure > Network > DHCP snapshot). 

These are all separate physical ports

Hi OldMtnGoat  Thank you for sharing the DHCP details. Can you please share Network > Interface config details which cover Port1, Port3, Port4, Port5, Port6 network, and subnet details? 

Hi OldMtnGoat Thank you for sharing the network interface details, I would suggest logging a Support case to investigate this issue further and to confirm the cause or what is creating an issue for DHCP. 

Before I log a support case I am going to re-do my subnet addressing.  I am going to us a /21 scheme instead of a /27 scheme.  This will separate my physical addresses more and allow more addressing.  This is going to require more work because i will have to go adjust all static addresses to the new scheme.  I will wait till the weekend to do this because I don't want to disrupt users with much downtime.  After I make this update and do a backup I will try the update again.  My new subnet mask will be 255.255.248.0. 

Hi OldMtnGoat Noted with thanks, in case of any issue with DHCP IP leased after re-do subnet addressing, please do not hesitate to log a support case to investigate it further, so the support team may review TCPDUMP, drop, PCAP, and other relevant info to drill down the issue further. 

Hi OldMtnGoat Noted with thanks, in case of any issue with DHCP IP leased after re-do subnet addressing, please do not hesitate to log a support case to investigate it further, so the support team may review TCPDUMP, drop, PCAP, and other relevant info to drill down the issue further. 

I reconfigured the interface in ver 19.5.3-652.  That was definitely not fun.  It got locked twice and I had to do a  factory reset and reload backups.   I made sure there was no overlap in the subnets.  I think the reason it got locked up is because I missed  checking for the same subnet on two different physical ports.  The current configuration is shown below.  I used CIDR /24  on all ports and gave them a range in DHCP.  I may have had some overlap before, but there is none now.  All of my devices have access and I can from print from IPhone and Android using apps; they are on different subnets then the printers.  I had a lot of static addresses that needed to be adjusted so there was some significant down time.    With the new addressing I have tons of space (more that I will ever need) to add more devices.  After I verified that everything in ver 19.5.3 worked I upgraded to ver 20.0-222.  So far ver 20.0-222 is working, it only been up a couple of hours.  No locked ports this time.  In the previous scheme I tried to split up the same subnet  on several different ports.

My static addresses are set up in neighbors ARP-NDP,  not DHCP.  I only have one DHCP static IP.

Hi OldMtnGoat Thank you for sharing the update with us and I hope things are fine until now with DHCP with V20..!