INF321 Local Area Network Design – Assignment #1

Assignment topic - Implement VLANs and Trunking

Due Date: 13th June, 2024
Total Score: /100 (each part is worth 20 marks each)
Lab – Implement VLANs and Trunking
Background / Scenario

Modern switches use virtual local-area networks (VLANs) to improve network performance by
separating large Layer 2 broadcast domains into smaller ones. VLANs address scalability,
security, and network management. In general, VLANs make it easier to design a network to
support the goals of an organization. Communication between VLANs requires a device
operating at Layer 3 of the OSI model.

VLAN trunks are used to span VLANs across multiple devices. Trunks allow the traffic from
multiple VLANs to travel over a single link, while keeping the VLAN identification and
segmentation intact.

In this lab, you will create VLANs on both switches in the topology, assign VLANs to switch
access ports, verify that VLANs are working as expected and create VLAN trunks between the
two switches.

Note: The switches used with CCNA hands-on labs are Cisco Catalyst 2960s with Cisco IOS
Release 15.2(2) (lanbasek9 image). Other switches and Cisco IOS versions can be used.
Depending on the model and Cisco IOS version, the commands available and the output
produced might vary from what is shown in the labs. Refer to the Router Interface Summary
Table at the end of the lab for the correct interface identifiers.
Note: Ensure that the switches have been erased and have no startup configurations. If you are
unsure contact your instructor.

Required Resources

• 2 Switches (Cisco 2960 with Cisco IOS Release 15.2(2) lanbasek9 image or comparable)
• 2 PCs (Windows with a terminal emulation program, such as Tera Term)
• Console cables to configure the Cisco IOS devices via the console ports
• Ethernet cables as shown in the topology

Instructions
Part 1: Build the Network and Configure Basic Device Settings

In Part 1, you will set up the network topology and configure basic settings on the PC hosts and
switches.

Step 1: Cable the network as shown in the topology.

Attach the devices as shown in the topology diagram, and cable as necessary.

Step 2: Configure basic settings for each switch.

a. Console into the switch and enable privileged EXEC mode.

switch>

b. Assign a device name to each switch.

switch(config)#
switch(config)#

c. Disable DNS lookup.

S1(config)#

S2(config)#

d. Assign class as the privileged EXEC encrypted password.

S1(config)#

S2(config)#

e. Assign cisco as the console password and enable login.

S1(config)#
S1(config-line)#
S1(config-line)#
S2(config)#
S2(config-line)#
S2(config-line)#

f. Assign cisco as the VTY password and enable login.

S1(config)#
S1(config-line)#
S1(config-line)#

S2(config)#
S2(config-line)#
S2(config-line)#

g. Encrypt the plaintext passwords.

S1(config)#

S2(config)#

h. Create a banner that warns anyone accessing the device that unauthorized access is prohibited.

S1(config)#

S2(config)#

i. Copy the running configuration to the startup configuration.

S1#

S2#

Step 3: Configure PC hosts.

Refer to the Addressing Table for PC host address information.

Step 4: Test connectivity.

Verify that the PC hosts can ping one another.

Note: It may be necessary to disable the PCs firewall to ping between PCs.

Can PC-A ping PC-B?

Can PC-A ping S1?

Can PC-B ping S2?

Can S1 ping S2?

If you answered no to any of the above questions, why were the pings unsuccessful?

Part 2: Create VLANs and Assign Switch Ports

In Part 2, you will create Management, Sales, Operations, Parking_Lot, and Native VLANs on both
switches. You will then assign the VLANs to the appropriate interface. The show vlan command is used to
verify your configuration settings.Step 1: Create VLANs on both switches.

a. Create and name the required VLANs on each switch from the table above.

S1(config)# vlan 10
S1(config-vlan)# name Management
S1(config-vlan)# vlan 20
S1(config-vlan)# name Sales
S1(config-vlan)# vlan 30
S1(config-vlan)# name Operations
S1(config-vlan)# vlan 99
S1(config-vlan)# name ParkingLot
S1(config-vlan)# vlan 1000
S1(config-vlan)# name Native

