Showing posts with label Packet Tracer Simulator. Show all posts
Showing posts with label Packet Tracer Simulator. Show all posts

Thursday, December 20, 2012

Static Routing and Default Routing Configurations















Use the knowledge you gain from the previous posts of router configuration since this activity needs knowledge up to static routing and we are going to learn something called Default routing here something which is similar to static routing.

Step1 

Design the above network and load it in to Packet Tracer Simulator.
(Router 2811 has 1 Ethernet and 2 Serial interfaces.Select R1 – S0 and R2 – S1 as DCE side for clocking inside the simulator)


















For R1 and R2, use 1841 routers and add single serial port for each.


















Since R3 needs two serial ports, use 1841 router but add two serial ports as shown above.

Step2

Name R1, R2 and R3 as Malabe, Metro and Matara.

For R0 -->
Router(config)#hostname MALABE

For R1 -->
Router(config)#hostname METRO

For R2 -->
Router(config)#hostname MATARA

Step3

Design a suitable IP plan for the above networks.Note: Subnetting can be applied. (eg. 10.1.0.0 255.255.0.0)


Applying Subnetting

Assume that the given Network address is 192.168.10.0 It belongs to class C. Therefore cannot harm to the first three Bytes. We have to make 5 subnets (3 LANs and 2 WANs) we can go for creating 8 subnets using 3 bits from the host side of the given Network address (23)

It's easy if you write the host ID expanded in binary to represent the eight bits meanwhile e leaving the network ID part as it is because we are not suppose to change it.

The possible combinations are:-

 Sub net addresses |   possible IP addresses
192.168.10.0000 0000 à 192.168.10.0         192.168.10.0   X because it is the network address of subnet zero
                                                            192.168.10.1                                                                
                                                            192.168.10.2
                                                            192.168.10.31 X because it is the DB address of subnet zero

192.168.10.0010 0000 à 192.168.10.32       192.168.10.32 X because it is the network address of subnet 1
                                                            192.168.10.33                                                             
                                                            192.168.10.34
                                                            192.168.10.63 X because it is the DB address of subnet 1

192.168.10.0100 0000 à 192.168.10.64       192.168.10.64 X because it is the network address of subnet 2
                                                            192.168.10.65                                                             
                                                            192.168.10.66
                                                            192.168.10.95 X because it is the DB address of subnet 2

192.168.10.0110 0000 à 192.168.10.96       192.168.10.96 X because it is the DB address of subnet 3
                                                            192.168.10.97                                                             
                                                            192.168.10.98
                                                            192.168.10.127 X because it is the DB address of subnet 3
192.168.10.1000 0000 à 192.168.10.128     192.168.10.128 X because it is the network address of subnet 4
                                                            192.168.10.129                                                          
                                                            192.168.10.130
                                                            192.168.10.159 X because it is the DB address of subnet 4

192.168.10.1010 0000 à 192.168.10.160     192.168.10.160 X because it is the network address of subnet 5
                                                            192.168.10.161                                                          
                                                            192.168.10.162
                                                            192.168.10.191 X because it is the DB address of subnet 5

192.168.10.1100 0000 à 192.168.10.192     192.168.10.192 X because it is the network address of subnet 6
                                                            192.168.10.193                                                          
                                                            192.168.10.194
                                                            192.168.10.223 X because it is the DB address of subnet 6

192.168.10.1100 0000 à 192.168.10.224     192.168.10.224 X because it is the network address of subnet 7
                                                            192.168.10.225                                                          
                                                            192.168.10.226
Note that the IP addresses within the above shown purple colored addresses for each subnet could be used as valid IP addresses for each sub network’s hosts. Make sure to omit the network address and direct broadcast (DB) address in each sub network. Since we only need two IP addresses for each of our five networks, simply the first two IPs could be used.

Step4 

Configure the Serial and Ethernet interfaces of routers and assign clock rate as 64000 for the R1 serial 0 and R2 serial 1 interfaces.

For Router1
MALABE(config)#interface fastEthernet 0/0
MALABE(config-if)#ip address 192.168.10.1 255.255.255.224
MALABE(config-if)#no shutdown

MALABE(config-if)#exit
MALABE(config)#interface serial 0/0/0
MALABE(config-if)#ip address 192.168.10.97 255.255.255.224
MALABE(config-if)#clock rate 64000

MALABE(config-if)#no shutdown
MALABE(config-if)#exit

For Router2
MATARA(config)#interface fastEthernet 0/0
MATARA(config-if)#ip address 192.168.10.65 255.255.255.224
MATARA(config-if)#no shutdown

MATARA(config-if)#exit
MATARA(config)#interface serial 0/0/0
MATARA(config-if)#ip address 192.168.10.130 255.255.255.224
MATARA(config-if)#no shutdown
MATARA(config-if)#exit

For Router3
METRO(config)#interface fastEthernet 0/0
METRO(config-if)#ip address 192.168.10.33 255.255.255.224
METRO(config-if)#no shutdown

METRO(config-if)#exit
METRO(config)#interface serial 0/0/0
METRO(config-if)#ip address 192.168.10.98 255.255.255.224
METRO(config-if)#no shutdown

