From: Rodolfo Giometti <giometti@enneenne.com>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] MSTPd in RSTP mode is sometimes slow...
Date: Tue, 9 Oct 2012 16:23:37 +0200 [thread overview]
Message-ID: <20121009142337.GO28136@enneenne.com> (raw)
Hello,
I'm currently using the MSTPd daemon on a custom PowerPC based board
and I notice that when forced in RSTP mode a port trnasition to the
forwarding state, sometimes, needs about 1.2s and, sometimes, needs
about 80ms!
When the transition is quick I get the following log:
1038912050.392513: bridge_bpdu_rcv: ifindex 6, len 60
1038912050.397313: MSTP_IN_rx_bpdu: br0:mrvl4 received RST BPDU
1038912050.431810: PISM_to_UPDATE: br0:mrvl4:0
1038912050.436557: PISM_to_CURRENT: br0:mrvl4:0
1038912050.440949: PISM_to_RECEIVE: br0:mrvl4:0
1038912050.445431: PISM_to_NOT_DESIGNATED: br0:mrvl4:0
1038912050.449905: PISM_to_CURRENT: br0:mrvl4:0
1038912050.468990: MSTP_OUT_set_state: br0:mrvl4:0 entering learning state
1038912050.476744: set_port_role: port mrvl4 role 3
1038912050.483704: MSTP_OUT_set_state: br0:mrvl4:0 entering forwarding state
1038912050.488299: set_port_role: port mrvl4 role 3
1038912050.506378: MSTP_OUT_flush_all_fids: br0:mrvl5:0 Flushing forwarding data base
1038912051.199682: MSTP_OUT_tx_bpdu: br0:mrvl4 sending RST BPDU
On the other hand when the transition is slow I get:
1038911701.406963: bridge_bpdu_rcv: ifindex 6, len 60
1038911701.411766: MSTP_IN_rx_bpdu: br0:mrvl4 received RST BPDU
1038911701.446256: PISM_to_RECEIVE: br0:mrvl4:0
1038911701.451015: PISM_to_SUPERIOR_DESIGNATED: br0:mrvl4:0
1038911701.455493: PISM_to_CURRENT: br0:mrvl4:0
1038911702.021584: PISM_to_UPDATE: br0:mrvl4:0
1038911702.026330: PISM_to_CURRENT: br0:mrvl4:0
1038911702.204368: PISM_to_UPDATE: br0:mrvl4:0
1038911702.209114: PISM_to_CURRENT: br0:mrvl4:0
1038911703.199645: MSTP_OUT_tx_bpdu: br0:mrvl4 sending RST BPDU
1038911703.224464: MSTP_OUT_set_state: br0:mrvl4:0 entering learning state
1038911703.232292: set_port_role: port mrvl4 role 3
1038911703.245552: bridge_bpdu_rcv: ifindex 6, len 60
1038911703.250359: MSTP_IN_rx_bpdu: br0:mrvl4 received RST BPDU
1038911703.284849: PISM_to_RECEIVE: br0:mrvl4:0
1038911703.289604: PISM_to_NOT_DESIGNATED: br0:mrvl4:0
1038911703.294079: PISM_to_CURRENT: br0:mrvl4:0
1038911703.313165: MSTP_OUT_set_state: br0:mrvl4:0 entering forwarding state
Note that my machine is NOT the root bridge and the connection is a
simple ring where I remove the connection between the other two
machines.
Any advice? :)
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it
next reply other threads:[~2012-10-09 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 14:23 Rodolfo Giometti [this message]
2012-10-09 15:42 ` [Bridge] MSTPd in RSTP mode is sometimes slow Vitalii Demianets
2012-10-09 15:58 ` Rodolfo Giometti
2012-10-12 9:37 ` Rodolfo Giometti
2012-10-15 15:24 ` Rodolfo Giometti
2012-10-15 15:45 ` Rodolfo Giometti
2012-10-15 16:39 ` Rodolfo Giometti
2012-10-09 15:47 ` Rodolfo Giometti
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=20121009142337.GO28136@enneenne.com \
--to=giometti@enneenne.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox