Vicky Burvi (15-379594-PA-16652)

LAPORAN EKSPERIMEN
JARINGAN KOMPUTER C
Konfigurasi IPv4 dan IPv6
Disusun oleh:
Nama : Vicky Burvi
NIM : 15/379594/PA/16652
Tanggal : 6 Maret 2017
LABORATORIUM ELEKTRONIKA DASAR DAN INSTRUMENTASI DASAR

DEPARTEMEN ILMU KOMPUTER DAN ELEKTRONIKA
FAKULTAS MATEMATIKA DAN ILMU PENGETAHUAN ALAM
UNIVERSITAS GADJAH MADA
2017
Packet Tracer - Connecting a Wired and Wireless LAN
Topology
Addressing Table
Device Interface IP Address Connects To
Eth6 N/A Fa0/0

Cloud
Coax7 N/A Port0
Port0 N/A Coax7
Cable Modem
Port1 N/A Internet
Console N/A RS232
Fa0/0 192.168.2.1/24 Eth6
Router0
Fa0/1 10.0.0.1/24 Fa0
Ser0/0/0 172.31.0.1/24 Ser0/0
Ser0/0 172.31.0.2/24 Ser0/0/0
Router1
Fa1/0 172.16.0.1/24 Fa0/1
Internet 192.168.2.2/24 Port 1
WirelessRouter
Eth1 192.168.1.1 Fa0
Family PC Fa0 192.168.1.102 Eth1
Switch Fa0/1 172.16.0.2 Fa1/0
Netacad.pka Fa0 10.0.0.1 Fa0/1
Configuration Terminal RS232 N/A Console
Objectives
Part 1: Connect to the Cloud
Part 2: Connect Router0
Part 3: Connect Remaining Devices
Part 4: Verify Connections
Part 5: Examine the Physical Topology
Background
When working in Packet Tracer (a lab environment or a corporate setting), you should know how to select the
appropriate cable and how to properly connect devices. This activity will examine device configurations in
Packet Tracer, selecting the proper cable based on the configuration, and connecting the devices. This
activity will also explore the physical view of the network in Packet Tracer.
Part 1: Connect to the Cloud
Step 1: Connect the cloud to Router0.

a. At the bottom left, click the orange lightning icon to open the available Connections.
b. Choose the correct cable to connect Router0 Fa0/0 to Cloud Eth6. Cloud is a type of switch, so use a
Copper Straight-Through connection. If you attached the correct cable, the link lights on the cable
turn green.
Step 2: Connect the cloud to Cable Modem.

Choose the correct cable to connect Cloud Coax7 to Modem Port0.
If you attached the correct cable, the link lights on the cable turn green.
Part 2: Connect Router0
Step 1: Connect Router0 to Router1.

Choose the correct cable to connect Router0 Ser0/0/0 to Router1 Ser0/0. Use one of the available Serial
cables.
Step 2: Connect Router0 to netacad.pka.

Choose the correct cable to connect Router0 Fa0/1 to netacad.pka Fa0. Routers and computers
traditionally use the same wires to transmit (1 and 2) and receive (3 and 6). The correct cable to choose
consists of these crossed wires. Although many NICs can now autosense which pair is used to transmit and
receive, Router0 and netacad.pka do not have autosensing NICs.
Step 3: Connect Router0 to the Configuration Terminal.

Choose the correct cable to connect Router0 Console to Configuration Terminal RS232. This cable
does not provide network access to Configuration Terminal, but allows you to configure Router0 through
its terminal.
If you attached the correct cable, the link lights on the cable turn black.
Part 3: Connect Remaining Devices

Step 1: Connect Router1 to Switch.
Choose the correct cable to connect Router1 Fa1/0 to Switch Fa0/1.
If you attached the correct cable, the link lights on the cable turn green. Allow a few seconds for the light
to transition from amber to green.
Step 2: Connect Cable Modem to Wireless Router.

Choose the correct cable to connect Modem Port1 to Wireless Router Internet
port. If you attached the correct cable, the link lights on the cable will turn green.
Step 3: Connect Wireless Router to Family PC.

Choose the correct cable to connect Wireless Router Ethernet 1 to Family
PC. If you attached the correct cable, the link lights on the cable turn green.
Hasil akhir:
Part 4: Verify Connections

Step 1: Test the connection from Family PC to netacad.pka.
a. Open the Family PC command prompt and ping netacad.pka.
b. Open the Web Browser and the web address http://netacad.pka.
Step 2: Ping the Switch from Home PC.

Open the Home PC command prompt and ping the Switch IP address of to verify the connection.
Step 3: Open Router0 from Configuration Terminal.

a. Open the Terminal of Configuration Terminal and accept the default
settings. b. Press Enter to view the Router0 command prompt.
c. Type show ip interface brief to view interface statuses.
Part 5: Examine the Physical Topology

