<div>Mark</div>
<div> Can you open a bug on this? We will try to replicate - with Cisco 7200 - in the Xorp QA lab.</div>
<div>Syed<br><br></div>
<div class="gmail_quote">On Wed, Apr 15, 2009 at 9:11 AM, Williams, Mark <span dir="ltr"><<a href="mailto:william@losrios.edu">william@losrios.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I will be deploying Xorp on Linux systems soon to handle multicast routing with PIM-SM. Everything has worked well, but I have had problems with bootstrap router messages. In my testing, I used two Alcatel-Lucent routers and an Xorp system. Each router had two interfaces, and were in a chain in Alcatel - Xorp - Alcatel order.<br>
<br>When the Xorp box was configured as the candidate BSR, the Alcatel routers both picked up the Xorp box as the BSR after the election time passed.<br><br>However, if the Alcatel router on the "left" was configured as the CBSR, there was a strange problem. The Xorp box would learn the correct BSR, and so would the Alcatel router on the "right". However, the boostrap messages to the Alcatel router on the "right" did not get passed frequently enough, and the BSR would expire after 130 seconds. Then about 30 seconds later, the Alcatel on the "right" would pick of the BSR again. It seemed that the BSR had to expire before it would get renewed. The BSR never expired on the Xorp box.<br>
<br>I reversed the order and put the BSR on the "right", and got the same results. I could not find any tunable parameters for BSR expiration on the Alcatels or the Xorp system.<br><br>Any help is appreciated.<br>
<br>-Mark Williams<br><br>_______________________________________________<br>Xorp-users mailing list<br><a href="mailto:Xorp-users@xorp.org">Xorp-users@xorp.org</a><br><a href="http://mailman.icsi.berkeley.edu/mailman/listinfo/xorp-users" target="_blank">http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users</a><br>
</blockquote></div><br>