Configuration of static dhcp binding on d-serie Switch don ́t work

  • 0
  • 1
  • Question
  • Updated 5 years ago
  • Answered
i Need to config some dhcp Clients on my D2G124-12P with a different Gateway ... all Clients are in the same subnet .

Following Config don ́t work :

set dhcp enable
set dhcp exclude 192.168.46.2 192.168.46.10
set dhcp exclude 192.168.46.199 192.168.46.254

set dhcp pool kolbe
set dhcp pool kolbe lease 0 12 0
set dhcp pool kolbe dns-server 192.168.46.254 8.8.8.8
set dhcp pool kolbe default-router 192.168.46.254
set dhcp pool kolbe network 192.168.46.0 255.255.255.0
set dhcp pool kolbe option 78 hex 01c0.a82e.03

set dhcp pool ap-gs10
set dhcp pool ap-gs10 dns-server 192.168.46.2
set dhcp pool ap-gs10 default-router 192.168.46.2
set dhcp pool ap-gs10 hardware-address 50:26:90:18:ed:1e
set dhcp pool ap-gs10 host 192.168.46.195 255.255.255.0


I tried this of course already with "dhcp pool client iedentifier"  Option .. 
i tried this with the dhcp hardware-adress Option

.. but nothig works, the Client everytime gets an address from pool "Kolbe"
the Standard pool. It ́s not possible to work with a static dhcp entry.


Of course i tried different devices .. with wireless  and wired Interfaces .. nothing works.

is anybody here who has successful config a D-Series Switch with such static dhcp bindings ?

Chassis Serial Number:      13260009905Y
Chassis Firmware Revision:  06.03.13.0001

 

Thanks

 

Christian

 

Photo of info@systemhaus-genthin.de

Posted 5 years ago

  • 0
  • 1
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 48,880 Points 20k badge 2x thumb
Hi Chris,

I've tried only the static part of the configuration and it looks like that the command "set dhcp pool XXX hardware-address" isn't working.

Use the "set dhcp pool XXX client-identifier" instead.

Here my example...
set dhcp pool test
set dhcp pool test client-identifier 01:20:b3:99:85:14:b5
set dhcp pool test host 10.12.0.33 255.255.255.0

The identifier is the MAC of the client with a 01 (=ENet address) in front.
So my MAC was 20:b3:99:85:14:b5 and I've put the 01 in front to create the ID 01:20:b3:99:85:14:b5

Hope that works for you.

Ron
(Edited)
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 48,880 Points 20k badge 2x thumb
Here with dynamic pool & static binding, as you'd see from the "show dhcp binding" it works...
!
set dhcp enable
set dhcp exclude 10.12.0.1 10.12.0.50
set dhcp exclude 10.12.0.70 10.12.0.254
!
set dhcp pool dynamic
set dhcp pool dynamic network 10.12.0.0 255.255.255.0
!
set dhcp pool static
set dhcp pool static client-identifier 01:20:b3:99:85:14:b5
set dhcp pool static host 10.12.0.60 255.255.255.0!!
!

D2_desk(su)->show dhcp bin
IP address         Hardware Address     Lease Expiration     Type
10.12.0.51         00:1a:e8:14:11:3e    00:23:58            Automatic
10.12.0.60         20:b3:99:85:14:b5    00:23:56            Manual

I run the same version as you've installed on your D2.

Hello Ronald,



thanks for your reply ...

this System is located on a cutomer site as a WLAN Demo System .... thats why i need 3 or 4 days to test your suggestion .. but  i will reply

I've tried only the static part of the configuration and it looks like that the command "set dhcp pool XXX hardware-address" isn't working.

I ́m reasssued about this .. it was not my lack of knowledge to configure such a easy command like a dhcp binding ....




Regards

Chris






Photo of Tamera Rousseau-Vesta

Tamera Rousseau-Vesta, Extreme Alumna

  • 2,760 Points 2k badge 2x thumb
Looking forward to seeing the results of your test Chris!
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 48,880 Points 20k badge 2x thumb
Article ID: 10424 was released today, exactly the problem that you've reported, the only thing that is missing in the article is that also the D2 is affected as we'd see in our tests...

Ron

https://community.enterasys.com/enterasys/topics/securestack_dhcp_server_fails_to_reserve_ip_address_based_on_mac_address 

.. i think this article follow our communication.. because yesterday i put my question into a GTAC Case

and the(n)  tech guys discovered the fact ... that all Switches are affected ..



this bug should get my name :-)