Differences

This shows you the differences between two versions of the page.

--- training:sanog32:d-dhcpv6pd [2018/07/26 15:54] – [Removing IPv6 configuration on Customer Router] philip
+++ training:sanog32:d-dhcpv6pd [2018/08/17 18:00] (current) – [Activating the link to the Customer Router] philip
@@ Line 11: / Line 11: @@
 Before we start this lab, remove any previous extra lab configuration on the Access and Customer routers and revert both routers to the configuration as it was at the end of the [[training:sanog32:d-static|Static Lab]]. Check connectivity is working from the Customer router to the rest of the lab network as expected.
+The following notes assume that changes need to be made from those required for the Static Lab.
 ==== Removing IPv6 on the link to the Customer ====
@@ Line 69: / Line 70: @@
   * `dns-server` specifies a DNS resolver to use - this is just an example
   * `domain-name` specifies the default domain-name for unqualified names - again this is just an example
 ==== Advertising the DHCPv6-PD pool to the rest of the network ====
@@ Line 95: / Line 96: @@
    description P2P Link to CustX
    ipv6 enable
-   ipv6 dhcp server DHCPv6
+   ipv6 dhcp server DHCPv6 rapid-commit
   !
@@ Line 104: / Line 105: @@
 With the Access Router configuration now completed, we can turn our attention to the Customer router configuration.
-We need to configure the point-to-point link to the Access Router to request an IPv6 address block by DHCPv6-PD. We will use a feature in Cisco IOS called “general-prefix”. This allows us to refer to learned addresses (by 6rd, DHCPv6PD etc) without configuring specific addresses on each prefix.
+We need to configure the point-to-point link to the Access Router to request an IPv6 address block by DHCPv6-PD. We will use a feature in Cisco IOS called `general-prefix`. This allows us to refer to learned addresses (by 6rd, DHCPv6PD etc) without configuring specific addresses on each prefix.
 This following configuration example will do the needful:
@@ Line 117: / Line 118: @@
   * `ipv6 address autoconfig default` will set up the interface for auto configuration – this does two things, the first enabling IPv6 on the interface, and the second by setting IPv6 address depending on what is configured on the other end of the link. In our case it will result in just a link local address being used. The `default` keyword means that the router will install a default route on this interface to whatever the destination is at the other end of the link. This saves the requirement of configuring a static default route else where in the configuration.
-  * `ipv6 dhcp client pd PDLAB rapid-commit` says that the interface will operate in DHCPv6 client mode, using Prefix Delegation to learn the address block from the neighbouring router, and it will save the address block in `PDLAB`. `rapid-commit` simply speeds up the DHCPv6 process between client and server (2 messages are used rather than 4) and is generally recommended by most network operators.
+  * `ipv6 dhcp client pd PDLAB rapid-commit` says that the interface will operate in DHCPv6 client mode, using Prefix Delegation to learn the address block from the neighbouring router, and it will save the address block in `PDLAB`.
+  * `rapid-commit` simply speeds up the DHCPv6 process between client and server (2 messages are used rather than 4) and is generally recommended by most network operators.
 ==== Configuring Local Interfaces ====
@@ Line 156: / Line 158: @@
 ===== Testing =====
-With the DHCPv6-PD now set up, trying some IPv4 and IPv6 traceroutes from the Customer router to the backbone Transit providers and out to the Internet. (Note that the lab doesn’t have IPv6 connectivity, but at least try IPv6 traceroutes into the Transit backbone and to other groups.)
+With the DHCPv6-PD now set up, trying some IPv4 and IPv6 traceroutes from the Customer router to the backbone Transit providers and out to the Internet. **Hint**: Use the Loopback interface as the source of your traceroutes and pings.
+(Note that the lab doesn’t have IPv6 connectivity, but at least try IPv6 traceroutes into the Transit backbone and to other groups.)
 What do you see?
+[[:training:sanog32:agenda| Back to Agenda page]]