[Bridge] MSTPd in RSTP mode is sometimes slow...

[Vitalii Demianets]

Hello, Rodolfo!

Please, describe your setup: how many devices do you have and how exactly are 
they connected? 
Also, please specify which events exactly are you measuring the time interval 
between. As I understand, you are measuring the time interval between some 
event X not shown in the logs end the event Y = "br0:mrvl4:0 entering 
forwarding state". What is event X?
Also see one more question below the quoted text.

On Tuesday 09 October 2012 17:23:37 Rodolfo Giometti wrote:
> 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.
>

I guess you have three devices connected in the ring. If so, is the device 
under examination NOT the root bridge before event X, or after event X or in 
both cases?

-- 
With Best Regards,
Vitalii Demianets