Operation Manual DHCP. Table of Contents

Transcription

1 Table of Contents Table of Contents Chapter 1 DHCP Overview Introduction to DHCP DHCP IP Address Assignment IP Address Assignment Policy Obtaining IP Addresses Dynamically Updating IP Address Lease DHCP Packet Format DHCP Packet Processing Modes Protocols and Standards Chapter 2 DHCP Server Configuration Introduction to DHCP Server Usage of DHCP Server DHCP Address Pool DHCP IP Address Preferences Global Address Pool-Based DHCP Server Configuration Configuration Task List Enabling DHCP Configuring Global Address Pool Mode on Interface(s) Configuring How to Assign IP Addresses in a Global Address Pool Configuring DNS Services for the DHCP Server Configuring NetBIOS Services for the DHCP Server Customizing DHCP Service Configuring Gateway Addresses for DHCP Clients Interface Address Pool-Based DHCP Server Configuration Configuration Overview Enabling DHCP Configuring to Assign the IP Addresses of Interface Address Pools to DHCP Clients Configuring to Assign IP Addresses of DHCP Address Pools to DHCP Clients Configuring DNS Services for the DHCP Server Configuring NetBIOS Services for DHCP Clients Customizing DHCP Service DHCP Security Configuration Prerequisites Configuring Private DHCP Server Detecting Configuring IP Address Detecting Displaying and Maintaining a DHCP Server i

2 Table of Contents 2.6 DHCP Server Configuration Example Troubleshooting a DHCP Server Chapter 3 DHCP Relay Agent Configuration Introduction to DHCP Relay Agent Usage of DHCP Relay Agent DHCP Relay Agent Fundamentals Option 82 Supporting Configuring DHCP Relay Agent DHCP Relay Agent Configuration Task List Enabling DHCP Configuring an Interface to Operate in DHCP Relay Agent Mode Configuring DHCP Relay Agent Security Configuring Option 82 Supporting Displaying and Maintaining DHCP Relay Agent DHCP Relay Agent Configuration Example Troubleshooting DHCP Relay Agent Chapter 4 DHCP Snooping Configuration Configuring DHCP Snooping Introduction to DHCP Snooping Configuring DHCP Snooping DHCP-Snooping Option Overview of DHCP-Snooping Option Enabling DHCP-Snooping Option Displaying and Maintaining DHCP Snooping DHCP Snooping Configuration Example ii

3 Chapter 1 DHCP Overview Chapter 1 DHCP Overview When configuring DHCP, go to these sections for information you are interested in: Introduction to DHCP DHCP IP Address Assignment DHCP Packet Format DHCP Packet Processing Modes Protocols and Standards 1.1 Introduction to DHCP With networks getting larger in size and more complicated in structure, lack of available IP addresses becomes the common situation the network administrators have to face, and network configuration becomes a tough task for the network administrators. With the emerging of wireless networks and the using of laptops, the position change of hosts and frequent change of IP addresses also require new technology. Dynamic host configuration protocol (DHCP) is developed in this background. DHCP adopts a client/server model, where DHCP clients send requests to DHCP servers for configuration parameters; and the DHCP servers return the corresponding configuration information such as IP addresses to configure IP addresses dynamically. A typical DHCP application includes one DHCP server and multiple clients (such as PCs and laptops), as shown in Figure 1-1. DHCP client DHCP client DHCP server DHCP client DHCP client Figure 1-1 Typical DHCP application 1-1

4 Chapter 1 DHCP Overview 1.2 DHCP IP Address Assignment IP Address Assignment Policy Currently, DHCP provides the following three IP address assignment policies to meet the requirements of different clients: Manual assignment. The administrator statically binds IP addresses to few clients with special uses (such as WWW server). Then the DHCP server assigns these fixed IP addresses to the clients. Automatic assignment. The DHCP server assigns IP addresses to DHCP clients. The IP addresses will be occupied by the DHCP clients permanently. Dynamic assignment. The DHCP server assigns IP addresses to DHCP clients for predetermined period of time. In this case, a DHCP client must apply for an IP address at the expiration of the period. This policy applies to most clients Obtaining IP Addresses Dynamically A DHCP client undergoes the following four phases to dynamically obtain an IP address from a DHCP server: 1) Discover: In this phase, the DHCP client tries to find a DHCP server by broadcasting a DHCP-DISCOVER packet. 2) Offer: In this phase, the DHCP server offers an IP address. Each DHCP server that receives the DHCP-DISCOVER packet chooses an unassigned IP address from the address pool based on the IP address assignment policy and then sends a DHCP-OFFER packet (which carries the IP address and other configuration information) to the DHCP client. The transmission mode depends on the flag field in the DHCP-DISCOVER packet. For details, see section DHCP Packet Format. 3) Select: In this phase, the DHCP client selects an IP address. If more than one DHCP server sends DHCP-OFFER packets to the DHCP client, the DHCP client only accepts the DHCP-OFFER packet that first arrives, and then broadcasts a DHCP-REQUEST packet containing the assigned IP address carried in the DHCP-OFFER packet. 4) Acknowledge: Upon receiving the DHCP-REQUEST packet, the DHCP server returns a DHCP-ACK packet to the DHCP client to confirm the assignment of the IP address to the client, or returns a DHCP-NAK packet to refuse the assignment of the IP address to the client. When the client receives the DHCP-ACK packet, it broadcasts an ARP packet with the assigned IP address as the destination address to detect the assigned IP address, and uses the IP address only if it does not receive any response within a specified period. 1-2

