IT it's easy in English

Connecting and configuring Frame Relay switch in GNS3

noreply@blogger.com (Unknown) — Fri, 13 Apr 2012 12:38:00 +0000

God day!!!

Just want to apologize for my English. I am from Belarus and if there are errors, then feel free to write about them, I will correct them :).
Not so time ago, I faced with the need to work with the Frame Relay network. I have looked some guide and find that in GNS3 have Frame Relay switch.
Who want to know how install and configure him – welcome to post!!!

Run GNS3. Add one frame relay switch to working place (from left menu) and three routers (I choose cisco 2961) for future tests. If you don’t know how to add devices in GNS3 you may look this post. In the end you will have this scheme:

If you now try to connect routers directly to the switch, then will not work. Let’s fix this.
Click right mouse button on switch and go to "configuration" from drop down menu. Choose our device and you must see something like this:

Now we must to fink about how many ports we need and what links between routers we will be configure. For each link we must choose DLCI (Data Link Connection Identifier) and prescribe them to match the switch.
Let’s define what DLCI will be between all routers. Create this table:

R1--R2 – DLCI 52
R1--R3 – DLCI 53
R2--R1 – DLCI 25
R2--R3 – DLCI 23
R3--R1 – DLCI 35
R3--R2 – DLCI 32

From this table we see that we have a full-mesh topology.
Come back to configuration Frame Relay switch. For adding link you must choose pair source-port with source-DLCI and destination-port with destination-DLCI. Click «Add» and this pair appear, like on next picture:

Make this configuration for all of our relationships in the table (note that in the table we have indicated all the possible connections, but when you add them will need only three matches, because we indicated at once the source and destination).
The final table of the switch should look like this:

Click «Apply» and then «OK».
After that you may add links between routers and Frame Relay switch. The final scheme for further adjustments should be like this:

Now let’s configure our routers (IP-addresses for routers you can see in the top picture).
Router R1:


R1>en

R1#conf t

R1(config)#int serial 0/0

R1(config-if)#ip address 172.16.1.1 255.255.255.0

R1(config-if)#encapsulation frame-relay – turn on frame-relay encapsulation on interface;

R1(config-if)#frame-relay map ip 172.16.1.2 52 – define correspondence between the IP and DLCI;

R1(config-if)#frame-relay map ip 172.16.1.3 53

R1(config-if)#no shutdown

R1(config-if)#exit

R1(config)#exit

R1#wr

R1#

Router R2:


R2>en

R2#conf t

R2(config)#int serial 0/0

R2(config-if)#ip address 172.16.1.2 255.255.255.0

R2(config-if)#encapsulation frame-relay

R2(config-if)#frame-relay map ip 172.16.1.1 25

R2(config-if)#frame-relay map ip 172.16.1.3 23

R2(config-if)#no shutdown

R2(config-if)#exit

R2(config)#exit

R2#wr

R2#

Router R3:


R3>en

R3#conf t

R3(config)#int serial 0/0

R3(config-if)#ip address 172.16.1.3 255.255.255.0

R3(config-if)#encapsulation frame-relay

R3(config-if)#frame-relay map ip 172.16.1.1 35

R3(config-if)#frame-relay map ip 172.16.1.2 32

R3(config-if)#no shutdown

R3(config-if)#exit

R3(config)#exit

R3#wr

R3#

Well, everything should work :). Let's go back to the routers, try to execute ping command and check what we have.
Router R1:

Router R2:

Router R3:

As you can see, all we have works. I congratulate you!!!
On this, I want to finish this post. I hope he was informative for you and I want to thank you for your attention.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

I’m waiting for you in next posts!!!

With best regards, Ant0ni0n

Configure OSPF on cisco routers. Part №1.

noreply@blogger.com (Unknown) — Tue, 10 Apr 2012 11:48:00 +0000

God day!!!

Just want to apologize for my English. I am from Belarus and if there are errors, then feel free to write about them, I will correct them :).
In last posts we have looked how to configure RIP (Routing Information Protocol) and EIGRP (Enhanced Interior Gateway Routing Protocol). Today, I want to introduce you the following routing protocol, namely OSPF (Open Shortest Path First). This is one of the most popular protocol for using in local networks. And for that reason I suggest to divide our post on two parts.
In part №1 we will see commands of basic configuration of OSPF.
So, who interested, welcome…

In the Internet you may find a lot of information about that protocol. So, we begin our configurations right now.
Our network diagram will look like that:

Some explanations to the diagram. Routers R1 and R3 – are area border routers, called ABR (they have interfaces in area 0 (called backbone area) and other areas). Router R2 call autonomous system boundary router (ASBR), which has interfaces in backbone area 0 and in other autonomous systems. Router 4 – is internal router (IR), which has all interfaces in one area.
As the router ID will be using Loopback - interfaces (or rather their IP - address). Network 10.1.0.0/24 will be used to «exit to the outside world», and our default route will be going through that network. Networks 11.0.0.0/8, 12.0.0.0/8 and 13.0.0.0/8 will uses for emulate remote networks. We will set static routs to them and then we configure redistribution these networks into OSPF.
Successful implementation of this scheme we will assume the presence of network availability between hosts (command ping), the presence of all the routes in the routing table of each router (default route, static routes to remote networks and etc), obtained via OSPF.
So, let’s begin. Start with router R2:


R2>en

R2#conf t

R2(config)#interface loopback 0 – create loopback interface;

R2(config-if)#ip address 192.168.1.1 255.255.255.255 – set up IP-address to this interface;

R2(config-if)#exit

R2(config)#interface fa 0/0

R2(config-if)#ip address 172.16.1.1 255.255.255.0

R2(config-if)#no sh

R2(config-if)#exit

R2(config)#interface fa 0/1

R2(config-if)#ip address 10.1.0.1 255.255.255.0

R2(config-if)#no sh

R2(config-if)#exit

R2(config)#ip route 0.0.0.0 0.0.0.0 10.1.0.2 – configure default route;

R2(config)#ip route 11.0.0.0 255.0.0.0 null 0 – add a static route ( we use null interface for destination for example);

