Objectives Upon completion of this exercise, you will be able to:
• Cable a network according to the topology diagram
• Erase the startup configuration and reload a switch to the default state
• Perform basic configuration tasks on a switch
• Create VLANs
• Assign switch ports to a VLAN
• Add, move, and change ports
• Verify VLAN configuration
• Enable trunking on inter-switch connections
• Verify trunk configuration
• Save the VLAN configuration
Task 1: Prepare the Network
Step 1: Cable a network that is similar to the one in the topology diagram.
You can use any current switch in packet tracer as long as it has the required interfaces shown in the topology.
Step 2: Clear any existing configurations on the switches (S2 and S3), and initialize all ports in the shutdown
Procedure to clear switch configurations.
Switch#delete flash:vlan.dat @ delete vlan.dat
Delete filename [vlan.dat]? [Press Enter Key]
Delete flash:vlan.dat? [confirm] [ Reconfirm by pressing enter key]
Switch#erase startup-config @ erase start
It is a good practice to disable any unused ports on the switches by putting them in shutdown. Disable all
ports on the switches:
Switch(config)#interface range fa0/1-24
Switch(config-if-range)#interface range gi0/1-2
Task 2: Perform Basic Switch Configurations
Step 1: Configure the switches according to the following guidelines.
• Configure the switch hostname.
• Configure Banner Motd
We’ll start with the message of the day banner that will be presented to anyone accessing the router:
S1(config)#banner motd “Authorized users only, violators will be shot on sight!”
• Disable DNS lookup
S1(config)#no ip domain-lookup
• Configure an EXEC mode password of class.
Why is it not necessary to use the enable password class command? Because the enable secret is a more secure password to use on the router or switch.
R1(config)#enable secret class
• Configure a password of cisco for console connections.
S1(config)#line console 0
First, I use the password command to set a password. I also need to supply the login
command otherwise the switch will not ask for the password.
• Configure a password of cisco for vty connections.
A switch or router has several virtual lines that you can use for remote access. These
are called VTY (Virtual Terminal) lines. I can configure these using the line vty command.
In my example, I’m selecting VTY line 0 up to 4 so that‟s 5 virtual lines total.
S1(config)#line vty 0 4
Noted: The configuration on S2 and S3 follow Step 1
Step 2: Re-enable the use of ports on S2 and S3.
S2(config-if-range)#int range fa0/6, fa0/11, fa0/18
S2(config-if-range)#switchport mode access
S3(config-if-range)#int range fa0/6, fa0/11, fa0/18
S3(config-if-range)#switchport mode access
Task 3: Configure and Activate Ethernet Interfaces
Step 1: Configure the PCs.
You can complete this exercise by configuring six PCs. Each VLAN will be assigned 2 PCs. Refer to the table above for PCs configuration.
Task 4: Configure VLANs on the Switch
Step 1: Create VLANs on switch S1.
Use the VLAN vlan-id command in global configuration mode to add a VLAN to switch S1. There are four VLANS configured for this lab: VLAN 10 (faculty/staff); VLAN 20 (students); VLAN 30 (guest); and VLAN 99 (management). After you create the VLAN, you will be in VLAN configuration mode, where you can assign a name to the VLAN with the name vlan name command.
Step 2: Verify that the VLANs have been created on S1.
Use the show vlan brief command to verify that the VLANs have been created.
S1#show vlan brief
VLAN Name Status Ports
1 default active Fa0/1, 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/18, Fa0/19, Fa0/20
Fa0/21, Fa0/22, Fa0/23, Fa0/24
10 faculty/staff active
20 students active
30 guest active
99 management active
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active
Step 3: Configure and name VLANs on switches S2 and S3.
Create and name VLANs 10, 20, 30, and 99 on S2 and S3 using the commands from Step 1. Verify the
correct configuration with the show vlan brief command.
Step 4: Assign switch ports to VLANs on S2 and S3.
Refer to the port assignment table on page 1. Ports are assigned to VLANs in interface configuration mode, using the switchport access vlan vlan-id command. You can assign each port individually or you can use the interface range command to simplify this task, as shown here. The commands are shown for S3 only, but you should configure both S2 and S3 similarly. Save your configuration when done.
S3(config)#int range fa0/6-10
S3(config-if-range)#switchport access vlan 30
S3(config-if-range)#int range fa0/11-17
S3(config-if-range)#switchport access vlan 10
S3(config-if-range)#int range fa0/18-24
S3(config-if-range)#switchport access vlan 20
Step 4: Determine which ports have been added.
Use the show vlan id vlan-number command on S2 to see which ports are assigned to VLAN 10.
Which ports are assigned to VLAN 10?
Ans: Fa0/11, Fa0/12, Fa0/13, Fa0/14, Fa0/15, Fa0/16, Fa0/17
Note: The show vlan id vlan-name displays the same output.
You can also view VLAN assignment information using the show interfaces interface switchport command.
Step 5: Assign the management VLAN.
A management VLAN is any VLAN that you configure to access the management capabilities of a switch. VLAN 1 serves as the management VLAN if you did not specifically define another VLAN. You assign the management VLAN an IP address and subnet mask. A switch can be managed via HTTP, Telnet, SSH, or SNMP. Because the out-of-the-box configuration of a Cisco switch has VLAN 1 as the default VLAN, VLAN 1 is a bad choice as the management VLAN. You do not want an arbitrary user who is connecting to a switch to default to the management VLAN. Recall that you configured the management VLAN as VLAN 99 earlier in this lab.
From interface configuration mode, use the ip address command to assign the management IP address
S1(config)#int vlan 99
S1(config-if)#ip add 172.17.99.11 255.255.255.0
S2(config)#int vlan 99
S2(config-if)#ip add 172.17.99.12 255.255.255.0
S3(config)#int vlan 99
S3(config-if)#ip add 172.17.99.13 255.255.255.0
Assigning a management address allows IP communication between the switches, and also allows any host connected to a port assigned to VLAN 99 to connect to the switches. Because VLAN 99 is configured as the management VLAN, any ports assigned to this VLAN are considered management ports and should be secured to control which devices can connect to these ports.
Step 6: Configure trunking and the native VLAN for the trunking ports on all switches.
Trunks are connections between the switches that allow the switches to exchange information for all VLANS. By default, a trunk port belongs to all VLANs, as opposed to an access port, which can only belong to a single VLAN. If the switch supports both ISL and 802.1Q VLAN encapsulation, the trunks must specify which method is being used. Because the 2960 switch only supports 802.1Q trunking, it is not specified in this lab.
A native VLAN is assigned to an 802.1Q trunk port. In the topology, the native VLAN is VLAN 99. An 802.1Q trunk port supports traffic coming from many VLANs (tagged traffic) as well as traffic that does not come from a VLAN (untagged traffic). The 802.1Q trunk port places untagged traffic on the native VLAN.
Untagged traffic is generated by a computer attached to a switch port that is configured with the native VLAN. One of the IEEE 802.1Q specifications for Native VLANs is to maintain backward compatibility with untagged traffic common to legacy LAN scenarios. For the purposes of this lab, a native VLAN serves as a common identifier on opposing ends of a trunk link. It is a best practice to use a VLAN other than VLAN 1 as the native VLAN.
Use the interface range command in global configuration mode to simplify configuring trunking.
S1(config-if-range)#int range fa0/1-5
S1(config-if-range)#switchport mode trunk
S1(config-if-range)#switchport trunk native vlan 99
S2(config)#int range fa0/1-5
S2(config-if-range)#switchport mode trunk
S2(config-if-range)#switchport trunk native vlan 99
S3(config)#int range fa0/1-5
S3(config-if-range)#switchport mode trunk
S3(config-if-range)#switchport trunk native vlan 99
Verify that the trunks have been configured with the show interface trunk command.
S1(config-if-range)#do show interface trunk
Port Mode Encapsulation Status Native vlan
Fa0/1 on 802.1q trunking 99
Port Vlans allowed on trunk
Port Vlans allowed and active in management domain
Port Vlans in spanning tree forwarding state and not pruned
Port Vlans in spanning tree forwarding state and not pruned
Step 7: Verify that the switches can communicate.
From S1, ping the management address on both S2 and S3.
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.17.99.12, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/9 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.17.99.13, timeout is 2 seconds:
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms
Step 8: Ping several hosts from PC2.
Ping from host PC2 to host PC1 (172.17.10.21). Is the ping attempt successful?
Ping from host PC2 to the switch VLAN 99 IP address 172.17.99.12. Is the ping attempt successful?
Because these hosts are on different subnets and in different VLANs, they cannot communicate without a Layer 3 device to route between the separate subnetworks.
Ping from host PC2 to host PC5. Is the ping attempt successful?
Because PC2 is in the same VLAN and the same subnet as PC5, the ping is successful.
Step 9: Move PC1 into the same VLAN as PC2.
The port connected to PC2 (S2 Fa0/18) is assigned to VLAN 20, and the port connected to PC1 (S2 Fa0/11) is assigned to VLAN 10. Reassign the S2 Fa0/11 port to VLAN 20. You do not need to first remove a port from a VLAN to change its VLAN membership. After you reassign a port to a new VLAN, that port is automatically removed from its previous VLAN.
Enter configuration commands, one per line. End with CNTL/Z.
S2(config)#interface fastethernet 0/11
S2(config-if)#switchport access vlan 20
Ping from host PC2 to host PC1. Is the ping attempt successful?
Even though the ports used by PC1 and PC2 are in the same VLAN, they are still in different
subnetworks, so they cannot communicate directly.