[Xorp-hackers] {Disarmed} Re: xorp: enable IGMP/PIM-SM over a VLAN interface on Linux

[Ray Soucy]

Try the following:

Don't define "register_vif" as an interface under the interfaces block.

Create your plumbing block first and commit the change, then try to
add the register_vif interface to your pimsm4 block.  It should not be
added to the igmp block.

Also don't forget your fib2mrib block.

I'm not sure about the current version, but I know that for 1.6 the
order you applied configuration steps was very touchy.

On Thu, Dec 8, 2011 at 2:08 PM, frank hu <frank.1975.hu at gmail.com> wrote:
>
> Hi,
>
> I still need more help.
>
> I rebooted my x86 box with xorp and restarted the xorp configuration from
> scratch. I configured PIM over the interface "vlan300" and IGMP over
> "vlan800" and committed the configurations. It went well. Then I tried to
> add plumbing/mfea4 and also the PIM register interface "register_vif".
> Unfortunately it failed at this step.
>
> xorp at feng-desktop# show
>     protocols {
>         igmp {
>             interface vlan800 {
>                 vif vlan800 {
>
>                 }
>             }
>         }
>         pimsm4 {
>             interface vlan300 {
>                 vif vlan300 {
>                     dr-priority: 41
>                 }
>             }
>>           interface "register_vif" {
>>               vif "register_vif" {
>>               }
>>           }
>             bootstrap {
>             }
>         }
>     }
>     interfaces {
>
>         interface vlan300 {
>             vif vlan300 {
>                 address 172.15.3.212 {
>                     prefix-length: 24
>                 }
>             }
>         }
>         interface vlan800 {
>             vif vlan800 {
>                 address 172.15.80.212 {
>                     prefix-length: 24
>                 }
>             }
>         }
>>       interface "register_vif" {
>>           vif "register_vif" {
>>           }
>>       }
>     }
>>   plumbing {
>>       mfea4 {
>>           interface vlan300 {
>>               vif vlan300 {
>>               }
>>           }
>>           interface vlan800 {
>>               vif vlan800 {
>>               }
>>           }
>>           interface "register_vif" {
>>               vif "register_vif" {
>>               }
>>           }
>>       }
>>   }
>     rtrmgr {
>         config-directory: "/etc/xorp/"
>     }
> [edit]
> xorp at desktop# commit
> ERROR: failed to lock the configuration. No Finder?
> The configuration has not been changed.
> Fix this error, and run "commit" again.
> xorp at desktop# commit
> ERROR: failed to lock the configuration. No Finder?
> The configuration has not been changed.
> Fix this error, and run "commit" again.
> xorp at desktop#
> "
>
> The error message seems weird. It complained "failed to lock the
> configuration".
>
> "xorp at desktop# quit
> ERROR: There are uncommitted changes.
> Use "commit" to commit the changes, or "exit discard" to discard them.
> xorp at desktop# exit discard
> ERROR: failed to inform rtrmgr of leaving config mode. No Finder?
> xorp at desktop> quit at feng-desktop>
> $ ./sbin/xorpsh
> Waiting for xorp_rtrmgr...
> $ ps -ef|grep xorp
> xorp      2241  2112  0 09:28 pts/1    00:00:00 su xorp
> xorp      2249  2241  0 09:29 pts/1    00:00:00 sh
> xorp      2290  2249  0 10:07 pts/1    00:00:00 ps -ef
> xorp      2291  2249  0 10:07 pts/1    00:00:00 grep xorp
> $
> "
> So the critical process "xorp_rtrmgr" was gone, along with "xorp_pim" and
> "xorp_igmp".
>
> It seems that a configuration change triggered the above to happen.
>
>



-- 
Ray Soucy

Epic Communications Specialist

Phone: +1 (207) 561-3526

Networkmaine, a Unit of the University of Maine System
http://www.networkmaine.net/