<div>Bruce</div>
<div> This bug was closed as it appeared to be an Alcatel bug (bug 1071).</div>
<div>Syed<br><br></div>
<div class="gmail_quote">On Thu, May 7, 2009 at 8:26 AM, Bruce Simpson <span dir="ltr"><<a href="mailto:bms@incunabulum.net">bms@incunabulum.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Mark,<br><br>Sorry for my late reply...<br>
<div class="im"><br>Williams, Mark wrote:<br>> 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><br></div>It wouldn't surprise me if there were cobwebs in the Cand-BSR<br>
mechanisms, but as Syed has said, it would need to be reproduced in a<br>lab situation to better understand the problem and how to fix.<br><br>thanks,<br>BMS<br>
<div>
<div></div>
<div class="h5"><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>
</div></div></blockquote></div><br>