SecureStack DHCP Server fails to Reserve IP Address Based on MAC Address

  • 0
  • 1
  • Article
  • Updated 5 years ago
Article ID: 10424 

Products
SecureStack C3; firmware 1.01.01.0051, 1.01.01.0049
SecureStack C2; firmware 5.01.01.0051, 5.01.01.0049
SecureStack B3; firmware 1.01.01.0051, 1.01.01.0049
SecureStack B2; firmware 4.01.01.0051, 4.01.01.0049
SecureStack A2; firmware 2.01.00.0012, 2.01.00.0011, 2.01.00.0010, 2.00.00.0012, 1.04.12, 1.03.24 

Changes
Configured a static binding of a DHCP IP address and user MAC address, using a set of DHCP commands associated with a 'set dhcp pool <pool_name> hardware-address <MAC_address>' command (7724). 

Symptoms
The static assignment is ignored by the switch.
The client gets an IP address from the pool rather than the one statically specified for its MAC address. 

Solution/Workaround
Upgrade to firmware version:
SecureStack C3 firmware version 01.01.02.0007 or higher.
SecureStack C2 firmware version 05.01.03.0007 or higher.
SecureStack B3 firmware version 01.01.02.0007 or higher.
SecureStack B2 firmware version 04.01.03.0007 or higher.
SecureStack A2 firmware version 02.01.01.0001 or higher. 

You will also need to modify your configuration to use the client-identifier option instead of the hardware-address option. 

set dhcp enable
set dhcp pool auto
set dhcp pool auto network 10.10.10.0 255.255.255.0
set dhcp pool static
set dhcp pool static client-identifier 01:00:00:1d:01:23:45
set dhcp pool static host 10.10.10.10 255.255.255.0

The client-identifier is 01 for ethernet followed by a colon and then the MAC address with no spaces in between.
Note: The client-identifier is 7 octets in length.
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.