Using TCP/IP to Configure a Dynamic IP Client
Monitoring the DHCP and Dynamic IP Client
Obtaining Information for a Static Client
Customizing DHCP Client Operation
This information describes client use of Dynamic Host Configuration Protocol (DHCP) services and Dynamic Domain Name Server (DDNS) services.
This section describes:
The introductory sections in this information are intended for DHCP client users who obtain an IP address from a DHCP server and register a client host name with a DDNS server. Additional, expert-level information is also provided.
This information describes:
Syntax descriptions in this information use highlighting or special characters to indicate:
For example, the following statement releases client information at the DDNS server:
releaseDNS string
The following function is new in this release:
For more information about:
In a network with DHCP and DDNS services, a client computer may:
Before you start, obtain your DDNS domain configuration information. To configure a client computer for Dynamic IP operation:
Your computer is now configured. On restart, your computer automatically uses DHCP to configure itself for IP network access.
If you operate the client with DDNS, your computer asks for the following information as it restarts:
The name your computer is known by in your domain.
The name for the dynamic domain to which your host is assigned. If DHCP provides the domain name, the domain name value appears in this field. Alternatively, enter a domain name provided by your network administrator.
The fully-qualified host name or IP address of the DDNS server which is primary for your computer's domain. This value defaults to the host name "ns-updates.<domain name>". Accept the default or manually enter a value provided by your network administrator.
Additional information can be required by the system administrator, using DHCP option 192. This information is saved in the client TXT record on the DDNS server.
Once configured, the DDNS and DHCP client programs automatically register and, when appropriate, update your DDNS server with the host name information you entered, the IP address obtained by the DHCP client, and any information entered in the TXT record.
To change your host name or reconfigure other DDNS client program parameters, re-invoke the DDNS Client Configuration Program with one of the following:
Click the DDNS Client Configuration program object located in the System Setup folder inside the System folder.
To view DHCP client configuration status and events, use the DHCP Client Monitor program, DHCPMON.EXE, which displays current lease and options values. For more detailed information about using the DHCP Client Monitor program, select Getting Started or General Help from the DHCP Client Monitor Help pull-down menu.
To start the DHCP Client Monitor program, click the DHCP Client Monitor icon located in the System Setup folder inside the System folder. Alternatively, start the DHCP Client Monitor program by entering the dhcpmon command at a command prompt.
The DHCP Client Monitor program (DHCPMON.EXE) and the DDNS Client Configuration program (DDNSCFG.EXE) display messages to help you diagnose error conditions, listed in Client Error Messages. DDNSCFG displays messages in windows following the execution of a CONFIGURE action. DHCPMON displays messages through the Message log window of the Details view.
A signed number which appears at the end of a DHCP log message indicates an error code from the DDNS client program, nsupdate, listed in nsupdate Return Codes.
After a Configuration action, the DDNS Client Configuration program displays one of these messages:
MSG00 Configuration failed: The DHCP configuration file was not found.
Explanation:
The DDNS Client Configuration program could not find the DHCPCD.CFG file in the directory specified by the ETC environment variable. This file, which is usually created during installation, contains DDNS information that is needed by the DHCP client. Check to see if you can use the sample file, which is in the TCPIP\ETC\SAMPLES directory.
MSG01 Configuration failed: The DHCP configuration file was not updated.
Explanation:
The DDNS Client Configuration program could not update the DHCPCD.CFG file in the directory specified by the ETC environment variable with a valid updatednsa or updatednstxt statement. This file, which is usually created during installation, contains DDNS information that is needed by the DHCP client.
MSG02 Configuration failed: Your workstation memory has been exceeded.
Explanation:
Not enough memory is available. Try closing some other programs to free memory.
MSG03 Each label in the host name must not exceed 63 alphanumeric characters.
Explanation:
One or more of the labels in the host name is longer than 63 alphanumeric characters. Reduce the number of characters in any labels that are too long.
MSG04 Configuration failed: DHCP client is not running.
Explanation:
The DDNS client configuration program could not read from the DHCP client shared memory, probably because the DHCP client is not running.
MSG05 Configuration failed: DHCP client is not running.
Explanation:
The DDNS client configuration program could not signal the DHCP client program with the new host name entered, probably because the DHCP client is not running.
MSG06 Configuration succeeded.
Explanation:
Your host name has been registered with the DDNS server. Other users can now contact you using your host name (as well as your IP address).
MSG07 Configuration failed: DHCP client has not been initialized by a DHCP server.
Explanation:
The DDNS client configuration program could not obtain DHCP-served parameters required for DDNS name registration because the DHCP client has not received a response from a DHCP server. The DHCP client might not have a connection to the server(s) or the server(s) might be down.
MSG08 Each label in the domain name must not exceed 63 alphanumeric characters.
Explanation:
One or more of the labels in the domain name is longer than 63 alphanumeric characters. Reduce the number of characters in any labels that are too long.
MSG09 Configuration failed: DHCP client is not running.
Explanation:
The DDNS client configuration program could not update the shared memory segment used to communicate information between the DHCP and DDNS client programs. The DHCP client is not running or is failing.
MSG10 You must specify a host name.
Explanation:
The host name is missing. Enter a host name. This is a name of your choosing, a name by which you would like your system to be known.
MSG11 You must specify a domain name.
Explanation:
The domain name is missing. Enter the domain name. If you do not know the domain name, contact your system administrator.
MSG12 Each label in the DDNS server name must not exceed 63 alphanumeric characters.
Explanation:
One or more of the labels in the DDNS server name is longer than 63 alphanumeric characters. Reduce the number of characters in any labels that are too long.
MSG13 Host name must consist of one or more labels separated by a single dot character (.). Each label may be alphanumeric, but the fully qualified name must contain at least 1 letter.
Explanation:
The name entered is not valid. Some examples of valid names are:
myhost host123 secretary 9999999c
MSG14 Domain name must consist of one or more labels separated by a single dot character (.). Each label may be alphanumeric, but the fully qualified name must contain at least 1 letter.
Explanation:
The name entered is not valid. Some examples of valid names are:
raleigh.ibm.com eng.mit.edu sailclub.org
MSG15 DDNS server name must consist of one or more labels separated by a single dot character (.). Each label may be alphanumeric, but the fully qualified name must contain at least 1 letter.
Explanation:
The name entered is not valid. Some examples of valid names are:
ddns10.raleigh.ibm.com nserver2.eng.mit.edu names.sailclub.org
Note:
The IP address is also valid and can be used instead of the name.
MSG16 Configuration failed: DDNS server did not respond. The DDNS server specified is either unreachable or does not exist.
Explanation:
The DDNS client program (NSUPDATE) failed with error code -12.
This error code indicates that no response was received from the specified DDNS server.
MSG17 Configuration failed: You are not authorized to update the host name.
Explanation:
The DDNS client program (NSUPDATE) failed with error code -11.
This error code indicates that the DDNS server rejected the DDNS client program's update request because the digital signature for the message failed authentication, that is, because the key in the DDNS.DAT file in the directory specified by the ETC environment variable is not valid.
This happens when your private security key, used to generate the digital signature for the message, does not pair with the corresponding public key registered at the server for the specified host name. NSUPDATE obtains the security key information from DDNS.DAT. If the file is corrupted or deleted, your DDNS update requests will fail authentication.
MSG18 Configuration failed: You are not authorized to create the host name because it already exists and is owned by another host. Select an alternate host name and re-configure.
Explanation:
The DDNS client program (NSUPDATE) failed with error code -10.
This error code indicates that no key was found in the DDNS.DAT file in the directory specified by the ETC environment variable. If public security key information is already registered with the DDNS server for the specified host name or the -f parameter was specified on the NSUPDATE command, your DDNS.DAT file must contain the necessary key information. Either your DDNS.DAT file has been deleted or corrupted or the appropriate wildcard entry has not been correctly generated.
MSG19 Configuration failed: General DDNS update failure.
Explanation:
The DDNS client program (NSUPDATE) failed with error code -2.
This error code indicates an error in the parameters specified. Make sure that the updatednsa or updatednstxt statement in the DHCPCD.CFG file has not been corrupted. If either has been corrupted, delete the entire statement from the client configuration file (DHCPCD.CFG) and re-run the DDNS client configuration program (DDNSCFG.EXE), which will automatically reinsert a valid updatednsa or updatednstxt statement.
MSG20 Configuration failed: General DDNS update failure.
Explanation:
The DDNS client program (NSUPDATE) failed with error code -1.
This error code indicates an unexpected internal error.
MSG21 Configuration failed: DDNS server did not understand the request.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 1.
This error code indicates a format error. The DDNS name server was unable to interpret the request.
MSG22 Configuration failed: DDNS server failure.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 2.
This error code indicates a server error. The DDNS name server was unable to process this request because of a problem with the name server.
MSG23 Configuration failed: The domain name specified does not exist.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 3.
This error code indicates a name error. The DDNS server did not recognize the fully-qualified host name specified in the request.
MSG24 Configuration failed: DDNS server did not understand the request.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 4.
This error code indicates that the DDNS server did not recognize the operation in the update request.
MSG25 Configuration failed: DDNS server rejected the request.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 5.
This error code indicates that the DDNS server refused the requested operation for security or policy reasons, for example, when attempting to update a zone that is not dynamic.
MSG26 Configuration failed: The domain name specified is an alias. Please specify a non-aliased domain name.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 6.
This error code indicates an alias error. The DDNS server refused the requested operation because the fully-qualified host name specified is an alias for another host name.
MSG27 Configuration failed: The host name specified is not available. Please specify another host name.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 7.
This error code indicates a name error. The DDNS server refused the ADDNAMENEW request operation because the host name specified already exists.
MSG28 Configuration failed: The host name specified could not be deleted.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 8.
This error code indicates that a resource record for this host does not exist. The DDNS server refused the requested DELETE operation because the host name specified does not exist.
MSG29 Configuration failed: The DDNS server specified is not authoritative for the domain.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 9.
This error code indicates a zone error. The DDNS server refused the requested operation because the server is not authoritative for the domain name specified or because the records to be updated exist in more than one zone.
MSG30 Configuration failed: DDNS server rejected the request because of a sequencing error.
Explanation:
The DDNS client program (NSUPDATE) failed with error code 10.
This error code indicates a timestamp problem. The DDNS server refused the requested operation because the timestamp preceded that used in an earlier request.
MSG31 Configuration failed: The DDNS client program encountered an unexpected error.
Explanation:
The DDNS client configuration program encountered an unexpected internal processing error.
MSG32 The maximum allowable length for a fully-qualified domain name is 255 characters. The host name and domain name you entered exceed this length when combined.
Explanation:
The fully qualified domain name is too long. Try using a shorter host name.
MSG34 Open DDNS key file failed: unexpected system return code. (The local key file will be used.)
Explanation:
The key file could not be opened because the general file dialog could not be displayed.
MSG35 Replace DDNS key file failed: Copy of the specified key file failed. (The local key file will be used.)
Explanation:
The key file could not be copied. Either the file is being used by another process or it cannot be copied due to insufficent space.
MSG36 Import key file error: Open file failed.
Explanation:
The key file cannot be opened. The file specified does not exist, has an error, or is already is use.
MSG37 Import key file warning: The file contains at least one entry with invalid syntax. Do you wish to continue importing the file?
Explanation:
The program encountered something unexpected in the key file. Click Yes to continue or No to stop.
MSG38 Usage: -?hpql# where: -h = fully qualified host name (required); -p = fully qualified host name/IP address of name server (required); -l# = user values for system administrator required fields (#=1-4); -? = print this message; -q = quiet mode
Explanation:
The syntax of the ddnscfg command is incorrect. Retype the command, specifying the parameters as shown, where:
Note:
This value cannot contain colons (:) or semicolons (;).
MSG39 Configuration error: You must supply information for all the required fields.
Explanation:
Information is missing for one or more fields. Type the required information in each field.
This list describes the nsupdate error codes.
0
Explanation:
-12
Explanation:
This error code indicates that no response was received from the specified DDNS server.
-11
Explanation:
This error code indicates that the DDNS server rejected the DDNS client program's update request because the digital signature for the message failed authentication, that is, because the key in the DDNS.DAT file in the directory specified by the ETC environment variable is not valid.
This happens when your private security key, used to generate the digital signature for the message, does not pair with the corresponding public key registered at the server for the specified host name. NSUPDATE obtains the security key information from DDNS.DAT. If the file is corrupted or deleted, your DDNS update requests will fail authentication.
-10
Explanation:
This error code indicates that no key was found in the DDNS.DAT file in the directory specified by the ETC environment variable. If public security key information is already registered with the DDNS server for the specified host name or the -f parameter was specified on the NSUPDATE command, your DDNS.DAT file must contain the necessary key information. Either your DDNS.DAT file has been deleted or corrupted or the appropriate wildcard entry has not been correctly generated.
-2
Explanation:
This error code indicates an error in the parameters specified. Make sure that the updatednsa or updatednstxt statement in the DHCPCD.CFG file has not been corrupted. If either has been corrupted, delete the entire statement from the client configuration file (DHCPCD.CFG) and re-run the DDNS client configuration program (DDNSCFG.EXE), which will automatically reinsert a valid updatednsa or updatednstxt statement.
-1
Explanation:
This error code indicates an unexpected internal error.
1
Explanation:
This error code indicates a format error. The DDNS name server was unable to interpret the request.
2
Explanation:
This error code indicates a server error. The DDNS name server was unable to process this request because of a problem with the name server.
3
Explanation:
This error code indicates a name error. The DDNS server did not recognize the fully-qualified host name specified in the request.
4
Explanation:
This error code indicates that the DDNS server did not recognize the operation in the update request.
5
Explanation:
This error code indicates that the DDNS server refused the requested operation for security or policy reasons, for example, when attempting to update a zone that is not dynamic.
6
Explanation:
This error code indicates an alias error. The DDNS server refused the requested operation because the fully-qualified host name specified is an alias for another host name.
7
Explanation:
This error code indicates a name error. The DDNS server refused the ADDNAMENEW request operation because the host name specified already exists.
8
Explanation:
This error code indicates that a resource record for this host does not exist. The DDNS server refused the requested DELETE operation because the host name specified does not exist.
9
Explanation:
This error code indicates a zone error. The DDNS server refused the requested operation because the server is not authoritative for the domain name specified or because the records to be updated exist in more than one zone.
10
Explanation:
This error code indicates a timestamp problem. The DDNS server refused the requested operation because the timestamp preceded that used in an earlier request.
The DHCP Client Monitor graphical user interface provides menus to control DHCP clients. Any actions allowed by the graphic interface (and other actions) may also be performed with command line parameters. For more information about controlling a DHCP client, see help provided by the DHCP Client Monitor program.
Tasks that control DHCP clients include:
Manually start the DHCP client program, using:
dhcpstrt
Note:
The client normally starts in the background when the computer boots. You may prefer to use the dhcpcd command to start the DHCP client program in a foreground session, which is visible in the task list. The dhcpstrt command starts the DHCP client program in a background session, which is not visible in the task list.
The DHCP Client Monitor program monitors a DHCP client, displaying client lease information. Start the DHCP Client Monitor graphical user interface, using:
dhcpmon
To request a lease for a DHCP client, using the DHCP Client Monitor graphical user interface, click Request Lease on the Actions pull-down. At a command prompt, you can also type:
dhcpmon -r
To release a lease for a DHCP client, using the DHCP Client Monitor graphical user interface, click Release Lease on the Actions pull-down. At a command prompt, you can also type:
dhcpmon -l
Terminates the DHCP client, regardless of how the DHCP client was started. Use:
dhcpmon -t
Attention: The terminated DHCP client will not attempt to renew its lease. The interface remains configured for the IP address the client has been assigned until the computer is shut down.
When you specify options for a statically-configured client with an IP address, it can be helpful to locate information about other dynamically-configured DHCP clients, such as a local printer specified by the LPR printer option. You can then specify that option for the statically-configured client.
Obtain DHCP client information, using:
dhcpcd -inform ip_address
To obtain operational and protocol configuration parameters, the DHCP client program uses the file \DHCPCD.CFG located in the directory specified by the ETC environment variable. Modifying this file changes the operation and behavior of the DHCP client.
Attention: Incorrect configuration of the DHCP client program may result in the failure of your host to access the IP network. Only network administrators and authorized, informed network programmers should modify the contents of this file.
Before editing this configuration file, review the information in this section carefully. Before making changes to the file, make a backup copy of \DHCPCD.CFG. An alternate configuration filename may be used if you start the client from the command line with the dhcpcd command and the -c option.
You can:
Configuration keywords, which are not case sensitive, and basic DHCP client parameters are described as comment lines in the \DHCPCD.CFG file. Keywords include:
Tasks that define log files include:
Specify the number of log files maintained, using:
numLogFiles value
Notes:
Specify the size of the log file, using:
logFileSize value
Name the log file, using:
logFileName file_path
If no directory is specified, the default is the directory specified by the ETC environment variable. If the specified path is not valid, the DHCP client continues to operate but does not log any information. If no log file name is specified, the logged information is displayed on the screen.
Some problems may not halt the DHCP client, but still cause difficulties. Logging can identify such problems. Specify information types to log, using:
logItem object
SYSERR
Errors at the interface to the operating system
OBJERR
Errors between objects in the DHCP client program, such as missing records or records in inconsistent states
PROTERR
Protocol errors between the client and server
WARNING
Warnings that warrant the user's attention
EVENT
Events in the DHCP client program
ACTION
Actions taken by the DHCP client program
INFO
Useful information
ACNTING
Accounting information, such as who was served and when
TRACE
Trace information
Use this parameter to specify network parameters not assigned through DHCP, such as which network interface the DHCP client uses. Tasks include:
Specify the interface, using:
interface ifName
Specify the type of client ID for all communication with the server, using:
clientID value
Specify advanced options accepted by the ifconfig command, using:
ifconfig_options option_list
The DHCP client program and the DDNSCFG program communicate, when necessary, with the DDNS client program nsupdate.
DDNS client communication tasks include:
Update the Dynamic DNS server with the current host name to IP address mapping for the specified host name, using:
updateDNSA string
Note:
Only one updateDNSA string is allowed in the DHCPCD.CFG file. If multiple instances occur, the last valid statement found in the file is used.To have the server update A and PTR records:
- The non-dynamic client is required to pass option 12 (hostname) and option 15 (domain name) to the server, or use DHCP-DNS option 81.
- In the IBM DHCP server configuration file, enter updateDNSA, releaseDNSA, updateDNSP, releaseDNSP, and proxyARec parameters.
The following is an example of an updateDNSA keyword and update string:
updateDNSA "nsupdate -h%s -s"d;a;*;a;a;%s;s;%s;3110400;q""
The string contains:
Delete all A (hostname-to-IP-address) records for this host.
Add an A record using an IP address (%s) provided by the server.
Send a lease time (%s) provided by the server for the IP address.
The effect of this value is to reserve the host name for an additional time interval after the A record expiration. In this case, an interval of 36 days (3110400 seconds) is added to the A record expiration time. This value works to preserve a user's host name during times when the name-to-address mapping might expire, such as holidays, vacation, or other times of inactivity.
Quit delimiter for the command string
Several steps are necessary to obtain additional information from a DHCP client user:
The DHCPCD.CFG file can be installed remotely. For more information on specifying installation and configuration parameters remotely, using TCP/IP remote installation response files, refer to the TCP/IP readme file, or to the TCP/IP User's Guide.
To update the DDNS server with the current TXT record for the specified host name, use:
updateDNSTxt string
updateDNSTxt "nsupdate -f -h%s -s"d;txt;%s;a;txt;%s;s;%s;3110400;q""
Fields such as txt are text strings defined by the system administrator, requiring the client user to enter a value such as a host name, a room number, or other identifying information.
The example string contains:
Delete the host's previous TXT resource record
Add a new text record for the host
Send the lease time plus an additional interval
The effect of this value is to reserve the host name for an additional time interval after the A record expiration. In this case, an interval of 36 days (3110400 seconds) is added to the A record expiration time. This value works to preserve a user's host name during times when the name-to-address mapping might expire, such as holidays, vacation, or other times of inactivity.
Quit delimiter for the command string
Release the client host name and TXT information at the DDNS server, using:
releaseDNS string
The following is an example of a releaseDNS string:
releaseDNS "nsupdate -h%s -s"d;a;%s;d;txt;%s;s;%s;0;q""
This example deletes the A record and (optionally) also the text record that the DHCP client and DDNSCFG programs have created on the DNS name server.
The string contains:
Delete the A (hostname-to-IP-address) record for this host.
Delete the TXT record previously updated by DDNSCFG or the DHCP client for this host. Deleting the TXT record is necessary only if you use option 192 to obtain additional information to store in the TXT record.
Send a lease time (%s) provided by the server for the IP address.
The signature expiration pad time for the A resource record. In this case, the value is zero because the record is deleted.
Quit delimiter for the command string
Release the client IP address at the DHCP server, using:
releaseADDR shutdown
You can define what options the DHCP client will request of DHCP servers and how the options and values returned from DHCP servers will be processed. Tasks include:
Define an option for a request, using:
option code [value] [exec string]
The command string specified after the exec keyword is expected to be an executable shell script or program. A %s in the string represents the served value.
The format of the served value depends on which option is passed from the server. For architected options, the value is formatted according to its type, such as a character string. On non-architected options, the value is formatted as a hexadecimal string and enclosed in double quotes (") and prefixed with the word "hex", as shown in the following example:
hex "ab 01 35 36 ......."
Synchronous: If multiple options are requested, the respective exec string executes before the next option is processed. This is the default. Use synchronous execution when you have option processing interdependencies.
Asynchronous: To specify asynchronous execution, you must place an @ sign in front of the command.
For example:
option 200 exec "@dhcplpr.cmd 200 %s"
This indicates that the client should continue to the next option without waiting for the DHCPLPR program to complete execution. Consider using asynchronous execution if the specified command will take a long time to execute.
To specify processing for a REXX program you provide, place a dollar sign ($) before the command filename. For example:
option 208 exec "$myrexx.cmd %s"
To specify processing for a Presentation Manager program you provide, place an ampersand (&) before the command filename. For example:
option 208 exec "&mypm.exe %s"
For example, the following option statement specifies the DHCP client will request that the DHCP server return a value for option 200, the default LPR Printer, and that the program DHCPLPR.CMD be invoked to process the value.
option 200 exec "dhcplpr.cmd 200 %s"
You can also configure option 9 using the IBM command DHCPLPR.CMD to specify the IP address of the default LPR server. For example:
option 9 9.67.96.15
An OS/2 client stores the updated option value in the TCPOS2.INI file.
Reject an option offered to the client, using:
reject code
Handle options not explicitly requested, using:
otherOptions value
To re-use your previously-stored client information when the client cannot reach the DHCP server but still has a valid lease, use:
previousCFG
If this keyword is specified, when a DHCP server is down and a DHCP client still has a valid lease, the last set of configuration parameters which were in the client database file, are set by the DHCP client. The previous configuration parameters remain active on the DHCP client until the lease expires. If the DHCP client is not a mobile client, as specified in the TCP/IP configuration notebook, this is the default behavior.
If the lease has not expired, the client continues to try to reach a DHCP server. Types of information which are re-used include:
IBM provides a REXX command script, DHCPLPR.CMD, with the DHCP client to configure the default LPR server using DHCP option 9, and the default LPR printer using DHCP option 200.
Option code 200 is a user-defined option.
The following options were previously supported by the command script DHCPIBM.CMD, but are no longer shipped or supported:
Additionally, DHCPLPR.CMD no longer supports option 205, Default SOCKS Server.
DHCP classing refers to mechanisms in DHCP to administer groups of hosts independent of where they are located in a network. You can specify a membership in a user class and add DHCP site-specific options and processing. Tasks include:
The client tells the DHCP server in what class the client belongs. "Classing" is a general mechanism for network administrators to define groups of users with common configuration requirements. For example, create a class called "bigbatch" so that hosts that identify themselves as belonging to that class are served a separate LPR printer (option 9) from others on the same subnet or across many subnets.
DHCP clients use option 77 to indicate to DHCP servers what class the host is a member of. The user class must be manually entered in the \DHCPCD.CFG file as the value for option 77 in order to receive parameters defined for the class at a DHCP server.
Vendor classing is a special-purpose mechanism for DHCP vendors to specify the "make and model" of the requesting client software. Vendors may use this option to optimize the operation of DHCP when both the client and server are their own brand.
DHCP clients use DHCP option 60 to indicate to DHCP servers what vendor type they are. The vendor class is specified in the default file \DHCPCD.CFG.
The IBM vendor class is provided as "IBMWARP_V41". You should not change this value.
Option 43, Vendor-specific Information, is used by clients and servers to exchange information. It allows for the expansion of the number of options that can be supported, and is used in conjunction with Option 60, the vendor class identifier.
The following example illustrates the use of the vendor keyword in the \DHCPCD.CFG file:
vendor exec "dhcpopt.exe %s" { option 63 option 70 option 200 }
The option numbers you specify within the braces can be any number from 0 to 255. The option numbers in this environment do not correlate to the architected option numbers specified in RFC 2132. The exec parameter is used only in the vendor statement, not on option statements within braces.
The following file is an example of DHCPCD.CFG, used by DHCP clients for servers that require clients to explicitly request options:
#
# Default DHCP Client configuration file -- dhcpcd.cfg
#
#
# This file must be placed in the directory specified by the ETC
# environment variable.
#
# Basic options required
clientid MAC
interface lan0
# Uncomment as desired for logging
#numLogFiles 4
#logFileSize 100
#logFileName dhcpcd.log
#logItem SYSERR
#logItem OBJERR
#logItem PROTERR
#logItem WARNING
#logItem EVENT
#logItem ACTION
#logItem INFO
#logItem ACNTING
#logItem TRACE
# The following are requested for interoperability with some servers which
# need explicit requests.
option 1 # Subnet Mask
option 3 # Router
option 6 # Domain Name Server
option 15 # Domain Name
option 28 # Broadcast Address
option 33 # Static Routes
option 60 "IBMWARP_V4.1" # Vendor Class
option 77 "IBMWARP_V4.1" # User Class
updateDNSA "nsupdate -h%s -s"d;a;*;a;a;%s;s;%s;3110400;q""
updateDNSTxt "nsupdate -h%s -s"d;txt;%s;a;txt;%s;s;%s3110400;q""
# The following are options for which IBM supplies an instantiation script,
# dhcplpr.cmd, to automatically configure the remote print application
# with a printer and server name. Uncomment them if desired.
option 200 exec "dhcplpr.cmd 200 %s" # Default LPR Printer
Second Edition (September 1997)
The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you.
This publication might include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time.
This publication was developed for products and services offered in the United States of America. IBM may not offer the products, services, or features discussed in this document in other countries, and the information is subject to change without notice. Consult your local IBM representative for information on the products, services, and features available in your area.
Requests for technical information about IBM products should be made to your IBM reseller or IBM marketing representative.
© Copyright International Business Machines Corporation 1996, 1997. All rights reserved.
Note to U.S. government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
IBM is required to include the following statements in order to distribute portions of this document and the software described herein.
__________________________________
The TCP/IP client and server software included herein contains network security technology licensed from RSA Data Security, Inc. This technology is licensed solely for use with software using technology previously licensed from RSA Data Security, Inc.
References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program or service is not intended to state or imply that only IBM's product, program, or service may be used. Subject to IBM's valid intellectual property or other legally protectable rights, any functionally equivalent product, program, or service may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, programs, or services, except those expressly designated by IBM, are the user's responsibility.
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing IBM Corporation 500 Columbus Avenue Thornwood, NY 10594 U.S.A.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact IBM Corporation, Department LZKS, 11400 Burnet Road, Austin, TX 78758, U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
TCP/IP for OS/2 incorporates compression code by the Info-ZIP group. There are no extra charges or costs due to the use of this code, and the original compression sources are freely available from Compuserve in the OS2USER forum and by anonymous ftp from the Internet site ftp.uu.net:/pub/archiving/zip.
The following terms are trademarks of the IBM Corporation in the United States or other countries or both:
Other company, product, and service names which may be denoted by a double asterisk (**), may be trademarks or service marks of others.