R2(config)#ip route 12.0.0.0 255.0.0.0 null 0

R2(config)#ip route 13.0.0.0 255.0.0.0 null 0

R2(config)#router ospf 1 – start OSPF process (the process ID is any positive integer value between 1 and 65,535);

R2(config-router)#network 172.16.1.0 0.0.0.255 area 0 – OSPF determines interfaces to process, not networks. So, with this command we add all interfaces that have IP addresses from 172.16.1.0/24 network (use wildcard mask in this case);

R2(config-router)#default-information originate – set default route to be propagated to all OSPF routers;

R2(config-router)#redistribute static subnets – enable redistribute static routes into OSPF process. Now all routers in OSPF will know about these routes;

R2(config-router)#exit

R2(config)#exit

R2#wr

R2#

Ok, let’s check our configuration. Make «show run» command on router R2:

Now, go to configuration of router R1:


R1>en

R1#conf t

R1(config)#interface loopback 0

R1(config-if)#ip address 192.168.2.1 255.255.255.255

R1(config-if)#description Router ID

R1(config-if)#exit

R1(config)#interface fa 0/0

R1(config-if)#ip address 172.16.1.2 255.255.255.0

R1(config-if)#ip ospf priority 200 – change the OSPF interface priority. Now this router will be a designated router (DR);

R1(config-if)#no shutdown

R1(config-if)#exit

R1(config)#interface fa 0/1

R1(config-if)#ip address 172.16.51.1 255.255.255.0

R1(config-if)#description To_host

R1(config-if)#no shutdown

R1(config-if)#exit

R1(config)#router ospf 1

R1(config-router)#network 172.16.1.0 0.0.0.255 area 0

*Mar  1 00:04:40.663: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.1.1 on FastEthernet0/0 from LOADING to FULL, Loading Done – this message tell us about that relationship in OSPF process between routers are installed;

R1(config-router)#network 172.16.51.1 0.0.0.0 area 51 – the interface with an exact IP-address is to be put into Area 51;

R1(config-router)#exit

R1(config)#exit

R1#wr

Now, router R3:


R3>en

R3#conf t

R3(config)#interface loopback 0

R3(config-if)#ip address 192.168.3.1 255.255.255.255

R3(config-if)#description Router ID

R3(config-if)#exit

R3(config)#interface fastEthernet 0/0

R3(config-if)#ip address 172.16.1.3 255.255.255.0

R3(config-if)#ip ospf priority 100 – make this router a backup designated router (BDR);

R3(config-if)#no shutdown

R3(config-if)#exit

R3(config)#interface serial 0/0

R3(config-if)#ip address 172.16.10.5 255.255.255.252

R3(config-if)#clock rate 56000

R3(config-if)#no shutdown

R3(config-if)#exit

R3(config)#router ospf 1

R3(config-router)#network 172.16.1.0 0.0.0.255 area 0

*Mar  1 00:04:44.003: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.2.1 on FastEthernet0/0 from LOADING to FULL, Loading Done

*Mar  1 00:04:47.783: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.1.1 on FastEthernet0/0 from LOADING to FULL, Loading Done – relationship between routers are installed;

R3(config-router)#network 172.16.10.4 0.0.0.3 area 1

R3(config-router)#area 1 stub – defines Area 1 as a Stub area. A stub area is an area which does not receive route advertisements (LSA type 4 and 5). Router sends to this Area only internal routes and default route;

R3(config-router)#exit

R3(config)#exit

R3#wr

Last router R4:


R4>en

R4#conf t

R4(config)#interface loopback 0

R4(config-if)#ip address 192.168.4.1 255.255.255.255

R4(config-if)#description Router ID

R4(config-if)#exit

R4(config)#interface fa 0/0

R4(config-if)#ip address 172.16.20.1 255.255.255.0

R4(config-if)#description To_host

R4(config-if)#no shutdown

R4(config-if)#exit

R4(config)#interface serial 0/0

R4(config-if)#ip address 172.16.10.6 255.255.255.252

R4(config-if)#no shutdown

R4(config-if)#exit

R4(config)#router ospf 1

R4(config-router)#network 172.16.0.0 0.0.255.255 area 1 – add all interfaces that have IP addresses from 172.16.0.0/16 network in OSPF process;

R4(config-router)#area 1 stub – defines Area 1 as a Stub area;

*Mar  1 00:03:54.239: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.3.1 on Serial0/0 from LOADING to FULL, Loading Done – relationship between routers are installed;

R4(config-router)#exit

R4(config)#exit

R4#wr

Now we can check that we have configured. Let’s see routing table of our routers. We will use commands from «show» groups. After that we will make a ping commands between hosts.
Routing table of router R2:

1 – routes learned from the neighbors that are in other areas (Area 51 and Area 1);
2 –static routes to remote networks;
3 – router ID;
4 – default route.

Routing table of router R1:

1 – routes learned from the neighbors that are in other area (Area 1);
2 – this is external routes to remote networks. They have been redistributed into OSPF on router R2;
3 – router ID;
4 – this is the same external route, but he called is a default route and he was advertised on router R2 by the command «default-information originate».

Routing table of router R3:

1 – route learned from the neighbors that are in other area (Area 51);
2 – route learned from the neighbor (router R4) that is in the same area;
3 – this is external routes to remote networks;
4 – router ID;
5 – default route that was advertised on router R2.

Routing table of router R4:

1 – routes learned from the neighbors that are in other areas (Area 0 and Area 51);
2 – router ID;
3 – default route that was advertised on router R2. As you can see this route is "internal" route (IA) (not external E2) and in routing table we don't see any other external routes. This is specific of Stub Area. We have only «internal» routes (IA) and one default route.

Now look other commands on routers («show ip ospf » and « show ip ospf neighbor »).
Router R2:

Router R1:

Router R3:

Router R4:

On pictures you can see that OSPF process running successful. DR and BDR elections were held as we planned, by changing the priorities at appropriate routers.
In the end let’s check network availability between hosts and «remote» IP-address (10.1.0.2).
Host №1:

1 – ping on default gateway;
2 – ping on host №2;
3 – ping on «remote» IP-address.

Host №2:

1 – ping on default gateway;
2 – ping on host №1;
3 – ping on «remote» IP-address.

As you can see all works fine. Congratulate you!!!
In this post we have learned how to configure OSPF on cisco devices, how to make redistribute static routes into OSPF process and how define a default route.
In the next post (part №2) I will tell you about how configure OSPF with authentication in NBMA networks (Non-Broadcast Multiple Access), such as Frame Relay.
On this, I want to finish this post. I hope he was informative for you and I want to thank you for your attention.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!

I’m waiting for you in next posts!!!

With best regards, Ant0ni0n

Configure EIGRP on cisco routers

noreply@blogger.com (Unknown) — Wed, 04 Apr 2012 13:10:00 +0000

God day!!!

Just want to apologize for my English. I am from Belarus and if there are errors, then feel free to write about them, I will correct them :).
In last post I was told you about how to configure RIP on cisco routers. Today, I want to tell you about how configure EIGRP on devices of this vendor.
Who interested, let’s follow me…

How on last time, I will not stopping on the theory. You can find her in the internet. At once, we go to configuration.
For emulate all our devices and schemes I will use GNS3. Today, we will create and configure this scheme:

All devices have IP-addresses from 172.16.x.x/24 range. Default route for whole network is 0.0.0.0 0.0.0.0 192.168.0.2/24 (in the future we will redistribute them into EIGRP). For testing our job we will use ping from hosts and if he will be, then network work fine.
For more experience we will configure EIGRP with authentication.
Ok, let’s start our work. Go to first router (Router_1):


R1>en

R1#conf t

R1(config)#hostname Router_1

Router_1(config)#interface serial 0/0 – go to interface configuration mode;

Router_1(config-if)#ip address 172.16.20.1 255.255.255.0 – set IP-address;

Router_1(config-if)#clock rate 56000

Router_1(config-if)#description To_Router_2

Router_1(config-if)#ip authentication mode eigrp 100 md5 – enable MD5 authentication for EIGRP process;

Router_1(config-if)#ip authentication key-chain eigrp 100 test – configure key-chain named «test» for authentication;

Router_1(config-if)#no shutdown

Router_1(config-if)#interface fa 0/0

Router_1(config-if)#ip address 172.16.10.1 255.255.255.0

Router_1(config-if)#description To_host

Router_1(config-if)#no shutdown

Router_1(config-if)#exit

Router_1(config)#router eigrp 100 – go to EIGRP configuration mode;

Router_1(config-router)#no auto-summary – turn off the auto-summarization (if enable);

Router_1(config-router)#eigrp log-neighbor-changes – turn on logging all messages of EIGRP in console;

Router_1(config-router)#network 172.16.0.0 – configure network, that will work in EIGRP. In this case, all interfaces that have IP-address from that range will be included in EIGRP;

Router_1(config-router)#exit

Router_1(config)#key chain test – enter to key chain configuration mode;

Router_1(config-keychain)#key 1 – create key №1 (It is recommended that the key number be the same on all routers involved in the configuration);

Router_1(config-keychain-key)#key-string cisco – specify the key-string for the key;

Router_1(config-keychain-key)#exit

Router_1(config-keychain)#exit

Router_1(config)#exit

Router_1#wr

Router_1#

Now, go to second router and make the same configuration:


R2>

R2>en

R2#conf t

R2(config)#hostname Router_2

Router_2(config)#int serial 0/0

Router_2(config-if)#ip address 172.16.20.2 255.255.255.0

Router_2(config-if)#clock rate 56000

Router_2(config-if)#description To_Router_1

Router_2(config-if)#ip authentication mode eigrp 100 md5

Router_2(config-if)#ip authentication key-chain eigrp 100 test

Router_2(config-if)#no shutdown

Router_2(config-if)#exit

Router_2(config)#interface fa 0/0

Router_2(config-if)#ip address 172.16.30.1 255.255.255.0

Router_2(config-if)#no sh

Router_2(config-if)#no shutdown

Router_2(config-if)#exit

Router_2(config)#router eigrp 100

Router_2(config-router)#no auto-summary

Router_2(config-router)#eigrp log-neighbor-changes

Router_2(config-router)#network 172.16.0.0

Router_2(config-router)#exit

Router_2(config)#key chain fortest

Router_2(config-keychain)#key 1

Router_2(config-keychain-key)#key-string cisco

Router_2(config-keychain-key)#exit

*Mar  1 00:39:07.875: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 172.16.20.1 (Serial0/0) is up: new adjacency – this message indicates that our routers agreed each other and EIGRP with authentication work fine;

Router_2(config-keychain)#exit

Router_2(config)#int fa 0/1

Router_2(config-if)#ip address 192.168.0.1 255.255.255.0

Router_2(config-if)#no sh

Router_2(config-if)#exit

Router_2(config)#exit

Router_2#wr

Router_2#

Now, let’s stop and check what we have on that moment. We will check a routing table on routers check configuration EIGRP by show commands and check network availability between hosts:

As you can see all routes are presented and network connectivity established. Only one thing we do not have at the moment is default route to remote IP-address (192.168.0.2). Let’s fix this. Go to second router (Router_2):


Router_2#

Router_2#conf t

Router_2(config)#ip route 0.0.0.0 0.0.0.0 192.168.0.2

Router_2(config)#router eigrp 100

Router_2(config-router)#redistribute static

Router_2(config-router)#exit

Router_2(config)#exit

Router_2#

With that commands we add default static route and then we enable redistribution static routes to EIGRP process. As a result all other routers in EIGRP process will know about this network. Let’s check this:

Note that on the first router (Router_1) this route is received on EIGRP and is «external» (flag D* EX), and on the second router (which this route announces), it is marked as a static route by default (S *).
Now, let's ping IP 192.168.0.2 from hosts:

All work fines, network availability is provided :). I congratulate you!!!
For configuration EIGRP available and other commands:

Router(config-if)#bandwidth x – sets the bandwidth of this interface to x kilobits to allow EIGRP to make abetter metric calculation;
Router(config-router)#metric weights tos k1 k2 k3 k4 k5 – changes the default K values used in metric calculation;
Router#show ip eigrp neighbors – display neighbors table;
Router#show ip eigrp interfaces – shows information about all interfaces that are working in EIGPR;
Router#show ip route eigrp – shows routing table with only EIGRP entries;

For debug EIGRP use these commands:

Router#debug eigrp fsm
Router#debug eigrp packet
Router#debug eigrp neighbor
Router#debug ip eigrp neighbor
Router#debug ip eigrp notifications

On this, I want to finish this post. I hope it was informative for you and I want to thank you for your attention.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

I’m waiting for you in next posts!!!

With best regards, Ant0ni0n

Configuring RIP on cisco routers

noreply@blogger.com (Unknown) — Thu, 08 Dec 2011 12:24:00 +0000

God day!!!

Just want to apologize for my English. I am from Belarus and if there are errors, then feel free to write about them, I will correct them :).
In last post I was writing about how to configure a static routing on cisco routers. Today, I want to introduce to you post about how to configure a dynamic routing protocol RIP. In our time he use very rarely, but you need to know about him.
Interested? Then welcome…

Information, about this protocol, you may find in Internet, so we do not stop on this.
Network, which we will configure, look like this:

Our task is to have a ping between hosts.
Let’s begin to work. Start our routers and configure them.
Router R1:


Router_1>en

Router_1#conf t

Router_1(config)#int fa 0/0

Router_1(config-if)#ip address 172.16.10.1 255.255.255.0

Router_1(config-if)#description To_host

Router_1(config-if)#no sh

Router_1(config-if)#int ser 0/0

Router_1(config-if)#ip address 172.16.20.1 255.255.255.252

Router_1(config-if)#description To_Router_2

Router_1(config-if)#no sh

Router_1(config-if)#exit

Router_1(config)#^Z

Router_1#wr

Building configuration...

[OK]

Router_1#

Router R2:


R2>en

R2#conf t

R2(config)#hostname Router_2

Router_2(config)#int fa 0/0

Router_2(config-if)#ip address 172.16.30.1 255.255.255.0

Router_2(config-if)#description To_host

Router_2(config-if)#no sh

Router_2(config-if)#int ser 0/0

Router_2(config-if)#ip address 172.16.20.2 255.255.255.252

Router_2(config-if)#no sh

Router_2(config-if)#description To_Router_2

Router_2(config-if)#int ser 0/1

Router_2(config-if)#ip address 172.16.40.1 255.255.255.252

Router_2(config-if)#no sh

Router_2(config-if)#description To_Router_3

Router_2(config-if)#exit

Router_2(config)#^Z

Router_2#wr

Building configuration...

[OK]

Router_2#

Router R3:


R3>en

R3#conf t

R3(config)#hostname Router_3

Router_3(config)#int fa 0/0

Router_3(config-if)#ip address 172.16.50.1 255.255.255.0

Router_3(config-if)#no sh

Router_3(config-if)#description To_host

Router_3(config-if)#int ser 0/1

Router_3(config-if)#ip address 172.16.40.2 255.255.255.252

Router_3(config-if)#description To_Router_2

Router_3(config-if)#no sh

Router_3(config-if)#exit

Router_3(config)#^Z

Router_3#wr

Building configuration...

[OK]

Router_3#

Ok, now check network connection between routers:

Now, let’s test network availability between routers and hosts and make sure that there are no pings between hosts at this moment.

How you can see, we have ping between routers and hosts, but between hosts we don’t have any network availability. Let’s fix this problem.
Let's go to routers by turn and make the following configuration:


Router_1#conf t

Router_1(config)#router rip – enter on RIP configuration mode; 

Router_1(config-router)#version 2 – choosing version 2;

Router_1(config-router)#network 172.16.0.0 – add network;

Router_1(config-router)#no auto-summary – turn off auto-summary;

Router_1(config-router)#exit

Router_1(config)#exit

Router_1#wr


Router_2#conf t

Router_2(config)#router rip

Router_2(config-router)#version 2

Router_2(config-router)#network 172.16.0.0

Router_2(config-router)#no auto-summary

Router_2(config-router)#exit

Router_2(config)#exit

Router_2#wr


Router_3#conf t

Router_3(config)#router rip

Router_3(config-router)#version 2

Router_3(config-router)#network 172.16.0.0

Router_3(config-router)#no auto-summary

Router_3(config-router)#exit

Router_3(config)#exit

Router_3#

You must remember that adding networks in RIP process are doing by classful networks. That is correct 172.16.0.0, instead 172.16.10.0.
Ok, we finished. Let’s check our work. For this, we look at the routing table on routers and check network availability between hosts.

How you can see on the pictures, all work fine. We have configured RIP on cisco routers.
For detailed configuration of RIP there are some main commands:

Router(config-router)#no network w.x.y.z – delete network from RIP process;
Router(config-router)#version 1 – turn on RIP process version 1;
Router(config-router)#passive-interface s0/0/0 – disables sending RIP updates on a given interface (by default, sending updates enabled on all interfaces);
Router(config-router)#timers basic <> - with this command you may configure any RIP timers (time to response, time for updates and other);
Router#debug ip rip – turn on debug mode for RIP. In this mode you can view all information about protocol in real time;
Router#show ip rip – view information about RIP protocol;
Router#show ip rip database – view information about RIP routing database;

On this step, I want to finish my post. Thanks for attention, I hope, you have received for yourselves the helpful information.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

I’m waiting for you in next posts!!!

With best regards, Ant0ni0n

Configure a static routing on cisco router

noreply@blogger.com (Unknown) — Fri, 18 Nov 2011 07:56:00 +0000

Good day!!!

Just want to apologize for my English. I am from Belarus and if there are errors, then feel free to write about them, I will correct them :).
In last post I was speaking about initial configuration on cisco router. Today, I suggest you to configure a static routing on cisco devices.
If you interested, welcome to post…

For our work I will use GNS3. So, let’s begin and collect this scheme:

If we will configure all fine then we should see successful pings between hosts. Ok, let’s start our work :).
First configure pouter R1 towards a host (interface Fa 0/0):

