Lab 11 1: VLANs in Packet Tracer Part 1 - Hsanokklis/2022-2023-Tech-journal GitHub Wiki
Objective: Demonstrate understanding of VLAN uses and limitations and simple configuration of routing between VLANs
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
Doc Link
Configure Switchports for VLANs
1. On 1st Floor Switch, Go to Config/VLAN Database and add the VLANs to the switch
2. 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 is VLAN 10 (ENG)
- FastEthernet 0/2 is VLAN 20 (MKT)
- FastEthernet 0/3 is VLAN 30 (ACT)
IOS command to add a VLAN to the VLAN config is "vlan 30" and then "name ACT"
IOS command to switch to a certian ethernet is "interface FastEthernet0/3"
IOS command is "switchport access vlan 30" to configure the access port
3. 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)
IOS command to put it into trunk mode
4. Repeat 1-3 on 2nd Floor and 3rd Floor switches
- VLAN configuration for 2nd floor switch:
FastEthernet0/1, FastEthernet0/2, and FastEthernet0/3 have been configured with access VLAN ports and VLAN numbers 10,20, and 30
- GigabitEthernet0/1 and GigabitEthernet0/2 both configured with Trunk
- VLAN configuration for 3rd floor switch
_FastEthernet0/1, FastEthernet0/2, and FastEthernet0/3 have been configured with access VLAN ports
- GigabitEthernet0/1 configured with Trunk
Connect Devices
1. Assign Appropriate IP configurations to the PC's
ENG-PC3
ENG-PC2
ENG-PC1
MKT-PC3
MKT-PC2
MKT-PC1
ACT-PC3
ACT-PC2
ACT-PC1
2. Connect PC's to the switch on their floor.
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
TROUBLESHOOT my PCs could not ping each other on the VLANs and I could not figure out why, but I realized I didn't connect my switches with gigabit ports, I connected them with ethernet ports. I also didn't connect the correct ethernet ports to the correct switch ports, so I had to just reconnect them.
Machine Pinging
ENG-PC1 pinging ENG-PC2
MKT-PC2 pinging MKT-PC3
ACT-PC1 pinging ACT-PC3
Why can't PC's on different VLANs ping one another?
VLANs are designed to isolate and fragment devices on a network so devices on different VLANS cannot ping each other without being connected to a router.
What is Router on a Stick and how do you implement it?
Router on a Stick: A router on a stick is a router that has one physical connection to the network, which in the case of VLANs, can be used to allow VLANs to communicate with other VLANs
https://www.packettracerlab.com/router-on-a-stick-configuration/
Creating VLANs on a Switch:
- Go into the configuration section of the switch. Go to the VLAN database.
- Add the name and number of the VLAN you want to create.
Configuring an Interface as an Access Port:
- On each switch, assign the access port on a FastEthernet to a given VLAN
- That FastEthernet should be wired to the corresponding PC that is on the same VLAN.
Configuring an Interface as a Trunk Port:
- When configuring the switch or routers, there is one cable and the device will need to know about multiple VLANs.
- On a switch, configure the gigabit ethernet to be a trunk port with all of the VLANs selected.
- Do the same to all needed switches and routers.
Full network:
