- DHCP Overview
- Configuring the Cisco IOS DHCP Server
- DHCP Server MIB
- Configuring the DHCP Server On-Demand Address Pool Manager
- DHCP Server RADIUS Proxy
- Configuring the Cisco IOS DHCP Relay Agent
- Configuring the Cisco IOS DHCP Client
- DHCP Option 82 Configurable Circuit ID and Remote ID
- Configuring DHCP Services for Accounting and Security
- Configuring DHCP Enhancements for Edge Session Management
- ISSU and SSO--DHCP High Availability Features
- DHCP Option 82 Support for Routed Bridge Encapsulation
- DHCPv6 Bulk-Lease Query
- DHCPv6 Relay and Server - MPLS VPN Support
- DHCPv6 Relay Source Configuration
- IPv6 Access Services: DHCPv6 Relay Agent
- DHCPv6 Server Stateless Autoconfiguration
- IPv6 Access Services: Stateless DHCPv6
- DHCPv6 Repackaging
- IPv6 Access Services: DHCPv6 Prefix Delegation
- DHCPv6 Guard
IPv6 Access Services: DHCPv6 Relay Agent
A Dynamic Host Configuration Protocol for IPv6 (DHCPv6) relay agent, which may reside on the client's link, is used to relay messages between the client and the server.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
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.
Information About IPv6 Access Services: DHCPv6 Relay Agent
DHCPv6 Relay Agent
A DHCPv6 relay agent, which may reside on the client's link, is used to relay messages between the client and the server. The DHCPv6 relay agent operation is transparent to the client. A DHCPv6 client locates a DHCPv6 server using a reserved, link-scoped multicast address. For direct communication between the DHCPv6 client and the DHCPv6 server, both of them must be attached to the same link. However, in some situations where ease of management, economy, or scalability is a concern, it is desirable to allow a DHCPv6 client to send a message to a DHCPv6 server that is not connected to the same link.
DHCPv6 Relay Agent Notification for Prefix Delegation
The DHCPv6 relay agent notification for prefix delegation allows the device working as a DHCPv6 relay agent to find prefix delegation options by reviewing the contents of a DHCPv6 RELAY-REPLY packet that is relayed by the relay agent to the client. When a prefix delegation option is found by the relay agent, the relay agent extracts the information about the prefix that is being delegated and inserts an IPv6 static route matching the prefix delegation information onto the relay agent. Future packets destined to that prefix via relay will be forwarded based on the information contained in the prefix delegation. The IPv6 static route is then left in the routing table until the prefix delegation lease time expires or the relay agent receives a release packet from the client releasing the prefix delegation.
No user configuration is required for this feature. Static route management is done automatically by the relay agent.
IPv6 routes are added when the relay agent relays a RELAY-REPLY packet, and IPv6 routes are deleted when the prefix delegation lease time expires or the relay agent receives a release message. An IPv6 static route in the routing table of the relay agent can be updated when the prefix delegation lease time is extended.
The DHCP--DHCPv6 Relay Agent Notification for Prefix Delegation feature leaves a static IPv6 route on the routing table of the relay agent. The registered IPv6 address allows unicast reverse packet forwarding (uRPF) to work by allowing the device doing the reverse lookup to confirm that the IPv6 address on the relay agent is not malformed or spoofed. The static route that remains in the routing table of the relay agent can be redistributed to other routing protocols to advertise the subnets to other nodes. Static routes will be removed when a DHCP_DECLINE message is sent by the client.
DHCPv6 Relay SSO and ISSU
In specific Cisco networking devices that support dual route processors (RPs), stateful switchover (SSO) takes advantage of RP redundancy to increase network availability. The feature establishes one of the RPs as the active processor while the other RP is designated as the standby processor, and then synchronizing critical state information between them. Following an initial synchronization between the two processors, SSO dynamically maintains RP state information between them.
The Cisco in-service software upgrade (ISSU) process allows Cisco software to be updated or otherwise modified while packet forwarding continues. In most networks, planned software upgrades are a significant cause of downtime. ISSU allows the Cisco software to be modified while packet forwarding continues. This increases network availability and reduces downtime caused by planned software upgrades.
The SSO and the ISSU use redundant hardware, with the active and standby RP each running an instance of the DHCPv6 relay agent. Both instances exchange run-time state data.
- DHCPv6 Relay Options: Remote ID for Ethernet Interfaces
- DHCPv6 Relay Options: Reload Persistent Interface ID Option
DHCPv6 Relay Options: Remote ID for Ethernet Interfaces
This feature adds the remote identification (remote-ID) option to relayed (RELAY-FORWARD) DHCPv6 packets.
The remote-ID option provides information to the DHCPv6 server, including port information, the system's DUID, and the VLAN ID. Collectively, this information can be used to uniquely identify both the relay and the port on the relay through which the client's packet arrived. The DHCPv6 server uses this information to select parameters specific to a particular user, host, or subscriber modem. This feature works only for Ethernet interfaces at this time.
This feature introduces no user configuration. Because the addition of the remote-ID option to the RELAY-FORWARD packet occurs automatically, no user configuration is necessary.
The DHCPv6 server does not need to echo the remote-ID option in the RELAY-REPLY packet. Internet Assigned Numbers Authority (IANA) has assigned the DHCPv6 option code 37 for the relay agent remote-ID option.
If the remote-ID option is included in the RELAY-REPLY packet, the option is stripped out of the packet before the packet is relayed to the client.
DHCPv6 Relay Options: Reload Persistent Interface ID Option
This feature makes the interface-ID option, which is used by relay agents to decide which interface should be used when forwarding a RELAY-REPLY packet, persistent. A persistent interface-ID option will not change if the router acting as a relay agent goes offline (such as during a reload or a power outage). When the router acting as a relay agent returns online, it is possible that changes to the internal interface index of the relay agent may have occurred in certain scenarios (such as cases where the relay agent reboots and has a change in the number of interfaces in the interface index, or the relay agents boots up and has more virtual interfaces than it did before the reboot). This feature prevents this scenario from causing any problems.
This feature changes the DHCPv6 interface-ID option to be expressed as simply the short form of the interface name. This syntax helps avoid potential problems that could arise due to physical or logical interfaces changing on the relay agent after a reload.
How to Configure IPv6 Access Services: DHCPv6 Relay Agent
Configuring the DHCPv6 Relay Agent
DETAILED STEPS
Configuration Examples for IPv6 Access Services: DHCPv6 Relay Agent
Example: Configuring the DHCPv6 Relay Agent
Device# show ipv6 dhcp interface
Ethernet1/0 is in relay mode
Relay destinations:
3FFB:C00:C18:6:A8BB:CCFF:FE03:2701
Serial3/0 is in relay mode
Relay destinations:
3FFB:C00:C18:6:A8BB:CCFF:FE03:2600
FE80::A8BB:CCFF:FE03:2801 on Serial3/0
FF05::1:3
Additional References
Related Documents
| Related Topic | Document Title |
|---|---|
| IPv6 addressing and connectivity |
IPv6 Configuration Guide |
| Cisco IOS commands |
|
| IPv6 commands |
|
| Cisco IOS IPv6 features |
Cisco IOS IPv6 Feature Mapping |
Standards and RFCs
| Standard/RFC | Title |
|---|---|
| RFCs for IPv6 |
IPv6 RFCs |
MIBs
| MIB |
MIBs Link |
|---|---|
|
|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
Technical Assistance
| 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. |
Feature Information for IPv6 Access Services: DHCPv6 Relay Agent
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.
| Table 1 | Feature Information for IPv6 Access Services: DHCPv6 Relay Agent |
| Feature Name | Releases | Feature Information |
|---|---|---|
| IPv6 Access Services: DHCPv6 Relay Agent |
12.2(46)SE 12.2(50)SG 12.2(33)SRC 12.2(33)SXI 12.3(11)T 12.4 15.0(2)SG 3.2.0SG Cisco IOS XE Release 2.2 Cisco IOS XE Release 3.8 15.3(1)S |
A DHCP relay agent, which may reside on the client's link, is used to relay messages between the client and server. The following commands were introduced or modified: ipv6 dhcp relay destination, show ipv6 dhcp interface. |
| DHCP: DHCPv6 Relay SSO/ISSU |
12.2(33)SRE |
SSO and ISSU use redundant hardware, with the active and standby RP each running an instance of the DHCP relay agent. |
| DHCPv6 Ethernet Remote ID Option |
12.2(46)SE 12.2(52)SG 12.2(33)SRC 12.2(33)SXI 15.0(2)SG 3.2.0SG |
This feature adds the remote-ID option to relayed (RELAY-FORWARD) DHCPv6 packets. |
| DHCPv6 Relay Agent Notification for Prefix Delegation |
12.2(46)SE 12.2(33)SRC 12.2(33)SXI 15.0(1)S |
DHCPv6 relay agent notification for prefix delegation allows the device working as a DHCPv6 relay agent to find prefix delegation options by reviewing the contents of a DHCPv6 packet that is being relayed by the relay agent to the client. |
| DHCPv6 Relay: Reload Persistent Interface ID Option |
12.2(46)SE 12.2(52)SG 12.2(33)SRC 12.2(33)SXI 15.0(2)SG 3.2.0SG |
This feature makes the interface-ID option, which is used by relay agents to decide which interface should be used when forwarding a RELAY-REPLY packet, persistent. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Feedback