DHCP stopped working – Ruckus ICX7150

I am using a Ruckus ICX 7150-C12 switch as a core switch for my home lab. It is running the routing code “SPR08092a.bin (UFI)”. There are two VLAN SVI’s(interfaces) and the switch is also acting as a DHCP server with following settings:

ip dhcp-server enable
!
ip dhcp-server pool vlan10
 excluded-address 192.168.10.0 192.168.10.100
 lease 0 6 0
 network 192.168.10.0 255.255.255.0
 option  3 ip 192.168.10.1  
 option  6 ip 208.67.222.222  
 deploy
!
!
ip dhcp-server pool vlan20
 excluded-address 192.168.20.0 192.168.20.100
 lease 0 6 0                                                      
 network 192.168.20.0 255.255.255.0
 option  3 ip 192.168.20.1  
 option  6 ip 208.67.222.222  
 deploy
!

Yesterday I was in the switch just looking at some show commands and verifying what commands are available specifically under DHCP Pool settings.

config t
!
ip dhcp-server pool vlan10

I used the command shown above to go under the DHCP Pool and then exited out. Towards the evening I realized that all the devices using DHCP in the management VLAN10 had lost their IP and would not get an IP address. I logged into the switch and ran “show runn” to make sure that the DHCP pool exists still, and I did not delete it by mistake. Next I confirmed that there are no issues with the ports and cables. MAC addresses of the devices were showing up on the ports, there was a link light and interface was up/up. Surprisingly DHCP on VLAN20 was working without any issues.

I ran couple of “show” commands to verfiy DHCP and noted something interesting:
DHCP server pool name : vlan10(pending)
Address Pool State: pending

• 

• 

As shown in the screen shots, VLAN10 DHCP pool is pending while VLAN20 DHCP Pool is active. Even though I did not make any changes to the pool only ran some show and help commands to look at different options, VLAN10 DHCP Pool changed its state from “Active” to “Pending”. To fix this I simply typed “deploy” and that made the VLAN10 DHCP Pool “Active” again as shown below.

• 

• 

I tested it few times and it looks like if you have a DHCP Pool configured in a Ruckus switch. When you access the DHCP Pool using the command below, it will de-activate that DHCP Pool and you will need to redeploy it. So before exiting out of DHCP Pool configuration it would be necessary to redeploy:

config t
!
ip dhcp-server pool vlan10
## Type the following before exiting
deploy
end
!
wr mem