Task- 9

Aim- Creation of Networks using routers.

Apparatus:- Software – Cisco Packet
Tracer Procedure: -
Router: A router is a networking device that forwards data packets between computer networks.
Routers perform the traffic directing functions on the Internet. Data sent through the internet, such as a web
page or email, is in the form of data packets.
Steps to create a network topology with router.

1. Open Cisco Packet Tracer: Open Cisco Packet Tracer simulator or some
related tool to simulate a network topology and simulate web traffic in it.

2. Place some end devices in the topology: These end devices will
communicate each other in the network through switch and router.

3. Place network devices (router and switch) in the topology: Use the relevant
router and switch, which are compatible with another devices

Akashdeep Sant 2223594

 4.Connect every device with a relevant connection media for making a connection.

5. Configure IP Address and Subnet mask on every host: Configure every machine including host (PC) and
router by assigning it an IP address and subnet mask in order to make them communicate with each
other in the network. Add Default gateway to every host.

6. Configuring Router’s Interfaces: Configure router by assigning a IP address to each interface. Add
Gateway of hosts as the IP address of Router’s Interface of respective network.

Akashdeep Sant 2223594

 7. Check for connectivity: After configuring the given network a packet should be ping from one machine
to another

Akashdeep Sant 2223594

 Task- 10
Aim- Configuring networks using the concept of subnetting
Apparatus:- Software – Cisco Packet Tracer
Procedure: -
Sub networking becomes an important feature as your organization's networking needs grow. Sub
networking lets you divide up your pool of Internet Protocol version 4 (IPv4) addresses so you can split
those addresses across several physical networks within your organization. or administrative or technical
reasons, many organizations choose to divide one network into several subnets. Sub networking enables
several local networks to appear as a single Internet network to off-site hosts. It divides the addresses for a
single network to accommodate the fact that the network consists of several physical networks. You should
consider using subnets in the following instances:
•When you want to hide the local network topology from the outside world. Using subnets requires only a
single route to external gateways.
•When you want the ability to administer IP addresses locally. For example, a company may have an
engineering subnet, a product marketing subnet, and a sales subnet, each administered by a different
administrator who has control of IP addresses in a given range.
•When network bandwidth is limited due to cabling constrCSEnts. Setting up subnets,each separated by a
gateway host, limits local subnet packets to those that are either destined for or sent from a local host. In
this way, the overall network traffic seen by each host on the subnet is reduced.
Setting up a subnet requires you to:
•determine the appropriate IP addresses for your subnets
•configure subnet hosts with the correct IP addresses and network masks
•configure gateway hosts between subnets
Subnets allow you more flexibility when assigning network addresses. For detCSEls on network address
assignment and network classes, see ``Network address''.

Network masks:

Subnetting involves extending the network ID portion of an IP address by borrowing bits from the host
portion to create a subnet portion. The remaining bits in the host portion are used to assign individual host
addresses within each subnet.

 Number of Subnets: The number of subnets created depends on how many bits are borrowed from
the host portion. If m bits are borrowed, the number of subnets is 2m2^m2m.
 Number of Hosts per Subnet: The number of hosts that can be assigned within a subnet is
determined by the remaining bits in the host portion. If n bits are left for hosts, the number of usable host
addresses per subnet is 2n−22^n - 22n−2, accounting for the network and broadcast addresses that cannot
be assigned to hosts.
o For example, in a subnet with a /24 mask, there are 8 bits for hosts (since 32 bits total - 24 bits
for the network). This results in 28−2=2542^8 - 2 = 25428−2=254 usable host addresses per subnet.
 Subnet Portion Restrictions: The host portion of the address cannot consist entirely of zeros (for
the network address) or all ones (for the broadcast address).

Akashdeep Sant 2223594

 Example:
When a Class B network (e.g., 131.60.0.0/16 with a subnet mask of 255.255.0.0) is subnetted with a
mask of 255.255.255.0 (i.e., /24), it creates 256 subnets (since 8 bits are borrowed from the host portion)
with 254 usable host addresses per subnet. When subnetting a Class B network, you can create multiple
subnets by borrowing bits from the host portion of the IP address. Here's how it works:

 Creating Subnets:

 By borrowing 8 bits from the host portion, you can create 256 subnets (2^8), with each subnet
supporting 254 usable host addresses (2^8 - 2).
 Example: A Class B network like 131.60.0.0 with a subnet mask of 255.255.255.0 (or /24)
gives you 256 subnets, each with 254 hosts.

 Changing Network Masks:

 A Class B network (e.g., 172.16.0.0) can be split into 256 subnets by changing the network mask
from 255.255.0.0 (default) to 255.255.255.0.
 The broadcast address for each subnet reveals the network address while hiding the host part. For
instance, for subnet 172.16.246.0/24, the broadcast address is 172.16.246.255.

 Subnet Configuration:

 You can allocate bits from the host portion for subnets. For example, 8 bits for subnets and 8 bits for
hosts would be a typical configuration, allowing up to 256 subnets with 254 hosts in each.
 A Class C subnet mask (255.255.255.0) applied to a Class B network allows for 256 subnets with
254 hosts per subnet. If fewer hosts are needed but more subnets are required, you could use a mask of
255.255.255.128, creating 512 subnets with 126 hosts each.

 Example of Subnet Calculation:

 For a network 131.60.0.0/24, the first subnet would have the range from 131.60.0.1 to
131.60.0.126 with a broadcast address of 131.60.0.127.

 Subnetting Class C Networks:

 For a Class C network (e.g., 221.138.62.0), you can borrow bits from the host portion to create
subnets. For example, using a mask of 255.255.255.224 (or /27), you can create 8 subnets with 30
usable hosts per subnet, which is ideal for smaller networks.

Akashdeep Sant 2223594

 Task- 11
Aim- Practical implementation of basic network command and Network
configuration commands like ping, ipconfig, netstat, tracert etc. for troubleshooting
network related problems.
Apparatus:- Software – Cisco Packet Tracer
Procedure: -
All commands related to Network configuration which includes how to switch to privilege mode and
normal mode and how to configure router interface and how to save this configuration to flash memory or
permanent memory.
This command includes:
Configuring the Router commands General Commands to configure network Privileged Mode commands
of a router Processes & StatistiCSE
IP Commands
Other IP Commands e.g. show ip route etc.
1. ping: ping(8) sends an ICMP ECHO_REQUEST packet to the specified host. If the host responds, you
get an ICMP packet back. Sound strange? Well, you can “ping” an IP address to see if a machine is alive.
If there is no response, you know something is wrong.
2. Ipconfig: Displays all current TCP/IP network configuration values and refreshes Dynamic Host
Configuration Protocol (DHCP) and DomCSEn Name System (DNS) settings. Used without parameters,
ipconfig displays Internet Protocol version 4 (IPv4) and IPv6 addresses, subnet mask, and default
gateway for all adapters.
3. Netstat: The netstat command generates displays that show network status and protocol statistiCSE .
You can display the status of TCP and UDP endpoints in table format, routing table information, and
interface information. Netstat displays various types of network data depending on the command line
option selected. These displays are the most useful for system administration. The syntax for this form is:
netstat [-m] [-n] [-s] [-i | -r] [-f address_family]
4. The most frequently used options for determining network status are: s, r, and i. See the netstat(1M)
man page for a description of the options.
5. Traceroute: Tracert is a command which can show you the path a packet of information taken from
and is discarded. In addition to this, it will tell you how long each 'hop' from router to router takes.
6. nslookup: Displays information from DomCSEn Name System (DNS) name servers. NOTE: If you
write the command as above it shows as default your pc's server name firstly.
7. pathping: A better version of tracert that gives you statiCSE about packet lost and latency.

Akashdeep Sant 2223594

 Task- 12
Aim- Configuration of networks using static and default
routes Apparatus:- Software – Cisco Packet Tracer
Procedure: -
Step 1:
Test connectivity between the PCSE and the default gateway.
To determine if there is connectivity from each PC to its configured gateway, first use a simple
ping test.
a) Click BOpc and go to Desktop > Command Prompt.
b) From the command prompt, type the Ip config command. Note the IP address for BOpc and
the default gateway address. The default gateway address is the IP address for the Fast
Ethernet interface on Branch
c) Ping 192.168.1.1, the default gateway address for the Branch Office LAN, from the
command prompt on BOpc. This ping should be successful.
d) Click PNpc and go to Desktop > Command Prompt
e) From the command prompt, type the ipconfig command. Note the IP address for PNpc and
the default gateway address. The default gateway address is the IP address for the Fast
Ethernet interface on Partner.
f) Ping 192.168.3.1, the default gateway address for the PartnerNet LAN, from the command
prompt on tipping should be successful
g) Repeat steps a, b, and c for MOpc and its respective default gateway, the Fast Ethernet
interface on MCSEn Office. Each of these ping tests should be successful.
Step 2:
Ping between routers to test connectivity.
a) Use a console cable and terminal emulation software on BOpc to connect to BranchOffice.
b) Test connectivity with MCSEnOffice by pinging 10.10.10.1, the IP address of the directly
connected serial 3/0 interface. This ping should succeed.
c) Test connectivity with MCSEnOffice by pinging 10.10.10.5, the IP address of the serial 2/0
interface. This ping should fCSEl.
d) Issue the show ip route command from the terminal window of BOpc. Note that only
directly connected routes are shown in the BranchOffice routing table. The ping to 10.10.10.5
fCSEled because the BranchOffice router has no routing table entry for 10.10.10.5.
e) Repeat steps a through d on the other two PCSE. The pings to directly connected networks
will succeed. However, pings to remote networks will fCSEl.
f) What steps must be taken to reach all the networks from any PC in the activity?

Step 3:
Viewing the routing tables.
You can view routing tables in Packet Tracer using the Inspect tool. The Inspect tool is in the
Common Tools bar to the right of the topology. The Inspect tool is the icon that appears as a
magnifying glass.
a) In the Common Tools bar, click on the Inspect tool.

Tania 2223626
b) Click the MCSEn Office router and choose Routing Table.
c) Click the BranchOffice router and choose Routing Table.
d) Click the PartnerNet router and choose Routing Table.
e) Move the routing table windows around so that you can see all three at once.
f) What networks do each of the routers already know about?
g) Does each router know how to route to all networks in the topology? After comparing the
routing tables, close the window for each routing table by clicking the x in the upper right
corner of each window.
Step 4:
Configure default routes on the BranchOffice and PartnerNet routers.
To configure static routes for each router, first determine which routes need to be added for
each device. For the BranchOffice and the PartnerNet routers, a single default route allows
these devices to route traffic for all networks not directly connected. To configure a default
route, you must identify the IP address of the next hop router, which in this case is the
MCSEnOffice router.
a) From the Common toolbar, click the Select tool.
b) Move the cursor over the red serial link between the BranchOffice router and the
MCSEnOffice router. Notice that the interface of the next hop is S3/0.
c) Move the cursor over the MCSEnOffice router and note that the IP address for Serial 3/0 is
10.10.10.1.
d) Move the cursor over the red serial link between the PartnerNet router and the
MCSEnOffice router. Notice that the interface of the next hop is S2/0.
e) Move the cursor over the MCSEnOffice router and note that the IP address for Serial 2/0 is
10.10.10.5.
f) Configure the static routes on both the BranchOffice and PartnerNet routers using the CLI.
Click the BranchOffice router, and click the CLI tab.
g) At the BranchOffice> prompt, type enable to enter privileged EXEC mode.
h) At the BranchOffice# prompt, type configure terminal.
i) The syntax for a default route is ip route 0.0.0.0 0.0.0.0 next_hop_ip_address. Type ip route
0.0.0.0 0.0.0.0 10.10.10.1.
j) Type end to get back to the BranchOffice# prompt.
k) Type copy run start to save the configuration change.
l) Repeat steps f through k on the PartnerNet router, using 10.10.10.5 as the next hop IP
address. Step 5: Configure static routes at MCSEn Office.
a) The configuration of static routes at the MCSEn Office is a bit more complex because the
MCSEnOffice router is responsible for routing traffic to and from the Branch Office and
PartnerNet LAN segments. The MCSEnOffice router knows only about routes to the
10.10.10.0/30, 10.10.10.4/30, and 192.168.2.0/24 networks because they are directly
connected. Static routes to the 192.168.1.0/24 and 192.168.3.0/24 networks need to be added
so that the MCSEnOffice router can route traffic between the networks behind the
BranchOffice and PartnerNet routers. a. Click the MCSEnOffice router, and then click the CLI
tab.
b) At the MCSEnOffice> prompt, type enable to enter privileged EXEC mode.
c) At the MCSEnOffice# prompt, type configure terminal.

Tania 2223626
d) The syntax for a static route is ip route network
subnet_mask next_hop_ip_address: ip route 192.168.1.0 255.255.255.0 10.10.10.2 ip route
192.168.3.0 255.255.255.010.10.10.6
e) Type end to return to the MCSEnOffice# prompt.
f)Type copy run start to save the configuration change.
g) Repeat steps a through e from Step 3. View the routing tables and notice the difference in
the routing tables. The routing table for each router should have an “S” for each static route.
Step 6: Test connectivity.
a) Now that each router in the topology has static routes configured, all hosts should have
connectivity to all other hosts. Use ping to verify connectivity.
b) Click BOpc and click the Desktop tab.
c) Choose the Command prompt option.
d) Type ping 192.168.3.2. The ping should be successful, verifying that the static routes are
configured properly.
e) Type ping 192.168.2.2. Notice that the result is successful even though you did not
specifically add the 192.168.2.0 network as a static route into any of the routers. Because a
default route was used on the Branch Office and Partner Net routers, a route for the
192.168.2.0 network was not needed. The default route sends all traffic destined off network to
the MCSEn Office router. The 192.168.2.0 network is directly connected to the MCSEn Office
router; therefore, no additional routes needed to be added to the routing table
f) Click the Check Results button at the bottom of this instruction window to check your work

Tania 2223626