Target Networking

In this lab, same concept, IPv6 tunneling is used, as it is used in my previous lab IPv6 Tunnel over IPv4 Network. Concept of making tunnel over the network is same but in both the topologies network is different. In my previous lab there is normal network running EIGRP as routing protocol but here network is comprises of MPLS L3 VPN, eBGP and some other concepts like GLBP, VRRP etc.

In this topology IPv6 tunnel is made from Server_router to SEMBO_TECH router. Between these two routers there are redundant paths. one path is from MPLS Layer 3 VPN and other is of eBGP. From Server_router side, GLBP protocol is used for redundancy whereas on SEMBO_TECH side VRRP protocol is used. IPv6_host is the DHCPv6 host of SEMBO_TECH IPv6 DHCP server.

In lab IPv6 Tunnel over IPv4 Network , concept of Router-ID is shown, because there is two routers on which there is no IPv4 addresses so we have to give Router-ID to the router. This concept is not applicable here because on all the routers have IPv4 addresses, so there is no need of Router-ID.

In eBGP path, loopback interfaces are made for routing in BGP, because loopback interface is a logical interface so it will remain up forever. On other path MLPS Layer 3 VPN, a VPN with MPLS is made over PE2 ---> P---> PE1 routers. MPLS L3VPN is a PE-based L3VPN technology for service provider VPN solutions. It uses BGP to advertise VPN routes and uses MPLS to forward VPN packets on service provider backbones. It provides flexible networking modes, excellent scalability, and convenient support for MPLS QoS.

The MPLS L3VPN model consists of three kinds of devices:

• Provider edge router (PE): A PE resides on a service provider network and connects one or more CEs to the network. On an MPLS network, all VPN processing occurs on the PEs.
  
  
• Provider (P) router: It is a backbone router on a service provider network. It is not directly connected with any CE. It only needs to be equipped with basic MPLS forwarding capability.
  
  
• Customer edge device (CE): A CE resides on a customer network and has one or more interfaces directly connected with service provider networks. It can be a router, a switch, or a host. It neither can "sense" the existence of any VPN nor needs to support MPLS.
  
  

IPv6 Tunnel

On Router Server_router :-

In this topology IPv6 tunnel is made over IPv4 network, color dark red representing the IPv4 network whereas color blue is showing IPv6 Network with IPv6 tunnel. EIGRP routing protocol is used for communication between both network IPv4 as well as IPv6. IPv4 network is using EIGRP 1 and IPv6 network is using EIGRP 2.

This topology is a example of Manually Configured Tunnel (MCT) which is a type of Static Point-to-Point IPv6 Tunnel. This lab is based on Manually Configured tunnel in which Tunnel mode is ipv6ip. RFC 4213 is made for this MCT tunnel.
There are two types of Static Point-to-Point tunnel :-
1. Manually Configured Tunnels (MCT)
2. Generic Routing Encapsulation (GRE) tunnels

In order to support the IGP`s and other features in these static tunnels router will assign link local addresses on these links and allow the forwarding of IPv6 multicast traffic.

This topology is clearing the concept that, if Router has only IPv6 addresses over it and no IPv4 addresses then we have to give Router-ID in the routing protocol otherwise that router will not communicate with the other routers because it will not have any route to other routers.
So here Router R5 and R6 has the Router-ID 5.5.5.5 and 6.6.6.6 .
Tunneling is one of the way to communicate IPv6 with IPv4 network. In this topology IPv6 tunnel is made from Router R1 to R4, and this tunnel has the IP address from subnet 2003::/64.

In GNS3, IPv6 routing have to be enabled on interface, it can not enabled by the network command in routing protocol.

IPv6 Tunnel

On Router R1- interface Tunnel0

no ip address
ip mtu 1000
ipv6 address 2003::1/64
ipv6 eigrp 2
tunnel source FastEthernet0/0
tunnel destination 10.3.0.2
tunnel mode ipv6ip


On Router R4-
interface Tunnel0

no ip address
ip mtu 1000
ipv6 address 2003::2/64
ipv6 eigrp 2
tunnel source FastEthernet0/0
tunnel destination 10.1.0.1
tunnel mode ipv6ip

GRE Tunnel

Ping from Router R5 to R6
R5#ping 2002::1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2002::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 72/106/212 ms
  
Ping from Router R6 to R5
R6#ping 2001::1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 68/78/88 ms

Traceroute from R5 to R6

R5#traceroute 2002::1
Type escape sequence to abort.
Tracing the route to 2002::1

  1 2001::2 56 msec 8 msec *
  2 2003::2 80 msec 72 msec 56 msec
  3 2002::1 104 msec 76 msec 44 msec

Configuration File config.zip

If you are interested in procuring the .net file for GNS3 then enter your email id in comment box.