Thanks Justin for your complete reply:) I didn't know that there is a relation between forward delay and max-age, your explanation helps me a lot.
On Mon, Jun 18, 2012 at 12:05 AM, Justin Pettit <[email protected]> wrote: > I took a quick look at the code, and nothing obviously stood out as wrong. > Our STP library (which is taken almost verbatim out of the 802.1D spec) > has the following comment: > > /* Sets the desired forward delay for 'stp' to 'ms', in milliseconds. The > * actual forward delay is clamped to the range of 4 to 30 seconds and > subject > * to the relationship (2 * (bridge_forward_delay - 1 s) >= > bridge_max_age). > * The bridge forward delay is only used when 'stp' is the root bridge. */ > > By default, the max age is 20 seconds, which makes sense that the forward > delay can't be below 11. If you lower the max age > (other_config:stp-max-age), can you lower the forward delay? Clearly, this > information should make it outside the code. :-) I'll fix that up so it's > in ovs-vswitchd.conf.db. > > --Justin > > > On Jun 17, 2012, at 6:02 AM, h bagade wrote: > > > Hi all, > > > > I'm using openvswitch 1.4.1. when I enable stp on bridge and set the > forward delay lower than 11, in bridge status it is set correctly but the > forward delay on sending packets are not correct and is shown to be 11 > instead of what I set! for example, I set the fw time to 9, it is shown 9 > on bridge status but 11 on STP packets! > > Shouldn't the forward delay on packets be set to the value shown on > bridge status? > > > > Thanks in advance > > _______________________________________________ > > discuss mailing list > > [email protected] > > http://openvswitch.org/mailman/listinfo/discuss > >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