R1>
R1>en
R1#conf t
R1(config)#int fa 0/0
R1(config-if)#description Link_to_host
R1(config-if)#ip address 172.16.10.1 255.255.255.0
R1(config-if)#no sh
R1(config-if)#exit
R1(config)#

Then configure router R1 towards a router R2 (interface Ser 0/0/0):

R1(config)#int serial 0/0
R1(config-if)#description Link_to_R2
R1(config-if)#clock rate 56000
R1(config-if)#ip address 172.16.20.1 255.255.255.252
R1(config-if)#no sh
R1(config-if)#exit
R1(config)#exit
R1#wr

Make same configuration on routers R2 and R3, only with corresponding IP – addressing:

R2>en
R2#conf t
R2(config)#int fa 0/0
R2(config-if)#description Link_to_host
R2(config-if)#ip address 172.16.30.1 255.255.255.0
R2(config-if)#no sh
R2(config-if)#exit
R2(config)#int serial 0/0
R2(config-if)#clock rate 56000
R2(config-if)#ip address 172.16.20.2 255.255.255.252
R2(config-if)#no sh
R2(config-if)#description Link_to_R1
R2(config-if)#exit
R2(config)#int serial 0/1
R2(config-if)#clock rate 56000
R2(config-if)#ip address 172.16.40.1 255.255.255.252
R2(config-if)#no sh
R2(config-if)#description Link_to_R3
R2(config-if)#exit
R2(config)#exit
R2#wr

R3>
R3>en
R3#conf t
R3(config)#int fa 0/0
R3(config-if)#description Link_to_host
R3(config-if)#ip address 172.16.50.1 255.255.255.0
R3(config-if)#no sh
R3(config-if)#exit
R3(config)#int serial 0/1
R3(config-if)#description Link_to_R2
R3(config-if)#clock rate 56000
R3(config-if)#ip address 172.16.40.2 255.255.255.252
R3(config-if)#no sh
R3(config-if)#exit
R3(config)#exit
R3#wr

Check network availability between routers and look at the routing table:

Now, verify network availability between hosts and routers and check that ping between hosts are not working:

As we see, availability of routers is present, but further the traffic does not pass. Let's correct it.
Add adequate static routes on our routers.
For this, go to router R1 and add next commands:

R1>en
R1#conf t
R1(config)#ip route 172.16.30.0 255.255.255.0 172.16.20.2
R1(config)#ip route 172.16.40.0 255.255.255.252 172.16.20.2
R1(config)#ip route 172.16.50.0 255.255.255.0 172.16.20.2
R1(config)#exit
R1#

On other routers make this configuration:

R2>en
R2#conf t
R2(config)#ip route 172.16.10.0 255.255.255.0 serial 0/0
R2(config)#ip route 172.16.50.0 255.255.255.0 serial 0/1
R2(config)#exit
R2#wr

R3>en
R3#conf t
R3(config)#ip route 0.0.0.0 0.0.0.0 serial 0/1
R3(config)#exit
R3#wr

Note that on each router we configured routes differently. On router R1 we added routes to networks and put IP-address of the neighbor as a next-hop. On router R2 we added routes to networks and indicated interface through which traffic must go to destination. And on router R3 we added one «default route» which means that all unknown traffic (that not present in routing table) must go through specified interface.
As we can see, add static routes you may different ways and this is not so hard :).
Now, let’s check that ping between hosts are working:

As you can see on pictures, all working fine. Congratulate you!!! We have configured a static routing on our cisco routers :).

On this step, I want to finish my post. Thanks for attention, I hope, you have received for yourselves the helpful information.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

I’m waiting for you in next posts!!!

With best regards, Ant0ni0n

Initial configuration on cisco router

noreply@blogger.com (Unknown) — Tue, 15 Nov 2011 12:08:00 +0000

Good day!!!

Just want to apologize for my English. I am from Belarus and if there are errors, then feel free to write about them, I will correct them :).
From that post I start writing about cisco equipment. I will publish various examples of variants, scenarios, diagrams networks and an equipment configuration cisco.
I hope that for somebody will be easier to learn, understand or obtain something new in network equipment configuring on basis cisco.
Ok, first post I will dedicate for initial configuration of cisco router. I invite all of you …

I do not have any cisco router, so I will be use GNS3 to emulate device. In this program are used real IOS devices and all commands of configuration are available and identical to commands on real devices. Differences can be insignificant only because of version IOS.
Let’s launch GNS3, then add any router to the working area (I selected 3745) and then launch device. We assign to router IDLE-PC parameter and go on it through console. How do all these steps, I told in the posts devoted to installing, configuring and adding of devices in GNS3.
After all manipulation you should be see this window:

Cisco devices have different mode of configuration. Here they:

Router> - Restricted review of a configuration. You cannot make changes in this mode;
Router# - this is privilege mode, where you can view all configuration and make some changes in configuration (this mode known as «EXEC-level mode»);
Router(config)# - this is global configuration mode of the device (here introduced the basic commands for configuration);
Router(config-if)# - this is interface configuration mode;
Router(config-subif)# - this is subinterface configuration mode;
Router(config-line)# - this is line configuration mode (you can make configure vty (telnet, ssh) and console);
Router(config-router)# - this is router configuration mode (here you make configuration dynamic routing (such as RIP, IS-IS, OSPF, BGP).

So, we go to global configuration mode and begin our working:

R1>enable
R1#configure terminal
R1(config)#

Now, we name our router with this command:

R1(config)#hostname Router_1

Next we configure name and password for administrator and set password to enter in global configuration mode:

Router_1(config)#username administrator password cisco
Router_1(config)#enable secret ciscocisco

By default IOS encrypts only password to enter in global configuration mode, other passwords are stored in clear text. If you want to encrypt other passwords, use next command:

Router_1(config)#service password-encryption

Ok, now we will adjust our vty and console lines.
For this purpose, we go to line vty configuration mode and configure to use local database for authenticate us (username and password which we set hardly above), use telnet and ssh for connection, session idle time 10 (ten) minutes and option "carriage return" when you enter commands and issuing system messages:

