The objective of this lab is to configure a network with multiple VLANs on one network, with each VLAN representing a different department (sales, marketing and accounting).
-- Setup --
Devices Needed: 1 router, 1 switch, 9 computers (3 for each VLAN).
Connections: Connect the switch to the router using an Ethernet cable. Connect each computer to a switch port.
-
Open Packet Tracer and locate the router, switch, and computers in the device list near the bottom.
-
Drag and drop the router, switch, and nine computers (CTRL + click the computer to add multiples) onto the workspace.
-
Use straight-through Ethernet cables to connect the switch to the router's Ethernet interface (usually labeled as GigabitEthernet0/0 or Gig0/0/0).
-
Connect each computer to a switch port.
-
Pictured below is the topology that we will be working with. I've decided to provide a background color so that each VLAN is representative of the differing departments on the switch.
-
-
We need to access the CLI on the Router to configure the different VLANS that we require. Select the
CLI
tab at the top once the router is chosen. -
While on the Router's CLI, enter global configuration mode by typing
enable
and thenconfigure terminal
. -
Create subinterfaces on the router's Ethernet interface for each VLAN.
-
Note: It's a logical interface created within a physical interface of a router. It allows the router to support multiple virtual LANs (VLANs) or subnets on a single physical interface. Subinterfaces are typically used when a router needs to connect to multiple networks, each with its own subnet or VLAN.
-
For VLAN 10 (accounting): --> Router(config)# interface gigabitethernet0/0.10
For VLAN 20 (sales): --> Router(config)# interface gigabitethernet0/0.20
For VLAN 30 (marketing): --> Router(config)# interface gigabitethernet0/0.30
- Enable dot1Q for the different VLANs.
- This encapsulation method allows the router to understand and process VLAN-tagged frames that are received on the trunk link from the switch.
For VLAN 10 (accounting): --> Router(config-if)#: encapsulation dot1Q 10
For VLAN 20 (sales): --> Router(config-if)#: encapsulation dot1Q 20
For VLAN 30 (marketing): --> Router(config-if)#: encapsulation dot1Q 30
- Assign an IP address to each subinterface within the respective VLAN range:
For VLAN 10 (accounting):--> Router(config-if)# ip address 192.168.10.1 255.255.255.192
VLAN 20 (sales): --> Router(config-if)# ip address 192.168.20.1 255.255.255.192
VLAN 30 (marketing): --> Router(config-if)# ip address 192.168.30.1 255.255.255.192
- While in interface gigabitethernet0/0 enable the interface by typing
no shutdown
and this while enable the subinterfaces as well.
- Click on the switch and select "CLI" to access its configuration mode.
- Create VLANs on the switch for sales, marketing, and accounting:
Switch(config)# vlan 10
Switch(config-vlan)# name Sales
Switch(config)# vlan 20
Switch(config-vlan)# name Accounting
Switch(config)# vlan 30
Switch(config-vlan)# name Marketing
Assign switch ports to the appropriate VLAN using the interface and switchport access vlan commands.
Switch(config)# interface range fastethernet0/1 - 3
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Repeat the above steps for VLANs 20 (fastethernet0/4-6) and 30 (fastethernet0/7-9), assigning ports to the corresponding VLANs.
We will need to setup trunking on the switch inteface that is connected to the router and for this instance I select fastehter0/11 on the switch
Switch(config)# interface fastethernet0/11
Switch(config-if)# switchport mode trunk
Switch(config-if)# switchport trunk allowed 10,20,30
Allowing VLANs 10, 20, and 30 across the trunk link connecting to the router enables traffic from these VLANs to traverse the link and reach the router. Specifically, configuring the switch port connected to the router as a trunk port. The trunk link connecting to the router enables efficient communication between devices in these VLANs and facilitates inter-VLAN routing, contributing to a well-segmented and organized network architecture.
-
Click on each computer and access its configuration panel.
-
Assign IP addresses to the computers within each VLAN:
For VLAN 10 (sales):
Computer 1: IP address: 192.168.1.2, Subnet mask: 255.255.255.192, Default gateway: 192.168.1.1
Computer 2: IP address: 192.168.1.3, Subnet mask: 255.255.255.192, Default gateway: 192.168.1.1
Computer 3: IP address: 192.168.1.4, Subnet mask: 255.255.255.192, Default gateway: 192.168.1.1
Repeat the above steps for VLANs 20 (start at 192.168.1.66) and 30 (start at192.168.1.130), assigning appropriate IP addresses to computers in each VLAN.
Computer 4: IP address: 192.168.1.66, Subnet mask: 255.255.255.192, Default gateway: 192.168.1.65
Computer 5: IP address: 192.168.1.67, Subnet mask: 255.255.255.192, Default gateway: 192.168.1.65
Computer 6: IP address: 192.168.1.68, Subnet mask: 255.255.255.192, Default gateway: 192.168.1.65
- Test connectivity between computers within the same VLAN using the ping and outside of the VLAN command.
- Ensure that computers in the same VLAN can communicate with each other.
- Use the show
ip route
command in router CLI to verify that the router has learned routes for each VLAN subnet.
![updated vlan topology](https://private-user-images.githubusercontent.com/23303634/309582426-bc24d8ce-8e99-4e10-9f0e-ad9005053aba.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ2MDIwODksIm5iZiI6MTcyNDYwMTc4OSwicGF0aCI6Ii8yMzMwMzYzNC8zMDk1ODI0MjYtYmMyNGQ4Y2UtOGU5OS00ZTEwLTlmMGUtYWQ5MDA1MDUzYWJhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI1VDE2MDMwOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNkNTZiYzRhZWMyMGZjZDM0YzZmMDM4OTllM2UxOWQ3YTY2MmQyZmM4NjU5ZjM0M2UwNzVjZWQ0ZWE4NGNjMDMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.vaSCzQAm__9zw8xcmJkUJDLU5Lkzx4uBcFIOz-KGexo)
In conclusion, the setup of the network with multiple VLANs has been successfully completed, demonstrating efficient communication within each department represented by VLANs. Through VLAN segmentation, we've effectively organized network traffic and enhanced security by restricting communication between departments. Overall, this project has underscored the importance of VLANs in network design and management, paving the way for optimized communication and security within our organization.