<div> </div>
<div>Hi, Ray,</div>
<div> </div>
<div>thanks for the tips... Yes, it seems that XORP is happier with a complete configuration file. However, I still don't get multicast routing to work end-2-end with xorp.<br><br>Thanks!</div>
<div> </div>
<div class="gmail_quote">On Thu, Dec 8, 2011 at 12:16 PM, Ray Soucy <span dir="ltr"><<a href="mailto:rps@maine.edu">rps@maine.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">XORP is production quality in terms of its functionality. The XORP<br>shell doesn't work very well, and is "touchy" when trying to<br>
interactively configure it.<br><br>We script the generation of the "config.boot" file, and boot XORP<br>directly off the pre-written configuration, rather than trying to<br>configure it through the XORP shell.<br>
<br>We have not had any major stability or performance issues as a result.<br><br>To my knowledge, there are no other open source projects that<br>correctly support multicast. The closest is the pimd project for<br>Quagga, but it was very limited in its functionality last time I<br>
checked (only supports SSM for example).<br><br>The syntax of the XORP CLI is similar to what you would see from<br>Juniper. The majority of network engineers can intuitively make use<br>of it; bugs aside. I don't think it needs to be re-written to mirror<br>
Cisco. It just needs to be cleaned up. Perhaps by someone who would<br>find value in such functionality.<br>
<div>
<div></div>
<div class="h5"><br>On Thu, Dec 8, 2011 at 2:51 PM, frank hu <<a href="mailto:frank.1975.hu@gmail.com">frank.1975.hu@gmail.com</a>> wrote:<br>><br>> Thanks Ben for the kind help!<br>><br>> I did use the debuggers to look into the core dumps. However, I expected<br>
> xorp to be reasonably stable and such core dumps to happen only<br>> occasionally. From what I can see, the features XORP multicast routing<br>> engine offers are pretty nice -- not too complex but good enough for even a<br>
> lot enterprise users. However, the software suite doesn't seem mature enough<br>> to be bundled in industrial grade network devices.<br>><br>> Just some comment, if XORP also targets outside the academia community, its<br>
> overall configuration mechanism should be designed to be intuitive for Cisco<br>> IOS users for the simple reason that most router admins are much familiar<br>> with Cisco IOS CLIs. For example, why a multicast routing admin (of XORP)<br>
> needs to manually add register_vif interface? The software suite needs to do<br>> that under the hood, instead of having the user do it.<br>><br>><br>> I think that my assessment of XORP multicast routing will stop here.<br>
><br>> Also thanks a lot to Ray and everyone else that helped me through the issues<br>> that I ran into -- I appreciate your time and your in-depth expertise in<br>> XORP.<br>><br>> Frank<br>><br>><br>
> On Thu, Dec 8, 2011 at 11:11 AM, Ben Greear <<a href="mailto:greearb@candelatech.com">greearb@candelatech.com</a>> wrote:<br>>><br>>> On 12/08/2011 11:08 AM, frank hu wrote:<br>>>><br>>>><br>
>>> Hi,<br>>>> I still need more help.<br>>>> I rebooted my x86 box with xorp and restarted the xorp configuration from<br>>>> scratch. I configured PIM over the interface "vlan300" and IGMP over<br>
>>> "vlan800" and<br>>>> committed the configurations. It went well. Then I tried to add<br>>>> plumbing/mfea4 and also the PIM register interface "register_vif".<br>>>> Unfortunately it failed at<br>
>>> this step.<br>>><br>>><br>>> Look for core files and errors in the xorp logs. If you find cores, use<br>>> gdb to get<br>>> a backtrace (compile with debugging symbols if you haven't already).<br>
>><br>>> Use 'ulimit -c unlimited' before starting xorp_rtrmgr if it is crashing<br>>> and<br>>> not dumping core files.<br>>><br>>> Thanks,<br>>> Ben<br>>><br>>><br>
>>> So the critical process "xorp_rtrmgr" was gone, along with "xorp_pim" and<br>>>> "xorp_igmp".<br>>>> It seems that a configuration change triggered the above to happen.<br>
>><br>>><br>>><br>>> --<br>>> Ben Greear <<a href="mailto:greearb@candelatech.com">greearb@candelatech.com</a>><br>>> Candela Technologies Inc <a href="http://www.candelatech.com/" target="_blank">http://www.candelatech.com</a><br>
>><br>><br><br><br><br></div></div>
<div>
<div></div>
<div class="h5">--<br>Ray Soucy<br><br>Epic Communications Specialist<br><br>Phone: <a href="tel:%2B1%20%28207%29%20561-3526" value="+12075613526">+1 (207) 561-3526</a><br><br>Networkmaine, a Unit of the University of Maine System<br>
<a href="http://www.networkmaine.net/" target="_blank">http://www.networkmaine.net/</a><br></div></div></blockquote></div><br>