The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The DHCP Relay Server ID Override and Link Selection Option 82 Suboptions feature enables the relay agent to be part of all Dynamic Host Configuration Protocol (DHCP) message exchanges by supporting the use of two suboptions of the relay agent information option (option 82). This design allows DHCPv4 to operate in networks where direct communication between the client and server is not possible or desired. These two suboptions used together enable the deployment of an architecture where having all DHCP traffic flow through the relay agent is desirable, allowing for greater control of DHCP communications.
This feature also introduces the capability to manually configure the interface for the relay agent to use as the source IP address for messages relayed to the DHCP server. This configuration allows the network administrator to specify a stable, hardware-independent IP address (such as a loopback interface).
If the DHCP Relay Server ID Override and Link Selection Option 82 Suboptions feature and the DHCP Relay MPLS VPN Support feature are both configured, the DHCP Relay MPLS VPN Support feature takes precedence.
The server identifier (ID) override suboption allows the DHCP relay agent to specify a new value for the server ID option, which is inserted by the Dynamic Host Configuration Protocol (DHCP) server in the reply packet. This suboption allows the DHCP relay agent to act as the actual DHCP server such that the renew requests will come to the relay agent rather than the DHCP server directly. The server ID override suboption contains the incoming interface IP address, which is the IP address on the relay agent that is accessible from the client. The DHCP client uses this information to send all renew and release request packets to the relay agent. The relay agent adds all of the appropriate suboptions and then forwards the renew and release request packets to the original DHCP server.
The link selection suboption provides a mechanism to separate the subnet/link on which the DHCP client resides from the the gateway address (giaddr), which can be used to communicate with the relay agent by the DHCP server. The relay agent will set the suboption to the correct subscriber subnet and the DHCP server will use that value to assign an IP address rather than the giaddr value. The relay agent will set the giaddr to its own IP address so that DHCP messages are routable over the network.
The Dynamic Host Configuration Protocol (DHCP) IPv4 deployment model assumes a single routing domain between the DHCP client and DHCP server. In some network designs, the DHCP server cannot directly communicate with DHCP clients. Customers may choose this design to make critical infrastructure servers inaccessible and to protect the DHCP server from client attacks.
Relay agents are used to forward requests and replies between clients and servers when they are not on the same physical subnet. In all cases, the DHCP relay agent must be able to communicate directly with both the DHCP server and DHCP client. By using the relay agent information option (option 82), the DHCP relay agent can include additional information about itself when forwarding client-originated DHCP packets to a DHCP server.
The DHCP Relay Server ID Override and Link Selection Option 82 Suboptions feature enables the relay agent to be part of all DHCP message exchanges by supporting the use of two suboptions of option 82: server ID override and link selection. This design results in all DHCP messages flowing through the relay agent, allowing for greater control of DHCP communications.
Communication from the DHCP server through the relay agent can be an issue. If the server needs to reach the client, it must do so through the relay agent. The IP address of the relay agent might not be ideal. For example, if the network is renumbered or if the interface at the relay agent is down for some reason, the server may not be able to reach the client. This feature introduces the capability to manually configure the interface for the relay agent to use as the source IP address for messages relayed to the DHCP server. This configuration allows the network administrator to specify a stable, hardware-independent IP address (such as a loopback interface).
The figure and the numbered list that follows it shows the processing that occurs on the DHCP relay agent and DHCP server when this feature is configured.
The DHCP client generates a DHCP request and broadcasts it on the network.
The DHCP relay agent intercepts the broadcast DHCP request packet and inserts a server ID override suboption and link selection suboption to its relay agent information option in the DHCP packet. The server ID override and link selection suboptions contain the incoming interface IP address, which is the IP address on the relay agent that is accessible from the client (10.1.1.1 in this case).
The relay agent sets the gateway IP address (giaddr) to the IP address of an interface that is reachable by the DHCP server (typically the server-facing interface that will be used to transmit the message, 10.3.1.2 in this case).
If the source interface is explicitly configured on a loopback interface (using the ip dhcp-relay source-interface command), the relay agent will use that address as the source IP address (giaddr) for messages relayed to the DHCP server (10.2.1.1 in this case).
The following processing occurs on the DHCP server after receiving the forwarded packets from the relay agent:
The DHCP server uses the link selection suboption to locate the correct address pools for the DHCP client.
The DHCP server sets the server ID option to the value specified by the server ID override suboption of the DHCP packet.
The DHCP server sends the reply message to the IP address specified in the giaddr.
The DHCP client will see the relay agent address as the server ID and use that address when unicasting RENEW messages.
This DHCP server supports all the AireOS remote-id format combinations on eWLC along with delimiter ’:’ support.
 Note |