Step 1: Examine the Cloud.
a. Click the Physical Workspace tab or press Shift+P and Shift+L to toggle between the logical
and physical workspaces.
b. Click the Home City icon.
c. Click the Cloud icon. How many wires are connected to the switch in the blue rack?
2
d. Click Back to return to Home City.
Step 2: Examine the Primary Network.

a. Click the Primary Network icon. Hold the mouse pointer over the various cables. What is located on
the table to the right of the blue rack?
Yang berada pada meja di sebelah kanan rak biru adalah komputer Configuration Terminal
b. Click Back to return to Home City.
Step 3: Examine the Secondary Network.

a. Click the Secondary Network icon. Hold the mouse pointer over the various cables. Why are there
two orange cables connected to each device?
Karena dua kabel berwarna jingga yang terhubung ke tiap perangkat adalah kabel fiber optic.
b. Click Back to return to Home City.
Step 4: Examine the Home Network.

a. Why is there an oval mesh covering the home network?
Karena ada home network terdapat jaring oval yang merupakan daerah yang tercover oleh antena
Wireless Router.
b. Click the Home Network icon. Why is there no rack to hold the equipment?
Pada Home Network tidak terdapat rak untuk menaruh perangkat karena Home Network merupakan
jaringan pribadi/rumah, sedangkan rak digunakan untuk menaruh server, router, dan switch yang terdapat
pada jaringan publik.
c. Click the Logical Workspace tab to return to the logical topology.
Suggested Scoring Rubric
Question Possible Earned

Activity Section Location Points Points
Part 5: Examine the Step 1c 4 4

Physical Topology
Step 2a 4 4
Step 3a 4 4
Step 4a 4 4
Step 4b 4 4
Part 5 Total 20 20
Packet Tracer Score 80 80
Total Score 100 100
Packet Tracer - Verifying IPv4 and IPv6 Addressing

Topology
Addressing Table
IPv4 Address Subnet Mask
Device Interface Default Gateway
IPv6 Address/Prefix
10.10.1.97 255.255.255.224 N/A

G0/0
2001:DB8:1:1::1/64 N/A
R1 10.10.1.6 255.255.255.252 N/A
S0/0/1
2001:DB8:1:2::2/64 N/A
Link-local FE80::1 N/A
10.10.1.5 255.255.255.252 N/A
S0/0/0
2001:DB8:1:2::1/64 N/A
R2 10.10.1.9 255.255.255.252 N/A
S0/0/1
2001:DB8:1:3::1/64 N/A
10.10.1.17 255.255.255.240 N/A
G0/0
2001:DB8:1:4::1/64 N/A
R3 10.10.1.10 255.255.255.252 N/A
S0/0/1
2001:DB8:1:3::2/64 N/A
10.10.1.100 255.255.255.224 10.10.1.97
PC1 NIC
2001:DB8:1:1::A /64 FE80:1
10.10.1.20 255.255.255.240 10.10.1.17
PC2 NIC
2001:DB8:1:4::A /64 FE80::3
Objectives
Part 1: Complete the Addressing Table Documentation
Part 2: Test Connectivity Using Ping
Part 3: Discover the Path by Tracing the Route
Background
Dual-stack allows IPv4 and IPv6 to coexist on the same network. In this activity, you will investigate a dual-
stack implementation including documenting the IPv4 and IPv6 configuration for end devices, testing
connectivity for both IPv4 and IPv6 using ping, and tracing the path from end to end for IPv4 and IPv6.
Part 1: Complete the Addressing Table Documentation

Step 1: Use ipconfig to verify IPv4 addressing.
a. Click PC1 and click the Desktop tab > Command Prompt.
b. Enter the ipconfig /all command to collect the IPv4 information. Fill in the Addressing Table with the
IPv4 address, subnet mask, and default gateway
c. Click PC2 and click the Desktop tab > Command Prompt.
d. Enter the ipconfig /all command to collect the IPv4 information. Fill in the Addressing Table with the
IPv4 address, subnet mask, and default gateway.
Step 2: Use ipv6config to verify IPv6 addressing.

a. On PC1, enter the ipv6config /all command to collect the IPv6 information. Fill in the Addressing Table
with the IPv6 address, subnet prefix, and default gateway.
b. On PC2, enter the ipv6config /all command to collect the IPv6 information. Fill in the Addressing Table
with the IPv6 address, subnet prefix, and default gateway.
Part 2: Test Connectivity Using Ping

Step 1: Use ping to verify IPv4 connectivity.
a. From PC1, ping the IPv4 address for PC2. Was the result successful? Ya
b. From PC2, ping the IPv4 address for PC1. Was the result successful? Ya
Step 2: Use ping to verify IPv6 connectivity.

