The blog includes a vivid coverage of the concepts of CCNA, CCNP (Routing & Switching) , Basic Linux and Linux servers. Projects have also been simulated to give a practical exposure.

Wednesday, 21 May 2014

IPv6 Tunnel over MPLS & eBGP Network

No comments



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 :-

interface Tunnel0
  no ip address
 ipv6 address 2015::1/64
 ipv6 enable
 ipv6 eigrp 1
 tunnel source FastEthernet0/1
 tunnel destination 192.168.99.1
 tunnel mode ipv6ip

On Router Server_router :-

interface Tunnel0
 no ip address
 ipv6 address 2015::2/64
 ipv6 enable
 ipv6 eigrp 1
 tunnel source FastEthernet0/0
 tunnel destination 20.3.0.1
 tunnel mode ipv6ip

Verification 


Ping from Server_router to IPv6_host

Server_router#ping 2006::C805:12FF:FE58:8

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2006::C805:12FF:FE58:8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 120/177/260 ms

 Ping from IPv6_host to Server_host

IPv6_host#ping 2015::1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2015::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 108/133/152 ms

Configuration File config.zip

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

By : Vishal Sharma

No comments :

Post a Comment