Router_1(config)#line vty 0 14
Router_1(config-line)#login local
Router_1(config-line)#transport input telnet ssh
Router_1(config-line)#exec-timeout 10
Router_1(config-line)#logging synchronous
Router_1(config-line)#exit

Then we come into line console configuration mode and do same options (except parametres telnet and ssh):

Router_1(config)#line console 0
Router_1(config-line)#login local
Router_1(config-line)#logging synchronous
Router_1(config-line)#exec-timeout 10 0
Router_1(config-line)#exit
Router_1(config)#

Ok, now we create banner that will be seen when we will be connecting to the router:

Router_1(config)#banner login с "your text" с – «с» - a separator, its presence is required

If you do not want lose your time, you should turn off parameter «ip domain-lookup», which means name-to-address translation. For this purpose, use this command:

Router_1(config)#no ip domain-lookup

Save our configuration. For this purpose you may out from global configuration mode by execute «exit» command or use «do» before a command:

Router_1(config)#do wr
Building configuration...
[OK]
Router_1(config)#

Parameter «do» sometimes may be very useful when you need execute commands of group «show», commands to save configuration etc without leaving a mode in which you are.
Now go out into the privileged mode and take a look our configuration:

Router_1(config)#exit
Router_1#show running-config

Now, let’s check our work. Logout with command «exit». Then again login on our router. You should see this:

1 – our banner;
2 – our user;
3 – our password for user;
4 – our password enable secret.

Now, let’s make access by telnet and ssh. For begin let’s configure IP-address for connection.
Go to interface configuration mode:

Router_1#conf t
Router_1(config)#int fa 0/0
Router_1(config-if)#ip address 192.168.0.1 255.255.255.0
Router_1(config-if)#no shutdown
Router_1(config-if)#exit
Router_1(config)#

After that, you must generate key pair. For generate keys, IOS will use a domain name. Make following commands:

Router_1(config)#ip domain-name test.com
Router_1(config)#crypto key generate rsa
*Mar 1 02:18:20.731: %SSH-5-ENABLED: SSH 1.5 has been enabled
Router_1(config)#

When you see a question about length of key, specify 512 bit (for version 1.5). If you want to use ssh version 2 then length of key must be higher 768 bit.
Ok, ssh was started, telnet working by default. Save your configuration («do wr»).
For check, I must to connect our virtual router with physical network (how to do this, I described in this post). In the end, you must have this topology for check:

Let's start Putty on local PC and check access (telnet and ssh) on IP - the address of our router.

As you can see, telnet is working.

In this picture, we propose to keep the key from the router on our computer. Press "Yes".

As you can see, ssh is working.
Congratulate you!!! We are finished.

On this step, I want to finish my post. Thanks for attention, I hope, you have received for yourselves the helpful information.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

I’m waiting for you in next posts!!!

With best regards, Ant0ni0n

Router configuration in GNS3 are not saved

noreply@blogger.com (Unknown) — Fri, 21 Oct 2011 08:17:00 +0000

Good day!!!

Just want to apologize for my English. I am from Belarus and if there are errors, then feel free to write about them, I will correct them :).
By working with GNS3, I has found one problem. I has added a router 3700 series (3745), has configured him, has kept a configuration, has kept the project, has stopped it (or left the program). But next time, when I opened the project, the router was loaded with a «pure» configuration.
Looking on the Internet for the decision of this problem I found a variant. But the information is on different sources and I decided to collect it in a single whole.
If you interested, welcome…

So, start GNS3 and add a router 3700 series:

Run him (Click green triangle). Then we go to router by console and do some little adjustment. Later we will check our configuration restoration:

Let's remember a router name and IP – address, which we have configured previously. Save our configuration, close console and save project.
After saving a project, in «Console» window, you will see a message about process of saving configuration in local folder:

Now, you must stop our router («Stop») and again start («Start») (or, if you want, close and open the program). When router was started, again go to him by console. And what we see:

We see that our configuration was lost and have been loaded "pure" configuration :).
Then we do: on questions we answer «no», and then enter commands:

Router>en
Router#copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Router#

After that, without saving project, we go to bookmark «Import/Export Startup Configs» (on top menu GNS3), choose «Importing from directory» and then click «OK»:

Select folder with our configuration and click «OK». In «Console» window you must see a message:

Come back to our router and enter a command:

Router#copy startup-config running-config

And right after this we see that OUR configuration was loaded. Let’s look «running-config»:

All works. One moment, these actions you must do with every «Stop/Start» of routers of 3700 series. I not saw this problem with other devices.
On this step, I want to finish my post. Thanks for attention, I hope, you have received for yourselves the helpful information.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

With best regards, Ant0ni0

Connecting the router from the GNS3 to physical network

noreply@blogger.com (Unknown) — Thu, 20 Oct 2011 11:08:00 +0000

Good day!!!

Just want to apologize for my English. I am from Belarus and if there are errors, then feel free to write about them, I will correct them :).
Today I want to tell you about how to connect a virtual router in GNS3 to physical network. If you need it or you simply want to practice, I invite all of you …

Doing that very easy.
As an network adapter, I'll use a virtual network adapter windows (loopback network adapter). To begin, let’s create it :).
Windows 7 have a little feature. Virtual network adapter you can’t create with standard procedure (Control panel -- Hardware and sound -- Add devices). You need to use special wizard. For launching this wizard you may use a command line interface (cmd) or item «Run» from menu «Start». So, run cmd.exe and enter the command hdwwiz:

Add New Hardware Wizard will start:

Click on «Next» and select item «Install the hardware that I manually select from a list». From list select item «Network adapters»:

Click «Next». Choose «Microsoft» and «Microsoft Loopback Adapter» in next window:

Click «Next» twice, the network adapter will be installed. On last window click «Finish». Now this adapter you can see in the list:

Now, launch our program GNS3. Add any devices (I choose cisco 3640) and «cloud». If you don’t know how do this, see that post. As a result, you should have something like this:

Let’s configure our devices. How configure router I was tell you in previous post (put Slot NM-1FE-TX), but a cloud we configure now :). Click right mouse button on «cloud» and go to item «Configure»:

On tab «NIO Ethernet» in drop down menu select interface that we need (I remind you that it is our windows loopback interface) and click «Add». After that interface should be in the list:

Click «Apply» and then «OK». That’s all, configuring «cloud» is over. Now, let’s connect our scheme elements. Here is a working scheme you should get:

Run our router, connect to him by console and make the following small adjustments:

R1>enable
R1#configure terminal
R1(config)#interface fastEthernet 0/0
R1(config-if)#ip address 192.168.0.1 255.255.255.0
R1(config-if)#no shutdown
R1(config-if)#exit
R1(config)#exit
R1#wr

After configuration save the project. Check up, that the router configuration was saved. It will be visible in a program primary window under the circuit (a window "Console"):

Now, we pass to adjustment of our loopback adapter. We go to the list of our network adapters on PC, select necessary to us and go into its properties for adjustment its IP - address:

Specify IP – address 192.168.0.2, a mask 255.255.255.0. Click «OK» and then "Close".
All is ready for check. Now, you must launch the cmd.exe and try to ping our router. Then, return in a router console and ping our interface on the computer:

I congratulate you!!!! We connected the virtual router to a real (physical) network.
GNS3 It is possible to connect not only to the real computer, but also to VMWare. Where, it is possible to adjust your own networks. But, it is already extensive subject for following posts.
On this step, I want to finish my post. Thanks for attention, I hope, you have received for yourselves the helpful information.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

With best regards, Ant0ni0n

Add devices in GNS3

noreply@blogger.com (Unknown) — Fri, 07 Oct 2011 10:45:00 +0000

Good day!!!

Just want to apologize for my English. I am from Belarus and if there are errors, then feel free to write about them, I will correct them :).
In previous posts (1 and 2) we have installed and configured our program (GNS3). Today, I invite you to add the first devices in GNS3, start them and to make a simple configuration for the connection between them.
So, invite you…

Run our program. We will see working window:

Here, in the first column write the name of our project, in second column should be registered the path to save our project (if everything was configured correctly, the project folder will create in a subfolder «Project»). Select all checks (need to automatically save the configuration file and NVRAM when you click on «Save»). Click «OK».
To add device, simply select it from list on the left, hold the left mouse button drag it to the workspace and release button. For the first example I chose two cisco 3640 (from the platform of 3600). (If you are not tied the IOS to the device, read my previous post "Configure GNS3 on Windows 7", where I talked about it).
Now, before you run devices, we need to configure them a little. For this, push the right mouse button on device and select item «Configure» in dropdown menu. This window should be open:

Here, we choose our device (R1) and select the item «Slots» in the dialog box (right):

For Slot 0, in the dropdown menu, select the NM-1FE-TX (this is one port FastEthernet). For the first time, I think, as long as enough :). Push «Apply» and then «OK». To the second device we do all the same.
If you want to change the name of device, then before launch, click right mouse button on it and select item «Change the hostname» from dropdown menu.
Run our devices. For this, you can use the button on top toolbar (green triangle), then run all devices at once, or you can click by right mouse button on every devices and choose green triangle from dropdown menu. For control, that devices run, they will be green color in the right corner of the screen (the field «Topology Summary»).
When devices are running, you must define parameter Idle PC for each of them. This will save operative memory of our computer. For this, click again right mouse button on devices and choose item «Idle PC» from dropdown menu. If you see that Idle PC is already set, do nothing:

In the pop-up window from the dropdown menu select the value marked with *. (There are times when «*» is not set, then just choose any value.) Click «Apply» and then «OK». Do this with all other devices.
Now let’s connect our devices.

For this, activate mode «add connections», as shown above. After this, we direct the cursor to the first device, click on it, select interface that need (in our case it will be one), and drag the line to the next device. Click on second device and select interface from list. That’s all, our devices connected between each other. Turn off mode «add connections». As a result you should have something like this:

Let’s save our project. (File – Save, or click corresponding button on toolbar).
Now it's time to go to our devices from console. To do this, again, click right mouse button on device and select item «Console» from dropdown menu.
You should see window of program Putty:

Let's do some default adjustments for inspect connection between devices:

R1>en
R1#configure terminal
R1(config)#int fa 0/0
R1(config-if)#ip address 192.168.0.1 255.255.255.0
R1(config-if)#no shutdown
R1#wr
R1#

Go to the second device and do everything too, just IP set to 192.168.0.2 255.255.255.0

R2>en
R2#configure terminal
R2(config)#int fa 0/0
R2(config-if)#ip address 192.168.0.1 255.255.255.0
R2(config-if)#no shutdown
R2#wr
R2#

That’s all, now we can inspect our connection by command «ping». That's what I got:

How you can see, all working fine, our devices interconnected successful. Even CDP protocol is working fine:

Now, do «wr» command on all devices, close all console windows , stop all devices (red square on the toolbar or right click on each device) and save our project, exit the program and then relax :).
I congratulate you!!! Today we have added device in to program GNS3, configured them, have connected together and tested the connectivity.
This concludes this post. Hopefully, it will be useful to someone out of you, and maybe all :). Waiting for you in the following posts.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

With best regards, Ant0ni0n.

Configure GNS3 on Windows 7

noreply@blogger.com (Unknown) — Tue, 04 Oct 2011 08:25:00 +0000

Good day!!!

Just want to apologize for my English. I am from Belarus andif there are errors, then feel free to write about them, I will correct them :).
In the last post I explained how to install GNS3 on your computer. As you can see, nothing complicated, everything is easy :). At the time of this writing, has released new version of GNS3. You can download it from here, GNS3 v0.7.4 all-in-one. Installation remains the same, the settings too. The changes affected only the bags in the program.
Today, I want to tell you about how to configure GNS3 for normal and comfortable work. So, I invite all under the cat ...

Run our installed program. We see the first window:

We propose to set up and test Dinamips and verify that the working area available (№ 1) or add the IOS-s device (№ 2). Choose (№ 1).
Window with configuration will appear:

1- Language of the interface;
2- Folder, for our projects;
3- Folder, for our IOS;
4- Place, for our configuration file (for program GNS3).

