DHCP Vendor ID Implementation

in 1 Series
A Technote by
Systems Engineering
March 2006
Wyse Product Support
Summary

This technote describes how DHCP Vendor ID is used and implemented in Blazer or 1
Series Winterms. It assumes that the reader is familiar with basic DHCP and Blazer
specific server configuration parameters.

Audience

1st Level Support, Systems Engineering Group

Affected Products

WTOS 4.4 and 5.0 based 1000 series terminals.

Definition

DHCP (Dynamic Host Configuration Protocol) is an Internet protocol standard which

allows a booting host to configure itself dynamically without user supervision. It provides
a means to obtain IP configurations from DHCP servers. The interoperability of
configuration services based on the DHCP in an environment of heterogeneous clients
depends on clients accurately identifying themselves and their relevant characteristics to
configuration servers. The class identifier provided through DHCP option 60 helps in
this regard. Different IP configurations can be sent from the server based on the DHCP
vendor ID (DHCP option 60) provided by client.

It should be noted that theoretically Vendor Class Identifier (DHCP option 60) should
work together with Vendor Specific Information (DHCP option 43) to provide a complete
solution for customers who want to provide different set of network configurations to
individual Vendor Class product. Once configured, DHCP client sends a Vendor Class
Identifier in option 60 of its discovery/request/inform packets to identify itself to the
DHCP server. Using the Vendor Class Identifier information, DHCP server responds with
specific set of DHCP option values in option 43 of its offer and ack packets. DHCP
option values embedded in option 43 follows the same “Code-Length-Data” format that
is used in standard DHCP options field. But we will not implement option 43, the vendor
specific tag at this time in 1000 series terminals.

