Lab 9
Lab 9
Lab Topology
The topology diagram below represents the portion of the network you will configure in this lab.
IP Addresses
Device Interface IP Address Subnet Mask Default Gateway
Router1 Serial 0/0 175.10.1.1 255.255.255.0 -
FastEthernet 0/0 160.10.1.1 255.255.255.0 -
Router2 FastEthernet 0/1 160.10.1.2 255.255.255.0 -
Router3 Serial 0/0 175.10.1.2 255.255.255.0 -
FastEthernet 0/1 197.10.1.1 255.255.255.0 -
Switch3 VLAN 1 197.10.1.30 255.255.255.0 197.10.1.1
Switch4 VLAN 1 197.10.1.40 255.255.255.0 197.10.1.1
Lab Tasks
Task 1: Configure the VTP Mode and Domain
In this task, you will learn the steps necessary to configure a VTP mode, password, and domain on the
switches. Whenever a VLAN is added, modified, or deleted on a VTP-enabled switch in server mode, the
switch will send out VTP advertisements that contain the VLAN changes. A switch can belong to only one
VTP domain. A VTP domain contains all the switches that share a common VTP configuration. You can
increase VTP security by configuring an optional VTP password for the domain. However, all switches in
the VTP domain must be configured with the same password.
When prompted, you should use boson as a user name and cisco as a password.
1. On Switch3, which interfaces are used to connect to neighboring devices? ___________________
3. On Switch4, configure transparent as the VTP mode and configure boson as the VTP domain.
4. What effect does setting the VTP mode to transparent have on Switch4? ____________________
7. On Switch3, display VTP configuration information. What is the VTP mode on Switch3? _________
3. On Switch3, configure the FastEthernet 0/12 and FastEthernet 0/1 interfaces to perform trunking.
3. On Switch4, create VLAN 2 named Admin and VLAN 4 named Sales that will be used by the Admin
subnet and the Sales subnet:
4. On Switch3 and Switch4, display VLAN information. You should notice that VLAN 2 and VLAN 4
are displayed in the output for both switches and that no ports have been assigned to the two new
VLANs.
5. On Switch4, assign the port connected to PC2 to VLAN 2 (the Admin subnet) and the port connected
to PC4 to VLAN 4 (the Sales subnet).
6. On Switch4, verify that the ports are assigned to the correct VLANs on Switch4. VLAN 2 and VLAN
4 should not be listed in the output on Switch3.
7. Allow the network time to converge, and then ping from Switch4 to Router3 (197.10.1.1). The ping
should be successful.
4. Switch3 and Switch4 are Layer 2 switches; this means that they are not able to route packets.
Enable Router3 to route packets to the management VLAN and between the Admin and Sales
subnets. Use the appropriate VLAN number when creating subinterfaces.
2. From Router3, attempt to ping Router2 (160.10.1.2). The ping should be successful.
3. PC2 is in the Admin subnet, and PC4 is in the Sales subnet. On Router2, display the routing
table. Does the output include a route to the Admin subnet (197.10.2.0/24), or the Sales subnet
(197.10.4.0/24)? _________________________________________________________________
4. On the appropriate device, enable Router2 to dynamically learn a route to the subnets configured on
VLANs 1, 2, and 4. Use the EIGRP protocol with an autonomous system (AS) number of 100; do not
specify a wildcard mask when advertising the subnets.
5. On Router2, display the IP routing table. Routes to the Admin and Sales subnets should now be
displayed.
6. From PC2 and PC4, attempt to ping Router2 (160.10.1.2). The pings should be successful.
Once you have completed this lab, be sure to check your work by using the grading function.
You can do so by clicking the Grade Lab icon ( ) in the toolbar or by pressing Ctrl+G.
2. On Switch4, issue the following commands to disable the interface connected to Switch3:
3. On Switch4, issue the following commands to configure the VTP mode and domain:
4. Setting the VTP mode to transparent on Switch4 will prevent the switch from propagating any VLAN
changes you make on Switch4 to any other switches in the same VTP domain. Switches in VTP
transparent mode can forward VTP advertisements to other switches in the same VTP domain from
other switches, and you can create, modify, or delete VLANs on the switch. However, any changes
you make will not be propagated to other switches in the same VTP domain. Switches configured as
VTP transparent can store VLAN information in non-volatile random access memory (NVRAM) so
that if the switch is powered off, the VLAN configuration will be retained.
5. On Switch4, issue the following command to verify the VTP configuration. Sample output is shown
below:
7. On Switch3, issue the following command to display VTP configuration; sample output is shown
below:
The VTP mode on Switch3 is Server. By default, Cisco switches are configured for VTP server
mode. VTP server mode allows you to create, modify, and delete VLANs in the VTP domain. These
changes are then advertised to other switches participating in the same VTP domain. However, a
switch in VTP server mode will not originate VTP advertisements until a VTP domain name is set.
Switches configured as a VTP server store VLAN information in NVRAM, so that if the switch is
powered off, the VLAN configuration will be retained.
Note: A switch that is configured with a VTP mode of client does not store VLAN database
information in NVRAM when it is powered off. It must receive a VLAN advertisement from another
switch in its VTP domain to repopulate its VLAN database. Additionally, VLANs cannot be manually
created, modified, or deleted on a switch in VTP client mode.
8. On Switch3 and Switch4, issue the following commands to configure the VTP password:
Protected: false
3. On Switch3, issue the following commands to configure the FastEthernet 0/12 and FastEthernet 0/1
interfaces to perform trunking:
4. On Switch3 and Switch4, issue the following command to verify your trunking configuration. Sample
output from Switch3 is shown below:
Protected: false
Switch4#ping 197.10.1.1
8 Boson NetSim Lab Manual
Task 3: Create Separate VLANs to Expand the Switched Network
1. On Switch3 and Switch4, issue the following commands to change the VTP mode:
2. Issue the following command on Switch4 to display the ports assigned to each VLAN. Your output
should be similar to the following:
Switch4#show vlan
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
3. On Switch4, issue the following commands to create two new VLANs that will be used by the Admin
subnet and the Sales subnet:
Switch4(config)#vlan 2
VLAN 2 added:
Name:VLAN0002
Switch4(config-vlan)#name Admin
Switch4(config-vlan)#vlan 4
VLAN 4 added:
Name:VLAN0004
Switch4(config-vlan)#name Sales
Switch3#show vlan
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 0 0
2 enet 100002 1500 - - - - - 0 0
4 enet 100004 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
Switch4#show vlan
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 0 0
2 enet 100002 1500 - - - - - 0 0
4 enet 100004 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
6. On Switch4, issue the following show vlan command to verify that the ports are assigned to the
correct VLANs on Switch4. VLAN 2 and VLAN 4 should be listed in the output on Switch3. Sample
output from Switch4 is below:
Switch4#show vlan
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 0 0
2 enet 100002 1500 - - - - - 0 0
4 enet 100004 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
7. After the network converges, a ping from Switch4 to Router3 (197.10.1.1) should be successful.
C:>ping 197.10.1.4
2. On PC2, issue the following commands to change the IP address and default gateway:
4. Switch3 and Switch4 are Layer 2 switches; this means that they are not able to route packets. Issue
the following commands to enable Router3 to route packets to the management VLAN and between
the Admin and Sales subnets:
5. After the network has converged, a ping from PC2 to PC4 (197.10.4.4) should be successful.
C:>ping 197.10.4.4
C:>ping 160.10.1.2
Router3#ping 160.10.1.2
Router2#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B – BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
E1 - OSPF external type 1, E2 - OSPF external type 2, E – EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route
4. On Router3, issue the following commands to enable Router2 to dynamically learn a route to the
Admin subnet (197.10.2.0/24) and the Sales subnet (197.10.4.0/24):
5. On Router2, issue the following command after the network has converged. Routes to the Admin
and Sales subnets are displayed. Sample output is below:
Router2#show ip route
<output omitted>
C:>ping 160.10.1.2
Copyright © 1996–2017 Boson Software, LLC. All rights reserved. NetSim software and documentation are protected by copyright law.