#Find dhcp client id manuals#

On the next page you can now set individual DHCP option for devices with this vendor class: DHCP Vendor Class Identifier – Create Policy Optons They should use the same IP range as the scope itself. On the next screen, I do not want to define a special IP range for those devices. I only use the created vendor class from above as a rule to use the policy. Select the scope for which you would like to configure the options and create a new policy: DHCP Vendor Class Identifier – Create new PolicyĬlick “Next” to get to the screen, where to define the policy rules: DHCP Vendor Class Identifier – Create Policy Rules In the pop-up window select “Add”, to create a new class: DHCP Vendor Class Identifier – Add Vendor Class to ServerĪfter that, you just need to define a new policy for the scope. Open the DHCP management console on the windows server and right click the IPv4 server and select “Define Vendor Classes”. If you have the value for Option 60 for each device, you can start to use them. DHCP Vendor Class Identifier – Configure Windows Server Maybe a good point for a feature request.

#Find dhcp client id manuals#

I haven’t found this information in the manuals so far. For the Comware Device, which is a 1920, it is this: HPE. I always do a Wireshark trace and check option 60 in the DHCP Discover itself. The first step is to get the information, what is in option 60 for each device. DHCP Vendor Class Identifier – Get Option 60 I will provide a different config file for each switch via TFTP. I will use two different switches, an AubaOS switch and a Comware based switch to show the principles. The answer is to use the DHCP Vendor Class Identifier, DHCP option 60.Įvery device sends this option to the DHCP Server, and each DHCP Server can answer with specific options, depending on the option 60. In several meetings I get the question, how can I sent different DHCP options to different devices.