5 Chapter 1 DHCP Overview Note: The IP addresses offered by other DHCP servers (if any) are not used by the DHCP client and are still available to other clients Updating IP Address Lease After a DHCP server dynamically assigns an IP address to a DHCP client, the IP address keeps valid only within a specified lease time and will be reclaimed by the DHCP server when the lease expires. If the DHCP client wants to use the IP address for a longer time, it must update the IP lease. By default, a DHCP client updates its IP address lease automatically by unicasting a DHCP-REQUEST packet to the DHCP server when half of the lease time elapses. The DHCP server responds with a DHCP-ACK packet to notify the DHCP client of a new IP lease if the server can assign the same IP address to the client. Otherwise, the DHCP server responds with a DHCP-NAK packet to notify the DHCP client that the IP address will be reclaimed when the lease time expires. If the DHCP client fails to update its IP address lease when half of the lease time elapses, it will update its IP address lease by broadcasting a DHCP-REQUEST packet to the DHCP server again when seven-eighths of the lease time elapses. The DHCP server performs the same operations as those described in the previous section. 1.3 DHCP Packet Format DHCP has eight types of packets. They have the same format, but the values of some fields in the packets are different. The DHCP packet format is based on that of the BOOTP packets. The following table describes the packet format (the number in the brackets indicates the field length, in bytes): 1-3

6 Chapter 1 DHCP Overview op (1) htype (1) hlen (1) hops (1) xid (4) secs (2) flags (2) ciaddr (4) yiaddr (4) siaddr (4) giaddr (4) chaddr (16) sname (64) file (128) options (variable) Figure 1-2 Format of DHCP packets The field meanings are illustrated as follows: op: Operation types of DHCP packets: 1 for request packets and 2 for response packets. htype, hlen: Hardware address type and length of the DHCP client. hops: Number of DHCP relay agents which a DHCP packet passes. For each DHCP relay agent that the DHCP request packet passes, the field value increases by 1. xid: Random number that the client selects when it initiates a request. The number is used to identify an address-requesting process. secs: Elapsed time after the DHCP client initiates a DHCP request. flags: The first bit is the broadcast response flag bit. It is used to identify that the DHCP response packet is sent in the unicast or broadcast mode. Other bits are reserved. ciaddr: IP address of a DHCP client. yiaddr: IP address that the DHCP server assigns to a client. siaddr: IP address of the DHCP server. giaddr: IP address of the first DHCP relay agent that the DHCP client passes after it sent the request packet. chaddr: Hardware address of the DHCP client. sname: Name of the DHCP server. file: Name of the start configuration file that the DHCP server specifies for the DHCP client. option: Optional variable-length fields, including packet type, valid lease time, IP address of a DNS server, and IP address of the WINS server. 1-4

7 Chapter 1 DHCP Overview 1.4 DHCP Packet Processing Modes After the DHCP server is enabled on a device, the device processes the DHCP packet received from a DHCP client in one of the following three modes depending on your configuration: Global address pool: In response to the DHCP packets received from DHCP clients, the DHCP server picks IP addresses from its global address pools and assigns them to the DHCP clients. Interface address pool: In response to the DHCP packets received from DHCP clients, the DHCP server picks IP addresses from the interface address pools and assigns them to the DHCP clients. If there is no available IP address in the interface address pools, the DHCP server picks IP addresses from its global address pool that contains the interface address pool segment and assigns them to the DHCP clients. Trunk: DHCP packets received from DHCP clients are forwarded to an external DHCP server, which assigns IP addresses to the DHCP clients. You can specify the mode to process DHCP packets. For the configuration of the first two modes, see DHCP Server Configuration. For the configuration of the trunk mode, see DHCP Relay Agent Configuration. One interface only corresponds to one mode. In this case, the new configuration overwrites the previous one. 1.5 Protocols and Standards Protocol specifications related to DHCP include: RFC2131: Dynamic Host Configuration Protocol RFC2132: DHCP Options and BOOTP Vendor Extensions RFC1542: Clarifications and Extensions for the Bootstrap Protocol 1-5

8 Chapter 2 DHCP Server Configuration Chapter 2 DHCP Server Configuration When configuring DHCP servers, go to these sections for information you are interested in: Introduction to DHCP Server Global Address Pool-Based DHCP Server Configuration Interface Address Pool-Based DHCP Server Configuration DHCP Security Configuration Displaying and Maintaining a DHCP Server DHCP Server Configuration Example Troubleshooting a DHCP Server 2.1 Introduction to DHCP Server Usage of DHCP Server Generally, DHCP servers are used in the following networks to assign IP addresses: Large-sized networks, where manual configuration method bears heavy load and is difficult to manage the whole network in a centralized way. Networks where the number of available IP addresses is less than that of the hosts. In this type of networks, IP addresses are not enough for all the hosts to obtain a fixed IP address, and the number of on-line users is limited (such is the case in an ISP network). In these networks, a great number of hosts must dynamically obtain IP addresses through DHCP. Networks where only a few hosts need fixed IP addresses and most hosts do not need fixed IP addresses DHCP Address Pool A DHCP address pool holds the IP addresses to be assigned to DHCP clients. When a DHCP server receives a DHCP request from a DHCP client, it selects an address pool depending on the configuration, picks an IP address from the pool and sends the IP address and other related parameters (such as the IP address of the DNS server, and the lease time of the IP address) to the DHCP client. I. Types of address pools The address pools of a DHCP server fall into two types: global address pool and interface address pool. A global address pool is created by executing the dhcp server ip-pool command in system view. It is valid on the current device. 2-1

