- DHCPv4
- DHCPv6 Configuration
- DHCPv6 Router Advertisement
- DHCPv6 Router Roles
- Stateless DHCPv6 Configuration (Router-As-Server)
- Stateless DHCPv6 Configuration (Router-As-Client)
- Stateful DHCPv6 Configuration (Router-As-Server)
- Stateful DHCPv6 Configuration (Router-As-Client)
- DHCPv6 Relay Agent Configuration
- DHCPv6 Relay Agent Verification Commands
- DHCPv6 Server Verification Commands
Exclude IPv4 Addresses
Define a DHCPv4 Pool Name
Configure the DHCPv4 Pool
Configure a Router to relay DHCPv4 broadcasts to an external DHCPv4 server
By default, the ip helper-address
command forwards the following eight UDP services
Configure a Cisco IOS router as a DHCPv4 client - [connect the Ethernet interface to a cable or DSL modem]
To enable the sending of RA messages, a router must join the IPv6 all-routers group using the ipv6 unicast-routing global config command, as show in the output.
Stateless DHCPv6 is enabled on a router interface using the ipv6 nd other-config-flag
interface configuration command. This sets the O flag to 1
.
Use the command no ipv6 nd other-config-flag
to reset the interface to the default SLAAC only option (i.e. set the O flag to 0
).
Stateful DHCPv6 is enabled on a router interface using the ipv6 nd managed-config-flag
interface configuration command. This sets the M flag to 1
. The ipv6 nd prefix default no-autoconfig
interface command disables SLAAC by setting the A flag to 0
.
The stateless DHCPv6 server option requires that the router advertise the IPv6 network addressing information in RA messages. However, the client must contact a DHCPv6 server for more information.
Pool names do not have to be uppercase. However, using an uppercase name makes it easier to see in a configuration.
The DHCPv6 pool has to be bound to the interface using the ipv6 dhcp server POOL-NAME
interface config command as shown in the output.
The O flag must be manually changed from 0 to 1 using the interface command ipv6 nd other-config-flag
. The A flag is 1 by default, telling clients to use SLAAC to create their own GUA.
A router can also be a DHCPv6 client and get an IPv6 configuration from a DHCPv6 server, such as a router functioning as a DHCPv6 server.
It may take the interface a few seconds to complete the process.
The stateful DHCP server option requires that the IPv6 enabled router tells the host to contact a DHCPv6 server to obtain all necessary IPv6 network addressing information.
0
to 1
using the interface command ipv6 nd managed-config-flag
.1
to 0
using the interface command ipv6 nd prefix default no-autoconfig
. Setting the A flag to 0
tells the client not to use SLAAC to create a GUA.ipv6 dhcp server
command binds the DHCPv6 pool to the interface.You can use the no ipv6 nd managed-config-flag
command to set the M flag back to its default of 0
.
Similarly, no ipv6 nd prefix default no-autoconfig
command sets the A flag back to its default of 1
.
The client router needs to have ipv6 unicast-routing enabled and an IPv6 link-local address to send and receive IPv6 messages.
If the DHCPv6 server is located on a different network than the client, then the IPv6 router can be configured as a DHCPv6 relay agent. The configuration of a DHCPv6 relay agent is similar to the configuration of an IPv4 router as a DHCPv4 relay.
This command is configured on the interface facing the DHCPv6 clients and specifies the DHCPv6 server address and egress interface to reach the server, as shown above. The egress interface is only required when the next-hop address is an LLA.
The DHCPv6 relay agent can be verified using the show ipv6 dhcp interface
command. This will verify that the appropriate interface is in relay mode.
On the DHCPv6 server, use the show ipv6 dhcp binding
command to verify if any hosts have been assigned an IPv6 configuration.
The show ipv6 dhcp pool
command verifies the name of the DHCPv6 pool and its parameters. The command also identifies the number of active clients.
The show ipv6 dhcp binding
command displays the IPv6 link-local address of the client and the global unicast address assigned by the server.
This information is maintained by a stateful DHCPv6 server. A stateless DHCPv6 server would not maintain this information.