Differences

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

--- training:sanog32:d-6rd [2018/07/26 14:46] – philip
+++ training:sanog32:d-6rd [2018/08/05 19:56] (current) – [Disabling IPv6 on the Core and Access routers] philip
@@ Line 13: / Line 13: @@
 We also need to remove any IPv6 configured on the network as we will be replacing it with 6rd technology. The following subsections describe what needs to be done.
-==== Disabling IPv6 on the core router ====
+==== Disabling IPv6 on the Core and Access routers ====
 The first step is to disable IPv6 on the Access and Core routers. Be sure to keep a copy of the configuration of the Access and Core routers first! (We won’t worry about the Peering Router as it isn’t needed for this part of the lab work.)
@@ Line 20: / Line 20: @@
   no ipv6 unicast-routing
-This will remove all the IPv6 routing protocol configuration on the core router, including OSPF/IS-IS and BGP. The IPv4 configuration will still remain, and the IPv4 routing will still function. You will notice that IPv6 addressing will remain on the router interfaces, and configuration like IPv6 packet filters etc.
-Confirm that IPv4 routing still works.
 This will remove all the IPv6 routing protocol configuration on those two routers, including OSPF/IS-IS and BGP. The IPv4 configuration will still remain, and the IPv4 routing will still function. You will notice that IPv6 addressing will remain on the router interfaces, and configuration like IPv6 packet filters etc.
@@ Line 30: / Line 26: @@
 And confirm that IPv6 routing no longer works - you should no longer have any IPv6 connectivity between the Border, Peering and Access routers.
+==== Originating IPv6 Aggregate on the Border router ====
+Because we have removed IPv6 routing from the Core router, we have also stopped announcing our IPv6 aggregate to the Transit network. To test that our 6rd deployment is working, we need to temporarily originate our IPv6 aggregate from the Border router. Here is an example:
+  router bgp X0
+   address-family ipv6
+    network 2001:DB8:X::/48
+  !
+  ipv6 route 2001:DB8:X::/48 Null0
 ==== Removing IPv6 on the link to the Customer ====
@@ Line 72: / Line 80: @@
 What we will set up is something similar to the diagram below.
-![](diagrams/6rd-diagram.png)
+{{:training:sanog32:6rd-diagram.png?600|}}
 The Customer Router in the diagram is our Customer Router in our network. And the ISP 6rd BR capability will be configured on our autonomous system’s Border Router.
@@ Line 131: / Line 139: @@
    description Local LAN
    ipv6 address 6RDLAB ::1:0:0:0:1/64
+  !
+For good measure, let’s recreate our Loopback interface too; this will restore our anchor point we can test against:
+  interface Loopback0
+   description Customer Router Loopback
+   ipv6 address 6RDLAB ::2:0:0:0:1/64
+   no shutdown
   !
@@ Line 143: / Line 159: @@
   Tunnel0                [up/up]
       FE80::6444:3C22
+  Loopback0              [up/up]
+    FE80::C81D:5FF:FEAF:8
+:DB8:60:C222::1
+Refer to the earlier discussion about the “general-prefix”. We have `2001:DB8:6:C220::/60` as the IPv6 subnet created by 6rd. Taking this and appending `::1:0:0:0:0` results in the first subnet to be allocated to the network - the `FastEthernet0/0` interface there is automatically assigned `2001:DB8:6:C221::/64`, with the IPv6 address on the interface being `2001:DB8:6:C221::1/64`.
 ===== Configuring the Access Router =====
-The point-to-point link address from the network operator to the customer is normally not carried in the IGP or eve in the BGP. However, 6rd uses the point-to-point link address as the basis for the IPv6 prefix generated for 6rd. So the network operator needs to carry the point-to-point link address at least as far as the 6BR router so that the IPv6 tunnel can see its end point on the customer router.
+The point-to-point link address from the network operator to the customer is normally not carried in the IGP or even in the BGP. However, 6rd uses the point-to-point link address as the basis for the IPv6 prefix generated for 6rd. So the network operator needs to carry the point-to-point link address at least as far as the 6BR router so that the IPv6 tunnel can see its end point on the customer router.
 The simple and scalable way to do this is to put the point-to-point link address into iBGP on the Access Router. Like this:
@@ Line 191: / Line 212: @@
 ===== Testing =====
-With the 6BR and the Customer router now set up to support 6rd, 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 6BR and the Customer router now set up to support 6rd, 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?