9 Chapter 2 DHCP Server Configuration If an interface is configured with a valid unicast IP address, you can create an interface-based address pool for the interface by executing the dhcp select interface command in interface view. The IP addresses an interface address pool holds belong to the network segment the interface resides in and are available to the interface only. II. The structure of an address pool The address pools of a DHCP server are hierarchically organized in a tree-like structure. The root holds the IP addresses of the network segment, the branches hold the subnet IP addresses, and the leaves hold the IP addresses that are manually bound to specific clients. The address pools that are of the same level are sorted by their configuration precedence order. Such a structure enables configurations to be inherited. That is, the configurations of the network segment can be inherited by its subnets, whose configurations in turn can be inherited by their client address. So, for the parameters that are common to the whole network segment or some subnets (such as domain name), you just need to configure them on the network segment or the corresponding subnets. The following is the details of configuration inheritance. 1) A newly created child address pool inherits the configurations of its parent address pool. 2) For an existing parent-child address pool pair, when you perform a new configuration on the parent address pool: The child address pool inherits the new configuration if there is no corresponding configuration on the child address pool. The child address pool does not inherit the new configuration if there is already a corresponding configuration on the child address pool DHCP IP Address Preferences Interfaces of the DHCP server can work in the global address pool mode or in the interface address pool mode. If the DHCP server works in the interface address pool mode, it picks IP addresses from the interface address pools and assigns them to the DHCP clients. If there is no available IP address in the interface address pools, the DHCP server picks IP addresses from its global address pool that contains the interface address pool segment and assigns them to the DHCP clients. A DHCP server assigns IP addresses in interface address pools or global address pools to DHCP clients in the following sequence: IP addresses that are statically bound to the MAC addresses of DHCP clients IP addresses that are ever used by DHCP clients. That is, those in the assigned leases recorded by the DHCP server. If there is no record in the leases and the DHCP-DISCOVER packets sent by DHCP clients contain option 50 fields, the DHCP server assigns the IP address requested by option

10 Chapter 2 DHCP Server Configuration The first IP address found among the available IP addresses in the DHCP address pool. If no IP address is available, the DHCP server queries lease-expired and conflicted IP addresses. If the DHCP server finds such IP addresses, it assigns them; otherwise the DHCP server does not assign IP addresses. 2.2 Global Address Pool-Based DHCP Server Configuration Configuration Task List Complete the following tasks to configure global address pool-based DHCP server: Task Remarks Enabling DHCP Configuring Global Address Pool Mode on Interface(s) Optional Configuring How to Assign IP Addresses in a Global Address Pool Configuring to assign IP addresses by static binding Configuring to assign IP addresses dynamically One among these two options is required. Only one mode can be selected for the same global address pool. Configuring DNS Services for the DHCP Server Configuring NetBIOS Services for the DHCP Server Customizing DHCP Service Configuring Gateway Addresses for DHCP Clients Optional Optional Optional Optional Enabling DHCP You need to enable DHCP before performing other DHCP-related configurations, which takes effect only after DHCP is enabled. Follow these steps to enable DHCP: Enable DHCP dhcp enable By default, DHCP is enabled Configuring Global Address Pool Mode on Interface(s) You can configure the global address pool mode on the specified or all interfaces of a DHCP server. After that, when the DHCP server receives DHCP packets from DHCP 2-3

11 Chapter 2 DHCP Server Configuration clients through these interfaces, it assigns IP addresses in the global address pool to the DHCP clients. Follow these steps to configure the global address pool mode on interface(s): Configure the specified interface(s) or all interfaces to operate in global address pool mode Configure the current interface Configure multiple interfaces in system view interface interface-type interface-number dhcp select global quit dhcp select global { interface interface-type interface-number [ to interface-type interface-number ] all } Optional By default, a DHCP server assigns the IP addresses of the global address pool to DHCP clients in response to DHCP packets received from DHCP clients Configuring How to Assign IP Addresses in a Global Address Pool You can specify to bind an IP address in a global address pool statically to a DHCP client or assign IP addresses in the pool dynamically to DHCP clients as needed. In the global address pool, you can bind an IP address statically to a DHCP client and assign other IP addresses in the pool dynamically to DHCP clients. For dynamic IP address assigning, you need to specify the range of the IP addresses to be dynamically assigned. But for static IP address binding, you can consider an IP address statically bound to a DHCP client coming from a special DHCP address pool that contains only one IP address. I. Configuring to assign IP addresses by static binding Some DHCP clients, such as WWW servers, need fixed IP addresses. This can be achieved by binding IP addresses to the MAC addresses of these DHCP clients. When such a DHCP client applies for an IP address, the DHCP server searches for the IP address corresponding to the MAC address of the DHCP client and assigns the IP address to the DHCP client. Currently, only one IP address in a global DHCP address pool can be statically bound to a MAC address. Follow these steps to configure to assign IP addresses by static binding: 2-4

