
Assign an IP Address using DHCP
The following section describes DHCP and the client in a network.
When a client joins a network:
1.
The client initially broadcasts a
DHCPDISCOVER
message on the subnet to discover available DHCP servers. This message
includes the parameters that the client requires and might include suggested values for those parameters.
2.
Servers unicast or broadcast a
DHCPOFFER
message in response to the DHCPDISCOVER that offers to the client values for
the requested parameters. Multiple servers might respond to a single DHCPDISCOVER; the client might wait a period of time
and then act on the most preferred offer.
3.
The client broadcasts a
DHCPREQUEST
message in response to the offer, requesting the offered values.
4.
After receiving a DHCPREQUEST, the server binds the clients’ unique identifier (the hardware address plus IP address) to the
accepted configuration parameters and stores the data in a database called a binding table. The server then broadcasts a
DHCPACK
message, which signals to the client that it may begin using the assigned parameters.
5.
When the client leaves the network, or the lease time expires, returns its IP address to the server in a
DHCPRELEASE
message.
There are additional messages that are used in case the DHCP negotiation deviates from the process previously described and
shown in the illustration below.
DHCPDECLINE
A client sends this message to the server in response to a DHCPACK if the configuration parameters are
unacceptable; for example, if the offered address is already in use. In this case, the client starts the
configuration process over by sending a DHCPDISCOVER.
DHCPINFORM
A client uses this message to request configuration parameters when it assigned an IP address manually
rather than with DHCP. The server responds by unicast.
DHCPNAK
A server sends this message to the client if it is not able to fulfill a DHCPREQUEST; for example, if the
requested address is already in use. In this case, the client starts the configuration process over by sending a
DHCPDISCOVER.
Figure 38. Client and Server Messaging
Implementation Information
The following describes DHCP implementation.
•
Dell Networking implements DHCP based on RFC 2131 and RFC 3046.
•
IP source address validation is a sub-feature of DHCP Snooping; the Dell Networking OS uses access control lists (ACLs)
internally to implement this feature and as such, you cannot apply ACLs to an interface which has IP source address validation. If
Dynamic Host Configuration Protocol (DHCP)
283
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...