Scribd
Upload
593 views5 pages

CMIT 351 Project 2 Giri

Uploaded by

Sri Giri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
593 views5 pages

CMIT 351 Project 2 Giri

Uploaded by

Sri Giri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Version 2.

CMIT 351 Project 2 Template

Please input the following correctly in the PKA when the PKA file is opened as shown
below:

A starter network with labeled devices on the screen is presented already without them
connected when you open the PKA file.

After the completion of your configuration in the PKA answer the following items:

1. Test and validate connectivity following the instructions and explain why connectivity tests
work or fail. (2.5% of total)

After connecting all the hosts to switch and switch to the router, Configure the switch and
router. Set up all the host's IP addresses, gateway, and subnet. I test ping to all hosts to each
other. Found connectionless. VLAN and interfaces are not defined and VLAN was not trunking.
Thus was failing to connectivity among each other.
Version 2.0

After Defining VLANS, interfaces, and implementing VLAN trunking, ping testing this time
showed that PC-A, PC-B, and PC-C are connecting to each other, but PC-D's attempts to
establish a network connection with PC-A, PC-B, PC-C, and R1 are unsuccessful due to PC-
D's configuration to use VLAN 99 port 13 on Switch S1. Nevertheless, VLAN 99 is not set
up as a sub-interface of R1-fa0/1. Consequently, Router R1 is unable to receive packets
transmitted by PC-D via VLAN 99 on Switch S1. The absence of a link between VLAN 99
on Switch S1 and Router R1, which acts as the LAN's default gateway and enables routing
between VLANs, is the reason for this.

To get the 2.5% you are required to use the PC command line to run ping tests for
connectivity and paste screenshots of the connectivity tests you ran on the PCs in the PKA
after configuration HERE.
Note & Pro Tip: This Packet Tracer Activity has built in connectivity tests that will run once
you complete it and show the status and count towards the completion score. Once you have
completely configured everything correctly, it will take a minute or two to reach from 97% to
100% as the connectivity tests which are part of the assessment now run periodically and
Version 2.0

once, they run, it will reach 100%. Also, if you save the completed PKA and re-open it,
you will see it at 97% but after a minute or two it will reach 100% and if does not reach
100% click on “Check Results” button and that will force the connectivity tests to run
and it will reach 100%

2. Describe how you test and validate the VLAN implementation. Do NOT just paste switch
configuration but describe in words the commands you may use and why. (2.5% of total)

VLAN implementation can be tested and validated in numerous ways. VLAN formation and
configuration must be verified first. Access the switch's configuration interface using the
GUI or CLI.

Enter privileged EXEC mode with "enable" in the CLI, then global configuration mode with
"configure terminal." Next, build VLANs using "vlan <VLAN_ID>" command, where
<VLAN_ID> = desired VLAN number. To name VLANs, use the "name <VLAN_NAME>"
command.

To establish connectivity, assign access ports to VLANs using "interface <interface_id>" and
"switchport mode access" and "switchport access vlan <VLAN_ID>" commands. This
associates the interface with the VLAN and puts it in access mode.

Finally, activate VLANs with "no shutdown". VLANs are enabled and traffic flows via them.
Version 2.0

These stages allow VLAN installation to be verified and certified for network setup and
functionality.

3. Describe how you test and validate the sub-interface implementations. Do NOT just paste
router/switch configuration but describe in words the commands you may use and why.
(2.5% of total)

After configuring and assigning IP addresses to sub-interfaces for their subnets, check their
encapsulation type. Sub-interface VLAN IDs should match those on connected switches and
devices. Check that devices linked to sub-interfaces have proper IP configurations in their
subnets.

Next, ping 192.168.20.4 from PC-A to test connection from subnet 10 to subnet 20. Use
"show ip route" to check the router's routing table for accurate subnet entries and connected
subnets.

Finally, use "show interfaces" to verify sub-interfaces' uptime and IP addresses.

These methods ensure correct network segmentation and subnet communication by testing
and validating router sub-interface implementations in Packet Tracer.
Version 2.0

4. Describe how you test and validate the VLAN Trunking implementation. Do NOT just paste
router/switch configuration but describe in words the commands you may use and why.
(2.5% of total)
Validate the VLAN settings on both the Switch and router to confirm they are in agreement.
Verify that the VLANs on both ends of the trunk links are identical and that they are set up to
function as trunk links. Verify that the permitted VLANs are consistent on both ends and ensure
that ports are accurately allocated to their corresponding VLANs.

After the router has completed inter-VLAN routing, it is important to conduct testing to verify
that communication between devices in different VLANs is functioning properly. Utilize packet
capture tools to examine VLAN tags on trunk links and detect any discrepancies in VLAN
configuration, such as absent VLANs or inconsistent VLAN IDs.

Conduct connectivity testing between devices within the same VLAN and across separate
VLANs to confirm correct communication. Monitor the switch logs and alerts to detect any
issues linked to VLANs, and provide analysis and information about probable faults or
misconfigurations.

Consistent testing and validation of VLAN Trunking provide a stable and secure network
environment, facilitating the fast identification and resolution of any issues to minimize
disruptions to network services.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy