Differences

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

--- training:sanog32:2-bgp [2018/07/23 16:09] – [Adding a customer route] philip
+++ training:sanog32:2-bgp [2018/08/11 20:23] (current) – [Configuring Access and Peering Router iBGP] philip
@@ Line 113: / Line 113: @@
   !
+Where the example says “do the same for IPv6”, simply take the `route-map` name and create an IPv6 variant - for example “ibgp-rrv6”. You cannot use the same name of route-map for the IPv6 peering.
 ==== Configuring Border Router iBGP ====
@@ Line 175: / Line 176: @@
 ===== Adding a customer route =====
-Consult the address plan and now set up customer routes on the Access Router pointing to the Customer Router. We’ll just use one IPv4 and one IPv6 customer per Autonomous System. Take the address assigned for the “End User Space 1”; we will simply point a static route for the customer route to the other end of the point-to-point link to the Customer router. We’ll use a /26 for IPv4 and a /52 for IPv6 out of the “End User Space 1” assignments.
+Consult the address plan and now set up customer routes on the Access Router pointing to the Customer Router. We’ll just use one IPv4 and one IPv6 customer per Autonomous System. Take the address assigned for the “End User Space 1”; we will simply point a static route for the customer route to the Null0 interface as we do not have a Customer router in our network (at this point). We’ll use a /26 for IPv4 and a /52 for IPv6 out of the “End User Space 1” assignments.
 Here is an example for the Access router.
+  ip route 100.68.X.64 255.255.255.192 Null0
-  ip route 100.68.X.64 255.255.255.192 100.68.X.34
+  ipv6 route 2001:DB8:X:4000::/52 Null0
-  ipv6 route 2001:DB8:X:4000::/52 2001:DB8:X:20::1
   !
   router bgp X0
@@ Line 189: / Line 189: @@
     network 2001:DB8:X:4000::/52
   !
-On the Customer router, we need to set up a static default route (IPv4 and IPv6) pointing to the Access router, and we need to create a source anchor point for the address space we have assigned to the customer. The simplest way to do this is to route create a Loopback interface on the Customer router with the IPv4 and IPv6 address blocks in question. Here is an example configuration:
-  interface Loopback0
-   description Address anchor for Customer X
-   ip address 100.68.X.64 255.255.255.192
-   ipv6 address 2001:DB8:X:4000::/52
-  !
-  ip route 0.0.0.0 0.0.0.0 100.68.X.33
-  ipv6 route ::/0 2001:DB8:X:20::
 Once this has been configured you should then see the customer IPv4 /26 and IPv6 /52 visible in the iBGP for the AS. Check on the Border, Peering and Core routers, and make sure the prefix is visible. Use these commands:
   show ip bgp
   show bgp ipv6 unicast