METRO(config-if)#exit
METRO(config)#interface serial 0/0/1
METRO(config-if)#ip address 192.168.10.129 255.255.255.224
METRO(config-if)#clock rate 64000
METRO(config-if)#no shutdown

METRO(config-if)#exit




Step5

Configure the PC’s. (IP address, Subnet Mask and Default Gateway)


Step6

Use ‘ping’ command to check the connectivity.

IP Address......................: 192.168.10.2
Subnet Mask.....................: 255.255.255.224
Default Gateway.................: 192.168.10.1

PC>ping 192.168.10.1

Pinging 192.168.10.1 with 32 bytes of data:

Reply from 192.168.10.1: bytes=32 time=63ms TTL=255
Reply from 192.168.10.1: bytes=32 time=32ms TTL=255
Reply from 192.168.10.1: bytes=32 time=32ms TTL=255
Reply from 192.168.10.1: bytes=32 time=31ms TTL=255

Ping statistics for 192.168.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 63ms, Average = 39ms

PC>ping 192.168.10.34

Pinging 192.168.10.34 with 32 bytes of data:

Reply from 192.168.10.1: Destination host unreachable.
Reply from 192.168.10.1: Destination host unreachable.
Reply from 192.168.10.1: Destination host unreachable.
Reply from 192.168.10.1: Destination host unreachable.

Ping statistics for 192.168.10.34:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

PC>ping 192.168.10.66

Pinging 192.168.10.66 with 32 bytes of data:

Reply from 192.168.10.1: Destination host unreachable.
Reply from 192.168.10.1: Destination host unreachable.
Reply from 192.168.10.1: Destination host unreachable.
Reply from 192.168.10.1: Destination host unreachable.

Ping statistics for 192.168.10.66:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

PC>

The above ping commands of PC0 summarizes that still the data exchange could be done successfully within Local Networks only. Networks still cannot identify their remote networks successfully. So we need to route to perform that task.

Step7 

Assign Static Routing to all the routers and check the connectivity.

Static routing is done by the administrator to make the remote networks of each network to identify and exchange data when the remote network addresses and subnet masks are known.


Assigning Default Routing to necessary routers.

Default routing is kind of similar to static routing but this is done when the network administrator doesn’t know the exact network addresses and subnet masks of remotely situated networks.

Note: - If we need to perform default routing to the same networks that we have already done static routing, then first we need to remove the static routing commands from them and then assign default routing commands.

To remove all the static routings use the below shown commands for each.

MALABE(config)#no ip route 192.168.10.64 255.255.255.0 192.168.10.98
MALABE(config)# no ip route 192.168.10.32 255.255.255.0 192.168.10.98

METRO(config)# no ip route 192.168.10.0 255.255.255.0 192.168.10.97
METRO(config)# no ip route 192.168.10.64 255.255.255.0 192.168.10.130

MATARA(config)#no ip route 192.168.10.0 255.255.255.0 192.168.10.129
MATARA(config)# noip route 192.168.10.32 255.255.255.0 192.168.10.129

How to set default routing…

MALABE(config)# ip route 0.0.0.0 0.0.0.0 192.168.10.98
METRO(config)# ip route 0.0.0.0 0.0.0.0 192.168.10.97
MATARA(config)# ip route 0.0.0.0 0.0.0.0 192.168.10.129

Note :- Since we don’t know the destination Network addresses and subnet masks, we simply assign them as 0.0.0.0 but the default gateway, what we already should know should be assigned as it is.

Final Step

Check the connectivity again.
PC>ipconfig

IP Address......................: 192.168.10.2
Subnet Mask.....................: 255.255.255.224
Default Gateway.................: 192.168.10.1

PC>ping 192.168.10.1

Pinging 192.168.10.1 with 32 bytes of data:

Reply from 192.168.10.1: bytes=32 time=31ms TTL=255
Reply from 192.168.10.1: bytes=32 time=31ms TTL=255
Reply from 192.168.10.1: bytes=32 time=31ms TTL=255
Reply from 192.168.10.1: bytes=32 time=31ms TTL=255

Ping statistics for 192.168.10.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 31ms, Average = 31ms
PC>ping 192.168.10.34

Pinging 192.168.10.34 with 32 bytes of data:

Reply from 192.168.10.34: bytes=32 time=109ms TTL=124
Reply from 192.168.10.34: bytes=32 time=125ms TTL=124
Reply from 192.168.10.34: bytes=32 time=125ms TTL=124
Reply from 192.168.10.34: bytes=32 time=125ms TTL=124

Ping statistics for 192.168.10.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 109ms, Maximum = 125ms, Average = 121ms

PC>ping 192.168.10.66

Pinging 192.168.10.66 with 32 bytes of data:

Reply from 192.168.10.66: bytes=32 time=125ms TTL=125
Reply from 192.168.10.66: bytes=32 time=125ms TTL=125
Reply from 192.168.10.66: bytes=32 time=109ms TTL=125
Reply from 192.168.10.66: bytes=32 time=125ms TTL=125

Ping statistics for 192.168.10.66:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 109ms, Maximum = 125ms, Average = 121ms