Create the same VLANs for S2. Then issue the show vlan brief command to view
the list of VLANs on S1. Screenshot your output and paste in this answer
sheet then answer the following questions.

What is the default VLAN?

What ports are assigned to the default VLAN?

b. Configure the management interface on each switch using the IP address information in the
Addressing Table.

S1(config)#
S1(config-if)#
S1(config-if)#
S1(config-if)#
S1(config-if)#
S1(config-if)#
S2(config)#
S2(config-if)#

c. Assign all unused ports on the switch to the ParkingLot VLAN, configure them for static
access mode, and administratively deactivate them.

S1(config)#
S1(config-if-range)#
S1(config-if-range)#
S1(config-if-range)#

S2(config)#
S2(config-if-range)#
S2(config-if-range)#
S2(config-if-range)#

Step 2: Assign VLANs to the correct switch interfaces.

a. Assign used ports to the appropriate VLAN (specified in the VLAN table above) and
configure them for static access mode.

S1(config)#
S1(config-if)#
S1(config-if)#

S2(config)#
S2(config-if)#
S2(config-if)#

b. Verify that the VLANs are assigned to the correct interfaces.

S1# show vlan brief

VLAN Name Status Ports

--
1 default active Fa0/1
10 Management active
20 Sales active Fa0/6
30 Operations active
999 Parking_Lot active Fa0/2, Fa0/3, Fa0/4, Fa0/5
Fa0/7, Fa0/8, Fa0/9, Fa0/10

Fa0/11, Fa0/12, Fa0/13,

Fa0/14
Fa0/15, Fa0/16, Fa0/17,
Fa0/18
Fa0/19, Fa0/20, Fa0/21,
Fa0/22
Fa0/23, Fa0/24, Gi0/1, Gi0/2
1000 Native active
<output omitted>

S2# show vlan brief

VLAN Name Status Ports

--
1 default active Fa0/1
10 Management active
20 Sales active
30 Operations active Fa0/18
999 ParkingLot active Fa0/2, Fa0/3, Fa0/4, Fa0/5
Fa0/6, Fa0/7, Fa0/8, Fa0/9
Fa0/10, Fa0/11, Fa0/12,
Fa0/13
Fa0/14, Fa0/15, Fa0/16,
Fa0/17
Fa0/19, Fa0/20, Fa0/21,
Fa0/22
Fa0/23, Fa0/24, Gi0/1, Gi0/2
<output omitted>
Part 3: Configure an 802.1Q Trunk Between the Switches

In Part 3, you will manually configure interface F0/1 as a trunk.

Step 1: Manually configure trunk interface F0/1.

a. Change the switchport mode on interface F0/1 to force trunking. Make sure to do this on both
switches.

S1(config)#
S1(config-if)#

S2(config)#
S2(config-if)#

b. Set the native VLAN to 1000 on both switches.

S1(config-if)#

S2(config-if)#

c. As another part of trunk configuration, specify that only VLANs 10, 20, 30, and 1000 are
allowed to cross the trunk.

S1(config-if)#

S2(config-if)#

d. Issue the show interfaces trunk command to verify trunking ports, the native VLAN and
allowed VLANs across the trunk. You should be able to see the following output on your screen.

S1# show interfaces trunk

Port Mode Encapsulation Status Native vlan

Fa0/1 on 802.1q trunking 1000
Port Vlans allowed on trunk
Fa0/1 10,20,30,1000

Port Vlans allowed and active in management domain

Fa0/1 10,20,30,1000

Port Vlans in spanning tree forwarding state and not pruned

Fa0/1 10,20,30,1000

Step 2: Verify connectivity.

Verify connectivity within a VLAN. For example, PC-A should be able to ping S1 VLAN 20
successfully.

Were the pings from PC-B to S2 successful? Explain.

Device Configs – Final – issue the show run command to verify your entire configurations on both
switches, screenshot your output and paste in your answer sheet here.
Switch S1
S1# show run

Switch S2
S2# show run