12 Chapter 2 DHCP Server Configuration Create a DHCP address pool and enter DHCP address pool view Configure an IP address to be statically bound Configure a client MAC address to which an IP address is to be statically bound dhcp server ip-pool pool-name static-bind ip-address ip-address [ mask mask ] static-bind mac-address mac-address By default, no global DHCP address pool is created By default, no IP address is statically bound By default, no MAC address to which an IP address is to be statically bound is configured Note: The static-bind ip-address command and the static-bind mac-address command must be coupled. In the same global DHCP address pool, if the static-bind ip-address command or the static-bind mac-address command is executed repeatedly, the new configuration overwrites the previous one. The IP address to be statically bound cannot be an interface IP address of the DHCP server; otherwise static binding does not take effect. A client can permanently use the statically-bound IP address that it has obtained. The IP address is not limited by the lease time of the IP addresses in the address pool. II. Configuring to assign IP addresses dynamically IP addresses dynamically assigned to DHCP clients (including those that are permanently leased and those that are temporarily leased) belong to addresses segments that are previously specified. Currently, an address pool can contain only one address segment, whose ranges are determined by the subnet mask. To avoid IP address conflicts, the IP addresses to be dynamically assigned to DHCP clients are those that are not occupied by specific network devices (such as gateways and FTP servers). The lease time can differ with address pools. But that of the IP addresses of the same address pool are the same. Lease time is not inherited, that is to say, the lease time of a child address pool is not affected by the configuration of the parent address pool. Follow these steps to configure to assign IP addresses dynamically: 2-5

13 Chapter 2 DHCP Server Configuration Create a DHCP address pool and enter DHCP address pool view Set the IP address segment whose IP addresses are to be assigned dynamically Configure the lease time dhcp server ip-pool pool-name network ip-address [ mask mask ] expired { day day [ hour hour [ minute minute ] ] unlimited } By default, no DHCP address pool is created By default, no IP address segment is set. That is, no IP address is available for being assigned Optional The default lease time is one day Return to system view quit Specify the IP addresses that are not dynamically assigned dhcp server forbidden-ip low-ip-address [ high-ip-address ] Optional By default, all IP addresses in a DHCP address pool are available for being dynamically assigned Note: In the same DHCP global address pool, the network command can be executed repeatedly. In this case, the new configuration overwrites the previous one. The dhcp server forbidden-ip command can be executed repeatedly. That is, you can repeatedly configure IP addresses that are not dynamically assigned to DHCP clients Configuring DNS Services for the DHCP Server If a host accesses the Internet through domain names, DNS is needed to translate the domain names into the corresponding IP addresses. To enable DHCP clients to access the Internet through domain names, a DHCP server is required to provide DNS server addresses while assigning IP addresses to DHCP clients. Currently, you can configure up to eight DNS server addresses for a DHCP address pool. You can configure domain names to be used by DHCP clients for address pools. After you do this, the DHCP server provides the domain names to the DHCP clients as well while the former assigns IP addresses to the DHCP clients. Follow these steps to configure DNS services for the DHCP server: 2-6

14 Chapter 2 DHCP Server Configuration Create a DHCP address pool and enter DHCP address pool view Configure a domain name for DHCP clients Configure DNS server addresses for DHCP clients dhcp server ip-pool pool-name domain-name domain-name dns-list ip-address&<1-8> By default, no global DHCP address pool is created By default, no domain name is configured for DHCP clients By default, no DNS server address is configured Configuring NetBIOS Services for the DHCP Server For Microsoft Windows-based DHCP clients that communicate through NetBIOS protocol, the host name-to-ip address translation is carried out by Windows internet naming service (WINS) servers. So you need to perform WINS-related configuration for most Windows-based hosts. Currently, you can configure up to eight WINS addresses for a DHCP address pool. Host name-to-ip address mappings are needed for DHCP clients communicating through NetBIOS protocol. According to the way to establish the mapping, NetBIOS nodes fall into the following four categories: B-node. Nodes of this type establish their mappings through broadcasting (The character b stands for the word broadcast). The source node obtains the IP address of the destination node by sending the broadcast packet containing the host name of the destination node. After receiving the broadcast packet, the destination node returns its IP address to the source node. P-node. Nodes of this type establish their mappings by sending unicast packets to WINS servers. (The character p stands for peer-to-peer). The source node sends the unicast packet to the WINS server. After receiving the unicast packet, the WINS server returns the IP address corresponding to the destination node name to the source node. M-node. Nodes of this type are p-nodes mixed with broadcasting features (The character m stands for the word mixed), that is to say, this type of nodes obtain mappings by sending broadcast packets first. If they fail to obtain mappings, they send unicast packets to the WINS server to obtain mappings. H-node. Nodes of this type are b-nodes mixed with peer-to-peer features. (The character h stands for the word hybrid), that is to say, this type of nodes obtain 2-7

15 Chapter 2 DHCP Server Configuration mappings by sending unicast packets to WINS servers. If they fail to obtain mappings, they send broadcast packets to obtain mappings. Follow these steps to configure NetBIOS services for the DHCP server: Create a DHCP address pool and enter DHCP address pool view Configure WINS server addresses for DHCP clients Configure DHCP clients to be of a specific NetBIOS node type dhcp server ip-pool pool-name nbns-list ip-address&<1-8> netbios-type { b-node h-node m-node p-node } By default, no global DHCP address pool is created By default, no WINS server address is configured Optional By default, no NetBIOS node type of the DHCP client is specified and a DHCP client uses an h-node Customizing DHCP Service With the evolution of DHCP, new options are constantly coming into being. You can add the new options as the properties of DHCP servers by performing the following configuration. Follow these steps to customize DHCP service: Create a DHCP address pool and enter DHCP address pool view Configure customized options dhcp server ip-pool pool-name option code { ascii ascii-string hex hex-string&<1-10> ip-address ip-address&<1-8> } By default, no global DHCP address pool is created By default, no customized option is configured Configuring Gateway Addresses for DHCP Clients Gateways are necessary for DHCP clients to access servers/hosts outside the current network segment. After you configure gateway addresses on a DHCP server, the 2-8

