All of lore.kernel.org
 help / color / mirror / Atom feed
From: Butorina Lilya <lilybox@yandex.ru>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Time of topology change in root bridge
Date: Tue, 12 Jan 2010 11:32:43 +0300	[thread overview]
Message-ID: <39041263285163@webmail88.yandex.ru> (raw)

Sorry, I made mistakes in problem description:

Hi.

I have two bridges with RSTP:

     hdlc0------hdlc0
br0 |                | br1
     hdlc1------hdlc1

br0 is root bridge.

And my initial tree topology:
#rstpctl showport br0
*    hdlc0 8001 Fwd  8000-00ee10022202 8000-00ee10022202 8001 D
*    hdlc1 8002 Fwd  8000-00ee10022202 8000-00ee10022202 8002 D

#rstpctl showport br1
*    hdlc0 8001 Fwd 8000-00ee10022202 8000-00ee10022202 8002 R
*    hdlc1 8002 Blk  8000-00ee10022202 8000-00ee10022202 8001 A


Next I break link on br1 on root port hdlc0 and get new three topology 
immedatly:
#rstpctl showport br0
*    hdlc0 8001 Dis  8000-00ee10022202 8000-00ee10022202 8001
*    hdlc1 8002 Fwd  8000-00ee10022202 8000-00ee10022202 8002 D

#rstpctl showport br1
*    hdlc0 8001 Dis  8000-00ee10022202 8000-00ee10022202 8002 
*    hdlc1 8002 Fwd  8000-00ee10022202 8000-00ee10022202 8001 R


Next I restore link. 
Here I expect that bouth bridges calculate new (initial) tree topology in 4sec.

I see expected on br1:
*    hdlc0 8001 Fwd 8000-00ee10022202 8000-00ee10022202 8002 R
*    hdlc1 8002 Blk  8000-00ee10022202 8000-00ee10022202 8001 A

But on root bridge br0 I see new tree topology in 30sec.
This time interval looks like STP value.

Is this correct behavior of RSTP or bug?


Thanks. 
Lilya.

             reply	other threads:[~2010-01-12  8:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12  8:32 Butorina Lilya [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-12  8:15 [Bridge] Time of topology change in root bridge Butorina Lilya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39041263285163@webmail88.yandex.ru \
    --to=lilybox@yandex.ru \
    --cc=bridge@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.