If the choice of interface language is clear, then the remaining paragraphs lets discuss in more detail. For paragraph 2 and 3 I recommend to create separate subfolders in folder, where you was installed GNS3 (for example c:/program files (x86)/GNS3/projects and c:/program files (x86)/GNS3/images). To paragraph 4, leave all parameters by default. So, after you create the folders, you should have something like this:

Click the «Apply» button and go to tab «Terminal Settins». On this tab choose, what program we will use for connecting to our virtual devices. I chose from the drop down menu program Putty.

Click on «GUI Settings» tab.

Here, put a tick against the item marked with a circle. This means always use the manual mode then you add connections. Also, here you can specify the size of working area (width and height). After you put this parameters click on «Apply» button and go to tab «Dynamips».

On this step, for «Executable path» write the path to file, for «Working directory» create a subfolder «temp» in folder, where we installed program (c:/program files (x86)/GNS3). After that, click on «Test» and you should see a message, that «Dynamips» was successful launched. For «Hypervisor Manager» leave the default settings. Click on «Apply» and go to tab «Capture».

In this tab configure setting for program, which will be catch and display packets (traffic) in our network. In this case, the program Wireshark will use. It must be installed separately. For «Working directory for capture files» in root folder create subfolder «capture» (c:/program files (x86)/GNS3/capture) and then check a path to file wirwshark.exe. If a path not good, then prescribes the right path (parameter %c should be!). Again click on «Apply» and go to tab «Qemu».

On the tab «General Settings», as in previous phases, prescribes the specific file path specified in the relevant fields. For «Working directory» specify subfolder «temp», which we created earlier. After that, click on «Test» and you should see a message, that three major files (Qemuwrapper, qemu и qemu-img) were successfully launched. Click on «Apply» button.
For the next configuration you should have IOS for routers, PIX, ASA and images for QemuHosts. IOS for routers, PIX, ASA you may find in the Internet, images for QemuHosts you may download from that place. After you found and downloaded all you need, put this in subfolder «images».
So, if you are ready, then go to the tab «Qemu Host».

Here, write the name of your Qemu host (1). In drop down menu (2) you must choose image that you need. Below, you can specify parameter for RAM. Then, click «Save» button, you should see message that first Qemu Host was successful created. You may append many Hosts, if you want, procedure is similar.
Next, go to the tab «PIX» (on top).

Here doing a similar action as in previous case. Do not forget to click «Save»!!! The parameters that are marked «1» we will discuss in the next posts.
I do not going to tell you about the following tabs (JunOS, ASA, IDS) because I do not have images and I do not use them in my work yet. But I will tell you about them in the next posts.
Click «Apply» button and then «OK». You have to go back to the first page, that we began our work in this post (see first image). Click on item №2. You should see this window:

1 – image file (from folder with all IOS and images);
2 – platform of your virtual router;
3 – model of virtual router from that platform.

Make sure the image file (IOS) is fully consistent with the chosen platform and model, otherwise, your virtual router does not work. Click «Save» and you will see your first virtual router at the top. «Base config» parameter can be left by default. In the same way you must add the rest of IOS. Do not forget click «Save» button after each addition devices.
On tab «External hypervisors» you can leave all by default. If necessary, you may correct them at any time.
Click «Close» button. You have to go back to the first page, that we began our work in this post again. Click «OK» on it.
That is all done!!! I congratulate you!!! We have finished configuring basic parameters of GNS3.
This concludes this post. Hopefully, it will be useful to someone out of you, and maybe all :). Waiting for you in the following posts.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

With best regards, Ant0ni0n.

Installing GNS3 on Windows 7

noreply@blogger.com (Unknown) — Tue, 04 Oct 2011 07:29:00 +0000

Good day!!!

Just want to apologize for my English. I am from Belarus andif there are errors, then feel free to write about them, I will correct them :).
Today I suggest you to install a wonderful program product. This is a graphic simulator of network equipment GNS3, which allows you to simulate complex network solutions on a local computer.
This program uses real IOS of routers and L3-switches cisco, can emulate Linux-hosts, have support PIX/ASA, IPS and many other interesting things.
GNS3 - a great help in preparing for exams cisco (CCNA, CCNP, etc.), and just a good way to maintain you network knowledge to be good :), by creating different lessons and simulations of different situations on the network.
Welcome…

In the beginning, download the latest version of GNS3 from that place http://www.gns3.net/download. About IOS-s to routers and firewalls suggest you go to google, I think it will help :). Another way - is to buy everything you need on Amazon.com by clicking the link side of the page.
Let’s start the installation…
Running file GNS3-0.7.3-win32-all-in-one.exe (It was the latest version at the time of download).

Click «Next». We agree with the license, select the folder name in «Start menu». Then, choose which components to install:

WinPCap (Windows Packet Capture) – a program, that catches, count and transmit the network packets.
Dynamips – is an emulator program. Dynamips runs on Linux , Mac OS or Windows and can emulate the hardware of the Cisco series routing platforms by directly booting an actual Cisco IOS software image into the emulator.
QEMU - is an open source, fully emulates the PC. In addition to emulating a processor, QEMU can emulate all necessary subsystems, such as network adapters, and video adapters. It can also emulate the more advanced things, such as symmetric multiprocessing systems (up to 255 processors) and other processor architectures such as ARM or PowerPC.

On this screen I recommend to select all the components (by default). Click «Next», choose a folder to contain the program and click «Install».
If you have already installed WinPCap and you have not removed a tick in the choice of components, the following window will appear.

Click «OK», setup will prompt you to install WinPCap again (install, if your version is older than the package with GNS3). During installation WinPCap, all the time press «Next» (or «Install») without changing the default settings.
Immediately after the installation WinPCap, will continue installing the components of GNS3 and final window will appear:

Push the «Finish» button and… Congratulations!!!!! You have just installed GNS3 on your PC :).
This concludes this post. Hopefully, it will be useful to someone out of you, and maybe all :). Waiting for you in the following posts.

If you have a questions or comments, then do not be afraid to write me!!!! This is my contact information. I will pleased to answer!!!!

With best regards, Ant0ni0n.