- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Problems creating reserved IP address in a DHCP Pool
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problems creating reserved IP address in a DHCP Pool
We created a pool of reserved DHCP IP addresses under an older firmware release (13.0.4.13). We've upgraded to 13.0.4.17 and are now trying to both update existing reservations and add new reservations of manual IP addresses.
After the 13.0.4.17 upgrade, when I try to either add or update a static DHCP pool reservation I get the following error
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Problems creating reserved IP address in a DHCP Pool
Hi @psda ,
Sorry about this issue, maybe there is a conflict somewhere else - can you edit your config file or do a show run like I do below, to show your static pools and your VLAN interfaces? Alternatively, please send your tech-support file (Diagnostics\Support Diagnostics to ProAVDesign@netgear.com) with a link to this post and one of our SEs will help you.
On my side, using the latest NETGEAR Engage Controller (www.netgear.com/engage) and creating a VAN 10 with your IP scheme, I can create plenty of static pools easily in Engage (Site Settings\VLAN Routing and DHCP Server\Advanced\DHCP Reservations):
interface vlan 1
routing
ip address 192.168.253.1 255.255.255.0
exit
interface vlan 10
routing
ip address 10.4.0.1 255.255.255.0
exit
ip management vlan 1 192.168.253.1 255.255.255.0
router rip
exit
service dhcp
ip dhcp excluded-address 192.168.253.1 192.168.253.9
ip dhcp excluded-address 192.168.253.101 192.168.253.254
ip dhcp excluded-address 192.168.20.1 192.168.20.99
ip dhcp excluded-address 192.168.20.201 192.168.20.254
ip dhcp excluded-address 10.4.0.1 10.4.0.99
ip dhcp excluded-address 10.4.0.201 10.4.0.254
ip dhcp pool "pool_dynamic_1"
lease 0 4 0
dns-server 8.8.8.8 4.4.4.4
default-router 192.168.253.1
network 192.168.253.0 255.255.255.0
exit
ip dhcp pool "pool_dynamic_10"
lease 0 4 0
default-router 10.4.0.1
network 10.4.0.0 255.255.255.0
exit
ip dhcp pool "aabbccddeeff"
default-router 10.4.0.1
hardware-address aa:bb:cc:dd:ee:ff
host 10.4.0.101 255.255.255.0
netbios-node-type b-node
exit
ip dhcp pool "aabbccddeeaa"
default-router 10.4.0.1
hardware-address aa:bb:cc:dd:ee:aa
host 10.4.0.102 255.255.255.0
netbios-node-type b-node
exit
exit
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Problems creating reserved IP address in a DHCP Pool
I'm using the main UI and not the engage controller. I experimented with the engage controller and DHCP reservations but these only work if the controller is running and that isn't a viable scenario for our config.
What show option is dumping out the info you displayed above?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Problems creating reserved IP address in a DHCP Pool
Can you do "show run" after "enable" so in global admin mode, and copy paste the end of the config here, like me, starting with the VLAN IP interfaces, and all the DHCP services under?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Problems creating reserved IP address in a DHCP Pool
I emailed the info you requested to ProAVDesign@netgear.com
Note: the RDL entry is one that reports the error. However, all new ones that I create report it also.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Problems creating reserved IP address in a DHCP Pool
All right, we'll take it from there!
Several problems below that we will address together with the ProAV Design team and you:
- Your IP schemes are Class C with 255.255.255.0 but so far with an exclusion spanning across different Class C subnets
- Client-identifier shouldn’t be used (it’s for other DHCP options, here we do MAC reservation)
- Default-router is needed to me, in the main dynamic pool to be bound to VLAN 160, and in any static pool for correct binding as well