16 Chapter 2 DHCP Server Configuration DHCP server provides the gateway addresses to DHCP clients as well while assigning IP addresses to them. You can configure gateway addresses for address pools on a DHCP server. Currently, you can configure up to eight gateway addresses for a DHCP address pool. Follow these steps to configure gateway addresses for DHCP clients: Create a DHCP address pool and enter DHCP address pool view Configure gateway addresses for DHCP clients dhcp server ip-pool pool-name gateway-list ip-address&<1-8> By default, no global DHCP address pool is created By default, no gateway address is configured 2.3 Interface Address Pool-Based DHCP Server Configuration Caution: In the interface address pool mode, after the addresses in the interface address pool have been assigned, the DHCP server picks IP addresses from the global interface address pool containing the segment of the interface address pool and assigns them to the DHCP clients. As a result, the IP addresses obtained from global address pools and those obtained from interface address pools are not in the same network segment, so the clients cannot interoperate with each other. In the interface address pool mode, if the IP addresses in the same address pool are required to be assigned to the clients on the same VLAN interface, the number of clients that obtain IP addresses automatically cannot exceed the number of the IP addresses that can be assigned in the interface address pool Configuration Overview An interface address pool is created when the interface is assigned a valid unicast IP address and you execute the dhcp select interface command in interface view. The IP addresses contained in it belong to the network segment where the interface resides and are available to the interface only. 2-9

17 Chapter 2 DHCP Server Configuration You can perform certain configurations for DHCP address pools of an interface or multiple interfaces within specified interface ranges. Configuring for multiple interfaces eases configuration work load and makes you to configure in a more convenient way. Complete the following tasks to configure interface address pool-based DHCP server: Task Remarks Enabling DHCP Configuring to Assign the IP Addresses of Interface Address Pools to DHCP Clients Configuring to Assign IP Addresses of DHCP Address Pools to DHCP Clients Configuring to assign IP addresses by static binding Configuring to assign IP addresses dynamically One among these two options is required. These two options can be configured at the same time. Configuring DNS Services for the DHCP Server Configuring NetBIOS Services for DHCP Clients Customizing DHCP Service Optional Optional Optional Enabling DHCP You need to enable DHCP before performing DHCP configurations. DHCP-related configurations are valid only when DHCP is enabled. Follow these steps to enable DHCP: Enable DHCP dhcp enable By default, DHCP is enabled Configuring to Assign the IP Addresses of Interface Address Pools to DHCP Clients If the DHCP server works in the interface address pool mode, it picks IP addresses from the interface address pools and assigns them to the DHCP clients. If there is no available IP address in the interface address pools, the DHCP server picks IP addresses from its global address pool that contains the interface address pool segment and assigns them to the DHCP clients. 2-10

18 Chapter 2 DHCP Server Configuration Follow these steps to configure to assign the IP addresses of interface address pools to DHCP clients: Configure to assign the IP addresses of interface address pools to DHCP clients Configure the current interface Configure multiple interfaces in system view interface interface-type interface-number dhcp select interface quit dhcp select interface { interface interface-type interface-number [ to interface-type interface-number ] all } By default, a DHCP server assigns the IP addresses of the global address pool to DHCP clients Configuring to Assign IP Addresses of DHCP Address Pools to DHCP Clients You can assign IP addresses by static binding or assign IP addresses dynamically to DHCP clients as needed. I. Configuring to assign IP addresses by static binding Some DHCP clients, such as WWW servers, need fixed IP addresses. This is achieved by binding IP addresses to the MAC addresses of these DHCP clients. When such a DHCP client applies for an IP address, the DHCP server finds the IP address corresponding to the MAC address of the DHCP client, and then assigns the IP address to the DHCP client. Follow these steps to configure to assign IP addresses by static binding: Enter interface view Configure static binding interface interface-type interface-number dhcp server static-bind ip-address ip-address mac-address mac-address By default, static binding is not configured 2-11

19 Chapter 2 DHCP Server Configuration Note: The IP addresses statically bound in interface address pools and the interface IP addresses must be in the same segment. There is no limit to the number of IP addresses statically bound in an interface address pool, but the IP addresses statically bound in interface address pools and the interface IP addresses must be in the same segment. An IP address can be statically bound to only one MAC address. A MAC address can be bound with only one IP address statically. The IP address to be statically bound cannot be an interface IP address of the DHCP server; otherwise the static binding does not take effect. II. Configuring to assign IP addresses dynamically As an interface-based address pool is created after the interface is assigned a valid unicast IP address, the IP addresses contained in the address pool belong to the network segment where the interface resides and are available to the interface only. So specifying the range of the IP addresses to be dynamically assigned is unnecessary. To avoid IP address conflicts, the IP addresses to be dynamically assigned to DHCP clients are those not occupied by specific network devices (such as gateways and FTP servers). The lease time can differ with address pools. But that of the IP addresses of the same address pool is the same. Lease time is not inherited, that is to say, the lease time of a child address pool is not affected by the configuration of the parent address pool. Follow these steps to configure to assign IP addresses dynamically: Configure the lease time Configure for the current interface Configure multiple interfaces in system view interface interface-type interface-number dhcp server expired { day day [ hour hour [ minute minute ] ] unlimited } quit dhcp server expired { day day [ hour hour [ minute minute ] ] unlimited } { interface interface-type interface-number [ to interface-type interface-number ] all } Optional The default lease time is one day 2-12