DHCP Vendor ID is defined in RFC 2132 section 9.13 (http://www.ietf.org/rfc/rfc2132.txt).

Requirements

Based on DHCP Vendor ID sent by client, different configurations can be sent from
DHCP server to the client. This enables the customers to customize the environment the
terminals operate. An example is setting different FTP server rootpath (thus different
wnos.ini) for different group of clients. Similar requirement will arise if two different sets
of terminals should use two different Rapport servers.

DHCP Vendor ID implementation in 1 Series Page 2 of 5

Wyse Product Support
Procedure

Here are the steps to enable the DHCP Vendor ID for the 1 Series.

First, follow Microsoft’s procedures on configuring the DHCP Vendor ID server side.

How to Create a New DHCP User or Vendor Class

Windows 2000 provides two option classes an administrator can use to manage configuration details
for DHCP clients within a particular DHCP scope. These option classes are vendor-defined and user-
defined classes.

Vendor-defined classes are used for managing DHCP options assigned to clients identified by vendor
type.

User-defined classes are used for managing DHCP options assigned to clients identified by a
common need for a similar DHCP options configuration.

After defining an option class, individual scopes must be configured with any class-related options to
be provided to clients.

Create a New User or Vendor Option Class

1. Start DHCP Manager.
2. In the console tree, click the applicable DHCP server branch.
3. Right-click the server, and then click Define User Classes to create a new user class, or click
Define Vendor Classes to create a new vendor class.
4. Click Add.
5. In the New Class dialog box, type a descriptive identifying name for the new option in the
Display name box. You may also add additional information to the Description box.
6. Type in the data to be used by the DHCP Server service for matching the class ID provided by
DHCP clients under ID or ASCII. To enter the data as hexadecimal byte numeric values, click the
left side of the text box. To enter data as American Standard Code for Information Interchange
(ASCII) text character values, click the right side of the text box.
7. Click OK, and then click Close.

Configure a DHCP Scope with the New Class ID

1. In DHCP Manager, double-click the appropriate DHCP scope.
2. Right-click Scope Options and then click Configure Options.
3. Click Advanced.
4. Click to select the check box or boxes next to the features you want to use with the new vendor
or user class.
5. Click OK.

Next, make sure to specify the FTP directory for option tag 162 you wish to use. By
default we use “ftproot\wyse\wnos\wnos.ini”. I changed the 162 value to WyseDHCP1
and the new structure for the wnos.ini is now “ftproot\WyseDHCP1\wyse\wnos\wnos.ini”

Lastly amend the wnos.ini file w/ the appropriate command and DHCP Vendor ID.

DHCPVendorID=xxxxxx

My command looks like this in my test:

DHCPVendorID=WyseDHCP1

DHCP Vendor ID implementation in 1 Series Page 3 of 5

Wyse Product Support
Also if we want to configure from GUI we should go to the "Network Setup" dialog
box underneath "Subnet Mask" add "DHCP Vendor ID". This should be a text entry
box and should be ASCII characters not to exceed 50 characters.

DHCP Vendor ID implementation in 1 Series Page 4 of 5

Wyse Product Support
Limitation of Liability
IN NO EVENT SHALL MANUFACTURER, MANUFACTURER'S SUPPLIERS, ANY THIRD-
PARTY PRODUCER, OR ANY OTHER PARTY THAT HAS BEEN INVOLVED IN THE
CREATION, PRODUCTION, OR DELIVERY OF THE DOCUMENT BE LIABLE FOR ANY
DIRECT, CONSEQUENTIAL, INCIDENTAL, INDIRECT, OR SPECIAL DAMAGES,
INCLUDING WITHOUT LIMITATION LOST PROFITS OR LOSSES RESULTING FROM
BUSINESS INTERRUPTION OR LOSS OF DATA, REGARDLESS OF THE FORM OF
ACTION OR LEGAL THEORY UNDER WHICH THE LIABILITY MAY BE ASSERTED, EVEN
IF ADVISED OF THE POSSIBILITY OR LIKELIHOOD OF SUCH DAMAGES.

THIS DOCUMENT IS PROVIDED "AS IS" WITH NO WARRANTIES WHATSOEVER,

INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR ANY PARTICULAR
PURPOSE, OR ANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL,
SPECIFICATION OR SAMPLE. MANUFACTURER DOES NOT WARRANT THAT THE
INFORMATION CONTAINED IN THE DOCUMENT OR ANY SOFTWARE REFERRED
THEREIN WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION WILL BE
UNINTERRUPTED OR ERROR FREE. SOME JURISDICTIONS DO NOT ALLOW THE
LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL
DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.

If you have an technical enquiry please use the online knowledge portal at
http://www.wyse.com/serviceandsupport/support/askwyse.asp or contact the
numbers mentioned below.

Wyse Technology Inc. Wyse Sales: Or send email to:

3471 North First Street 800 GET WYSE sales@wyse.com
San Jose, CA 95134-1801 (800 438 9973)

International Sales: Visit our websites at: Wyse Customer

Australia 61 2 9319 3388
France 33 1 39 44 63 85
Germany 49 89 460099 26
Taiwan 886 3 577 9261
UK 44 118 982 8335
United States 408 473 1200
http://www.wyse.com.au Service Center:
http://www.wyse.fr 800 800 WYSE
http://www.wyse.de (800 800 9973)
http://www.wyse.com.tw
http://www.wyse.co.uk
http://www.wyse.com

© 2006 Wyse Technology Inc. All rights reserved. This material is copyrighted. You may not
reproduce, transmit, transcribe, store in a retrieval system, or translate into any language or
computer language, in any form or by any means, electronic, mechanical, magnetic, optical,
chemical, manual or otherwise, any part of this publication without express written permission.
Wyse, WY, and WyseWorks are registered trademarks, and the Wyse logo, Winterm logo, Wyse,
and Winterm are trademarks of Wyse Technology Inc. ICA is a registered trademark and MetaFrame
is a trademark of Citrix Systems Inc. Rapport is a registered trademark of Rapport Technologies,
Inc., a division of Wyse Technology Inc. Microsoft, Windows, and Windows NT are registered
trademarks of Microsoft Corporation. Other product names mentioned herein are for identification
purposes only and may be trademarks and/or registered trademarks of their respective companies.
09/04 880924-45 Rev. A

DHCP Vendor ID implementation in 1 Series Page 5 of 5