2.3.1.5 Packet Tracer - Configuring PVST+ Instructions
2.3.1.5 Packet Tracer - Configuring PVST+ Instructions
2.3.1.5 Packet Tracer - Configuring PVST+ Instructions
Topology
Addressing Table
Device
Interface
IP Address
Subnet Mask
Default Gateway
S1
VLAN 99
172.31.99.1
255.255.255.0
N/A
S2
VLAN 99
172.31.99.2
255.255.255.0
N/A
S3
VLAN 99
172.31.99.3
255.255.255.0
N/A
PC1
NIC
172.31.10.21
255.255.255.0
172.31.10.254
PC2
NIC
172.31.20.22
255.255.255.0
172.31.20.254
PC3
NIC
172.31.30.23
255.255.255.0
172.31.30.254
Assignments
Network
S1 F0/6
VLAN 30
172.17.30.0/24
S2 F0/18
VLAN 20
172.17.20.0/24
S3 F0/11
VLAN 10
172.17.10.0/24
Objectives
Part 1: Configure VLANs
Part 2: Configure Spanning Tree PVST+ and Load Balancing
Part 3: Configure PortFast and BPDU Guard
Background
In this activity, you will configure VLANs and trunks, and examine and configure the Spanning Tree Protocol
primary and secondary root bridges. You will also optimize the switched topology using PVST+, PortFast, and
BPDU guard.
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 3
Step 6: Configure the management interface on all three switches with an address.
Verify that the switches are correctly configured by pinging between them.
The root switch is responsible for generating BPDUs for STP 802.1D and is the focal point for spanning
tree to control traffic. The root switch must be capable of handling this additional load.
The placement of the root defines the active switched paths in the network. Random placement is likely to
lead to suboptimal paths. Ideally the root is in the distribution layer.
Consider the topology used in this activity. Of the six trunks configured, only three are carrying traffic.
While this prevents loops, it is a waste of resources. Because the root can be defined on the basis of the
VLAN, you can have some ports blocking for one VLAN and forwarding for another. This is demonstrated
below.
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 3
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 3 of 3