CCNA Layer 2 Switching - VLANs Lab Scenario

CertificationZone Page 1 of 17
http://www.certificationzone.com/studyguides.../?Issue=34&IssueDate=04-01-2001&CP= 11/06/01
Date of Issue: 04-01-2001
CCNA Layer 2 Switching - Virtual Local
Area Networks
Lab Scenario
by Leigh Anne Chisholm
Introduction
Preparing Your Switches
Section 1 - Configuring VLAN Trunk Protocol (VTP)
Section 2 - Creating VLANs
Section 3 - Verifying VLAN Functionality
Section 4 - Configuring an ISL Trunk Link
Section 5 - More VTP Configuration
Section 6 - Viewing Spanning Tree Protocol Information
Section 7 - Configuring ISL Routing
The VLAN Wrap-Up
Introduction
This lab is designed to walk you through a basic VLAN configuration using two Catalyst 1900 (or 2820) series
switches.
This lab shows you step-by-step what commands to type in and how to check that you have configured things
correctly. Each switch must be configured with the Enterprise edition software. The Cisco IOS software CLI is not
available if the switch has been configured with the Standard edition software.
While it is possible to complete most of this lab using a single Catalyst 1900/2820 series switch, a second Catalyst
1900/2820 series switch (or Cisco switch that supports ISL) is required to complete Section 4, "Configuring an ISL
Trunk Link."
Section 3, "Verifying VLAN Functionality" and Section 4, "Configuring an ISL Trunk Link," require access to two PCs
that can be connected directly to the switch ports of the primary switch that you will use for the lab. To successfully
complete these sections, you must be able to alter the IP address configuration information on each of these PCs.
To complete Section 4, "Configuring an ISL Trunk Link," you need one crossover cable to connect the switches.
Section 7, "Configuring ISL Routing," requires access to a Cisco router that supports ISL trunking and that is
equipped with a FastEthernet port.
Preparing Your Switches
Processes currently executing on the Catalyst switches involved in
this lab may interfere with the expected outcome from each section
of this lab. Therefore, it is recommended you begin working
through these labs only after resetting the configuration of each
switch to the factory defaults. To complete this process, issue the
privileged exec mode command delete nvram on each switch.
Once you have restored the settings on your switches to their
original configuration, establish a console connection with each switch. You should see the following menu:
1 user(s) now active on Management Console.
User Interface Menu
[M] Menus
IMPORTANT! Ensure you have the capability
of configuring each switch via the console port
prior to resetting the switch to its factory
defaults. All configuration information
including IP address assignment and IP
default gateway will be reset. You will be
unable to telnet to your switches.
[K] Command Line
[I] IP Configuration
[P] Console Password
Enter Selection:
Set up the switches using the following configuration information:
If you do not require step-by-step information on how to complete this process, then proceed to Section 1,
"Configuring VLAN Trunk Protocol (VTP)."
To configure the Primary Catalyst switch:
1. From the "User Interface Menu", select option "[K] Command Line".
A ">" prompt will be displayed, indicating you have entered the user exec mode of the switch.
2. Enter privileged exec mode by issuing the command
enable
A "# "prompt will be displayed.
3. To begin configuring the switch name, IP information, and password; enter global configuration mode by
issuing the command
configure terminal
The prompt "(config)#" will be displayed, indicating that you have entered global configuration mode.
4. To set the name of the switch to "SwitchA," issue the command
hostname SwitchA
You will notice that the prompt now displays the name of the switch as well as the global configuration mode
prompt: "SwitchA(config)#."
5. To set the IP address and subnet mask for the switch, issue the command
ip address 172.16.1.200 255.255.255.0
6. To set the default gateway for the switch, issue the command
ip default-gateway 172.16.1.1
7. To set the enable password to "secret," issue the command
enable secret secret
Primary Switch:
Switch Name: SwitchA
IP Address: 172.16.1.200
Subnet Mask: 255.255.255.0
Default Gateway: 172.16.1.1
Enable Password: secret
Secondary Switch:
Switch Name: SwitchB
IP Address: 172.16.1.201
Subnet Mask: 255.255.255.0
Enable Password: secret
8. To end the configuration process, type exit.
9. Confirm your configuration by issuing the command show running-config. You should see only:
the hostname of the switch (SwitchA)
IP address and default gateway information (ip address 172.16.1.200 255.255.255.0, ip default-
gateway 172.16.1.1)
privileged exec mode password encrypted (enable secret 5 $1$FMFQ$6meDTvWbwHZeuIPKLt7Rh/)
each individual interface on your switch (Ethernet 0/1 through 0/27)
"line console"
There should not be any configuration information under the Ethernet interfaces nor line console.
Repeat this procedure on SwitchB, substituting the appropriate values for configuring the switch.
Once you have completed configuring SwitchB, you are ready to begin working through the basic VLAN configuration
of this lab.
Section 1 - Configuring VLAN Trunk Protocol (VTP)
In this section, you will set SwitchA to operate in VTP transparent mode.
Recall that once a switch has been configured with a VTP domain name, its default mode of operation is that of VTP
server. In order to ensure that this information is not propagated throughout the network, the VTP mode must be set
to transparent before a VTP domain name is assigned.
Begin this part of the lab by configuring SwitchA.
1. On SwitchA, enter global configuration mode from the privileged exec mode prompt by issuing the command
configure terminal
The prompt "SwitchA(config)#" will be displayed, indicating that you have entered global configuration mode.
2. To set the VTP mode to transparent, issue the command
vtp transparent
3. To set the VTP domain name to "CertZone," issue the command
vtp domain CertZone
5. Confirm your configuration by issuing the command
show vtp
You should see the following output:
SwitchA#show vtp
VTP version: 1
Configuration revision: 0
Maximum VLANs supported locally: 1005
Number of existing VLANs: 6
VTP domain name : CertZone
VTP password :
VTP operating mode : Transparent
VTP pruning mode : Disabled
VTP traps generation : Enabled
Configuration last modified by: 172.16.1.200 at 00-00-0000 00:00:00
SwitchA#
6. Optional: Issue the command
show vtp ?
Note that the only keyword available with the show vtp command is "statistics".
show vtp statistics
SwitchA#show vtp statistics
Receive Statistics Transmit Statistics
-------------------------------- -------------------------------
Summary Adverts 0 Summary Adverts 0
Subset Adverts 0 Subset Adverts 0
Advert Requests 0 Advert Requests 0
Configuration Errors:
Revision Errors 0
Digest Errors 0
VTP Pruning Statistics:
Port Join Received Join Transmitted Summary Adverts received
with no pruning support
---- ------------- ---------------- ------------------------
A 0 0 0
B 0 0 0
SwitchA#
If the switch were operating in a mode other than VTP transparent, these counters would increment according
to the information transmitted/received. If a switch were operating as a VTP client, it would be expected that
"Transmit Statistics" counters would not increment since the switch would be set up to only receive VTP
information but not to transmit it.
8. Optional: On SwitchB, issue the command
show vtp
SwitchB#show vtp
VTP version: 1
VTP domain name :
VTP password :
VTP operating mode : Server
SwitchB#
SwitchB has not received any VTP information from SwitchA (which is to be expected).
Note that SwitchB's VTP operating mode is set to "Server." Recall that once a Catalyst 1900 series switch is
configured with a VTP domain name, its default VTP mode of operation is "Server."
Section 2 - Creating VLANs
In this section, you will create three VLANs: Engineering, Marketing, and Production. Once these VLANs have been
created, you will assign two ports to each VLAN using the static membership configuration option.
Begin this part of the lab by configuring SwitchA.
1. On SwitchA, enter global configuration mode from the privileged exec mode prompt by issuing the command
configure terminal
The prompt "SwitchA(config)#" will be displayed, indicating you have entered global configuration mode.
2. To create VLAN 2 - Engineering, issue the command
vlan 2 name Engineering
Note: When typing in the names of VLANs, remember that name information is case sensitive.
3. To create VLAN 3 - Marketing, issue the command
vlan 3 name Marketing
4. To create VLAN 4 - Production, issue the command
vlan 4 name Production
show vlan
SwitchA#show vlan
VLAN Name Status Ports
--------------------------------------
1 default Enabled 1-24, AUI, A, B
2 Engineering Enabled
3 Marketing Enabled
4 Production Enabled
1002 fddi-default Suspended
1003 token-ring-defau Suspended
1004 fddinet-default Suspended
1005 trnet-default Suspended
--------------------------------------
VLAN Type SAID MTU Parent RingNo BridgeNo Stp Trans1 Trans2
---------------------------------------------------------------------------
1 Ethernet 100001 1500 0 0 0 Unkn 1002 1003
2 Ethernet 100002 1500 0 1 1 Unkn 0 0
3 Ethernet 100003 1500 0 1 1 Unkn 0 0
4 Ethernet 100004 1500 0 1 1 Unkn 0 0
1002 FDDI 101002 1500 0 0 0 Unkn 1 1003
1003 Token-Ring 101003 1500 1005 1 0 Unkn 1 1002
1004 FDDI-Net 101004 1500 0 0 1 IEEE 0 0
1005 Token-Ring-Net 101005 1500 0 0 1 IEEE 0 0
---------------------------------------------------------------------------
SwitchA#
show vlan-membership
SwitchA#show vlan-membership
Port VLAN Membership Type Port VLAN Membership Type
----------------------------- -----------------------------
1 1 Static 13 1 Static
AUI 1 Static
A 1 Static
B 1 Static
SwitchA#
Note that all ports belong to VLAN 1 by default and that the membership type of each port is static.
8. Enter global configuration mode from the privileged exec mode prompt by issuing the command
configure terminal
9. Assign Ethernet ports 0/1 and Ethernet 0/2 to VLAN 2 - Engineering. To assign an Ethernet port membership
in a VLAN, you must enter interface configuration mode.
Enter interface configuration mode for Ethernet 0/1 by issuing the command
interface Ethernet 0/1
10. To assign Ethernet 0/1 to VLAN 2, issue the command
vlan-membership static 2
11. Repeat this process, assigning ports to VLANs as follows:
Ethernet 0/2 to VLAN 2
show vlan
SwitchA#show vlan
--------------------------------------
2 Engineering Enabled 1-2
3 Marketing Enabled 3-4
4 Production Enabled 5-6
--------------------------------------
---------------------------------------------------------------------------
1 Ethernet 100001 1500 0 0 0 Unkn 1002 1003
2 Ethernet 100002 1500 0 1 1 Unkn 0 0
3 Ethernet 100003 1500 0 1 1 Unkn 0 0
4 Ethernet 100004 1500 0 1 1 Unkn 0 0
1002 FDDI 101002 1500 0 0 0 Unkn 1 1003
1003 Token-Ring 101003 1500 1005 1 0 Unkn 1 1002
--More--
1004 FDDI-Net 101004 1500 0 0 1 IEEE 0 0
---------------------------------------------------------------------------
SwitchA#
Ethernet ports 0/1 through 0/6 appear in the VLANs as configured; however, Ethernet port 0/7 does not show
it belonging to any VLAN. Why?
14. Issue the privileged exec mode command
show interface ethernet 0/7
SwitchA#show int e 0/7
Ethernet 0/7 is Disabled-no-vlan
Hardware is Built-in 10Base-T
Address is 00B0.64D1.F747
MTU 1500 bytes, BW 10000 Kbits
802.1d STP State: Disabled Forward Transitions: 1
Port monitoring: Disabled
Unknown unicast flooding: Enabled
Unregistered multicast flooding: Enabled
Description:
Duplex setting: Half duplex
Back pressure: Disabled
Notice that Ethernet port 0/7 is reporting that it is "Disabled-no-vlan". This message appears when a port has
been assigned to a VLAN that has not yet been created.
15. Issue the privileged-exec mode command
SwitchA#show vlan-m
----------------------------- -----------------------------
AUI 1 Static
A 1 Static
B 1 Static
SwitchA#
From the output of the command show vlan-membership, we can determine that Ethernet port 0/7 has been
assigned to VLAN 5.
16. Enter global configuration mode from the privileged exec mode prompt by issuing the command
configure terminal
17. Create VLAN 5, naming it "Accounting."
18. Issue the privileged exec mode command
show vlan
SwitchA#show vlan
--------------------------------------
2 Engineering Enabled 1-2
3 Marketing Enabled 3-4
4 Production Enabled 5-6
5 Accounting Enabled 7
--------------------------------------
---------------------------------------------------------------------------
1 Ethernet 100001 1500 0 0 0 Unkn 1002 1003
2 Ethernet 100002 1500 0 1 1 Unkn 0 0
3 Ethernet 100003 1500 0 1 1 Unkn 0 0
4 Ethernet 100004 1500 0 1 1 Unkn 0 0
5 Ethernet 100005 1500 0 1 1 Unkn 0 0
--More--
1002 FDDI 101002 1500 0 0 0 Unkn 1 1003
1003 Token-Ring 101003 1500 1005 1 0 Unkn 1 1002
1004 FDDI-Net 101004 1500 0 0 1 IEEE 0 0
---------------------------------------------------------------------------
SwitchA#
Notice that Port 7 now appears in VLAN 5 - Accounting.
Section 3 - Verifying VLAN Functionality
In this section you will test the connectivity between two end-systems connected to ports that have been configured
as members of the same VLAN and then to ports that are configured as members of different VLANs.
1. Connect one of your two PCs to SwitchA's Ethernet port labeled "1x".
2. On this PC, set the following IP configuration information:
IP address: 172.16.1.20
Subnet mask: 255.255.255.0
3. Connect the second PC to SwitchA's Ethernet port labeled "2x."
4. On this PC, set the following IP configuration information:
IP address: 172.16.1.21
Subnet mask: 255.255.255.0
5. From the PC plugged into SwitchA's Ethernet port 1x, ping IP address 172.16.1.21. Were you successful?
Yes or No? Why?
Yes or No? Why?
7. You should have been able to ping between each PC because each is a member of the same VLAN.
Now without changing IP address information on the PCs, move the network cable from SwitchA's Ethernet
port 2x to 4x.
Yes or No? Why?
Yes or No? Why?
10. You should not have been able to ping between PCs. The PC attached to port 1x is a member of VLAN 2,
while the PC attached to port 4x is a member of VLAN 3. Note that they both exist in the same subnet.
11. Do you think you will be able to ping the IP address of the switch from either connected PC?
Why or why not?
12. Try to ping the IP address of SwitchA from the PC plugged into SwitchA's Ethernet port 1x. Were you
successful?
Yes or No? Why?
13. Try to ping the IP address of SwitchA from the PC plugged into SwitchA's Ethernet port 4x. Were you
successful?
Yes or No? Why?
14. The IP address of the switch is assigned membership to VLAN 1 by default. Only a PC that resides in the
same subnet as the switch that is also a member of VLAN 1 will be able to ping the switch.
Now without changing IP address information on the PCs, move the network cable from SwitchA's Ethernet
port 4x to 10x.
15. From the PC that is connected to SwitchA's Ethernet port 10x, attempt to ping the switch. Were you
successful?
Yes or No? Why?
16. You should have been able to ping the switch when you were plugged into SwitchA's Ethernet port 10x.
Ethernet port 10x is configured as a member of VLAN 1. Both the switch and the PC belong to the same
subnet.
If two end-systems were located in the same VLAN but were located on different subnets, would they still be
able to communicate?
Yes or No? Why?
Section 4 - Configuring an ISL Trunk Link
In this section, you will create an ISL trunk link that will carry VLAN traffic between your primary and your secondary
switch.
To demonstrate the functionality gained by using a trunk port rather than a dedicated link, you will begin this section
of the lab using a point-to-point configuration to forward VLAN traffic between the two switches. Once you have
become familiar with how to configure a standard single-VLAN link between the two switches, you will configure an
ISL trunk link.
Before you begin, connect the two FastEthernet A ports using a crossover cable. To ensure this lab will work as
expected, first test the connection between both switches. Ping the IP address of SwitchA (172.16.1.200). You should
be successful. If not, check the cable between the FastEthernet ports of both switches. Do not proceed further until
you can successfully ping between switches.
Begin this part of the lab by configuring SwitchB.
1. On SwitchB, enter global configuration mode from the privileged exec mode prompt by issuing the command
configure terminal
The prompt "SwitchB(config)#" will be displayed, indicating you have entered global configuration mode.
2. Create VLAN 2, specifying the name for the VLAN as "Engineering."
Note: When typing in the names of VLANs, remember that name information is case sensitive.
3. Create VLAN 3, specifying the name for the VLAN as "marketing." USE ALL lower CASE.
4. Assign Ethernet ports 0/1 and 0/2 to VLAN 2.
5. Assign Ethernet ports 0/3 and 0/4 to VLAN 3.
6. Disconnect the cable plugged into SwitchA's port labeled "10x." Connect it to SwitchB's Ethernet port labeled
1x.
7. From either PC, attempt to ping the corresponding PC. Were you successful?
Yes or No? Why?
8. You should not have been successful. When the switch received a ping for an end-system that was not
directly connected to it, it flooded the frame out all ports that belonged to the same VLAN as the originating
end-system. What is missing (but required) are ports on each switch that have been configured as a member
of VLAN 2 and are directly connected to each other.
9. On SwitchB, assign FastEthernet port 0/26 to VLAN2.
On SwitchA, assign FastEthernet port 0/26 to VLAN2.
A pathway between both switches that can carry traffic for VLAN 2 has been created.
10. From either PC, attempt to ping the corresponding PC. Were you successful?
Yes or No? Why?
11. You should have been successful.
From SwitchA, attempt to ping the IP address of SwitchB (172.16.1.201). Were you successful?
Yes or No? Why?
12. You should not have been successful. When you changed VLAN membership assignments on FastEthernet
port 0/26, you disabled VLAN 1 traffic from being propagated between both switches.
Now it's time to configure a trunk link that will support traffic from all VLANs.
13. Determine the current state of trunking on FastEthernet ports 0/26 and 0/27. Issue the privileged exec
commands
show trunk a
show trunk b
SwitchA#show trunk a
DISL state: Off, Trunking: Off, Encapsulation type: Unknown
SwitchA#show trunk b
DISL state: Off, Trunking: Off, Encapsulation type: Unknown
SwitchA#
Note that "Off" is the default DISL state. "Off" disables trunking on the port and negotiates with the connected
switch port to become a non-trunk port. There is no DISL trunking mode that will force a corresponding trunk
partner port to successfully establish a trunk when one of the partner ports is configured with the DISL setting
of "off."
14. Set the DISL trunk state to "Desirable." The DISL state "desirable" will to set the port to trunk mode if the
connected port is set to "on," "desirable," or "auto".
Enter global configuration mode from the privileged exec mode prompt by issuing the command
configure terminal
15. Enter interface configuration mode for trunk port a by issuing the command
interface fastethernet 0/26
16. Issue the command
trunk desirable
17. To exit from interface configuration mode to privileged exec mode, issue the key sequence Ctrl+Z.
show trunk a
SwitchA#show trunk a
DISL state: Desirable, Trunking: Off, Encapsulation type: Unknown
SwitchA#
If the DISL state reports other than what is expected, wait a few seconds and check the state of the trunk
again.
19. On SwitchB, set the DISL trunk state to "Auto". The DISL state "auto" will set the port to become a trunk if the
connected switch port has initiated negotiation. In order to successfully establish a trunk connection with a
partner port, the connected partner switch port must be set to the "on" or "desirable" state.
Enter global configuration mode from the privileged exec mode prompt by issuing the command
configure terminal
The prompt "SwitchB(config)#" will be displayed, indicating you have entered global configuration mode.
20. Enter interface configuration mode for trunk port a by issuing the command
interface fastethernet 0/26
21. Issue the command
trunk auto
22. To exit from interface configuration mode to privileged exec mode, issue the key sequence Ctrl+Z.
show trunk a
SwitchB#show trunk a
DISL state: Auto, Trunking: On, Encapsulation type: ISL
SwitchB#
If the trunking state reports a state other than what is expected, wait a few seconds -- the DISL negotiation
process between ports may still be in progress. Then, check the state of the trunk again. For example, the
following output was displayed the first two times the command show trunk a was issued when this lab
scenario was created:
DISL state: Auto, Trunking: Off, Encapsulation type: Unknown
SwitchB#
DISL state: Auto, Trunking: Off, Encapsulation type: Unknown
24. Determine if the trunk port is carrying traffic between switches for VLAN 1. Attempt to ping SwitchA from
SwitchB. Ping 172.16.1.200. Were you successful?
Yes or No? Why?
25. You should have been successful. The trunk link carries frames for all VLANs (by default) between switches.
Determine if the trunk port is carrying traffic between switches for VLAN 2. From either PC, attempt to ping the
corresponding PC. Were you successful?
Yes or No? Why?
26. You should have been successful. You have created a trunk that supports ISL encapsulation that transports
frames from all VLANs between your two switches.
27. From SwitchB, verify that your trunk is, in fact, configured to carry all VLAN traffic between switches. Issue the
command
show trunk a allowed-vlans
SwitchB#show trunk a allowed-vlans
1-1005
SwitchB#
When the Trunk Doesn't Appear To Work Properly:
28. On SwitchA, connect the network cable from the PC with the IP address 172.16.1.20 into the switch port
labeled "3x" (VLAN 3).
29. On SwitchB, connect the network cable from the PC with the IP address 172.16.1.21 into the switch port
labeled "3x" (VLAN 3).
30. From the PC that is connected to SwitchA's Ethernet port 3x, attempt to ping the IP address of the neighboring
PC (remember that both PCs are in VLAN 3 and the trunk has been verified to be working). Were you
successful?
Yes or No? Why?
31. You should not have been successful. Even though VLAN 3 exists on both switches, the VLAN name
"Marketing" on SwitchA is not the same as the VLAN name on SwitchB "marketing." CaSe matters when
configuring VLAN names. Using VTP to manage VLAN configuration for even two switches will help ensure
VLAN naming consistency in a network.
Section 5 - More VTP Configuration
In this section, you will learn more about VTP configuration. Specifically, you will see how VTP revision numbers are
important in determining which VLAN configuration information is maintained, and which is overwritten. Additionally,
you will learn about the implications of having a switch operate in VTP transparent mode and later decide to switch its
mode of operation to VTP client or VTP server.
Begin this part of the lab by working with SwitchB.
1. On SwitchB, issue the privileged exec command
show vtp
SwitchB#show vtp
VTP version: 1
VTP domain name :
VTP password :
Note the Configuration revision number (2). On this switch, two VLANs were created (VLAN 2 and VLAN 3).
The switch indicates that there are currently seven existing VLANs. They would be the default VLANs 1, 1002,
1003, 1004, 1005, and the administratively configured VLANs (2 and 3).
2. On SwitchA, issue the privileged exec command
show vtp
SwitchA#show vtp
VTP version: 1
VTP password :
VTP operating mode : Transparent
SwitchA#
Note the Configuration revision number is 0 even though on this switch four new VLANs have been created.
When a switch has been configured in VTP transparent mode, the configuration revision number does not
increment. The configuration revision number for a switch operating in VTP transparent mode will remain at
0.
3. On SwitchB, enable VTP operation on the switch. Set the VTP domain name to "CertZone." (Reference
Section 1, "Configuring VLAN Trunk Protocol (VTP)," if you require assistance).
show vtp
SwitchB#show vtp
VTP version: 1
VTP password :
SwitchB#
Note that the VTP domain name is identical to the VTP domain name set on SwitchA. Also note that SwitchB
is operating in VTP server mode.
5. On SwitchA, recall that there are nine existing VLANs (as noted in Step 2 of Section 5).
Set the VTP mode from transparent to server. From global configuration mode, issue the command
vtp server
show vtp
SwitchA#show vtp
VTP version: 1
VTP password :
SwitchA#
Although SwitchA had more VLANs configured, the VTP database information from SwitchB overwrote the
entire VLAN configuration that had been completed previously in Section 2, "Creating VLANs."
When changing a switch from vtp transparent operation to vtp client or vtp server mode, all
configuration information will be lost because vtp transparent mode does not maintain a configuration
revision value. Do not configure a switch offline using transparent mode operation and expect that this
switch will propagate all its information into the network.
7. What happened to the static VLAN port assignments on SwitchA when the VTP database from SwitchB
overwrote the VLAN configuration information on SwitchA?
Issue the privileged exec command
SwitchA#show vlan-membership
----------------------------- -----------------------------
AUI 1 Static
A 2 Static
B 1 Static
Even though the VLAN configuration information from SwitchB overwrote the VLAN configuration information
from SwitchA, the static VLAN assignments on SwitchA remained as configured in Section 2, "Creating
VLANs." If SwitchB had configured its VLANs differently, the end-system attached to port 7 assigned to VLAN
5 could have become a member of the "BalletSchool" rather than the "Accounting" VLAN. When you switch
VTP modes, make sure you are aware of all the consequences -- seen and unseen -- prior to making the
change.
Section 6 - Viewing Spanning Tree Protocol
Information
In this section, you will use the basic Spanning Tree Protocol (STP) command show spantree to verify STP
operation.
Begin this part of the lab by working with SwitchA.
1. On SwitchA, display the Spanning Tree Protocol configuration status of each port on the switch. Issue
privileged exec command
show spantree
The output of the command show spantree will display, in sequential order, STP information for all ports that
are members of each VLAN, beginning with VLAN 1. When all STP information for ports that are members of
VLAN 1 have been displayed, information for all ports that are members of VLAN 2 is displayed. This process
continues until all STP information for all VLANs has been displayed.
Section 7 - Configuring ISL Routing
In this section, you will configure inter-VLAN communication for VLANs 1, 2, and 3 in our network. The IP subnetting
information for this section is as follows:
1 default 172.16.1.0 /24
2 Engineering 172.16.2.0 /24
3 marketing 172.16.3.0 /24
1. Connect one end of a standard straight-through Category 5 cable to a Cisco router's FastEthernet interface
(the router must support ISL encapsulation in order for this to work properly).
2. Connect the other end of the standard straight-through Category 5 cable to Port B on SwitchA.
3. On SwitchA, set the DISL trunk mode to "On." (Reference Section 1, "Configuring VLAN Trunk Protocol
(VTP)," if you require assistance).
4. On the Cisco router's FastEthernet interface, create a subinterface for each VLAN to be routed.
5. For each subinterface, enable ISL encapsulation using the subinterface configuration command
encapsulation isl <VLAN ID>
6. Assign an IP address to the subinterface from the subnet range that corresponds to the VLAN to be routed on
the subinterface.
To route between VLANs, the configuration entered on the router should look like:
RouterA#configure terminal
RouterA(config)#interface fastethernet 0/0.1
RouterA(config-subif)#encapsulation isl 1
RouterA(config-subif)#ip address 172.16.1.100
7. To test routing between VLANs: on SwitchA, connect the network cable from the PC with the IP address
172.16.1.20 into the switch port labeled "1x" (VLAN 2).
8. Change the IP address of the PC connected to SwitchA port 1x to 172.16.2.20, subnet mask 255.255.255.0,
default gateway 172.16.2.100.
9. Change the IP address of the PC connected to SwitchB port 3x to 172.16.3.21, subnet mask 255.255.255.0,
default gateway 172.16.3.100.
10. From the PC connected to SwitchA, attempt to ping the IP address 172.16.3.21. Were you successful?
Yes or No? Why?
The VLAN Wrap-Up
Once you have completed the CCNA VLANs tutorial, study questions, and (this) accompanying lab, you should be
able to:
l Define the term "Virtual Local Area Network" or "VLAN"
l Describe the benefits of implementing VLANs
l Configure VLANs using Cisco Catalyst IOS-based LAN switches such as the Cisco Catalyst 1900 series
switch
l Identify key differences between Cisco's proprietary ISL and IEEE 802.1q industry-standard trunking protocols
l Configure trunking on a Cisco Catalyst IOS-based LAN switch such as the Cisco Catalyst 1900 series switch
l Identify the purpose of the VLAN Trunking Protocol (VTP)
l Configure VTP parameters including VTP domain name, VTP password, VTP operational modes
(Server/Client/Transparent), and VTP pruning
l Identify how Cisco's implementation of Spanning Tree Protocol operates when multiple VLANs are configured
and when connecting to non-Cisco Layer 2 devices
l Identify the appropriate "show" commands to verify VLAN connectivity and ensure proper Spanning Tree
operation
l Describe how to route between VLANs when using ISL
l Identify commands to troubleshoot common VLAN issues.
In this lab, you:
l Configured VLANs on an IOS-based LAN switch
l Configured trunking on an IOS-based LAN switch
l Configured VTP parameters that included VTP domain name and modified operational modes. (Consult the
CCNA VLANs white paper for information on how to set the VTP password and how to enable VTP pruning).
l Identified how Spanning Tree Protocol operates when multiple VLANs are configured
l Used a variety of show commands to verify VLAN connectivity, including the command show spantree to
ensure proper Spanning Tree Protocol operation.
l Set up routing between VLANs using ISL
l Used a variety of show commands to troubleshoot common VLAN issues.
Good luck with your exam!
[NA-VLAN-LS1-F03]
[2001-03-30-02]
Copyright 2001 Genium Publishing Corporation

CCNA Layer 2 Switching - VLANs Lab Scenario

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

CCNA Layer 2 Switching - VLANs Lab Scenario

Caricato da

Copyright:

Formati disponibili

CertificationZone Page 1 of 17

Potrebbero piacerti anche