Target Networking

The method to increase the bandwidth by aggregating or bundling parallel links is known as EtherChannel.

In this topology all the ports are in access mode, so all ports belong to same VLAN i.e vlan 10. There are 6 physical links in between the Switch R1 and R2. 1 port-channel group is made on both the switches. On switch R1 there is a vlan 10 interface which contain ip 192.168.1.1/30.  

Conditions of EtherChannel :-

Verification 

VLAN is the part of switching in networking, it is essential part of switch. Basically VLAN divides the switch into parts. VLANs are isolated from one from each other so that packets in one VLAN cannot communicate with other VLAN.
 To send packets from one VLAN to other, a Layer 3 device is needed. If router is used for this function then it must have a physical or logical connection to each VLAN so it can transfer packets between them. This is known as interVLAN routing.

In this topology Layer 3 device is Router R2, switch on which VLANs are created is SW1 and there are 4 hosts, connected to the switch, in which host C1, C2 are in VLAN 10 and C3, C4 are in VLAN 20.

When Host C1 in VLAN 10 needs to communicate with Host C2 in VLAN 10, it sends a packet
addressed to that host, Switch SW1 forwards the packet directly to Host C2, without sending it to the router. And when C1 want to communicate with C3 or C4 which are inn VLAN 20, then switch SW1 forwards the packets of C1 to router and router receive the traffic, send it to Hosts C3, C4 which are in VLAN 20. Router R2 is connected through two links with switch SW1, interface f0/0 is used for VLAN 10 and f0/1 is for VLAN 20.

Configuration of Router R2 :-

Configuration of Switch SW1 :-

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.

 

Download linux-tinycore-2.11.5

 

Firewall

Download ASA Firewall

By :- Vishal Sharma

I searched everywhere on internet about this error. I faced this error yesterday, on internet i found that this error is due to MTU packet size. It is quite surprising for me that MTU is creating problem, because I have learned that router perform fragmentation, segmentation if packet is large. But I found that these processes does not occur in this case. Because all EIGRP packets are trasported as IP protocol type 88 using Reliable Transport Protocol (RTP), not TCP or UDP, while Fragmentation is the mechanism in TCP transport.

EIGRP has a problem of flapping (up/down) in some topologies. It makes the network unstable, which creates problem in communication. This problem shows errors like this :-
 
%DUAL-5-NBRCHANGE: IPv6-EIGRP(0) 1: Neighbor FE80::2 (Tunnel0) is up: new adjacency

%DUAL-5-NBRCHANGE: IPv6-EIGRP(0) 1: Neighbor FE80::2 (Tunnel0) is down: holding time expired

In this topology Redistribution_point router is the mid point of the topology, to which each protocol is connected. All most all protocols are used in this topology and they distribute their routes to the other protocols through redistribution process.

Configuration of Redistribution_point router :-

IP addresses over Interfaces

interface FastEthernet0/0
 ip address 10.0.1.2 255.255.255.0
!
interface FastEthernet0/1
 ip address 10.0.2.2 255.255.255.0
!
interface FastEthernet1/0
 ip address 10.0.5.2 255.255.255.0
!
interface FastEthernet1/1
 ip address 10.0.4.2 255.255.255.0
!
interface FastEthernet2/0
 ip address 10.0.3.2 255.255.255.0

Routing protocols configuration :-

router eigrp 1
 redistribute static metric 100000 100 255 255 1500
 redistribute ospf 1 metric 100000 100 255 255 1500
 redistribute rip metric 100000 100 255 255 1500
 redistribute bgp 1 metric 100000 100 255 255 1500
 network 10.0.1.0 0.0.0.255
 auto-summary
router ospf 1
 log-adjacency-changes
 redistribute static metric 100000 metric-type 1 subnets
 redistribute eigrp 1 metric 100000 metric-type 1 subnets
 redistribute rip metric 100000 metric-type 1 subnets
 redistribute bgp 1 metric 100000 metric-type 1 subnets
 network 10.0.2.0 0.0.0.255 area 0
router rip
 version 2
 redistribute static metric 1
 redistribute eigrp 1 metric 1
 redistribute ospf 1 metric 1
 redistribute bgp 1 metric 1
 network 10.0.0.0
 no auto-summary
router bgp 1
 no synchronization
 bgp log-neighbor-changes
 network 10.0.5.0 mask 255.255.255.0
 redistribute static metric 1000000
 redistribute eigrp 1 metric 10000000
 redistribute ospf 1 metric 10000000
 redistribute rip metric 10000000
 neighbor 10.0.5.1 remote-as 1
 no auto-summary
ip forward-protocol nd
ip route 10.0.3.0 255.255.255.0 FastEthernet2/0

Configuration of Topology :- protocols_redistribution.zip

DHCP server is the server which provides IP address dynamically to the host. In GNS3 IOS 3725 image is used as Layer 3 Switch. It has NM-16ESW slot which has 16 fastethernet ports.





In this topology R1 is Layer 3 switch and SW1 is Layer 2 switch (unconfigurable), 2 hosts. Switch R1 has DHCP server which gives IP address automatically to the hosts.

Configuration of Layer 3 switch R1 :-

IP address on interface

interface FastEthernet1/0
 no switchport
 ip address 10.0.0.1 255.255.255.0
 duplex full
 speed 100

DHCP pool on router :-

ip dhcp pool cisco
network 10.0.0.0 255.255.255.0
default-router 10.0.0.1

Start DHCP service

 # service dhcp

On Layer 3 switch, dhcp service has to start, without this service dhcp server will not start working.

On router this service is enabled by default.

 

 Automatic IP address on Host_1 and Host_2
On Host_1


On Host_2



In last whole topology is working.

By :- Vishal Sharma

To use GNS3 in a proper manner, then one needs to know how to add IOS Image to GNS3. Because if a person do not know to add IOS image in GNS3 then he can not use Router, Switches and other features of the GNS3.

To add IOS image to GNS3, follow these steps :-

Step1. Install GNS3 in computer.

 

Simple steps to install GNS3.

Step2. Go to Edit ---> IOS Images and Hypervisors 

Select Image file in settings from your computer.
 

Step3 Calculation of IDLE PC :-

 

Click on IDLE PC to calculate Idle pc value, if there is no idle pc value then it will take 128 MB for each router, by which we can use only 3 -6 router if we have 4 GB RAM. Idle pc is the value on which router run on 0% usage of CPU. By which we can use 15 - 25 routers with 4GB RAM.

Step4 Save configuration :-

 

This post assumes that reader has basic knowledge of GNS. For those who does not know they can visit GNS3 official website www.gns3.net.

To communicate GNS3 with Linux, simple steps have to follow :-
1. Create loopback interface.
2. IP address to loopback interface.
3. Connect loopback to GNS3.
4. Connect Linux to windows.
5. Assign IP address to Linux.

Step 1. Create Loopback interface 

Loopback is the logical interface given by Microsoft in windows. To create loopback interface follow these steps.
    a. Type windows key + R, it will open run.
    b. write hdwwiz.exe in run, press enter.


    c. click next, then choose install the hardware manually.




    d. click next ---> Network adapters ---> Microsoft ---> Microsoft KM-TEST Loopback Adapter.



    It will add a new loopback interface in Network and Sharing Center.

Step2. IP address to loopback interface :- 

    Here loopback interface name is Ethernet 2, and IP address given to this interface is 100.0.0.1

 Step3. Connect loopback to GNS3.

    a. Add 1 router and a cloud in GNS3.
    b. Select loopback interface Ethernet 2 in cloud.

Step4. Connect Linux to windows.

 Step5. Assign IP address to Linux.

    a. Open Terminal , type setup, select network there and enter IP address 100.0.0.254/24

    b. Turn off firewall of Linux by setenforce 0.

Now you can ping Linux from Router.

Ping from Router to Linux.

IPv6 DNS Name Resolution