a. From PC1, ping the IPv6 address for PC2. Was the result successful? Ya
b. From PC2, ping the IPv6 address of PC1. Was the result successful? Ya
Part 3: Discover the Path by Tracing the Route

Step 1: Use tracert to discover the IPv4 path.
a. From PC1, trace the route to PC2.
PC> tracert 10.10.1.20
What addresses were encountered along the path?

10.10.1.97 10.10.1.5 10.10.1.10 10.10.1.20
With which interfaces are the four addresses associated?

G0/0 S0/0/0 S0/0/1 NIC Fa0
b. From PC2, trace the route to PC1.


10.10.1.17 10.10.1.9 10.10.1.6 10.10.1.100

G0/0 S0/0/1 S0/0/1 NIC Fa0
Step 2: Use tracert to discover the IPv6 path.

a. From PC1, trace the route to the IPv6 address for
PC2.
PC> tracert 2001:DB8:1:4::A

2001:DB8:1:1::1 2001:DB8:1:2::1 2001:DB8:1:3::2 2001:DB8:1:4::A

G0/0 S0/0/0 S0/0/1 NIC Fa0
b. From PC2, trace the route to the IPv6 address for

PC1.

2001:DB8:1:4::1 2001:DB8:1:3::1 2001:DB8:1:2::2 2001:DB8:1:1::A

G0/0 S0/0/1 S0/0/1 NIC Fa0
Suggested Scoring Rubric
Question Possible Earned

Activity Section Location Points Points
Part 1: Complete the Step 1b 10 10

Addressing Table
Documentation Step 1d 10 10
Step 2a 10 10
Step 2b 10 10
Part 1 Total 40 40
Part 2: Test Connectivity Step 1a 7 7
Using Ping
Step 1b 7 7
Step 2a 7 7
Step 2b 7 7
Part 2 Total 28 28
Part 3: Discover the Path by Step 1a 8 8
Tracing the Route
Step 1b 8 8
Step 2a 8 8
Step 2b 8 8
Part 3 Total 32 32
Total Score 100 100
Packet Tracer - Troubleshooting IPv4 and IPv6 Addressing

Topology
Addressing Table
IPv4 Address Subnet Mask
Device Interface Default Gateway
IPv6 Address/Prefix
G0/0 10.10.1.1 255.255.255.0 N/A

192.168.0.1 255.255.255.0 N/A
Ga0/1
2001:DB8:1:1::1/64 N/A
R1 G0/2 2001:DB8:1:2::1/64 N/A
209.165.201.2 255.255.255.252 N/A
S0/0/0
2001:DB8:1:A001::2/64 N/A
Dual Stack 64.100.1.254 255.255.255.0 64.100.1.1

NIC
Server 2001:DB8:CAFE:1::10/64 FE80::A
PC1 NIC 10.10.1.2 255.255.255.0 10.10.1.1
192.168.0.2 255.255.255.0 192.168.0.1
PC2 NIC
2001:DB8:1:1::2/64 FE80::1
PC3 NIC 2001:DB8:1:2::2/64 FE80::1
Objectives
Part 1: Troubleshoot First Issue
Part 2: Troubleshoot Second Issue
Part 3: Troubleshoot Third Issue
Scenario
You are a network technician working for a company that has decided to migrate from IPv4 to IPv6. In the
interim, they must support both protocols (dual-stack). Three co-workers have called the help desk with
problems and have received limited assistance. The help desk has escalated the matter to you, a Level 2
support technician. Your job is to locate the source of the problems and implement appropriate solutions.
Part 1: Troubleshoot First Issue

A customer using PC1 complains that she cannot access the dualstackserver.pka web page.
Step 1: Verify a detailed help desk ticket.

The help desk collected the following information from the customer, over the phone. Verify that it is correct.
Help Desk Ticket
Client Identifier: PC1

Issue: Unable to access the dualstackserver.pka web page.
Detailed information about the issue
Test: Does the computer have an IP address using ipconfig? Yes
Test: Can the computer contact its gateway using ping? Yes
Test: Can the computer contact the server using tracert? Yes
Test: Can the computer contact the server using nslookup? No
Resolution: Escalate to Level 2 support.
Step 2: Consider probable causes for the failure.

a. Note the tests that have been conducted. If possible, discuss possible scenarios that would create
this situation with your fellow network technicians (classmates).
b. Run more tests if it helps visualize the problem. Simulation mode is available.
ipconfig /all pada PC 1
ping Default Gateway:
Tampilan saat melakukan trace route server (berhasil)

Tampilan saat melakukan DNS lookup (gagal)
Step 3: Propose a solution to solve the problem.

Make a list of things that could be changed to solve this problem. Start with the solution that is most likely
to work.
Solusi yang mungkin:

Mengaktifkan layanan DNS pada Server
Mengganti DNS Server PC1 dengan IP Address penyedia layanan DNS, yaitu Server
DNS Service pada Server telah benar-benar aktif. Ini berarti permasalahan terletak pada pengaturan
DNS Server pada PC1. Setelah di cek, ternyata DNS Server pada PC 1 tidak sesuai dengan IP address
Server, dimana IP address server adalah 64.100.1.254
Step 4: Implement the plan.

Try the most likely solution from the list. If it has already been tried, move on to the next solution.
Solusi yang diimplementasikan adalah mengganti DNS Server pada PC 1 menjadi 64.100.1.254, sesuai
IP Address dari Server
Step 5: Verify the solution resolved the problem.

a. Repeat the tests from the help desk ticket. Did it solve the problem?
b. If the problem still exists, reverse the change if you are not sure it is correct and return to Step 4.
Saat membuka website dualstackserver.pka pada PC 1 berhasil. Permasalahan telah berhasil diselesaikan.
Step 6: Document the solution.

Record the solution to the problem. If you ever encounter the same problem again, your notes will be
very valuable.
Solusi dari permasalahan ini adalah mengubah DNS Server pada PC 1 menjadi 64.100.1.254, sesuai IP
Address dari Server
Part 2: Troubleshoot Second Issue

A customer using PC2 complains that he cannot access files on the DualStackServer.pka at
2001:DB8:CAFE:1::10.

The help desk collected the following information from the customer, over the phone. Verify that it is correct.
Help Desk Ticket

Issue: Unable to access the FTP service of 2001:DB8:CAFE:1:10.
Detail information about the Issue
Test: Does the computer have an IPv6 address using ipv6config? Yes
Test: Can the computer contact its gateway using ping? Yes
Test: Can the computer contact the server using tracert? No
Step 2: Complete Steps 2 to 5 from Part 1 for this problem.
ipv6config /all
ping Default Gateway (berhasil)
trace route Server (Gagal)

Solusi yang mungkin adalah mencocokkan konfigurasi Server sesuai addressing table. Setelah dilakukan
pengecekan, ternyata IPv6 Gateway dari server tidaklah sesuai, sehingga harus diganti menjadi FE80::A.
Setelah itu, barulah masalah gagal melakukan FTP terselesaikan.

very valuable.
Solusi dari permasalahan ini adalah mengganti IPv6 Gateway pada DualStackServer.pka sesuai dengan
addressing table, yaitu FE80::A
Part 3: Troubleshoot Third Issue

A customer using PC1 complains that he cannot communicate with PC2.

The help desk collected the following information from the user over the phone. Verify that it is correct.
Help Desk Ticket

Issue: Unable to communicate with PC2.
Detail information about the Issue
Test: Does the computer have an IP address using ipconfig? Yes
Test: Does computer have an IPv6 address using ipv6config? Yes
Test: Can the computer contact its IPv4 gateway using ping? No
Test: Can the computer contact its IPv6 gateway using ping? Yes
Test: Can the computer contact the IPv4 client using tracert? No
Test: Can the computer contact the IPv6 client using tracert? Yes
Step 2: Complete Steps 2 to 5 from Part 1 for this problem.
ipconfig /all
ipv6config /all
ping gateway IPv4 (gagal)
ping gateway IPv6 (berhasil)

trace route IPv4 dengan PC2 (gagal)
trace route IPv6 dengan PC2 (berhasil)
Permasalahan kasus ini terletak pada konfigurasi IPv4 dari kedua host. Solusi yang mungkin:
Melakukan konfigurasi IPv4 dari PC2 dan PC3 sesuai addressing table
Melakukan konfigurasi Router sesuai addressing table
Melakukan konfigurasi IPv4 dari PC2, PC3, dan Router sesuai kebutuhan
Setelah dilakukan pengecekan, ternyata Default Gateway PC2 tidak sesuai addressing table, sehingga perlu diubah
menjadi 192.168.0.1. IPv4 dari PC3 adalah 192.168.1.2, dengan Default Gateway 192.168.1.1 dan subnet mask
255.255.255.0. Pada addressing table, interface Router pada G0/2 yang terhubung dengan PC3 juga tidak memiliki
konfigurasi apapun, sehingga Router perlu diatur pengalamatan IPv4-nya.
Setelah itu, barulah PC3 dapat berkomunikasi dengan PC3, dalam hal ini melalui ping dan trace route

very valuable.
Solusi utama dari permasalahan ini adalah mengisikan Default Gateway pada PC 2 sesuai addressing
table, yaitu 192.168.0.1 dan konfigurasi Router R1 dengan IP address yang merupakan Default
Gateway PC 3. Pada PC 3, IP Address diatur menjadi 192.168.1.2 dengan Default Gateway
192.168.1.1. Oleh karena itu, pada router juga perlu diatur IP Address pada interface yang terhubung
dengan PC 3 (G0/2), yaitu 192.168.1.1 dengan subnet mask 255.255.255.0. Dengan ini, komunikasi
antara PC 2 dan PC 3 dapat dilakukan.
Lab Calculating IPv4 Subnets

Objectives
Part 1: Determine IPv4 Address Subnetting
Determine the network address.
Determine the broadcast address.
Determine the number of hosts.
Part 2: Calculate IPv4 Address Subnetting
Determine the number of subnets created.
Determine number of hosts per subnet.
Determine the subnet address.
Determine the host range for the subnet.
Determine the broadcast address for the subnet.
Background / Scenario
The ability to work with IPv4 subnets and determine network and host information based on a given IP
address and subnet mask is critical to understanding how IPv4 networks operate. The first part is designed to
reinforce how to compute network IP address information from a given IP address and subnet mask. When
given an IP address and subnet mask, you will be able to determine other information about the subnet such
as:
Network address
Broadcast address
Total number of host bits
Number of hosts per subnet
In the second part of the lab, for a given IP address and subnet mask, you will determine such information as
follows:
Network address of this subnet
Broadcast address of this subnet
Range of host addresses for this subnet
Number of subnets created
Number of hosts for each subnet
Required Resources
1 PC (Windows 7, Vista, or XP with Internet access)
Optional: IPv4 address calculator
Part 1: Determine IPv4 Address Subnetting

In Part 1, you will determine the network and broadcast addresses, as well as the number of hosts, given an
IPv4 address and subnet mask.
REVIEW: To determine the network address, perform binary ANDing on the IPv4 address using the subnet
mask provided. The result will be the network address. Hint: If the subnet mask has decimal value 255 in an
octet, the result will ALWAYS be the original value of that octet. If the subnet mask has decimal value 0 in an
octet, the result will ALWAYS be 0 for that octet.
Example:
IP Address 192.168.10.10
Subnet Mask 255.255.255.0
==========
Result (Network) 192.168.10.0
Knowing this, you may only have to perform binary ANDing on an octet that does not have 255 or 0 in its
subnet mask portion.
Example:
IP Address 172.30.239.145
Analyzing this example, you can see that you only have to perform binary ANDing on the third octet. The first
two octets will result in 172.30 due to the subnet mask. The fourth octet will result in 0 due to the subnet
mask.
IP Address 172.30.239.145
==========
Result (Network) 172.30.?.0
Perform binary ANDing on the third octet.
Decimal Binary
239 11101111
192 11000000
=======
Result 192 11000000
Analyzing this example again produces the following result:
IP Address 172.30.239.145
==========
Result (Network) 172.30.192.0
Continuing with this example, determining the number of hosts per network can be calculated by analyzing
the subnet mask. The subnet mask will be represented in dotted decimal format, such as 255.255.192.0, or in
network prefix format, such as /18. An IPv4 address always has 32 bits. Subtracting the number of bits used
for the network portion (as represented by the subnet mask) gives you the number of bits used for hosts.
Using our example above, the subnet mask 255.255.192.0 is equivalent to /18 in prefix notation. Subtracting
18 network bits from 32 bits results in 14 bits left for the host portion. From there, it is a simple calculation:
(number of host bits)
2 - 2 = Number of hosts
14
2 = 16,384 2 = 16,382 hosts
Determine the network and broadcast addresses and number of host bits and hosts for the given IPv4
addresses and prefixes in the following table.
IPv4 Total Number Total Number

Address/Prefix Network Address Broadcast Address of Host Bits of Hosts
192.168.100.25/28 192.168.100.16 192.168.100.31 4 14

172.30.10.130/30 172.30.10.128 172.30.10.131 2 2
10.1.113.75/19 10.1.96.0 10.1.127.255 13 8190

198.133.219.250/24 198.133.219.0 198.133.219.255 8 254
128.107.14.191/22 128.107.12.0 128.107.15.255 10 1022

172.16.104.99/27 172.16.104.96 172.16.104.127 5 30
Part 2: Calculate IPv4 Address Subnetting

When given an IPv4 address, the original subnet mask and the new subnet mask, you will be able to
determine:
Network address of this subnet
Broadcast address of this subnet
Range of host addresses of this subnet
Number of subnets created
Number of hosts per subnet
The following example shows a sample problem along with the solution for solving this problem:
Given:
Host IP Address: 172.16.77.120

Original Subnet Mask 255.255.0.0
New Subnet Mask: 255.255.240.0
Find:
Number of Subnet Bits 4

Number of Subnets Created 16
Number of Host Bits per Subnet 12
Number of Hosts per Subnet 4,094
Network Address of this Subnet 172.16.64.0
IPv4 Address of First Host on this Subnet 172.16.64.1
IPv4 Address of Last Host on this Subnet 172.16.79.254
IPv4 Broadcast Address on this Subnet 172.16.79.255
Lets analyze how this table was completed.

The original subnet mask was 255.255.0.0 or /16. The new subnet mask is 255.255.240.0 or /20. The
resulting difference is 4 bits. Because 4 bits were borrowed, we can determine that 16 subnets were created
4
because 2 = 16.
The new mask of 255.255.240.0 or /20 leaves 12 bits for hosts. With 12 bits left for hosts, we use the
12
following formula: 2 = 4,096 2 = 4,094 hosts per subnet.
Binary ANDing will help you determine the subnet for this problem, which results in the network 172.16.64.0.
Finally, you need to determine the first host, last host, and broadcast address for each subnet. One method to
determine the host range is to use binary math for the host portion of the address. In our example, the last 12
bits of the address is the host portion. The first host would have all significant bits set to zero and the least
significant bit set to 1. The last host would have all significant bits set to 1 and the least significant bit set to 0.
rd th
In this example, the host portion of the address resides in the 3 and 4 octets.
st nd rd th
Description 1 Octet 2 Octet 3 Octet 4 Octet Description
Network/Host nnnnnnnn nnnnnnnn nnnnhhhh hhhhhhhh Subnet Mask
Binary 10101100 00010000 01000000 00000001 First Host
Decimal 172 16 64 1 First Host
Binary 10101100 00010000 01001111 11111110 Last Host
Decimal 172 16 79 254 Last Host
Binary 10101100 00010000 01001111 11111111 Broadcast
Decimal 172 16 79 255 Broadcast
Step 1: Fill out the tables below with appropriate answers given the IPv4 address, original
subnet mask, and new subnet mask.
a. Problem 1:
Given:

Find:
Number of Subnets Created 23 = 8
Number of Hosts per Subnet 25 2 = 30
b. Problem 2:
Given:

Find:

c. Problem 3:
Given:

Find:
d. Problem 4:
Given:

Find:

e. Problem 5:
Given:

Find:
f. Problem 6:
Given:

Find:
Reflection
Why is the subnet mask so important when analyzing an IPv4 address?
Subnet mask menentukan semua informasi mengenai alamat, jumlah bit host, jumlah host dan alamat
broadcast IPv4
Lab Subnetting Network Topologies

Objectives
Parts 1 to 5, for each network topology:
Determine the number of subnets.

Design an appropriate addressing scheme.
Assign addresses and subnet mask pairs to device interfaces.
Examine the use of the available network address space and future growth potential.
Background / Scenario
When given a network topology, it is important to be able to determine the number of subnets required. In this
lab, several scenario topologies will be provided, along with a base network address and mask. You will
subnet the network address and provide an IP addressing scheme that will accommodate the number of
subnets displayed in the topology diagram. You must determine the number of bits to borrow, the number of
hosts per subnet, and potential for growth as specified by the instructions.
Part 1: Network Topology A

In Part 1, you have been given the 192.168.10.0/24 network address to subnet, with the following topology.
Determine the number of networks needed and then design an appropriate addressing scheme.
Step 1: Determine the number of subnets in Network Topology A.

a. How many subnets are there? 2
b. How many bits should you borrow to create the required number of subnets? 1
c. How many usable host addresses per subnet are in this addressing scheme? 126
d. What is the new subnet mask in dotted decimal format? 255.255.255.128
e. How many subnets are available for future use? 0
Step 2: Record the subnet information.

Fill in the following table with the subnet information:
Subnet First Usable Host Last Usable Host Broadcast

Number Subnet Address Address Address Address
0 192.168.10.0 192.168.10.1 192.168.10.126 192.168.10.127

1 192.168.10.128 192.168.10.129 192.168.10.254 192.168.10.255
2
3
4
5
Part 2: Network Topology B

The network topology from Part 1 has expanded to accommodate the addition of router R3 and its
accompanying network, as illustrated in the following topology. Use the 192.168.10.0/24 network address to
provide addresses to the network devices, and then design a new addressing scheme to support the
additional network requirement.
Step 1: Determine the number of subnets in Network Topology B.



0 192.168.10.0 192.168.10.1 192.168.10.62 192.168.10.63

1 192.168.10.64 192.168.10.65 192.168.10.126 192.168.10.127
2 192.168.10.128 192.168.10.129 192.168.10.190 192.168.10.191
3 192.168.10.192 192.168.10.193 192.168.10.254 192.168.10.255
4
5
6
7
Part 3: Network Topology C

The topology has changed again with a new LAN added to R2 and a redundant link between R1 and R3. Use
the 192.168.10.0/24 network address to provide addresses to the network devices. Also provide an IP
address scheme that will accommodate these additional devices. For this topology, assign a subnet to each
network.
Step 1: Determine the number of subnets in Network Topology C.



0 192.168.10.0 192.168.10.1 192.168.10.30 192.168.10.31

1 192.168.10.32 192.168.10.33 192.168.10.62 192.168.10.63
2 192.168.10.64 192.168.10.65 192.168.10.94 192.168.10.95
3 192.168.10.96 192.168.10.97 192.168.10.126 192.168.10.127
4 192.168.10.128 192.168.10.129 192.168.10.158 192.168.10.159
5 192.168.10.160 192.168.10.161 192.168.10.190 192.168.10.191
6 192.168.10.192 192.168.10.193 192.168.10.222 192.168.10.223
7 192.168.10.224 192.168.10.225 192.168.10.254 192.168.10.255
8
9
10
Kuning = Future Use
Step 3: Assign addresses to network devices in the subnets.

a. Fill in the following table with IP addresses and subnet masks for the router interfaces:
Device Interface IP Address Subnet Mask
R1 GigabitEthernet 0/1 192.168.10.1 255.255.255.224

Serial 0/0/0 192.168.10.33 255.255.255.224
Serial 0/0/1 192.168.10.65 255.255.255.224
Serial 0/0/0 192.168.10.34 255.255.255.224
Serial 0/0/1 192.168.10.129 255.255.255.224
Serial 0/0/0 192.168.10.66 255.255.255.224
Serial 0/0/1 192.168.10.130 255.255.255.224
b. Fill in the following table with the IP addresses and subnet masks for devices in the LAN as displayed in
topology.
Device Interface IP Address Subnet Mask Default Gateway
PC-A NIC 192.168.10.30 255.255.255.224 192.168.10.1

PC-B NIC 192.168.10.29 255.255.255.224 192.168.10.1
S1 VLAN 1 192.168.10.2 255.255.255.224 192.168.10.1
PC-C NIC 192.168.10.126 255.255.255.224 192.168.10.97
PC-D NIC 192.168.10.125 255.255.255.224 192.168.10.97
S2 VLAN 1 192.168.10.98 255.255.255.224 192.168.10.97
PC-E NIC 192.168.10.190 255.255.255.224 192.168.10.161
PC-F NIC 192.168.10.189 255.255.255.224 192.168.10.161
S3 VLAN 1 192.168.10.162 255.255.255.224 192.168.10.161
Part 4: Network Topology D

The network was modified to accommodate changes in the organization. The 192.168.10.0/24 network
address is used to provide the addresses in the network.
Step 1: Determine the number of subnets in Network Topology D.


Fill in the following table with the subnet information.

0 192.168.10.0 192.168.10.1 192.168.10.14 192.168.10.15

1 192.168.10.16 192.168.10.17 192.168.10.30 192.168.10.31
2 192.168.10.32 192.168.10.33 192.168.10.46 192.168.10.47
3 192.168.10.48 192.168.10.49 192.168.10.62 192.168.10.63
4 192.168.10.64 192.168.10.65 192.168.10.78 192.168.10.79
5 192.168.10.80 192.168.10.81 192.168.10.94 192.168.10.95
6 192.168.10.96 192.168.10.97 192.168.10.110 192.168.10.111
7 192.168.10.112 192.168.10.113 192.168.10.126 192.168.10.127
8 192.168.10.128 192.168.10.129 192.168.10.142 192.168.10.143
9 192.168.10.144 192.168.10.145 192.168.10.158 192.168.10.159
10 192.168.10.160 192.168.10.161 192.168.10.174 192.168.10.175
11 192.168.10.176 192.168.10.177 192.168.10.190 192.168.10.191
12 192.168.10.192 192.168.10.193 192.168.10.206 192.168.10.207
13 192.168.10.208 192.168.10.209 192.168.10.222 192.168.10.223
14 192.168.10.224 192.168.10.225 192.168.10.238 192.168.10.239
15 192.168.10.240 192.168.10.241 192.168.10.254 192.168.10.255
16
17
Kuning = Future Use
Part 5: Network Topology E

The organization has a network address of 172.16.128.0/17 to be divided as illustrated in the following
topology. You must choose an addressing scheme that can accommodate the number of networks and hosts
in the topology.
Step 1: Determine the number of subnets in Network Topology E.



0 172.16.128.0 172.16.128.1 172.16.135.254 172.16.135.255

1 172.16.136.0 172.16.136.1 172.16.143.254 172.16.143.255
2 172.16.144.0 172.16.144.1 172.16.151.254 172.16.151.255
3 172.16.152.0 172.16.152.1 172.16.159.254 172.16.159.255
4 172.16.160.0 172.16.160.1 172.16.167.254 172.16.167.255
5 172.16.168.0 172.16.168.1 172.16.175.254 172.16.175.255
6 172.16.176.0 172.16.176.1 172.16.183.254 172.16.183.255
7 172.16.184.0 172.16.184.1 172.16.191.254 172.16.191.255
8 172.16.192.0 172.16.192.1 172.16.199.254 172.16.199.255
9 172.16.200.0 172.16.200.1 172.16.207.254 172.16.207.255
10 172.16.208.0 172.16.208.1 172.16.215.254 172.16.215.255
11 172.16.216.0 172.16.216.1 172.16.223.254 172.16.223.255
12 172.16.224.0 172.16.224.1 172.16.231.254 172.16.231.255
13 172.16.232.0 172.16.232.1 172.16.239.254 172.16.239.255
14 172.16.240.0 172.16.240.1 172.16.247.254 172.16.247.255
15 172.16.248.0 172.16.248.1 172.16.255.254 172.16.255.255
16
17
Kuning = Future Use
Step 3: Assign addresses to network devices in the subnets.

a. Fill in the following table with IP addresses and subnet masks for the router interfaces:
Device Interface IP Address Subnet Mask

GigabitEthernet 0/1 172.16.136.1 255.255.248.0
Serial 0/0/0 172.16.144.1 255.255.248.0
Serial 0/0/1 172.16.152.1 255.255.248.0
Serial 0/0/0 172.16.144.2 255.255.248.0
Serial 0/0/1 172.16.176.1 255.255.248.0
Serial 0/0/0 172.16.152.2 255.255.248.0
Serial 0/0/1 172.16.176.2 255.255.248.0
Reflection
1. What information is needed when determining an appropriate addressing scheme for a network?
Jumlah jaringan yang direncanakan serta jumlah host tiap jaringan.
2. After the subnets are assigned, will all the host addresses be utilized in each subnet?
Tidak, kita hanya mengatur perangkat host sesuai kebutuhan. Pada serial, 2 alamat digunakan. Pada PC host,
tiap alamat dapat digunakan di tiap subnet.

Vicky Burvi (15-379594-PA-16652)

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Vicky Burvi (15-379594-PA-16652)

Transféré par

Droits d'auteur :

Formats disponibles

LAPORAN EKSPERIMEN

LABORATORIUM ELEKTRONIKA DASAR DAN INSTRUMENTASI DASAR

Eth6 N/A Fa0/0

Part 1: Connect to the Cloud

Step 1: Connect the cloud to Router0.

Step 2: Connect the cloud to Cable Modem.

Part 2: Connect Router0

Step 1: Connect Router0 to Router1.

Step 2: Connect Router0 to netacad.pka.

Step 3: Connect Router0 to the Configuration Terminal.

Part 3: Connect Remaining Devices

Step 2: Connect Cable Modem to Wireless Router.

Step 3: Connect Wireless Router to Family PC.

Part 4: Verify Connections

b. Open the Web Browser and the web address http://netacad.pka.

Step 2: Ping the Switch from Home PC.

Step 3: Open Router0 from Configuration Terminal.

Part 5: Examine the Physical Topology

Step 2: Examine the Primary Network.

b. Click Back to return to Home City.

Step 3: Examine the Secondary Network.

b. Click Back to return to Home City.

Step 4: Examine the Home Network.

c. Click the Logical Workspace tab to return to the logical topology.

Suggested Scoring Rubric

Question Possible Earned

Part 5: Examine the Step 1c 4 4

Packet Tracer - Verifying IPv4 and IPv6 Addressing

10.10.1.97 255.255.255.224 N/A

Part 1: Complete the Addressing Table Documentation

Step 2: Use ipv6config to verify IPv6 addressing.

Part 2: Test Connectivity Using Ping

Step 2: Use ping to verify IPv6 connectivity.

Part 3: Discover the Path by Tracing the Route

What addresses were encountered along the path?

With which interfaces are the four addresses associated?

b. From PC2, trace the route to PC1.

What addresses were encountered along the path?

With which interfaces are the four addresses associated?

Step 2: Use tracert to discover the IPv6 path.

What addresses were encountered along the path?

With which interfaces are the four addresses associated?

b. From PC2, trace the route to the IPv6 address for

What addresses were encountered along the path?

With which interfaces are the four addresses associated?

Suggested Scoring Rubric

Question Possible Earned

Part 1: Complete the Step 1b 10 10

Packet Tracer - Troubleshooting IPv4 and IPv6 Addressing

G0/0 10.10.1.1 255.255.255.0 N/A

Dual Stack 64.100.1.254 255.255.255.0 64.100.1.1

Part 1: Troubleshoot First Issue

Step 1: Verify a detailed help desk ticket.

Help Desk Ticket

Client Identifier: PC1

Step 2: Consider probable causes for the failure.

ping Default Gateway:

Tampilan saat melakukan trace route server (berhasil)

Tampilan saat melakukan DNS lookup (gagal)

Step 3: Propose a solution to solve the problem.

Solusi yang mungkin:

Step 4: Implement the plan.

Step 5: Verify the solution resolved the problem.