For this task, a new router R9 is added to the topology.
Router R9 represents the Internet from the perspective of AS17 and its clients. 

1. Configure the following interfaces on R9 to represent the "Internet":

          Loopback1, ipv4 address 11.11.11.11/8.

          Loopback2, ipv4 address 22.22.22.22/8.

          Loopback3, ipv4 address 33.33.33.33/8. 

2. Configure eBGP session between R1 and R9. 

3. Configure AS17, so all routers have access to AS9 and to the prefixes representing the internet           access.
4. Customer A has been allocated an IPv4 address block 67.0/16 and assigned an AS number 67.
    Each site is allocated /24 prefix from this block - 67.0.6/24 for R6 & 67.0.7/24 for R7.
    Router R6 represents the head office, and router R7 represents the branch.
    Customer A should be able to access the Internet from it's routable address space.
    Customer A site R7 should access the Internet via the head office site (R6).
    On the link between head office (R6) and its service provider (R5), separate between Internet-             bound and site-to-site traffic.
    Customer should be responsible for advertising it's public prefix upstream.
    You are allowed to use an additional prefix 17.0.65.0/24 for this requirement. 

5. Customer B has been allocated an IPv4 address block 48.0/16.
    Each site is allocated /24 prefix from this block.
    Each site should have an independent access to Internet, from it's routable address space,  via the service provider. (assume Customer     B has no additional connections, and AS17 is it's only upstream provider).
    Service provider is responsible for advertising the 67.0/16 prefix.  

Highlight the text below to reveal the solution.


This task requires an understanding of Internet access options for L3VPN solutions.





Requirement #3 - Enable ipv4 address-family on iBGP peerings inside AS17. Also, advertise AS17                                  prefix 17.0/16 to R9 via eBGP. On R1, either advertise the network 9.0.19/24 to                                    ISIS, or set "next-hop-self" on iBGP sessions to neighbors. The first method is                                      recommended for faster convergence.


Requirement #4 - For Customer A, Internet traffic is separated from site-to-site traffic using two                                      logical interfaces.
                             One interface is between CE to PE VRF, and provides site-to-site traffic. 
                             Add a second interface between CE to PE global routing table, to provides Internet                              access.
                             Branch site should have a default route towards the head office site.
                             Keep the specific routes in branch routing table, in case there is branch to branch                                  traffic, so it won't have to traverse the head office, and take the optimal route. 
                             This type of solution allows separation of Internet and site-to-site traffic.

Requirement #5 - For Customer B, Internet access is configured using static routing on PE router                                    only. PE router has a default route from VRF to global routing table (towards                                        Internet) and from global routing table to VRF. Only configuration change required                              on CE router is to add a default route towards the PE.

R1:

R2: 

R4:

R5:

R6: 

R8:

Verification: