UNSOLVED

JoePTI

updated

3 years ago

Closed

J

JoePTI

2 Posts

0

443

June 15th, 2023 06:00

"Invisible" DHCP Pool - PowerSwitch S4148F-ON

Hi folks, any thoughts would be appreciated here. 

Our core is a pair of PowerSwitch S4148F-ONs (Core01 and Core02 - using VRRP - both running 10.5.0.9.766), and these serve DHCP to some of our less important VLANs. Due to some project work, I needed to remove DHCP from one of these VLANs. 

Although the DHCP pool on our core is seemingly deleted/disabled (no longer shows in running-config), it is still issuing DHCP addresses. I have confirmed with Wireshark that the DHCP ACKs are indeed coming back from the IP of Core01. Both cores have had the pool removed and show no evidence of these pools existing. Both configs of both cores have been saved.

The config and steps I followed are as thus:

Example config:

Pool VLAN_010

network 192.168.10.0/24

default-router 192.168.10.1

dns-server 8.8.8.8 8.8.4.4

range 192.168.10.10 192.168.10.220

 

The commands ran to "remove":

core01(config)#ip DHCP server

(config-dhcp)#no pool VLAN_010

 

Thanks in advance.

 

  • DELL-Chris H

    7 Practitioner

    9682 Posts

    48046 Points

    233

    0

    Posted June 15th, 2023 13:00

     

    JoePTI,

     

     

    From the looks of it, you will likely have to restart the DHCP for it to take effect, so you may have to do no ip dhcp server to turn it off fully, or you may need to restart the switch.  On a side note though, you should ensure DHCP server is only enabled on 1 switch as running two I don't believe would be supported.

     

    Let me know if this helps.

     

    DELL-Chris H

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

  • JoePTI

    2 Posts

    196

    0

    Posted June 21st, 2023 01:00

    Thanks for this Chris, we did this under an out of hours change control and this did resolve the issue. We only had to disable/enable the DHCP server, thankfully no restart of the core was needed.

    Thanks for your help.