Dhcp options, Dhcp options overview, Introduction to dhcp options – H3C Technologies H3C S7500E Series Switches User Manual
Page 39
4-4
z
giaddr: IP address of the first relay agent a request message traveled.
z
chaddr: Client hardware address.
z
sname: Server host name, from which the client obtained configuration parameters.
z
file: Bootfile name and path information, defined by the server to the client.
z
options: Optional parameters field that is variable in length, which includes the message type,
lease, domain name server IP address, and WINS IP address.
DHCP Options
DHCP Options Overview
The DHCP message adopts the same format as the Bootstrap Protocol (BOOTP) message for
compatibility, but differs from it in the option field, which identifies new features for DHCP.
DHCP uses the option field in DHCP messages to carry control information and network configuration
parameters, implementing dynamic address allocation and providing more network configuration
information for clients.
shows the DHCP option format.
Figure 4-4 DHCP option format
Introduction to DHCP Options
The common DHCP options are as follows:
z
Option 3: Router option. It specifies the gateway address to be assigned to the client.
z
Option 6: DNS server option. It specifies the DNS server IP address to be assigned to the client.
z
Option 51: IP address lease option.
z
Option 53: DHCP message type option. It identifies the type of the DHCP message.
z
Option 55: Parameter request list option. It is used by a DHCP client to request specified
configuration parameters. The option contains values that correspond to the parameters
requested by the client.
z
Option 66: TFTP server name option. It specifies a TFTP server to be assigned to the client.
z
Option 67: Bootfile name option. It specifies the bootfile name to be assigned to the client.
z
Option 150: TFTP server IP address option. It specifies the TFTP server IP address to be
assigned to the client.
z
Option 121: Classless route option. It specifies a list of classless static routes (the destination
addresses in these static routes are classless) that the requesting client should add to its routing
table.