PC>

Now the data exchange throughout the network is done successfully.

Do not forget to copy the running-config files to the startup configuration files as shown below. This makes the running-configuration information (that are volatile and lost when the router is switched off). To non-volatile memory in NVRAM.

MALABE#copy running-config  startup-config
METRO#copy running-config startup-config
MATARA#copy running-config startup-config

How to assign passwords for routers?

Before starting with the activity of this post, it's better if you can design the below shown network and load it in to Packet Tracer Simulator. Also have an IP plan as described below. If you need clarifications in designing the network, please refer the previous posts carefully and then come back here. 

















How to assign host names for the routers?

This was a task that I should have told you earlier since it's such a simple but useful task to remember the routers easily when we deal with a considerable amount of routers in a network.

  1. click on a router0 
  2. select CLI tab
  3. if it prompts the question 'Continue with configuration dialog? [yes/no]: ' type no and press Enter key
  4. type enable and go to the privileged mode
  5. type config t and go to the configuration mode
  6. type hostname IT and press Enter (or type any name for the router instead of IT)
so, your router is ready with the assigned hostname. note that from this pint onward, the CLI displays the assigned name of the router instead of displaying 'Router' word by default. this makes you easy to remember the router that you currently working with via the CLI.

refer the below shown CLI commands for clarification

Router>
Router>enable
Router#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#hostname IT
IT(config)#end
IT#

follow the same steps and assign router-1 as FINANCE as the hostname

Designing a suitable IP plan for the above networks

When you design an IP plan for a network, it’s better to use private IP addresses for LAN(private networks ) and IPs in out of private IP ranges for WAN’s. Here Fe2 ( fastethernet port of PC-0) and Fe1( fastethernet port of IT router)  belong to the same network and therefore we can select IP addresses from the following ranges.







If the above table is not that clear to you, this is what it says. out of all the network IDs available in ClassA, only 10.0.0.0 is considered as a private network ID. the same way out of all the network IDs of Class B and classB the number of available private network IDs are 16 and 256 respectively. 
Generally Class A IPs are more expensive and Class C are less expensive than above classes, since we only need two IP addresses for each of our LANs , it’s good to select Network addresses within class C range.





For the WAN’s serial port IP addresses, the above shown table's addresses can be avoided because WAN is a public network. 

R0 –Serial Port (S1) --> 5.0.0.3
R1–Serial Port (S2) --> 5.0.0.4

following the previous posts, configure the given simple network assigning hostnames for routers, IP addresses for routers and PCs and assign clock rate for the router's serial ports as well. Since the main target of this post is to focus on the password settings in routers and therefore I thought not to repeat the simple network configurations here.

What are the types of passwords that can be assigned to routers?

Follow the below image to understand the password classification of routers that are mainly divided in to two as user level passwords and privileged level passwords (of course there is nothing called as configuration level passwords :))














How to set Privileged level password?


Password settings can be done only in the configuration mode.

though there are two methods to set passwords for the privileged level, both are not considered as same. Assume that you used both the commands and set two different passwords to the privileged level, when you tried to it from User level (enable) it asks for the password but here the priority is given for the enable secret rather than enable password.








Go to privileged level and type show running-config to see all your configurations (whatever the commands that you have given to the particular router so far). Since you set privileged level passwords, they also would be displayed there as below.













according to the above image, you should understand that enable secret  is more powerful than the enable password. Also when you see the running configurations, the password that you assigned via enable password will show as it was typed whereas the enable secret will be displayed encrypted.

How to set User level passwords?


Since there are three types of passwords depending on the Router access method that we used (That are Console, Auxiliary and Telnet), there are three types of set of commands should be followed for each.

  • How to set Console pw?


Go to configuration mode --> type line ? and press Enter --> type line console 0 and press Enter--> type  password dccn  and press Enter --> login 

refre the below shown CLI commands


IT(config)#line ?
  <0-81>   First Line number
  console  Primary terminal line
  vty      Virtual terminal
IT(config)#line console 0
IT(config-line)#password dccn
IT(config-line)#login
IT(config-line)#end
IT#
%SYS-5-CONFIG_I: Configured from console by console
IT#
IT#exit                    <-------trying to enter to the user level where the user access verification is required

IT con0 is now available

Press RETURN to get started.
User Access Verification

Password:             <-------typed dccn but the password typing is invisible

IT>                      <-------accessed user level

Now whenever you tried to enter to the User level from privileged level (by typing exit) it asks for the User level password (here it is your console user password)

  • How to set Auxiliary pw?


Go to configuration mode   -->  type line ? and press Enter--> type line aux 0 and press Enter--> type password dccn and press Enter--> type login and press Enter

  • How to set Telnet pw?

Go to configuration mode --> type line ? and press Enter --> type  line vty 0  4 and press Enter--> type password dccn  and press Enter--> type login and press Enter

Note: - in Telnet we can connect a LAN with any number of PCs to a Router but only five of them could be accessed by the Router simultaneously. That is what we state 0  4 when setting Telnet password as above.




I will be continuing the same network system with the next post to describe static routing vs dynamic routing.