20 Chapter 2 DHCP Server Configuration Specify the IP addresses that are not dynamically assigned dhcp server forbidden-ip low-ip-address [ high-ip-address ] Optional By default, all IP addresses in a DHCP address pool are available for being dynamically assigned. Note: The dhcp server forbidden-ip command can be executed repeatedly. That is, you can repeatedly configure IP addresses that are not dynamically assigned to DHCP clients. Use the dhcp server forbidden-ip command to configure the IP addresses that are not assigned dynamically in global address pools and interface address pools Configuring DNS Services for the DHCP Server If a host accesses the Internet through domain names, DNS is needed to translate the domain names into the corresponding IP addresses. To enable DHCP clients to access the Internet through domain names, a DHCP server is required to provide DNS server addresses while assigning IP addresses to DHCP clients. Currently, you can configure up to eight DNS server addresses for a DHCP address pool. On the DHCP server, you can configure domain names to be used by DHCP clients for address pools. After you do this, the DHCP server provides the domain names to the DHCP clients while the DHCP server assigns IP addresses to the DHCP clients. Follow these steps to configure DNS services for the DHCP server: 2-13

21 Chapter 2 DHCP Server Configuration Configure a domain name for DHCP clients Configure the current interface Configure multiple interfaces in system view interface interface-type interface-number dhcp server domain-name domain-name quit dhcp server domain-name domain-name { interface interface-type interface-number [ to interface-type interface-number ] all } By default, no domain name is configured for DHCP clients Configure DNS server addresses for DHCP clients Configure the current interface Configure multiple interfaces in system view interface interface-type interface-number dhcp server dns-list ip-address&<1-8> quit dhcp server dns-list ip-address&<1-8> { interface interface-type interface-number [ to interface-type interface-number ] all } By default, no DNS server address is configured Configuring NetBIOS Services for DHCP Clients For Microsoft Windows-based DHCP clients that communicate through NetBIOS protocol, the host name-to-ip address translation is carried out by WINS servers. So you need to perform WINS-related configuration for most Windows-based hosts. Currently, you can configure up to eight WINS addresses for a DHCP address pool. Host name-to-ip address mappings are needed for DHCP clients communicating through the NetBIOS protocol. According to the way to establish the mapping, NetBIOS nodes fall into the following four categories: B-node. Nodes of this type establish their mappings through broadcasting (The character b stands for the word broadcast). The source node obtains the IP address of the destination node by sending the broadcast packet containing the host name of the destination node. After receiving the broadcast packet, the destination node returns its IP address to the source node. P-node. Nodes of this type establish their mappings by communicating with WINS servers (The character p stands for peer-to-peer). The source node sends the unicast packet to the WINS server. After receiving the unicast packet, the 2-14

22 Chapter 2 DHCP Server Configuration WINS server returns the IP address corresponding to the destination node name to the source node. M-node. Nodes of this type are p-nodes mixed with broadcasting features (The character m stands for the word mixed), that is to say, this type of nodes obtain mappings by sending broadcast packets first. If they fail to obtain mappings, they send unicast packets to the WINS server to obtain mappings. H-node. Nodes of this type are b-nodes mixed with peer-to-peer features (The character h stands for the word hybrid), that is to say, this type of nodes obtain mappings by sending unicast packets to WINS servers. If they fail to obtain mappings, they send broadcast packets to obtain mappings. Follow these steps to configure NetBIOS services for the DHCP server: Configure the WINS server address for DHCP clients Configure the current interface Configure multiple interfaces in system view interface interface-type interface-number dhcp server nbns-list ip-address&<1-8> quit dhcp server nbns-list ip-address&<1-8> { interface interface-type interface-number [ to interface-type interface-number ] all } By default, no WINS server address is configured Configure NetBIOS node types for DHCP clients Configure the current interface Configure multiple interfaces in system view interface interface-type interface-number dhcp server netbios-type { b-node h-node m-node p-node } quit dhcp server netbios-type { b-node h-node m-node p-node } { interface interface-type interface-number [ to interface-type interface-number ] all } By default, no NetBIOS node type is specified and a DHCP client uses an h-node Customizing DHCP Service With the evolution of DHCP, new options are constantly coming into being. You can add the new options as the properties of DHCP servers by performing the following configuration. Follow these steps to customize DHCP service: 2-15

23 Chapter 2 DHCP Server Configuration Configure customize d options Configure the current interface Configure multiple interfaces in system view interface interface-type interface-number dhcp server option code { ascii ascii-string hex hex-string&<1-10> ip-address ip-address&<1-8> } quit dhcp server option code { ascii ascii-string hex hex-string&<1-10> ip-address ip-address&<1-8> } { interface interface-type interface-number [ to interface-type interface-number ] all } By default, no customized option is configured 2.4 DHCP Security Configuration DHCP security configuration is needed to ensure the security of DHCP service Prerequisites Before configuring DHCP security, you should first complete the DHCP server configuration (either global address pool-based or interface address pool-based DHCP server configuration) Configuring Private DHCP Server Detecting A private DHCP server on a network also answers IP address request packets and assigns IP addresses to DHCP clients. However, the IP addresses they assigned may conflict with those of other hosts. As a result, users cannot normally access networks. This kind of DHCP servers are known as private DHCP servers. With the private DHCP server detecting function enabled, when a DHCP client sends the DHCP-REQUEST packet, the DHCP server tracks the information (such as the IP addresses and interfaces) of DHCP servers to enable the administrator to detect private DHCP servers in time and take proper measures. Follow these steps to enable detection of a private DHCP server: 2-16

24 Chapter 2 DHCP Server Configuration Enable the private DHCP server detecting function dhcp server detect By default, the private DHCP server detecting function is disabled Configuring IP Address Detecting To avoid IP address conflicts caused by assigning the same IP address to multiple DHCP clients simultaneously, you can configure a DHCP server to detect an IP address before it assigns the address to a DHCP client. IP address detecting is achieved by performing ping operations. To detect whether an IP address is currently in use, the DHCP server sends an ICMP packet with the IP address to be assigned as the destination and waits for a response. If the DHCP server receives no response within a specified time, it resends an ICMP packet. This procedure repeats until the DHCP server receives a response or the number of the sent ICMP packets reaches the specified maximum number. The DHCP server assigns the IP address to the DHCP client only when no response is received during the whole course, thus ensuring that an IP address is assigned to one DHCP client exclusively. Follow these steps to configure IP address detecting: Set the maximum number of ICMP packets a DHCP server sends in a ping test Set the response timeout time of each ICMP packet dhcp server ping packets number dhcp server ping timeout milliseconds Optional By default, a DHCP server performs the ping operation twice to test an IP address Optional The default timeout time is 500 milliseconds 2-17

25 Chapter 2 DHCP Server Configuration 2.5 Displaying and Maintaining a DHCP Server Display the statistics on IP address conflicts Display lease expiration information Display the free IP addresses Display information about address binding Display the statistics on a DHCP server Display information about DHCP address pool tree Clear IP address conflict statistics Clear dynamic address binding information Clear the statistics on a DHCP server display dhcp server conflict { all ip ip-address } display dhcp server expired { ip ip-address pool [ pool-name ] interface [ interface-type interface-number ] all } display dhcp server free-ip display dhcp server ip-in-use { ip ip-address pool [ pool-name ] interface [ interface-type interface-number ] all } display dhcp server statistics display dhcp server tree { pool [ pool-name ] interface [ interface-type interface-number ] all } reset dhcp server conflict { all ip ip-address } reset dhcp server ip-in-use { ip ip-address pool [ pool-name ] interface [ interface-type interface-number ] all } reset dhcp server statistics Available in any view Available in user view Note: Executing the save command will not save the lease information on a DHCP server to the flash memory. Therefore, the configuration file contains no lease information after the DHCP server restarts or you clear the lease information by executing the reset dhcp server ip-in-use command. In this case, any lease-update requests will be denied, and the clients must apply for IP addresses again. 2.6 DHCP Server Configuration Example Currently, DHCP networking can be implemented in two ways. One is to deploy the DHCP server and DHCP clients in the same network segment. This enables the clients to communicate with the server directly. The other is to deploy the DHCP server and DHCP clients in different network segments. In this case, IP address 2-18

26 Chapter 2 DHCP Server Configuration assigning is carried out through DHCP relay agent. Note that DHCP server configuration is the same in both scenarios. I. Network requirements The DHCP server assigns IP addresses dynamically to the DHCP clients on the same network segment. The network segment /24, to which the IP addresses of the address pool belong, is divided into two sub-network segments: /25 and /25. The switch operating as the DHCP server hosts two VLANs, whose interface IP addresses are /25 and /25 respectively. The DHCP settings of the /25 network segment are as follows: Lease time: 10 days plus 12 hours Domain name: aabbcc.com DNS server: WINS server: none Gateway: The DHCP settings of the /25 network segment are as follows: Lease time: 5 days Domain name: aabbcc.com DNS server: WINS server: Gateway: Note: If you use the inheriting relation of parent and child address pools, make sure that the number of the assigned IP addresses does not exceed the number of the IP addresses in the child address pool; otherwise extra IP addresses will be obtained from the parent address pool. The attributes (for example, gateway) also are based on the configuration of the parent address pool. For example, in the network to which VLAN-interface 1 is connected, if multiple clients apply for IP addresses, the child address pool /25 assigns IP addresses first. When the IP addresses in the child address pool have been assigned, if other clients need IP addresses, the IP addresses will be assigned from the parent address pool /24 and the attributes will be based on the configuration of the parent address pool. For this example, the number of clients applying for IP addresses from VLAN-interface 1 is recommended to be less than or equal to 122 and the number of clients applying for IP addresses from VLAN-interface 2 is recommended to be less than or equal to

