I am not sure if it's me running on 50% power this Sunday morning (most
likely), if it's the book that is written like a white house speech, or if
it's both. Anyway, the reason for this e-mail is that I am reading something
that to me doesn't make sense.

For those of you who would like to comment on this, if you have Cisco Press'
BCMSN book, I am refereing to "Handling Topology Changes in Spanning Tree"
on pages 142 and 143.

If you do not have that book, here's a quick description:

Switch A is the ROOT bridge.

Switch B and C are both connected to Switch A.

Switch D is connected to both Switch B and C.

Switch E is connected to Switch D.

Since A and D can see each other through both Switch B and C, the connection
between D and C is blocked.

The situation is that Switch D's link to E fails, and Switch D sends a
notice to Switch A (the root bridge) via Switch B.

The root bridge (Switch A) now sets the topology change in its configuration
for a period of time equal to the sum of the fwd delay and max age
parameters.

According to step 5 (in the book): "A bridge receiving the topology change
configuration message from the root bridge uses the fwd delay timer to age
out entries in its address table. This allows it to age out entries faster
than the normal five-minute default so that stations that are no longer
available due to the topology change will be aged out faster. It does this
until it no longer receives topology change configuration messages from the
root bridge."

The last line in that quote makes it sound like it keeps receiving messages
about the link E being down until it's up again - but what if the Switch E
never comes up again because it was sold to someone else - will the root
bridge keep sending messages about it forever??? - I don't think so, but
that is how I read it.

Can someone please clarify this for me?

Thanks in advance,

Ole

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Ole Drews Jensen
 Systems Network Manager
 CCNA, MCSE, MCP+I
 RWR Enterprises, Inc.
 [EMAIL PROTECTED]
 http://www.insync.net/~drews/ccnp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to