CCNA 3 v3.1 Module 7 Spanning Tree Protocol: © 2004, Cisco Systems, Inc. All Rights Reserved

Download as ppt
Download as ppt
You are on page 1of 22

CCNA 3 v3.

1 Module 7
Spanning Tree Protocol

© 2004, Cisco Systems, Inc. All rights reserved. 1


Purpose of This PowerPoint
• This PowerPoint primarily consists of the Target
Indicators (TIs) of this module in CCNA version
3.1.
• It was created to give instructors a PowerPoint to
take and modify as their own.
• This PowerPoint is:
NOT a study guide for the module final assessment.
NOT a study guide for the CCNA certification exam.
• Please report any mistakes you find in this
PowerPoint by using the Academy Connection
Help link.

© 2004, Cisco Systems, Inc. All rights reserved. 2


To Locate Instructional Resource Materials
on Academy Connection:

• Go to the Community FTP Center to locate


materials created by the instructor community
• Go to the Tools section
• Go to the Alpha Preview section
• Go to the Community link under Resources
• See the resources available on the Class home
page for classes you are offering
• Search http://www.cisco.com
• Contact your parent academy!

© 2004, Cisco Systems, Inc. All rights reserved. 3


Objectives

© 2004, Cisco Systems, Inc. All rights reserved. 4


Redundancy

Redundant networking topologies are


designed to ensure that networks continue
to function in the presence of single points
of failure.

© 2004, Cisco Systems, Inc. All rights reserved. 5


Redundant Topologies

• A goal of redundant topologies is to


eliminate network outages caused by a
single point of failure.
• All networks need redundancy for
enhanced reliability.

© 2004, Cisco Systems, Inc. All rights reserved. 6


Simple Redundant Switched Topology

© 2004, Cisco Systems, Inc. All rights reserved. 7


Broadcast Storm

© 2004, Cisco Systems, Inc. All rights reserved. 8


Multiple Frame Transmissions

© 2004, Cisco Systems, Inc. All rights reserved. 9


Media Access Control Database Instability

In a redundant switched network, it is


possible for switches to learn the wrong
information. A switch can learn that a MAC
address is on a port when it is not.
© 2004, Cisco Systems, Inc. All rights reserved. 10
Using Bridging Loops for Redundancy

© 2004, Cisco Systems, Inc. All rights reserved. 11


Spanning-Tree Protocol

© 2004, Cisco Systems, Inc. All rights reserved. 12


Spanning Tree Link Costs

© 2004, Cisco Systems, Inc. All rights reserved. 13


A Spanning Tree

© 2004, Cisco Systems, Inc. All rights reserved. 14


Spanning-Tree Operation

• One root bridge per


network.
• One root port per
nonroot bridge.
• One designated
port per segment.
• Nondesignated
ports are unused.

© 2004, Cisco Systems, Inc. All rights reserved. 15


Bridge Protocol Data Unit

Bridge protocol data unit


(BPDU)

© 2004, Cisco Systems, Inc. All rights reserved. 16


Bridge IDs

© 2004, Cisco Systems, Inc. All rights reserved. 17


Spanning-Tree Port States

© 2004, Cisco Systems, Inc. All rights reserved. 18


Spanning-Tree Recalculation

A switched internetwork has converged when


all the switch and bridge ports are in either the
forwarding or blocked state.
© 2004, Cisco Systems, Inc. All rights reserved. 19
Rapid Spanning-Tree Protocol

• The standard and protocol introduce the


following:
Clarification of port states and roles
Definition of a set of link types that can go
to forwarding state rapidly
Allowing switches, in a converged network,
to generate their own BPDUs rather than
relaying root bridge BPDUs

© 2004, Cisco Systems, Inc. All rights reserved. 20


Rapid Spanning-Tree Port Designations

The Rapid Spanning Tree Protocol, IEEE


802.1w, will eventually replace the Spanning
Tree Protocol, IEEE 802.1D.
© 2004, Cisco Systems, Inc. All rights reserved. 21
Summary

© 2004, Cisco Systems, Inc. All rights reserved. 22

You might also like