From Holger.Kummert at sophos.com Fri Mar 7 06:13:49 2014 From: Holger.Kummert at sophos.com (Holger Kummert) Date: Fri, 7 Mar 2014 15:13:49 +0100 Subject: [Xorp-hackers] PIM/SM: xorpsh cannot be started if bgp is disabled Message-ID: <5319D41D.3090002@Sophos.com> Hello, I'm new to this list and also new to XORP. In my use case only PIM/SM is needed and therefore other routing protocols like bgp, ospf, rip, vrrp, olsr are disabled in scons configuration (enable_bgp=no ...). xorpsh is enabled. After installation of XORP the call of xorpsh lead to the message: # xorpsh [ 2014/03/07 11:32:45.685376 ERROR xorpsh:18451 RTRMGR rtrmgr/xorpsh_main.cc:900 main ] xorpsh exiting due to an init error: PARSE ERROR [Operational Command File: /share/xorp/templates/policy.cmds line 73]: Bad variable name: $(policy.community-list.*); Last symbol parsed was "$(policy.community-list.*)" I inspected policy.cmds and found out that the four items for community-list and as-path-list are all related to BGP. Therefore a simple deletion of those items in policy.cmds lead to an error-free call of xorpsh. So I have a workaround for the problem, but my questions are: - Is my analysis right? - If yes, shouldn't the four items in question moved to another place (e.g. bgp.cmds)? Thanks in advance, Holger From greearb at candelatech.com Thu Mar 13 10:47:34 2014 From: greearb at candelatech.com (Ben Greear) Date: Thu, 13 Mar 2014 10:47:34 -0700 Subject: [Xorp-hackers] PIM/SM: xorpsh cannot be started if bgp is disabled In-Reply-To: <5319D41D.3090002@Sophos.com> References: <5319D41D.3090002@Sophos.com> Message-ID: <5321EF36.6000304@candelatech.com> On 03/07/2014 06:13 AM, Holger Kummert wrote: > Hello, > > I'm new to this list and also new to XORP. > In my use case only PIM/SM is needed and therefore other > routing protocols like > bgp, ospf, rip, vrrp, olsr are disabled in scons configuration > (enable_bgp=no ...). > xorpsh is enabled. > After installation of XORP the call of xorpsh lead to the message: > # xorpsh > [ 2014/03/07 11:32:45.685376 ERROR xorpsh:18451 RTRMGR > rtrmgr/xorpsh_main.cc:900 main ] xorpsh exiting due to an init error: > PARSE ERROR [Operational Command File: /share/xorp/templates/policy.cmds > line 73]: Bad variable name: $(policy.community-list.*); Last symbol > parsed was "$(policy.community-list.*)" > > I inspected policy.cmds and found out that the four items for > community-list and > as-path-list > are all related to BGP. Therefore a simple deletion of those items in > policy.cmds lead to an error-free call of xorpsh. > So I have a workaround for the problem, but my questions are: > > - Is my analysis right? > - If yes, shouldn't the four items in question moved to another place > (e.g. bgp.cmds)? Can you send a patch (git format-patch -s ....) and an example config file that reproduces the problem? Thanks, Ben > > > Thanks in advance, > Holger > > _______________________________________________ > Xorp-hackers mailing list > Xorp-hackers at icir.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers > -- Ben Greear Candela Technologies Inc http://www.candelatech.com From Holger.Kummert at sophos.com Fri Mar 14 10:51:56 2014 From: Holger.Kummert at sophos.com (Holger Kummert) Date: Fri, 14 Mar 2014 18:51:56 +0100 Subject: [Xorp-hackers] PIM/SM: xorpsh cannot be started if bgp is disabled In-Reply-To: <5321EF36.6000304@candelatech.com> References: <5319D41D.3090002@Sophos.com> <5321EF36.6000304@candelatech.com> Message-ID: <532341BC.6040902@Sophos.com> Yes, of course. You can find both in the attachments. Please remember that this patch is not the whole story: I didn't cross-check with BGP enabled. I assume that the removed policy-definitions have to be put to another place. Best regards, Holger Am 13.03.2014 18:47, schrieb Ben Greear: > On 03/07/2014 06:13 AM, Holger Kummert wrote: >> Hello, >> >> I'm new to this list and also new to XORP. >> In my use case only PIM/SM is needed and therefore other >> routing protocols like >> bgp, ospf, rip, vrrp, olsr are disabled in scons configuration >> (enable_bgp=no ...). >> xorpsh is enabled. >> After installation of XORP the call of xorpsh lead to the message: >> # xorpsh >> [ 2014/03/07 11:32:45.685376 ERROR xorpsh:18451 RTRMGR >> rtrmgr/xorpsh_main.cc:900 main ] xorpsh exiting due to an init error: >> PARSE ERROR [Operational Command File: /share/xorp/templates/policy.cmds >> line 73]: Bad variable name: $(policy.community-list.*); Last symbol >> parsed was "$(policy.community-list.*)" >> >> I inspected policy.cmds and found out that the four items for >> community-list and >> as-path-list >> are all related to BGP. Therefore a simple deletion of those items in >> policy.cmds lead to an error-free call of xorpsh. >> So I have a workaround for the problem, but my questions are: >> >> - Is my analysis right? >> - If yes, shouldn't the four items in question moved to another place >> (e.g. bgp.cmds)? > > Can you send a patch (git format-patch -s ....) and an example config > file that reproduces the problem? > > Thanks, > Ben > >> >> >> Thanks in advance, >> Holger >> >> _______________________________________________ >> Xorp-hackers mailing list >> Xorp-hackers at icir.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers >> > > -------------- next part -------------- A non-text attachment was scrubbed... Name: remove_bgp4_commands_from_policy.patch Type: text/x-patch Size: 1542 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20140314/b39fc2c4/attachment.bin -------------- next part -------------- # cat xorp.conf interfaces { interface eth2 { default-system-config } interface eth1 { default-system-config } interface eth3 { default-system-config } } fea { unicast-forwarding4 { } } plumbing { mfea4 { interface eth2 { vif eth2 { } } interface eth1 { vif eth1 { } } interface eth3 { vif eth3 { } } interface register_vif { vif register_vif { } } traceoptions { flag all { disable: false } } } } protocols { static { } igmp { interface eth2 { vif eth2 { version: 2 } vif eth2 { version: 3 } } interface eth1 { vif eth1 { version: 2 } vif eth1 { version: 3 } } interface eth3 { vif eth3 { version: 2 } vif eth3 { version: 3 } } traceoptions { flag all { disable: false } } } pimsm4 { interface eth2 { vif eth2 { dr-priority: 0 } } interface eth1 { vif eth1 { dr-priority: 10 } } interface eth3 { vif eth3 { dr-priority: 0 } } interface register_vif { vif register_vif { } } static-rps { rp 10.145.48.49 { group-prefix 239.0.0.1/32 { rp-priority: 10 } } } switch-to-spt-threshold { disable: false interval: 60 bytes: 10000 } traceoptions { flag all { disable: false } } } fib2mrib { } }