If the DHCP Relay Server ID Override and Link Selection Option 82 Suboptions feature and the DHCP Relay MPLS VPN Support feature are both configured, the DHCP Relay MPLS VPN Support feature takes precedence. The eWLC does not support the ap-group and flex-connect group options, so “ap-group-name” and “flex-group-name” CLI is not supported. However, the eWLC supports policy-tag CLI which adds the site-tag to the remote-id. This CLI can be used as an alternative. |
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
ip dhcp-relay information option server-override Example: |
Enables the system to globally insert the server ID override and link selection suboptions into the DHCP relay agent information option in forwarded BOOTREQUEST messages to a Dynamic Host Configuration Protocol (DHCP) server.
|
|
Step 4 |
ip dhcp-relay source-interface type number Example: |
(Optional) Globally configures the source interface for the relay agent to use as the source IP address for relayed messages.
|
|
Step 5 |
interface type number Example: |
(Optional) Configures an interface and enters interface configuration mode. |
|
Step 6 |
ip dhcp relay information option server-id-override Example: |
(Optional) Enables the system to insert the server ID override and link selection suboptions on a specific interface into the DHCP relay agent information option in forwarded BOOTREQUEST messages to a DHCP server. |
|
Step 7 |
ipdhcpcompatibilitysuboptionlink-selection<standard/cisco> Example: |
Enables the system to configure corresponding link selection suboptions to the outgoing DHCP packets. |
|
Step 8 |
ipdhcpcompatibilitysuboptionserver-override<standard/cisco> Example: |
Enables the system to configure corresponding server-override sub-option values to the outgoing DHCP packets. |
|
Step 9 |
ip dhcp relay source-interface type number Example: |
(Optional) Configures the source interface for the relay agent to use as the source IP address for relayed messages. |
|
Step 10 |
end Example: |
Exits interface configuration mode and returns to privileged EXEC mode. |
In the following example, the IP address of the loopback interface is used as the source IP address for relayed messages. The client initiates IP address negotiation from GigabitEthernet interface 0/0/0. The Dynamic Host Configuration Protocol (DHCP) relay agent is configured globally to insert the server ID override suboption and link selection suboption into the relay agent information option of the DHCP packet. The relay agent uses the server ID override suboption to force the DHCP server to use that value as the server ID in the DHCP message. The DHCP server uses the link selection suboption to determine from which subnet to assign an IP address.
interface GigabitEthernet 0/0/0
ip address dhcp
ip dhcp-relay information option server-override
ip dhcp-relay source-interface loopback 0
!
interface Loopback0
ip address 10.2.1.1 255.255.255.0
!
interface GigabitEthernet 0/0/0
ip address 10.1.1.1 255.255.255.0
ip helper-address 10.3.1.1
!
interface GigabitEthernet 1/0/0
ip address 10.3.1.2 255.255.255.0
ip dhcp compatibility suboption link-selection <standard/cisco>
ip dhcp compatibility suboption server-override <standard/cisco>
ip dhcp excluded-address 10.3.0.1
ip dhcp pool pool1
network 10.1.1.0 255.255.255.0
lease 0 0 1
!
interface GigabitEthernet 0/0/0
ip address 10.3.1.1 255.255.255.0|
Related Topic |
Document Title |
|---|---|
|
Cisco IOS commands |
|
|
IP addressing commands |
|
|
DHCP conceptual information |
DHCP Overview |
|
DHCP server configuration tasks, examples, and conceptual information |
Configuring the Cisco IOS DHCP Server |
|
DHCP relay agent configuration tasks, examples, and conceptual information |
Configuring the Cisco IOS DHCP Relay Agent |
|
Standard/RFC |
Title |
|---|---|
|
RFC 3527 |
Link Selection Suboption |
|
RFC 5107 |
DHCP Server Identifier Override Suboption |
|
Description |
Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.|
Feature Name |
Releases |
Feature Configuration Information |
|---|---|---|
|
DHCP Relay Server ID Override and Link Selection Option 82 Suboptions |
The DHCP Relay Server ID Override and Link Selection Option 82 Suboptions feature enables the relay agent to be part of all Dynamic Host Configuration Protocol (DHCP) message exchanges by supporting the use of two suboptions of the relay agent information option (option 82). This design allows DHCPv4 to operate in networks where direct communication between the client and server is not possible or desired. These two suboptions used together enable the deployment of an architecture where having all DHCP traffic flow through the relay agent is desirable, allowing for greater control of DHCP communications. The following commands were introduced or modified: ip dhcp relay information option server-id-override, ip dhcp relay source-interface, ip dhcp-relay information option server-override, ip dhcp-relay source-interface. |
client —A host trying to configure its interface (obtain an IP address) using DHCP or BOOTP protocols.
DHCP —Dynamic Host Configuration Protocol.
DHCP options and suboptions —Configuration parameters and other control information are carried in tagged data items that are stored in the options field of the DHCP message. Options provide a method of appending additional information. Vendors that want to provide additional information to their client not designed into the protocol can use options.
giaddr —Gateway IP address field of the DHCP packet. The giaddr provides the DHCP server with information about the IP address subnet in which the client resides. The giaddr also provides the DHCP server with an IP address where the DHCP response messages can be sent.
relay agent —A router that forwards DHCP and BOOTP messages between a server and a client on different subnets.
Feedback