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 at enneenne.com Linux Device Driver giometti at linux.it Embedded Systems phone: +39 349 2432127 UNIX programming skype: rodolfo.giometti Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it
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
On Tue, Oct 09, 2012 at 04:23:37PM +0200, 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!Just to be more complete as possible here a packets dump. At 17.449146 the ingress BPDU: 0000 01 80 c2 00 00 00 00 0a dc 5a f6 8d 00 27 42 42 .........Z...'BB 0010 03 00 00 02 02 0e 80 00 00 0a dc 5a f6 80 00 00 ...........Z.... 0020 00 00 80 00 00 0a dc 5a f6 80 80 0d 00 00 14 00 .......Z........ 0030 02 00 10 00 00 31 30 30 4e 43 2d 52 .....100NC-R At 18.814988 my machine's answer: 0000 01 80 c2 00 00 00 00 02 3e 99 f5 01 00 27 42 42 ........>....'BB 0010 03 00 00 02 02 0e 50 00 00 0a dc 5a e5 20 00 03 ......P....Z. .. 0020 0d 40 80 00 00 02 3e 99 f5 01 80 01 01 00 14 00 . at ....>......... 0030 02 00 10 00 00 00 00 00 00 00 00 00 ............ At 18.818471 another ingress BPDU: 0000 01 80 c2 00 00 00 00 0a dc 5a f6 8d 00 27 42 42 .........Z...'BB 0010 03 00 00 02 02 78 50 00 00 0a dc 5a e5 20 00 03 .....xP....Z. .. 0020 0d 53 80 00 00 0a dc 5a f6 80 80 0d 01 00 14 00 .S.....Z........ 0030 02 00 10 00 00 31 30 30 4e 43 2d 52 .....100NC-R And at 19.183731 my machine's answer: 0000 01 80 c2 00 00 00 00 02 3e 99 f5 01 00 27 42 42 ........>....'BB 0010 03 00 00 02 02 3d 50 00 00 0a dc 5a e5 20 00 03 .....=P....Z. .. 0020 0d 40 80 00 00 02 3e 99 f5 01 80 01 01 00 14 00 . at ....>......... 0030 02 00 10 00 00 00 00 00 00 00 00 00 ............ Ciao, Rodolfo -- GNU/Linux Solutions e-mail: giometti at enneenne.com Linux Device Driver giometti at linux.it Embedded Systems phone: +39 349 2432127 UNIX programming skype: rodolfo.giometti Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it
On Tue, Oct 09, 2012 at 06:42:36PM +0300, Vitalii Demianets wrote:> Hello, Rodolfo! > > Please, describe your setup: how many devices do you have and how exactly are > they connected?ASCII Art: +------------+ | my machine |----+ +------------+ | | +------------+ | | | | +------------+ +------------+ | | root |----+ <----[A] +------------+ The "Event" is: the ring is opened in [A]> 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?Since I receive the external BPDU related with the Event (see "bridge_bpdu_rcv: ifindex 6, len 60") to the message "MSTP_OUT_set_state: br0:mrvl4:0 entering forwarding".> 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?My device is not the root bridge and it never becomes the root bridge nor before and after the Event. Ciao, Rodolfo -- GNU/Linux Solutions e-mail: giometti at enneenne.com Linux Device Driver giometti at linux.it Embedded Systems phone: +39 349 2432127 UNIX programming skype: rodolfo.giometti Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it