<div>thanks Ray. Here is the configuration that consistently triggered the issue. </div>
<div> </div>
<div><a href="mailto:xorp@desktop">xorp@desktop</a># show<br> protocols {<br> igmp {<br> interface vlan800 {<br> vif vlan800 {<br> }<br> }<br> }<br> pimsm4 {<br>
interface vlan300 {<br> vif vlan300 {<br> dr-priority: 32<br> }<br> }<br>> interface "register_vif" {<br>> vif "register_vif" {<br>
> }<br>> }<br> bootstrap {<br> }<br> }<br> }<br> interfaces {<br> interface vlan300 {</div>
<div> vif vlan300 {<br> address 172.15.3.212 {<br> prefix-length: 24<br> }<br> }<br> }<br> interface vlan800 {<br> vif vlan800 {<br>
address 172.15.80.212 {<br> prefix-length: 24<br> }<br> }<br> }<br> }<br> rtrmgr {<br> config-directory: "/etc/xorp/"<br> }</div>
<div>[edit]<br><br><a href="mailto:xorp@desktop">xorp@desktop</a># commit<br>Finder disconnected. No Finder?<br>OK<br>[edit]<br><a href="mailto:xorp@desktop">xorp@desktop</a># <br></div>
<div><br><br> </div>
<div class="gmail_quote">On Thu, Dec 8, 2011 at 11:41 AM, 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">Try the following:<br><br>Don't define "register_vif" as an interface under the interfaces block.<br>
<br>Create your plumbing block first and commit the change, then try to<br>add the register_vif interface to your pimsm4 block. It should not be<br>added to the igmp block.<br><br>Also don't forget your fib2mrib block.<br>
<br>I'm not sure about the current version, but I know that for 1.6 the<br>order you applied configuration steps was very touchy.<br>
<div>
<div></div>
<div class="h5"><br>On Thu, Dec 8, 2011 at 2:08 PM, frank hu <<a href="mailto:frank.1975.hu@gmail.com">frank.1975.hu@gmail.com</a>> wrote:<br>><br>> Hi,<br>><br>> I still need more help.<br>><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 committed the configurations. It went well. Then I tried to<br>> add plumbing/mfea4 and also the PIM register interface "register_vif".<br>
> Unfortunately it failed at this step.<br>><br>> xorp@feng-desktop# show<br>> protocols {<br>> igmp {<br>> interface vlan800 {<br>> vif vlan800 {<br>><br>> }<br>
> }<br>> }<br>> pimsm4 {<br>> interface vlan300 {<br>> vif vlan300 {<br>> dr-priority: 41<br>> }<br>> }<br>
>> interface "register_vif" {<br>>> vif "register_vif" {<br>>> }<br>>> }<br>> bootstrap {<br>> }<br>
> }<br>> }<br>> interfaces {<br>><br>> interface vlan300 {<br>> vif vlan300 {<br>> address 172.15.3.212 {<br>> prefix-length: 24<br>
> }<br>> }<br>> }<br>> interface vlan800 {<br>> vif vlan800 {<br>> address 172.15.80.212 {<br>> prefix-length: 24<br>
> }<br>> }<br>> }<br>>> interface "register_vif" {<br>>> vif "register_vif" {<br>>> }<br>>> }<br>> }<br>
>> plumbing {<br>>> mfea4 {<br>>> interface vlan300 {<br>>> vif vlan300 {<br>>> }<br>>> }<br>>> interface vlan800 {<br>
>> vif vlan800 {<br>>> }<br>>> }<br>>> interface "register_vif" {<br>>> vif "register_vif" {<br>>> }<br>
>> }<br>>> }<br>>> }<br>> rtrmgr {<br>> config-directory: "/etc/xorp/"<br>> }<br>> [edit]<br>> xorp@desktop# commit<br>> ERROR: failed to lock the configuration. No Finder?<br>
> The configuration has not been changed.<br>> Fix this error, and run "commit" again.<br>> xorp@desktop# commit<br>> ERROR: failed to lock the configuration. No Finder?<br>> The configuration has not been changed.<br>
> Fix this error, and run "commit" again.<br>> xorp@desktop#<br>> "<br>><br>> The error message seems weird. It complained "failed to lock the<br>> configuration".<br>><br>> "xorp@desktop# quit<br>
> ERROR: There are uncommitted changes.<br>> Use "commit" to commit the changes, or "exit discard" to discard them.<br>> xorp@desktop# exit discard<br>> ERROR: failed to inform rtrmgr of leaving config mode. No Finder?<br>
> xorp@desktop> quit@feng-desktop><br>> $ ./sbin/xorpsh<br>> Waiting for xorp_rtrmgr...<br>> $ ps -ef|grep xorp<br>> xorp 2241 2112 0 09:28 pts/1 00:00:00 su xorp<br>> xorp 2249 2241 0 09:29 pts/1 00:00:00 sh<br>
> xorp 2290 2249 0 10:07 pts/1 00:00:00 ps -ef<br>> xorp 2291 2249 0 10:07 pts/1 00:00:00 grep xorp<br>> $<br>> "<br>> So the critical process "xorp_rtrmgr" was gone, along with "xorp_pim" and<br>
> "xorp_igmp".<br>><br>> It seems that a configuration change triggered the above to happen.<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>