27 Chapter 2 DHCP Server Configuration II. Network diagram Client WINS server Client Client /25 Vlan-int /25 Vlan-int / /25 Gateway A /25 Vlan-int1 Switch A DHCP server /25 Gateway B DNS server Switch B Client Client Client Figure 2-1 Network diagram for DHCP configuration III. Configuration procedure 1) Configure a VLAN and add a port in this VLAN, and then configure the IP address of the VLAN interface (omitted). 2) Configure DHCP service. # Enable DHCP. <H3C> system-view [H3C] dhcp enable # Configure the IP addresses that are not dynamically assigned. (That is, the IP addresses of the DNS server, WINS server, and gateways.) [H3C] dhcp server forbidden-ip [H3C] dhcp server forbidden-ip [H3C] dhcp server forbidden-ip [H3C] dhcp server forbidden-ip # Configure DHCP address pool 0, including address range and DNS server address. [H3C] dhcp server ip-pool 0 [H3C-dhcp-pool-0] network mask [H3C-dhcp-pool-0] domain-name aabbcc.com [H3C-dhcp-pool-0] dns-list [H3C-dhcp-pool-0] quit # Configure DHCP address pool 1, including address range, gateway, and lease time. [H3C] dhcp server ip-pool 1 [H3C-dhcp-pool-1] network mask [H3C-dhcp-pool-1] gateway-list [H3C-dhcp-pool-1] expired day 10 hour 12 [H3C-dhcp-pool-1] quit 2-20

28 Chapter 2 DHCP Server Configuration # Configure DHCP address pool 2, including address range, gateway, WINS server address, and lease time. [H3C] dhcp server ip-pool 2 [H3C-dhcp-pool-2] network mask [H3C-dhcp-pool-2] expired day 5 [H3C-dhcp-pool-2] nbns-list [H3C-dhcp-pool-2] gateway-list Troubleshooting a DHCP Server I. Symptom The IP address dynamically assigned by a DHCP server to a client conflicts with the IP address of another host. II. Analysis With DHCP enabled, IP address conflicts are usually caused by IP addresses that are manually configured on hosts. III. Solution Disconnect the DHCP client from the network and then check whether there is a host using the conflicting IP address by performing ping operation on another host on the network, with the conflicting IP address as the destination and an enough timeout time. The IP address is manually configured on a host if you receive a response packet of the ping operation. You can then disable the IP address from being dynamically assigned by using the dhcp server forbidden-ip command on the DHCP server. Attach the DHCP client to the network, release the dynamically assigned IP address and obtain an IP address again. For example, enter DOS by executing the cmd command in Windows XP, and then release the IP address by executing the ipconfig/release command. Then obtain an IP address again by executing the ipconfig/renew command. 2-21

29 Chapter 3 DHCP Relay Agent Configuration Chapter 3 DHCP Relay Agent Configuration When configuring DHCP relay agents, go to these sections for information you are interested in: Introduction to DHCP Relay Agent Configuring DHCP Relay Agent Displaying and Maintaining DHCP Relay Agent DHCP Relay Agent Configuration Example Troubleshooting DHCP Relay Agent 3.1 Introduction to DHCP Relay Agent Usage of DHCP Relay Agent Since the packets are broadcasted in the process of obtaining IP addresses, DHCP is only applicable to the situation that DHCP clients and DHCP servers are in the same network segment, that is, you need to deploy at least one DHCP server for each network segment, which is far from economical. The DHCP relay agent is designed to address this problem. It enables DHCP clients in a subnet to communicate with the DHCP server in another subnet so that the DHCP clients can obtain IP addresses. In this case, the DHCP clients in multiple networks can use the same DHCP server, which can decrease your cost and provide a centralized administration DHCP Relay Agent Fundamentals Figure 3-1 illustrates a typical DHCP relay agent application. DHCP client DHCP client IP network DHCP relay agent DHCP client DHCP client DHCP server Figure 3-1 Typical DHCP relay agent application 3-1

30 Chapter 3 DHCP Relay Agent Configuration DHCP relay agents can transparently transmit broadcast packets on DHCP clients or servers to the DHCP servers or clients in other network segments. In the process of dynamic IP address assignment through the DHCP relay agent, the DHCP client and DHCP server interoperate with each other in a similar way as they do without the DHCP relay agent. The following sections only describe the forwarding process of the DHCP relay agent. For the interaction process of the packets, see Obtaining IP Addresses Dynamically. 1) The DHCP client broadcasts the DHCP-DISCOVER packet. 2) After receiving the packets, the network device providing the DHCP relay agent function unicasts the packet to the designated DHCP server based on the configuration. 3) The DHCP server assigns IP addresses and transmits the configuration information to the clients through the DHCP relay agent so that the clients can be configured dynamically. The transmission mode depends on the flag field in the DHCP-DISCOVER packet. For details, see section DHCP Packet Format Option 82 Supporting I. Introduction to option 82 supporting Option 82 is a relay agent information option in DHCP packets. When a request packet from a DHCP client travels through a DHCP relay agent on its way to the DHCP server, the DHCP relay agent adds option 82 into the request packet. Option 82 includes many sub-options, but the DHCP server supports only sub-option 1 and sub-option 2 at present. Sub-option 1 defines agent circuit ID (that is, Circuit ID) and sub-option 2 defines remote agent ID (that is, Remote ID). Option 82 enables a DHCP server to track the address information of DHCP relay agents, through which and other proper software, you can achieve the DHCP assignment limitation and accounting functions. II. Primary terminologies Option: A length-variable field in DHCP packets, carrying information such as part of the lease information and packet type. It includes at least one option and at most 255 options. Option 82: Also known as relay agent information option. This option is a part of the Option field in DHCP packet. According to RFC3046, option 82 lies before option 255 and after the other options. Option 82 includes at least one sub-option and at most 255 sub-options. Currently, the commonly used sub-options in option 82 are sub-option 1 and sub-option 2. Sub-option 1: A sub-option of option 82. Sub-option 1 represents the agent circuit ID, namely Circuit ID. It holds the port number and VLAN-ID of the switch port connected to the DHCP client, and is usually configured on the DHCP relay 3-2