#### Summary:
In this lab we created VLANs and showed how VLANs work. 

I had no issues while completing the lab

#### Summary of understanding:
- Why can't PC's on different VLANs ping one another?
	- Pcs on different vlans cant ping one another because the networks are virtually separated. It is like each is on its own switch.
- Determine the difference between Trunk and Access ports
	- A trunk port has multiple VLANs on it, whereas an access port has one, and is used for traffic to one device, where trunk ports are used for traffic to other trunk ports.

**Goals**:

- Demonstrate  need and impact of  VLANs on networks
- Recognize the distinction between logical and physical switching
- Determine the difference between Trunk and Access ports
- Configure a switch to support multiple VLANs
- Configure switch access ports
- Configure switch trunk ports

**Lab:** Using the starting [Packet Tracer File](https://champlain.instructure.com/courses/2682962/files/401278145/download?wrap=1 "Packet Tracer -NET150- VLAN-StarterFile.pkt")[Download Packet Tracer File](https://champlain.instructure.com/courses/2682962/files/401278145/download?download_frd=1), you will configure VLANs similar to our example slide:

![](https://champlain.instructure.com/courses/2682962/files/401278071/download?wrap=1)

**I. Configure Switchports for VLANs**

1. On 1st Floor Switch, Go to Config/VLAN Database and add the VLANs the switch will support:
    - VLAN Number: 10 Name: ENG
    - VLAN Number: 20 Name: MKT
    - VLAN Number: 30 Name: ACT
2. Then, configure which ports are in which VLAN from Config tab by changing the VLAN number for the Access Port configuration per interface
    - FastEthernet 0/1 can be VLAN 10 (ENG)
    - FastEthernet 0/2 can be VLAN 20 (MKT)
    - FastEthernet 0/3 can be VLAN 30 (ACT)
3. Then, configure the Trunk port that will be used to connect the switch to the 2nd Floor Switch
    - GigabitEthernet 0/1 change to Trunk and add VLANs 10, 20, and 30 (leaving the other default VLANs checked is fine)
4. Repeat 1-3 on 2nd Floor and 3rd Floor switches
    - **Note:** On 2nd Floor switch, you will need to configure both GigabitEthernet 0/1 and Gigabit/Ethernet 0/2 as Trunk ports (step 3) as it connects to two switches

**II. Connect Devices**

1. Assign Appropriate IP configurations to the PC's
    - ENG network is 192.168.10.0/24 and the default gateway will be 192.168.10.1
    - MKT network is 192.168.20.0/24 and the default gateway will be 192.168.20.1
    - ACT network is 192.168.30.0/24 and the default gateway will be 192.168.30.1
    - Remember, every PC needs a unique address
2. Connect PC's to the switch on their floor.
    - **Make sure to connect the PC to the Port on the switch that is in their VLAN!**
3. Connect switches to each other using **Crossover Cables**  and the configured Trunk ports
4. If everything is connected and addressed correctly
    - All PC's on the same VLAN should be able to ping each other
    - But, PC's on different VLANs (even on the same switch) should not be able to ping
5. **At this point, All PC's on the same VLAN should ping one another - BUT PC's on different VLANs should not be able to ping one another**

**SUBMIT:**

- Screenshot of ENG-PC1 pinging ENG-PC2 (2 Points)
- Screenshot of MKT-PC2 pinging MKT-PC3 (2 Points)
- Screenshot of ACT-PC1 pinging ACT-PC3 (2 Points)
![[Pasted image 20261108205810.png]]
- Answer to question: Why can't PC's on different VLANs ping one another? (3 Points)
	- Pcs on different vlans cant ping one another because the networks are virtually separated. It is like each is on its own switch.
