From tsche at mitre.org Tue Apr 1 11:50:23 2008 From: tsche at mitre.org (Che, Ting-Shuo T.) Date: Tue, 1 Apr 2008 14:50:23 -0400 Subject: [Xorp-users] 2 BGP Peers Simultaneously Message-ID: <9FDF44CB3E9C9943B656E85501CF36FA022BF165@IMCSRV1.MITRE.ORG> Installed XORP on Linux PC, started "./xorp_rtrmgr -b ipv6bgp.boot" (2000::1) and then connect to test equipment representing 2 BGP peers (2000::2 and 2000::3) with a lot of prefixes each. Both peers reached ESTABLISHED state in "show bgp peers detail" and started route injection, but only those prefixes from one peer (2000::3) shows up in "show bgp routes ipv6" and "show route table ipv6 unicast ebgp terse". Did I made mistake in the following configuration file? Thank you very much for your help. Ting Che /*XORP Configuration File, v1.0*/ protocols { bgp { bgp-id: 192.168.2.3 local-as: 65503 enable-4byte-as-numbers: false peer 2000::2 { peer-port: 179 local-port: 179 local-ip: 2000::1 as: 65504 next-hop: 192.168.2.6 next-hop6: 2000::1 holdtime: 90 delay-open-time: 0 client: false confederation-member: false disable: false ipv4-unicast: false ipv4-multicast: false ipv6-unicast: true ipv6-multicast: false } peer 2000::3 { peer-port: 179 local-port: 179 local-ip: 2000::1 as: 65505 next-hop: 192.168.2.6 next-hop6: 2000::1 holdtime: 90 delay-open-time: 0 client: false confederation-member: false disable: false ipv4-unicast: false ipv4-multicast: false ipv6-unicast: true ipv6-multicast: false } export: "block" } } fea { unicast-forwarding6 { disable: false } } interfaces { restore-original-config-on-shutdown: false interface eth0 { description: "" disable: false discard: false unreachable: false management: false vif eth0 { disable: false address 192.168.2.3 { prefix-length: 24 disable: false } address 2000::1 { prefix-length: 64 disable: false } address fe80::20f:1fff:fea8:70e4 { prefix-length: 64 disable: false } } } } policy { policy-statement block { term bgp_65503 { from { protocol: "bgp" } then { accept } } } } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080401/9a9ded33/attachment.html From yueli.m at gmail.com Tue Apr 1 14:55:43 2008 From: yueli.m at gmail.com (Yue Li) Date: Tue, 1 Apr 2008 17:55:43 -0400 Subject: [Xorp-users] Routes redistribution between OSPF and BGP In-Reply-To: <82941.1207016116@tigger.icir.org> References: <49567c360803272139k5244b0ds4df50a14f5218e54@mail.gmail.com> <82941.1207016116@tigger.icir.org> Message-ID: <49567c360804011455w5092e8base6615891bd6c2204@mail.gmail.com> Hi, Atanu I have this working now. And then I want to redistributing routes from BGP (learned from eBGP peers) to OSPF, I use this configurations on an AS border router: policy { network4-list myroutes { network 10.0.0.0/30 network 10.0.0.16/30 } policy-statement ospf_out { term 100 { from { protocol: "connected" } } } policy-statement bgp_out { term 200 { from { protocol: "ospf4" } to { neighbor: 10.0.0.6 /* not advertising OSPF routes to iBGP peers */ } then { reject } } term 300 { from { protocol: "connected" network4-list: "myroutes" } to { neighbor: 10.0.0.6 } then { reject } } } policy-statement bgp2ospf { term 400 { from { protocol: "bgp" neighbor: 10.0.0.66 /* eBGP peer */ } then { accept } } } } But this doesn't work. Could you point out how to config correctly? Thanks! On Mon, Mar 31, 2008 at 10:15 PM, Atanu Ghosh wrote: > Hi, > > When redistributing routes from OSPF to BGP only the routes that OSPF > has learned from its neighbours will be redistributed. The connected > routes will not be redistributed, so you are correct you also need to > redistribute connected. > > > Atanu. > From M.Handley at cs.ucl.ac.uk Wed Apr 2 00:11:29 2008 From: M.Handley at cs.ucl.ac.uk (Mark Handley) Date: Wed, 2 Apr 2008 08:11:29 +0100 Subject: [Xorp-users] 2 BGP Peers Simultaneously In-Reply-To: <9FDF44CB3E9C9943B656E85501CF36FA022BF165@IMCSRV1.MITRE.ORG> References: <9FDF44CB3E9C9943B656E85501CF36FA022BF165@IMCSRV1.MITRE.ORG> Message-ID: <84a612dd0804020011n45b15419kc4c9c5a4c4c4aeb1@mail.gmail.com> Was there something you were trying to do with the policy statement? If you remove that, does it make any difference? - Mark On Tue, Apr 1, 2008 at 7:50 PM, Che, Ting-Shuo T. wrote: > > > Installed XORP on Linux PC, started "./xorp_rtrmgr -b ipv6bgp.boot" > (2000::1) and then connect to > test equipment representing 2 BGP peers (2000::2 and 2000::3) with a lot of > prefixes each. > > Both peers reached ESTABLISHED state in "show bgp peers detail" and started > route injection, but > only those prefixes from one peer (2000::3) shows up in "show bgp routes > ipv6" and "show route > table ipv6 unicast ebgp terse". > > Did I made mistake in the following configuration file? > > Thank you very much for your help. > > Ting Che > > /*XORP Configuration File, v1.0*/ > protocols { > bgp { > bgp-id: 192.168.2.3 > local-as: 65503 > enable-4byte-as-numbers: false > peer 2000::2 { > peer-port: 179 > local-port: 179 > local-ip: 2000::1 > as: 65504 > next-hop: 192.168.2.6 > next-hop6: 2000::1 > holdtime: 90 > delay-open-time: 0 > client: false > confederation-member: false > disable: false > ipv4-unicast: false > ipv4-multicast: false > ipv6-unicast: true > ipv6-multicast: false > } > peer 2000::3 { > peer-port: 179 > local-port: 179 > local-ip: 2000::1 > as: 65505 > next-hop: 192.168.2.6 > next-hop6: 2000::1 > holdtime: 90 > delay-open-time: 0 > client: false > confederation-member: false > disable: false > ipv4-unicast: false > ipv4-multicast: false > ipv6-unicast: true > ipv6-multicast: false > } > export: "block" > } > } > fea { > unicast-forwarding6 { > disable: false > } > } > interfaces { > restore-original-config-on-shutdown: false > interface eth0 { > description: "" > disable: false > discard: false > unreachable: false > management: false > vif eth0 { > disable: false > address 192.168.2.3 { > prefix-length: 24 > disable: false > } > address 2000::1 { > prefix-length: 64 > disable: false > } > address fe80::20f:1fff:fea8:70e4 { > prefix-length: 64 > disable: false > } > } > } > } > > policy { > policy-statement block { > term bgp_65503 { > from { > protocol: "bgp" > } > then { > accept > } > } > } > } > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > From tsche at mitre.org Thu Apr 3 02:20:58 2008 From: tsche at mitre.org (Che, Ting-Shuo T.) Date: Thu, 3 Apr 2008 05:20:58 -0400 Subject: [Xorp-users] 2 BGP Peers Simultaneously References: <9FDF44CB3E9C9943B656E85501CF36FA022BF165@IMCSRV1.MITRE.ORG> <84a612dd0804020011n45b15419kc4c9c5a4c4c4aeb1@mail.gmail.com> Message-ID: <9FDF44CB3E9C9943B656E85501CF36FA01CC28A6@IMCSRV1.MITRE.ORG> Hi Mark, Thanks a lot for getting back to me. Nothing particular with the policy statement, and it makes no difference. The XORP Linux PC (65503) is configured with IPv6 2000::1/64 and IPv4 192.168.2.3/24. One BGP peer (65504) has 2000::2/64 and 192.168.2.4/24. Another BGP peer (65505) has 2000::3/64 and 192.168.2.5/24. Had tried next-hop: 192.168.2.3, instead of 192.168.2.6, for both peer 2000::2 and 2000::3, but did not succeed either. Any other recommendation for the configuration? Ting Che ________________________________ From: mark.j.handley at gmail.com ?? Mark Handley Sent: 2008/4/2 [???] ?? 03:11 To: Che, Ting-Shuo T. Cc: xorp-users Subject: Re: [Xorp-users] 2 BGP Peers Simultaneously Was there something you were trying to do with the policy statement? If you remove that, does it make any difference? - Mark On Tue, Apr 1, 2008 at 7:50 PM, Che, Ting-Shuo T. wrote: > > > Installed XORP on Linux PC, started "./xorp_rtrmgr -b ipv6bgp.boot" > (2000::1) and then connect to > test equipment representing 2 BGP peers (2000::2 and 2000::3) with a lot of > prefixes each. > > Both peers reached ESTABLISHED state in "show bgp peers detail" and started > route injection, but > only those prefixes from one peer (2000::3) shows up in "show bgp routes > ipv6" and "show route > table ipv6 unicast ebgp terse". > > Did I made mistake in the following configuration file? > > Thank you very much for your help. > > Ting Che > > /*XORP Configuration File, v1.0*/ > protocols { > bgp { > bgp-id: 192.168.2.3 > local-as: 65503 > enable-4byte-as-numbers: false > peer 2000::2 { > peer-port: 179 > local-port: 179 > local-ip: 2000::1 > as: 65504 > next-hop: 192.168.2.6 > next-hop6: 2000::1 > holdtime: 90 > delay-open-time: 0 > client: false > confederation-member: false > disable: false > ipv4-unicast: false > ipv4-multicast: false > ipv6-unicast: true > ipv6-multicast: false > } > peer 2000::3 { > peer-port: 179 > local-port: 179 > local-ip: 2000::1 > as: 65505 > next-hop: 192.168.2.6 > next-hop6: 2000::1 > holdtime: 90 > delay-open-time: 0 > client: false > confederation-member: false > disable: false > ipv4-unicast: false > ipv4-multicast: false > ipv6-unicast: true > ipv6-multicast: false > } > export: "block" > } > } > fea { > unicast-forwarding6 { > disable: false > } > } > interfaces { > restore-original-config-on-shutdown: false > interface eth0 { > description: "" > disable: false > discard: false > unreachable: false > management: false > vif eth0 { > disable: false > address 192.168.2.3 { > prefix-length: 24 > disable: false > } > address 2000::1 { > prefix-length: 64 > disable: false > } > address fe80::20f:1fff:fea8:70e4 { > prefix-length: 64 > disable: false > } > } > } > } > > policy { > policy-statement block { > term bgp_65503 { > from { > protocol: "bgp" > } > then { > accept > } > } > } > } > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080403/cac950b0/attachment.html From johansson500 at gmail.com Thu Apr 3 03:37:43 2008 From: johansson500 at gmail.com (Mikael Johansson) Date: Thu, 3 Apr 2008 13:37:43 +0300 Subject: [Xorp-users] two BSRs Message-ID: I am trying to configure two BSRs so that one router is BSR for some multicast groups and another router is BSR for different multicast groups. Routers are connected like this: A --- B --- C Both Router B and Router C are defined as BSR candidates, Router B for 225.13.0.0/24 (eth1, 10.0.0.1) and Router C for 225.12.0.0/24 (eth1, 10.0.0.2). I would expect to see both 10.0.0.1 and 10.0.0.2 as BSRs on Router A, but command "show pim bootstrap" on Router A shows only one BSR: > show pim bootstrap Active zones: BSR Pri LocalAddress Pri State Timeout SZTimeout 10.0.0.2 1 0.0.0.0 0 AcceptPreferred 73 1243 Expiring zones: BSR Pri LocalAddress Pri State Timeout SZTimeout Configured zones: BSR Pri LocalAddress Pri State Timeout SZTimeout ---Router A--- interfaces { interface eth1 { default-system-config } } protocols { static { route 10.0.0.0/24 { next-hop: 11.0.0.1 } } } protocols { pimsm4 { interface eth1 { vif eth1 { } } interface register_vif { vif register_vif { } } bootstrap { } } } protocols { fib2mrib { } } plumbing { mfea4 { interface eth1 { vif eth1 { } } interface register_vif { vif register_vif { } } } } ---Router B--- interfaces { interface eth1 { default-system-config } interface eth2 { default-system-config } } protocols { pimsm4 { interface eth1 { vif eth1 { } } interface eth2 { vif eth2 { } } interface register_vif { vif register_vif { } } bootstrap { cand-bsr { scope-zone 225.13.0.0/24 { cand-bsr-by-vif-name: "eth1" } } } } } protocols { fib2mrib { } } plumbing { mfea4 { interface eth1 { vif eth1 { } } interface eth2 { vif eth2 { } } interface register_vif { vif register_vif { } } } } ---Router C--- interfaces { interface eth1 { default-system-config } } protocols { static { route 11.0.0.0/24 { next-hop: 10.0.0.1 } } } protocols { pimsm4 { interface eth1 { vif eth1 { } } interface register_vif { vif register_vif { } } bootstrap { cand-bsr { scope-zone 225.12.0.0/24 { cand-bsr-by-vif-name: "eth1" } } } } } protocols { fib2mrib { } } plumbing { mfea4 { interface eth1 { vif eth1 { } } interface register_vif { vif register_vif { } } } } From M.Handley at cs.ucl.ac.uk Thu Apr 3 03:43:52 2008 From: M.Handley at cs.ucl.ac.uk (Mark Handley) Date: Thu, 3 Apr 2008 11:43:52 +0100 Subject: [Xorp-users] 2 BGP Peers Simultaneously In-Reply-To: <9FDF44CB3E9C9943B656E85501CF36FA01CC28A6@IMCSRV1.MITRE.ORG> References: <9FDF44CB3E9C9943B656E85501CF36FA022BF165@IMCSRV1.MITRE.ORG> <84a612dd0804020011n45b15419kc4c9c5a4c4c4aeb1@mail.gmail.com> <9FDF44CB3E9C9943B656E85501CF36FA01CC28A6@IMCSRV1.MITRE.ORG> Message-ID: <84a612dd0804030343h314437d8s14aeeb04bb8d5bd6@mail.gmail.com> There are several possibilities, and it's hard to distinguish them from the information so far. - The connection isn't getting properly established. This seems unlikely, given show bgp peers indicates it's up. - The 2002::2 peer isn't happy with the connection and isn't sending you routes. - XORP is dropping routes from 2002::2 in the inbound filters for some reason. I can't see any obvious reason. - The 2002::2 peer prefers the routes from 2001::1 to its own routes. - There's a bug. This seems unlikely given how simple the config is. So, some questions: 1. Does 2002::2 think the peering is reaching established state? 2. Is 2002::2 receiving routes from 2001::1? As the peering is EBGP, it should be receiving routes that 2001::1 received from 2003::1 and forwarded. Now, if 2002::2 did receive all the routes from 2001::1 and preferred them to its own routes, then (depending on which BGP implentation it is) it might not resend your routes back to you, or it might send them back but you'd drop them due to the loop filter. Cheers, Mark On Thu, Apr 3, 2008 at 10:20 AM, Che, Ting-Shuo T. wrote: > > > > Hi Mark, > > Thanks a lot for getting back to me. Nothing particular with the policy > statement, and it makes no difference. The XORP Linux PC (65503) is > configured with IPv6 2000::1/64 and IPv4 192.168.2.3/24. One BGP peer > (65504) has 2000::2/64 and 192.168.2.4/24. Another BGP peer (65505) has > 2000::3/64 and 192.168.2.5/24. Had tried next-hop: 192.168.2.3, instead of > 192.168.2.6, for both peer 2000::2 and 2000::3, but did not succeed either. > Any other recommendation for the configuration? > > Ting Che > > ________________________________ > From: mark.j.handley at gmail.com ?? Mark Handley > Sent: 2008/4/2 [???] ?? 03:11 > To: Che, Ting-Shuo T. > Cc: xorp-users > Subject: Re: [Xorp-users] 2 BGP Peers Simultaneously > > > > > > Was there something you were trying to do with the policy statement? > If you remove that, does it make any difference? > > - Mark > > On Tue, Apr 1, 2008 at 7:50 PM, Che, Ting-Shuo T. wrote: > > > > > > Installed XORP on Linux PC, started "./xorp_rtrmgr -b ipv6bgp.boot" > > (2000::1) and then connect to > > test equipment representing 2 BGP peers (2000::2 and 2000::3) with a lot > of > > prefixes each. > > > > Both peers reached ESTABLISHED state in "show bgp peers detail" and > started > > route injection, but > > only those prefixes from one peer (2000::3) shows up in "show bgp routes > > ipv6" and "show route > > table ipv6 unicast ebgp terse". > > > > Did I made mistake in the following configuration file? > > > > Thank you very much for your help. > > > > Ting Che > > > > /*XORP Configuration File, v1.0*/ > > protocols { > > bgp { > > bgp-id: 192.168.2.3 > > local-as: 65503 > > enable-4byte-as-numbers: false > > peer 2000::2 { > > peer-port: 179 > > local-port: 179 > > local-ip: 2000::1 > > as: 65504 > > next-hop: 192.168.2.6 > > next-hop6: 2000::1 > > holdtime: 90 > > delay-open-time: 0 > > client: false > > confederation-member: false > > disable: false > > ipv4-unicast: false > > ipv4-multicast: false > > ipv6-unicast: true > > ipv6-multicast: false > > } > > peer 2000::3 { > > peer-port: 179 > > local-port: 179 > > local-ip: 2000::1 > > as: 65505 > > next-hop: 192.168.2.6 > > next-hop6: 2000::1 > > holdtime: 90 > > delay-open-time: 0 > > client: false > > confederation-member: false > > disable: false > > ipv4-unicast: false > > ipv4-multicast: false > > ipv6-unicast: true > > ipv6-multicast: false > > } > > export: "block" > > } > > } > > fea { > > unicast-forwarding6 { > > disable: false > > } > > } > > interfaces { > > restore-original-config-on-shutdown: false > > interface eth0 { > > description: "" > > disable: false > > discard: false > > unreachable: false > > management: false > > vif eth0 { > > disable: false > > address 192.168.2.3 { > > prefix-length: 24 > > disable: false > > } > > address 2000::1 { > > prefix-length: 64 > > disable: false > > } > > address fe80::20f:1fff:fea8:70e4 { > > prefix-length: 64 > > disable: false > > } > > } > > } > > } > > > > policy { > > policy-statement block { > > term bgp_65503 { > > from { > > protocol: "bgp" > > } > > then { > > accept > > } > > } > > } > > } > > > > _______________________________________________ > > Xorp-users mailing list > > Xorp-users at xorp.org > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > > From pavlin at ICSI.Berkeley.EDU Fri Apr 4 00:10:55 2008 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Fri, 04 Apr 2008 00:10:55 -0700 Subject: [Xorp-users] two BSRs In-Reply-To: References: Message-ID: <200804040710.m347AtNP021800@fruitcake.ICSI.Berkeley.EDU> Mikael Johansson wrote: > I am trying to configure two BSRs so that one router is BSR for some > multicast groups and another router is BSR for different multicast > groups. > > Routers are connected like this: > > A --- B --- C > > Both Router B and Router C are defined as BSR candidates, Router B for > 225.13.0.0/24 (eth1, 10.0.0.1) and Router C for 225.12.0.0/24 (eth1, > 10.0.0.2). > > I would expect to see both 10.0.0.1 and 10.0.0.2 as BSRs on Router A, > but command "show pim bootstrap" on Router A shows only one BSR: You need to check the following: * Are the Bootstrap messages from C forwarded by B on the A-B subnet. For that purpose you need to use a tool like tcpdump or wireshark that understands the Bootstrap messages format so you could match the content. Note that the Bootstrap messages are processed hop-by-hop such that only the payload of the message is preserved, but the IP header is replaced (i.e., the src IP address won't match the BSR IP address). * Check that the (unicast) reverse-path forwarding information in A points to B as the next-hop toward C. * Check for any suspicious warning or error messages in the XORP log output. Pavlin > > show pim bootstrap > Active zones: > BSR Pri LocalAddress Pri State Timeout SZTimeout > 10.0.0.2 1 0.0.0.0 0 AcceptPreferred 73 1243 > Expiring zones: > BSR Pri LocalAddress Pri State Timeout SZTimeout > Configured zones: > BSR Pri LocalAddress Pri State Timeout SZTimeout > > > > ---Router A--- > > interfaces { > interface eth1 { > default-system-config > } > } > > protocols { > static { > route 10.0.0.0/24 { > next-hop: 11.0.0.1 > } > } > } > > protocols { > pimsm4 { > interface eth1 { > vif eth1 { > } > } > > interface register_vif { > vif register_vif { > } > } > > bootstrap { > } > } > } > > protocols { > fib2mrib { > } > } > > plumbing { > mfea4 { > interface eth1 { > vif eth1 { > } > } > interface register_vif { > vif register_vif { > } > } > } > } > > > ---Router B--- > > interfaces { > interface eth1 { > default-system-config > } > interface eth2 { > default-system-config > } > } > > protocols { > pimsm4 { > interface eth1 { > vif eth1 { > } > } > > interface eth2 { > vif eth2 { > } > } > > interface register_vif { > vif register_vif { > } > } > > bootstrap { > cand-bsr { > scope-zone 225.13.0.0/24 { > cand-bsr-by-vif-name: "eth1" > } > } > } > } > } > > protocols { > fib2mrib { > } > } > > plumbing { > mfea4 { > interface eth1 { > vif eth1 { > } > } > interface eth2 { > vif eth2 { > } > } > interface register_vif { > vif register_vif { > } > } > } > } > > > ---Router C--- > > interfaces { > interface eth1 { > default-system-config > } > } > > protocols { > static { > route 11.0.0.0/24 { > next-hop: 10.0.0.1 > } > } > } > > protocols { > pimsm4 { > interface eth1 { > vif eth1 { > } > } > > interface register_vif { > vif register_vif { > } > } > > bootstrap { > cand-bsr { > scope-zone 225.12.0.0/24 { > cand-bsr-by-vif-name: "eth1" > } > } > } > } > } > > protocols { > fib2mrib { > } > } > > plumbing { > mfea4 { > interface eth1 { > vif eth1 { > } > } > interface register_vif { > vif register_vif { > } > } > > } > } > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at ICSI.Berkeley.EDU Fri Apr 4 08:56:24 2008 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Fri, 04 Apr 2008 08:56:24 -0700 Subject: [Xorp-users] two BSRs In-Reply-To: <200804040710.m347AtNP021800@fruitcake.ICSI.Berkeley.EDU> References: <200804040710.m347AtNP021800@fruitcake.ICSI.Berkeley.EDU> Message-ID: <200804041556.m34FuOVt029987@fruitcake.ICSI.Berkeley.EDU> > You need to check the following: > > * Are the Bootstrap messages from C forwarded by B on the > A-B subnet. > For that purpose you need to use a tool like tcpdump or > wireshark that understands the Bootstrap messages format so you > could match the content. Note that the Bootstrap messages are > processed hop-by-hop such that only the payload of the message is > preserved, but the IP header is replaced (i.e., the src IP address > won't match the BSR IP address). > > * Check that the (unicast) reverse-path forwarding information in A > points to B as the next-hop toward C. Forgot to mention that the xorpsh command for this check is: show pim mrib Pavlin > * Check for any suspicious warning or error messages in the XORP log > output. From pavlin at ICSI.Berkeley.EDU Fri Apr 4 09:24:12 2008 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Fri, 04 Apr 2008 09:24:12 -0700 Subject: [Xorp-users] two BSRs In-Reply-To: <200804040710.m347AtNP021800@fruitcake.ICSI.Berkeley.EDU> References: <200804040710.m347AtNP021800@fruitcake.ICSI.Berkeley.EDU> Message-ID: <200804041624.m34GOCox006421@fruitcake.ICSI.Berkeley.EDU> Pavlin Radoslavov wrote: > Mikael Johansson wrote: > > > I am trying to configure two BSRs so that one router is BSR for some > > multicast groups and another router is BSR for different multicast > > groups. > > > > Routers are connected like this: > > > > A --- B --- C > > > > Both Router B and Router C are defined as BSR candidates, Router B for > > 225.13.0.0/24 (eth1, 10.0.0.1) and Router C for 225.12.0.0/24 (eth1, > > 10.0.0.2). > > > > I would expect to see both 10.0.0.1 and 10.0.0.2 as BSRs on Router A, > > but command "show pim bootstrap" on Router A shows only one BSR: > > You need to check the following: > > * Are the Bootstrap messages from C forwarded by B on the > A-B subnet. > For that purpose you need to use a tool like tcpdump or > wireshark that understands the Bootstrap messages format so you > could match the content. Note that the Bootstrap messages are > processed hop-by-hop such that only the payload of the message is > preserved, but the IP header is replaced (i.e., the src IP address > won't match the BSR IP address). > > * Check that the (unicast) reverse-path forwarding information in A > points to B as the next-hop toward C. > > * Check for any suspicious warning or error messages in the XORP log > output. Ignore the above. On second thought, I think the problem is that inside your "scope-zone {}" nodes you must set "is-scope-zone: true", because it is false by default. For reason for that is according to the PIM BSR spec there is one BSR state machine per scope zone. If a configured zone's "is-scope-zone" flag is false, then it automatically belongs to the global 224.0.0.0/4 non-scoped zone. I.e., in your configuration both configured entries for 225.13.0.0/24 and 225.12.0.0/24 will be controlled by the same state machine. Setting the "is-scope-zone" flag to true for at least one of them will put them on separate state machines, but a good practice would be to enable the "is-scope-zone" flag for both of them. Please let me know whether this fixes the problem. Pavlin > Pavlin > > > > show pim bootstrap > > Active zones: > > BSR Pri LocalAddress Pri State Timeout SZTimeout > > 10.0.0.2 1 0.0.0.0 0 AcceptPreferred 73 1243 > > Expiring zones: > > BSR Pri LocalAddress Pri State Timeout SZTimeout > > Configured zones: > > BSR Pri LocalAddress Pri State Timeout SZTimeout > > > > > > > > ---Router A--- > > > > interfaces { > > interface eth1 { > > default-system-config > > } > > } > > > > protocols { > > static { > > route 10.0.0.0/24 { > > next-hop: 11.0.0.1 > > } > > } > > } > > > > protocols { > > pimsm4 { > > interface eth1 { > > vif eth1 { > > } > > } > > > > interface register_vif { > > vif register_vif { > > } > > } > > > > bootstrap { > > } > > } > > } > > > > protocols { > > fib2mrib { > > } > > } > > > > plumbing { > > mfea4 { > > interface eth1 { > > vif eth1 { > > } > > } > > interface register_vif { > > vif register_vif { > > } > > } > > } > > } > > > > > > ---Router B--- > > > > interfaces { > > interface eth1 { > > default-system-config > > } > > interface eth2 { > > default-system-config > > } > > } > > > > protocols { > > pimsm4 { > > interface eth1 { > > vif eth1 { > > } > > } > > > > interface eth2 { > > vif eth2 { > > } > > } > > > > interface register_vif { > > vif register_vif { > > } > > } > > > > bootstrap { > > cand-bsr { > > scope-zone 225.13.0.0/24 { > > cand-bsr-by-vif-name: "eth1" > > } > > } > > } > > } > > } > > > > protocols { > > fib2mrib { > > } > > } > > > > plumbing { > > mfea4 { > > interface eth1 { > > vif eth1 { > > } > > } > > interface eth2 { > > vif eth2 { > > } > > } > > interface register_vif { > > vif register_vif { > > } > > } > > } > > } > > > > > > ---Router C--- > > > > interfaces { > > interface eth1 { > > default-system-config > > } > > } > > > > protocols { > > static { > > route 11.0.0.0/24 { > > next-hop: 10.0.0.1 > > } > > } > > } > > > > protocols { > > pimsm4 { > > interface eth1 { > > vif eth1 { > > } > > } > > > > interface register_vif { > > vif register_vif { > > } > > } > > > > bootstrap { > > cand-bsr { > > scope-zone 225.12.0.0/24 { > > cand-bsr-by-vif-name: "eth1" > > } > > } > > } > > } > > } > > > > protocols { > > fib2mrib { > > } > > } > > > > plumbing { > > mfea4 { > > interface eth1 { > > vif eth1 { > > } > > } > > interface register_vif { > > vif register_vif { > > } > > } > > > > } > > } > > > > _______________________________________________ > > Xorp-users mailing list > > Xorp-users at xorp.org > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From atanu at ICSI.Berkeley.EDU Tue Apr 8 19:06:41 2008 From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh) Date: Tue, 08 Apr 2008 19:06:41 -0700 Subject: [Xorp-users] Routes redistribution between OSPF and BGP In-Reply-To: Message from "Yue Li" of "Tue, 01 Apr 2008 17:55:43 EDT." <49567c360804011455w5092e8base6615891bd6c2204@mail.gmail.com> Message-ID: <93835.1207706801@tigger.icir.org> Hi, I tried your configuration between two BGP routers, the remote BGP router is announcing 10.10.10.0/24. Xorp> show bgp routes Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ------ ------- ---- ------- *> 10.10.10.0/24 192.168.1.40 192.168.1.40 65002 i Xorp> show ospf4 database OSPF link state database, Area 0.0.0.0 Type ID Adv Rtr Seq Age Opt Cksum Len Router *192.168.1.144 192.168.1.144 0x80000001 249 0x2 0x9d52 36 ASExt-2 *192.168.1.0 192.168.1.144 0x80000001 249 0x2 0xd49d 36 ASExt-2 *10.10.10.0 192.168.1.144 0x80000001 249 0x2 0x72b4 36 The incoming eBGP route is redistributed to OSPF, I have attached the whole config file. Atanu. ---------------------------------------- interfaces { restore-original-config-on-shutdown: true interface em0 { vif em0 { address 192.168.1.144 { prefix-length: 24 } } } } protocols { bgp { bgp-id: 192.168.1.144 local-as: 65001 export "bgp_out" peer 192.168.1.40 { local-ip: 192.168.1.144 as: 65002 next-hop: 192.168.1.144 } } } protocols { ospf4 { router-id: 192.168.1.144 export "bgp2ospf,ospf_out" area 0.0.0.0 { interface em0 { vif em0 { address 192.168.1.144 { } } } } } } policy { network4-list myroutes { network 10.0.0.0/30 network 10.0.0.16/30 } policy-statement ospf_out { term 100 { from { protocol: "connected" } } } policy-statement bgp_out { term 200 { from { protocol: "ospf4" } to { neighbor: 10.0.0.6 /* not advertising OSPF routes to iBGP peers */ } then { reject } } term 300 { from { protocol: "connected" network4-list: "myroutes" } to { neighbor: 10.0.0.6 } then { reject } } } policy-statement bgp2ospf { term 400 { from { protocol: "bgp" neighbor: 192.168.1.40 /* eBGP peer */ } then { accept } } } } ---------------------------------------- >>>>> "Yue" == Yue Li writes: Yue> Hi, Atanu Yue> I have this working now. Yue> And then I want to redistributing routes from BGP (learned from eBGP Yue> peers) to OSPF, I use this configurations on an AS border router: Yue> policy { Yue> network4-list myroutes { Yue> network 10.0.0.0/30 Yue> network 10.0.0.16/30 Yue> } Yue> policy-statement ospf_out { Yue> term 100 { Yue> from { Yue> protocol: "connected" Yue> } Yue> } Yue> } Yue> policy-statement bgp_out { Yue> term 200 { Yue> from { Yue> protocol: "ospf4" Yue> } Yue> to { Yue> neighbor: 10.0.0.6 /* not advertising OSPF routes to iBGP peers */ Yue> } Yue> then { Yue> reject Yue> } Yue> } Yue> term 300 { Yue> from { Yue> protocol: "connected" Yue> network4-list: "myroutes" Yue> } Yue> to { Yue> neighbor: 10.0.0.6 Yue> } Yue> then { Yue> reject Yue> } Yue> } Yue> } Yue> policy-statement bgp2ospf { Yue> term 400 { Yue> from { Yue> protocol: "bgp" Yue> neighbor: 10.0.0.66 /* eBGP peer */ Yue> } Yue> then { Yue> accept Yue> } Yue> } Yue> } Yue> } Yue> But this doesn't work. Could you point out how to config correctly? Yue> Thanks! Yue> On Mon, Mar 31, 2008 at 10:15 PM, Atanu Ghosh wrote: >> Hi, >> >> When redistributing routes from OSPF to BGP only the routes that OSPF >> has learned from its neighbours will be redistributed. The connected >> routes will not be redistributed, so you are correct you also need to >> redistribute connected. >> >> >> Atanu. >> From johansson500 at gmail.com Thu Apr 10 06:08:29 2008 From: johansson500 at gmail.com (Mikael Johansson) Date: Thu, 10 Apr 2008 16:08:29 +0300 Subject: [Xorp-users] two BSRs In-Reply-To: <200804041624.m34GOCox006421@fruitcake.ICSI.Berkeley.EDU> References: <200804040710.m347AtNP021800@fruitcake.ICSI.Berkeley.EDU> <200804041624.m34GOCox006421@fruitcake.ICSI.Berkeley.EDU> Message-ID: On Fri, Apr 4, 2008 at 7:24 PM, Pavlin Radoslavov wrote: > > Pavlin Radoslavov wrote: > > > Mikael Johansson wrote: > > > > > I am trying to configure two BSRs so that one router is BSR for some > > > multicast groups and another router is BSR for different multicast > > > groups. > > > > > > Routers are connected like this: > > > > > > A --- B --- C > > > > > > Both Router B and Router C are defined as BSR candidates, Router B for > > > 225.13.0.0/24 (eth1, 10.0.0.1) and Router C for 225.12.0.0/24 (eth1, > > > 10.0.0.2). > > > > > > I would expect to see both 10.0.0.1 and 10.0.0.2 as BSRs on Router A, > > > but command "show pim bootstrap" on Router A shows only one BSR: > > > > You need to check the following: > > > > * Are the Bootstrap messages from C forwarded by B on the > > A-B subnet. > > For that purpose you need to use a tool like tcpdump or > > wireshark that understands the Bootstrap messages format so you > > could match the content. Note that the Bootstrap messages are > > processed hop-by-hop such that only the payload of the message is > > preserved, but the IP header is replaced (i.e., the src IP address > > won't match the BSR IP address). > > > > * Check that the (unicast) reverse-path forwarding information in A > > points to B as the next-hop toward C. > > > > * Check for any suspicious warning or error messages in the XORP log > > output. > > Ignore the above. > On second thought, I think the problem is that inside your > "scope-zone {}" nodes you must set "is-scope-zone: true", > because it is false by default. > > For reason for that is according to the PIM BSR spec there is one > BSR state machine per scope zone. > If a configured zone's "is-scope-zone" flag is false, then it > automatically belongs to the global 224.0.0.0/4 non-scoped zone. > I.e., in your configuration both configured entries for > 225.13.0.0/24 and 225.12.0.0/24 will be controlled by the same state > machine. > > Setting the "is-scope-zone" flag to true for at least one of them > will put them on separate state machines, but a good practice would > be to enable the "is-scope-zone" flag for both of them. > > Please let me know whether this fixes the problem. > > Pavlin I set "is-scope-zone" flag to true, and now I see both BSRs on Router A. Thanks, Mikael From yueli.m at gmail.com Thu Apr 10 16:52:35 2008 From: yueli.m at gmail.com (Yue Li) Date: Thu, 10 Apr 2008 19:52:35 -0400 Subject: [Xorp-users] BGP terminated Message-ID: <49567c360804101652m6c92bd78tbf0c5203e4cb5a12@mail.gmail.com> Hi, All The BGP module is terminated with signal 6. The error messages are listed below. I run eight BGP speakers with similar config files, only one is terminated abnormally, others run well. Could anyone give some clues? [ 2008/04/10 17:01:47 FATAL xorp_bgp:12244 BGP +465 route_table_decision.cc find_alternative_routes ] Assertion (previous_winner == NULL) failed [ 2008/04/10 17:01:47 INFO xorp_rib RIB ] Received death event for protocol bgp shutting down ------- OriginTable: ebgp EGP next table = Merged:(ebgp)+(ibgp) [ 2008/04/10 17:01:47 INFO xorp_rib RIB ] Received death event for protocol bgp shutting down ------- OriginTable: ebgp EGP next table = Merged:(ebgp)+(ibgp) [ 2008/04/10 17:01:47 INFO xorp_rib RIB ] Received death event for protocol bgp shutting down ------- OriginTable: ebgp EGP next table = Merged:(ebgp)+(ibgp) [ 2008/04/10 17:01:47 INFO xorp_rib RIB ] Received death event for protocol bgp shutting down ------- OriginTable: ebgp EGP next table = Merged:(ebgp)+(ibgp) From ssohn at gmu.edu Tue Apr 15 13:37:32 2008 From: ssohn at gmu.edu (Eric Sohn) Date: Tue, 15 Apr 2008 16:37:32 -0400 Subject: [Xorp-users] running xorp+click Message-ID: <001a01c89f38$88241470$986c3d50$@edu> Hello, I am a newbie in xorp. I am trying to run xorp with click on emulab.net. I hope somebody can resolve the error. I attach the boot file and error message. NW topology is organized with 2 routers and 2 end systems. 2 routers are using xorp + click with RIP. Each router has two interfaces and each end system has one interface. Linking is source - r1 - r2 - sink Followings are the content of boot file; ---------------------------------------------------------------------------- --- interfaces{ restore-original-config-on-shutdown: false interface eth2 { disable: false default-system-config } interface eth5 { disable: false default-system-config } } /* */ fea{ unicast-forwarding4 { disable: false } unicast-forwarding6 { disable: true } click { disable: false duplicate-routes-to-kernel: true kernel-click{ disable: true } user-click{ disable: false command-file: "/users/ssohn/click/bin/click" command-extra-arguments: "-R" command-execute-on-startup: true control-address: 127.0.0.1 control-socket-port: 13000 startup-config-file: "/dev/null" user-click-config-generator-file: "/tmp/xorp-1.4/fea/xorp_fea_click_config_generator" <- no change in this file } } } /* */ protocols { static { route 10.1.1.0/24 { next-hop: 10.1.1.2 metric: 1 } route 10.1.3.0/24 { next-hop: 10.1.1.2 metric: 1 } mrib-route 10.1.1.0/24 { next-hop: 10.1.1.2 metric: 1 } mrib-route 10.1.3.0/24 { next-hop: 10.1.1.2 metric: 1 } } } protocols { rip { export connected { metric: 0 tag: 0 } export static { metric: 1 tag: 0 } interface eth2 { vif eth2 { address 10.1.2.2 { disable: false } } } interface eth5 { vif eth5 { address 10.1.1.3 { disable: false } } } } } ---------------------------------------------------------------------------- ------------------------------------- When I run this boot file, I got error message as follows; [ssohn at r2 ~/2routers]$ sudo /tmp/xorp-1.4/rtrmgr/xorp_rtrmgr -b ~/2routers/R2.boot.rip [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +239 master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, policy, rip, static_routes [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started [ 2008/04/15 14:14:52 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2008/04/15 14:14:57 ERROR xorp_fea:4312 FEA +777 ifconfig_set_click.cc click_config_generator_done ] Failed to write the Click configuration: User-level Click command error: 520-Write handler 'hotconfig' error: 520-:10: While configuring 'Print at 15 :: Print': 520- argument 1 takes string (label) 520-:17: While configuring 'Print at 27 :: Print': 520- argument 1 takes string (label) 520 Router could not be initialized! [ 2008/04/15 14:14:59 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc execute ] Executing module: rib (rib/xorp_rib) [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing port number for the Click forwarding table element to add entry net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = true [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71 fti_transaction.cc operation_result ] FTI transaction commit failed on AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = true [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing port number for the Click forwarding table element to add entry net = 10.1.1.0/24 nexthop = 10.1.1.3 ifname = eth5 vifname = eth5 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = true [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling method for redist_transaction4/0.1/commit_transaction failed: XrlCmdError 102 Command failed AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = true [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc dispatch_complete ] Failed to commit transaction: 102 Command failed AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = true [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing port number for the Click forwarding table element to add entry net = fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = true [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71 fti_transaction.cc operation_result ] FTI transaction commit failed on AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = true [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling method for redist_transaction6/0.1/commit_transaction failed: XrlCmdError 102 Command failed AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = true [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc dispatch_complete ] Failed to commit transaction: 102 Command failed AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = true [ 2008/04/15 14:15:01 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc execute ] Executing module: policy (policy/xorp_policy) [ 2008/04/15 14:15:03 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc execute ] Executing module: rip (rip/xorp_rip) [ 2008/04/15 14:15:05 WARNING xorp_policy:4317 XrlPolicyTarget +567 policy_base.cc handle_policy_0_1_export ] Handling method for policy/0.1/export failed: XrlCmdError 102 Command failed Export of rip failed: ConfError from line 179 of configuration.cc: exports: Protocol rip unknown [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +675 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Export of rip failed: ConfError from line 179 of configuration.cc: exports: Protocol rip unknown [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +251 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Export of rip failed: ConfError from line 179 of configuration.cc: exports: Protocol rip unknown [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +2228 task.cc run_task ] No more tasks to run [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc terminate ] Terminating module: fea [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc terminate ] Terminating module: interfaces [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 module_manager.cc terminate ] Killing module: interfaces [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc terminate ] Terminating module: policy [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 module_manager.cc terminate ] Killing module: policy [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc terminate ] Terminating module: rib [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 module_manager.cc terminate ] Killing module: rib [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc terminate ] Terminating module: rip [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 module_manager.cc terminate ] Killing module: rip [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 module_manager.cc done_cb ] Command "/tmp/xorp-1.4/rib/xorp_rib": terminated with signal 15. [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 module_manager.cc module_exited ] Module killed during shutdown: rib [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 module_manager.cc done_cb ] Command "/tmp/xorp-1.4/policy/xorp_policy": terminated with signal 15. [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 module_manager.cc module_exited ] Module killed during shutdown: policy [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 module_manager.cc done_cb ] Command "/tmp/xorp-1.4/rip/xorp_rip": terminated with signal 15. [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 module_manager.cc module_exited ] Module killed during shutdown: rip [ 2008/04/15 14:15:07 INFO xorp_rtrmgr:4310 RTRMGR +233 module_manager.cc terminate_with_prejudice ] Killing module with prejudice: interfaces Plz plz help me out. Thank you in advance. Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080415/33f8de49/attachment-0001.html From pavlin at ICSI.Berkeley.EDU Tue Apr 15 13:55:35 2008 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Tue, 15 Apr 2008 13:55:35 -0700 Subject: [Xorp-users] running xorp+click In-Reply-To: <001a01c89f38$88241470$986c3d50$@edu> References: <001a01c89f38$88241470$986c3d50$@edu> Message-ID: <200804152055.m3FKtZRb003271@fruitcake.ICSI.Berkeley.EDU> Eric Sohn wrote: > Hello, > > > > I am a newbie in xorp. > > I am trying to run xorp with click on emulab.net. > > I hope somebody can resolve the error. > > I attach the boot file and error message. What Click version are you using? Admitably, the support for newer Click releases is lagging behind. Could you try some of the following: * Use explicit interface configuration in the "interfaces" section instead of using the "default-system-config" statement; i.e., explicitly add the vif and IP address information to the XORP configuration. * Use the latest XORP code from anon. CVS: http://www.xorp.org/cvs.html * Use an older Click version. If I remember correctly, originally we had XORP working with Click-1.4.3 (and/or Click-1.4.2?). Regards, Pavlin > NW topology is organized with 2 routers and 2 end systems. 2 routers are > using xorp + click with RIP. > > Each router has two interfaces and each end system has one interface. > > Linking is source - r1 - r2 - sink > > > > Followings are the content of boot file; > > ---------------------------------------------------------------------------- > --- > > interfaces{ > > restore-original-config-on-shutdown: false > > interface eth2 { > > disable: false > > default-system-config > > } > > interface eth5 { > > disable: false > > default-system-config > > } > > } /* */ > > > > fea{ > > unicast-forwarding4 { > > disable: false > > } > > > > unicast-forwarding6 { > > disable: true > > } > > > > click { > > disable: false > > duplicate-routes-to-kernel: true > > > > kernel-click{ > > disable: true > > } > > > > user-click{ > > disable: false > > command-file: "/users/ssohn/click/bin/click" > > command-extra-arguments: "-R" > > command-execute-on-startup: true > > control-address: 127.0.0.1 > > control-socket-port: 13000 > > startup-config-file: "/dev/null" > > user-click-config-generator-file: > "/tmp/xorp-1.4/fea/xorp_fea_click_config_generator" <- no change in this > file > > } > > } > > > > } /* */ > > > > protocols { > > static { > > route 10.1.1.0/24 { > > next-hop: 10.1.1.2 > > metric: 1 > > } > > route 10.1.3.0/24 { > > next-hop: 10.1.1.2 > > metric: 1 > > } > > mrib-route 10.1.1.0/24 { > > next-hop: 10.1.1.2 > > metric: 1 > > } > > mrib-route 10.1.3.0/24 { > > next-hop: 10.1.1.2 > > metric: 1 > > } > > } > > } > > > > protocols { > > rip { > > export connected { > > metric: 0 > > tag: 0 > > } > > export static { > > metric: 1 > > tag: 0 > > } > > interface eth2 { > > vif eth2 { > > address 10.1.2.2 { > > disable: false > > } > > } > > } > > interface eth5 { > > vif eth5 { > > address 10.1.1.3 { > > disable: false > > } > > } > > } > > } > > } > > ---------------------------------------------------------------------------- > ------------------------------------- > > > > > > When I run this boot file, I got error message as follows; > > > > [ssohn at r2 ~/2routers]$ sudo /tmp/xorp-1.4/rtrmgr/xorp_rtrmgr -b > ~/2routers/R2.boot.rip > > [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +239 master_conf_tree.cc > execute ] Changed modules: interfaces, fea, rib, policy, rip, static_routes > > [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc > execute ] Executing module: interfaces (fea/xorp_fea) > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started > > [ 2008/04/15 14:14:52 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc > execute ] Executing module: fea (fea/xorp_fea) > > [ 2008/04/15 14:14:57 ERROR xorp_fea:4312 FEA +777 ifconfig_set_click.cc > click_config_generator_done ] Failed to write the Click configuration: > User-level Click command error: 520-Write handler 'hotconfig' error: > > 520-:10: While configuring 'Print at 15 :: Print': > > 520- argument 1 takes string (label) > > 520-:17: While configuring 'Print at 27 :: Print': > > 520- argument 1 takes string (label) > > 520 Router could not be initialized! > > [ 2008/04/15 14:14:59 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc > execute ] Executing module: rib (rib/xorp_rib) > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing port number > for the Click forwarding table element to add entry net = 10.1.2.0/24 > nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 metric = 0 admin_distance = > 0 xorp_route = true is_deleted = false is_unresolved = false > is_connected_route = true > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71 fti_transaction.cc > operation_result ] FTI transaction commit failed on AddEntry4: net = > 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 metric = 0 > admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = > false is_connected_route = true > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing port number > for the Click forwarding table element to add entry net = 10.1.1.0/24 > nexthop = 10.1.1.3 ifname = eth5 vifname = eth5 metric = 0 admin_distance = > 0 xorp_route = true is_deleted = false is_unresolved = false > is_connected_route = true > > [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling method for > redist_transaction4/0.1/commit_transaction failed: XrlCmdError 102 Command > failed AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname > = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = false > is_unresolved = false is_connected_route = true > > [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc > dispatch_complete ] Failed to commit transaction: 102 Command failed > AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 > metric = 0 admin_distance = 0 xorp_route = true is_deleted = false > is_unresolved = false is_connected_route = true > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing port number > for the Click forwarding table element to add entry net = fe80::/64 nexthop > = fe80::204:23ff:feb7:26dc ifname = eth2 vifname = eth2 metric = 0 > admin_distance = 0 xorp_route = true is_deleted = false is_unresolved = > false is_connected_route = true > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71 fti_transaction.cc > operation_result ] FTI transaction commit failed on AddEntry6: net = > fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname = eth2 vifname = eth2 > metric = 0 admin_distance = 0 xorp_route = true is_deleted = false > is_unresolved = false is_connected_route = true > > [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling method for > redist_transaction6/0.1/commit_transaction failed: XrlCmdError 102 Command > failed AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname > = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true > is_deleted = false is_unresolved = false is_connected_route = true > > [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc > dispatch_complete ] Failed to commit transaction: 102 Command failed > AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname = eth2 > vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true is_deleted = > false is_unresolved = false is_connected_route = true > > [ 2008/04/15 14:15:01 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc > execute ] Executing module: policy (policy/xorp_policy) > > [ 2008/04/15 14:15:03 INFO xorp_rtrmgr:4310 RTRMGR +96 module_manager.cc > execute ] Executing module: rip (rip/xorp_rip) > > [ 2008/04/15 14:15:05 WARNING xorp_policy:4317 XrlPolicyTarget +567 > policy_base.cc handle_policy_0_1_export ] Handling method for > policy/0.1/export failed: XrlCmdError 102 Command failed Export of rip > failed: ConfError from line 179 of configuration.cc: exports: Protocol rip > unknown > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +675 > master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed > Export of rip failed: ConfError from line 179 of configuration.cc: exports: > Protocol rip unknown > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +251 > master_conf_tree.cc config_done ] Configuration failed: 102 Command failed > Export of rip failed: ConfError from line 179 of configuration.cc: exports: > Protocol rip unknown > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +2228 task.cc run_task ] > No more tasks to run > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc > terminate ] Terminating module: fea > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc > terminate ] Terminating module: interfaces > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 module_manager.cc > terminate ] Killing module: interfaces > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc > terminate ] Terminating module: policy > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 module_manager.cc > terminate ] Killing module: policy > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc > terminate ] Terminating module: rib > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 module_manager.cc > terminate ] Killing module: rib > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 module_manager.cc > terminate ] Terminating module: rip > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 module_manager.cc > terminate ] Killing module: rip > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 module_manager.cc > done_cb ] Command "/tmp/xorp-1.4/rib/xorp_rib": terminated with signal 15. > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 module_manager.cc > module_exited ] Module killed during shutdown: rib > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 module_manager.cc > done_cb ] Command "/tmp/xorp-1.4/policy/xorp_policy": terminated with signal > 15. > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 module_manager.cc > module_exited ] Module killed during shutdown: policy > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 module_manager.cc > done_cb ] Command "/tmp/xorp-1.4/rip/xorp_rip": terminated with signal 15. > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 module_manager.cc > module_exited ] Module killed during shutdown: rip > > [ 2008/04/15 14:15:07 INFO xorp_rtrmgr:4310 RTRMGR +233 module_manager.cc > terminate_with_prejudice ] Killing module with prejudice: interfaces > > > > > > > > Plz plz help me out. > > > > > > Thank you in advance. > > > > Eric > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From ssohn at gmu.edu Thu Apr 17 19:46:49 2008 From: ssohn at gmu.edu (Soon-Yong Sohn) Date: Thu, 17 Apr 2008 22:46:49 -0400 Subject: [Xorp-users] Xorp-users Digest, Vol 25, Issue 9 In-Reply-To: References: Message-ID: Thank you for the reply. I did all three as you mentioned, update xorp through cvs, install old version (1.4.3) of click, specify interfaces in detail. It makes some change in running xorp+click. However, I got another error message at router as follows; ----------------------------------------------------------------------------------- [ 2008/04/17 20:38:03 ERROR xorp_fea:19062 FEA +833 click_socket.cc user_click_command_stderr_cb ] User-level Click stderr output: LinearIPLookup: no gw for 302010a LinearIPLookup: no gw for 302010a LinearIPLookup: no gw for 302010a LinearIPLookup: no gw for 302010a [ 2008/04/17 20:38:04 ERROR xorp_fea:19062 FEA +833 click_socket.cc user_click_command_stderr_cb ] User-level Click stderr output: LinearIPLookup: no gw for 50000e0 ------------------------------------------------------------------------------- When I ping sink1 from source1, I got several duplicate acks as follows: [ssohn at source1 ~]$ ping sink1 PING sink1-lan2 (10.1.2.3) 56(84) bytes of data. 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.765 ms 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.770 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.771 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.886 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.01 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.01 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.01 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.14 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.578 ms 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.581 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.583 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.584 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.586 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.703 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.706 ms (DUP!) 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.707 ms (DUP!) --------------------------------------------------------------------------- I am not sure these messages mean that xorp and click work fine. I look forward to hearing you soon. Thank you very much. Eric ----- Original Message ----- From: xorp-users-request at xorp.org Date: Wednesday, April 16, 2008 3:00 pm Subject: Xorp-users Digest, Vol 25, Issue 9 > Send Xorp-users mailing list submissions to > xorp-users at xorp.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > or, via email, send a message with subject or body 'help' to > xorp-users-request at xorp.org > > You can reach the person managing the list at > xorp-users-owner at xorp.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Xorp-users digest..." > > > Today's Topics: > > 1. Re: running xorp+click (Pavlin Radoslavov) > > > ------------------------------------------------------------------- > --- > > Message: 1 > Date: Tue, 15 Apr 2008 13:55:35 -0700 > From: Pavlin Radoslavov > Subject: Re: [Xorp-users] running xorp+click > To: Eric Sohn > Cc: xorp-users at xorp.org > Message-ID: <200804152055.m3FKtZRb003271 at fruitcake.ICSI.Berkeley.EDU> > > Eric Sohn wrote: > > > Hello, > > > > > > > > I am a newbie in xorp. > > > > I am trying to run xorp with click on emulab.net. > > > > I hope somebody can resolve the error. > > > > I attach the boot file and error message. > > What Click version are you using? > Admitably, the support for newer Click releases is lagging behind. > Could you try some of the following: > > * Use explicit interface configuration in the "interfaces" section > instead of using the "default-system-config" statement; i.e., > explicitly add the vif and IP address information to the > XORP configuration. > > * Use the latest XORP code from anon. CVS: > http://www.xorp.org/cvs.html > > * Use an older Click version. If I remember correctly, originally we > had XORP working with Click-1.4.3 (and/or Click-1.4.2?). > > Regards, > Pavlin > > > NW topology is organized with 2 routers and 2 end systems. 2 > routers are > > using xorp + click with RIP. > > > > Each router has two interfaces and each end system has one > interface.> > > Linking is source - r1 - r2 - sink > > > > > > > > Followings are the content of boot file; > > > > ----------------------------------------------------------------- > ----------- > > --- > > > > interfaces{ > > > > restore-original-config-on-shutdown: false > > > > interface eth2 { > > > > disable: false > > > > default-system-config > > > > } > > > > interface eth5 { > > > > disable: false > > > > default-system-config > > > > } > > > > } /* */ > > > > > > > > fea{ > > > > unicast-forwarding4 { > > > > disable: false > > > > } > > > > > > > > unicast-forwarding6 { > > > > disable: true > > > > } > > > > > > > > click { > > > > disable: false > > > > duplicate-routes-to-kernel: true > > > > > > > > kernel-click{ > > > > disable: true > > > > } > > > > > > > > user-click{ > > > > disable: false > > > > command-file: > "/users/ssohn/click/bin/click"> > > command-extra-arguments: "-R" > > > > command-execute-on-startup: true > > > > control-address: 127.0.0.1 > > > > control-socket-port: 13000 > > > > startup-config-file: "/dev/null" > > > > user-click-config-generator-file: > > "/tmp/xorp-1.4/fea/xorp_fea_click_config_generator" <- no > change in this > > file > > > > } > > > > } > > > > > > > > } /* */ > > > > > > > > protocols { > > > > static { > > > > route 10.1.1.0/24 { > > > > next-hop: 10.1.1.2 > > > > metric: 1 > > > > } > > > > route 10.1.3.0/24 { > > > > next-hop: 10.1.1.2 > > > > metric: 1 > > > > } > > > > mrib-route 10.1.1.0/24 { > > > > next-hop: 10.1.1.2 > > > > metric: 1 > > > > } > > > > mrib-route 10.1.3.0/24 { > > > > next-hop: 10.1.1.2 > > > > metric: 1 > > > > } > > > > } > > > > } > > > > > > > > protocols { > > > > rip { > > > > export connected { > > > > metric: 0 > > > > tag: 0 > > > > } > > > > export static { > > > > metric: 1 > > > > tag: 0 > > > > } > > > > interface eth2 { > > > > vif eth2 { > > > > address 10.1.2.2 { > > > > disable: false > > > > } > > > > } > > > > } > > > > interface eth5 { > > > > vif eth5 { > > > > address 10.1.1.3 { > > > > disable: false > > > > } > > > > } > > > > } > > > > } > > > > } > > > > ----------------------------------------------------------------- > ----------- > > ------------------------------------- > > > > > > > > > > > > When I run this boot file, I got error message as follows; > > > > > > > > [ssohn at r2 ~/2routers]$ sudo /tmp/xorp-1.4/rtrmgr/xorp_rtrmgr -b > > ~/2routers/R2.boot.rip > > > > [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +239 > master_conf_tree.cc> execute ] Changed modules: interfaces, fea, > rib, policy, rip, static_routes > > > > [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +96 > module_manager.cc> execute ] Executing module: interfaces > (fea/xorp_fea)> > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started > > > > [ 2008/04/15 14:14:52 INFO xorp_rtrmgr:4310 RTRMGR +96 > module_manager.cc> execute ] Executing module: fea (fea/xorp_fea) > > > > [ 2008/04/15 14:14:57 ERROR xorp_fea:4312 FEA +777 > ifconfig_set_click.cc> click_config_generator_done ] Failed to > write the Click configuration: > > User-level Click command error: 520-Write handler 'hotconfig' error: > > > > 520-:10: While configuring 'Print at 15 :: Print': > > > > 520- argument 1 takes string (label) > > > > 520-:17: While configuring 'Print at 27 :: Print': > > > > 520- argument 1 takes string (label) > > > > 520 Router could not be initialized! > > > > [ 2008/04/15 14:14:59 INFO xorp_rtrmgr:4310 RTRMGR +96 > module_manager.cc> execute ] Executing module: rib (rib/xorp_rib) > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 > > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing > port number > > for the Click forwarding table element to add entry net = > 10.1.2.0/24> nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 > metric = 0 admin_distance = > > 0 xorp_route = true is_deleted = false is_unresolved = false > > is_connected_route = true > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71 > fti_transaction.cc> operation_result ] FTI transaction commit > failed on AddEntry4: net = > > 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 > metric = 0 > > admin_distance = 0 xorp_route = true is_deleted = false > is_unresolved = > > false is_connected_route = true > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 > > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing > port number > > for the Click forwarding table element to add entry net = > 10.1.1.0/24> nexthop = 10.1.1.3 ifname = eth5 vifname = eth5 > metric = 0 admin_distance = > > 0 xorp_route = true is_deleted = false is_unresolved = false > > is_connected_route = true > > > > [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling > method for > > redist_transaction4/0.1/commit_transaction failed: XrlCmdError > 102 Command > > failed AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = > eth2 vifname > > = eth2 metric = 0 admin_distance = 0 xorp_route = true > is_deleted = false > > is_unresolved = false is_connected_route = true > > > > [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc > > dispatch_complete ] Failed to commit transaction: 102 Command failed > > AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 > vifname = eth2 > > metric = 0 admin_distance = 0 xorp_route = true is_deleted = false > > is_unresolved = false is_connected_route = true > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 > > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing > port number > > for the Click forwarding table element to add entry net = > fe80::/64 nexthop > > = fe80::204:23ff:feb7:26dc ifname = eth2 vifname = eth2 metric = 0 > > admin_distance = 0 xorp_route = true is_deleted = false > is_unresolved = > > false is_connected_route = true > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71 > fti_transaction.cc> operation_result ] FTI transaction commit > failed on AddEntry6: net = > > fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname = eth2 > vifname = eth2 > > metric = 0 admin_distance = 0 xorp_route = true is_deleted = false > > is_unresolved = false is_connected_route = true > > > > [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling > method for > > redist_transaction6/0.1/commit_transaction failed: XrlCmdError > 102 Command > > failed AddEntry6: net = fe80::/64 nexthop = > fe80::204:23ff:feb7:26dc ifname > > = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = > true> is_deleted = false is_unresolved = false is_connected_route > = true > > > > [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc > > dispatch_complete ] Failed to commit transaction: 102 Command failed > > AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:feb7:26dc > ifname = eth2 > > vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true > is_deleted = > > false is_unresolved = false is_connected_route = true > > > > [ 2008/04/15 14:15:01 INFO xorp_rtrmgr:4310 RTRMGR +96 > module_manager.cc> execute ] Executing module: policy > (policy/xorp_policy)> > > [ 2008/04/15 14:15:03 INFO xorp_rtrmgr:4310 RTRMGR +96 > module_manager.cc> execute ] Executing module: rip (rip/xorp_rip) > > > > [ 2008/04/15 14:15:05 WARNING xorp_policy:4317 XrlPolicyTarget +567 > > policy_base.cc handle_policy_0_1_export ] Handling method for > > policy/0.1/export failed: XrlCmdError 102 Command failed Export > of rip > > failed: ConfError from line 179 of configuration.cc: exports: > Protocol rip > > unknown > > > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +675 > > master_conf_tree.cc commit_pass2_done ] Commit failed: 102 > Command failed > > Export of rip failed: ConfError from line 179 of > configuration.cc: exports: > > Protocol rip unknown > > > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +251 > > master_conf_tree.cc config_done ] Configuration failed: 102 > Command failed > > Export of rip failed: ConfError from line 179 of > configuration.cc: exports: > > Protocol rip unknown > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +2228 > task.cc run_task ] > > No more tasks to run > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > module_manager.cc> terminate ] Terminating module: fea > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > module_manager.cc> terminate ] Terminating module: interfaces > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 > module_manager.cc> terminate ] Killing module: interfaces > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > module_manager.cc> terminate ] Terminating module: policy > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 > module_manager.cc> terminate ] Killing module: policy > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > module_manager.cc> terminate ] Terminating module: rib > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 > module_manager.cc> terminate ] Killing module: rib > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > module_manager.cc> terminate ] Terminating module: rip > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 > module_manager.cc> terminate ] Killing module: rip > > > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 > module_manager.cc> done_cb ] Command "/tmp/xorp-1.4/rib/xorp_rib": > terminated with signal 15. > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 > module_manager.cc> module_exited ] Module killed during shutdown: rib > > > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 > module_manager.cc> done_cb ] Command "/tmp/xorp- > 1.4/policy/xorp_policy": terminated with signal > > 15. > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 > module_manager.cc> module_exited ] Module killed during shutdown: > policy> > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 > module_manager.cc> done_cb ] Command "/tmp/xorp-1.4/rip/xorp_rip": > terminated with signal 15. > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 > module_manager.cc> module_exited ] Module killed during shutdown: rip > > > > [ 2008/04/15 14:15:07 INFO xorp_rtrmgr:4310 RTRMGR +233 > module_manager.cc> terminate_with_prejudice ] Killing module with > prejudice: interfaces > > > > > > > > > > > > > > > > Plz plz help me out. > > > > > > > > > > > > Thank you in advance. > > > > > > > > Eric > > > > _______________________________________________ > > Xorp-users mailing list > > Xorp-users at xorp.org > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > ------------------------------ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > End of Xorp-users Digest, Vol 25, Issue 9 > ***************************************** > From pavlin at ICSI.Berkeley.EDU Fri Apr 18 11:47:37 2008 From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov) Date: Fri, 18 Apr 2008 11:47:37 -0700 Subject: [Xorp-users] Xorp-users Digest, Vol 25, Issue 9 In-Reply-To: References: Message-ID: <200804181847.m3IIlb1N011552@fruitcake.ICSI.Berkeley.EDU> Soon-Yong Sohn wrote: > Thank you for the reply. > > I did all three as you mentioned, update xorp through cvs, install old version (1.4.3) of click, specify interfaces in detail. It makes some change in running xorp+click. > > However, I got another error message at router as follows; > > ----------------------------------------------------------------------------------- > [ 2008/04/17 20:38:03 ERROR xorp_fea:19062 FEA +833 click_socket.cc user_click_command_stderr_cb ] User-level Click stderr output: LinearIPLookup: no gw for 302010a > LinearIPLookup: no gw for 302010a > LinearIPLookup: no gw for 302010a > LinearIPLookup: no gw for 302010a > [ 2008/04/17 20:38:04 ERROR xorp_fea:19062 FEA +833 click_socket.cc user_click_command_stderr_cb ] User-level Click stderr output: LinearIPLookup: no gw for 50000e0 It looks like that the Click userland program is generating some output on the stderr, and the FEA is just printing it. I guess the particular error is that the LinearIPLookup table didn't contain a forwarding entry for destinations 302010a and 50000e0 which probably are 10.1.2.3 and 224.0.0.5 (i.e., the OSPF Routers multicast group). Those messages are probably harmless for low bw test experiments because they tell you that the Click lookup element doesn't have a forwarding entry for those packets. If you want to suppress the messages (and you can't do it by tweaking the Click configuration), then you would have to comment-out the XLOG_ERROR() message inside ClickSocket::user_click_command_stderr_cb() in file fea/data_plane/control_socket/click_socket.cc > ------------------------------------------------------------------------------- > > > When I ping sink1 from source1, I got several duplicate acks as follows: > > [ssohn at source1 ~]$ ping sink1 > PING sink1-lan2 (10.1.2.3) 56(84) bytes of data. > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.765 ms > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.770 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.771 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=0.886 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.01 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.01 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.01 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=38 ttl=62 time=1.14 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.578 ms > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.581 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.583 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.584 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.586 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.703 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.706 ms (DUP!) > 64 bytes from sink1-lan2 (10.1.2.3): icmp_seq=39 ttl=62 time=0.707 ms (DUP!) This is probably a different problem. In your earlier email on the subject, you had the following statement in your Click-related XORP configuration: duplicate-routes-to-kernel: true The result of that is that the same unicast route will be installed twice: once in the Linux kernel and once in the userland Click process. Because the Click process is snooping on the network interfaces and is forwarding packets on its own (independent from the kernel), as a result of that a packet will be forwarded twice: once by the Linux kernel and once by userland Click. If you set duplicate-routes-to-kernel to false then probably the duplicates will disappear. If not, hopefully some of the other folks on the list who are (or have been) doing more stuff with Click will come out of dormant state and give you a better answer :) Regards, Pavlin > --------------------------------------------------------------------------- > > I am not sure these messages mean that xorp and click work fine. > I look forward to hearing you soon. > Thank you very much. > > Eric > > > > ----- Original Message ----- > From: xorp-users-request at xorp.org > Date: Wednesday, April 16, 2008 3:00 pm > Subject: Xorp-users Digest, Vol 25, Issue 9 > > > Send Xorp-users mailing list submissions to > > xorp-users at xorp.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > or, via email, send a message with subject or body 'help' to > > xorp-users-request at xorp.org > > > > You can reach the person managing the list at > > xorp-users-owner at xorp.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Xorp-users digest..." > > > > > > Today's Topics: > > > > 1. Re: running xorp+click (Pavlin Radoslavov) > > > > > > ------------------------------------------------------------------- > > --- > > > > Message: 1 > > Date: Tue, 15 Apr 2008 13:55:35 -0700 > > From: Pavlin Radoslavov > > Subject: Re: [Xorp-users] running xorp+click > > To: Eric Sohn > > Cc: xorp-users at xorp.org > > Message-ID: <200804152055.m3FKtZRb003271 at fruitcake.ICSI.Berkeley.EDU> > > > > Eric Sohn wrote: > > > > > Hello, > > > > > > > > > > > > I am a newbie in xorp. > > > > > > I am trying to run xorp with click on emulab.net. > > > > > > I hope somebody can resolve the error. > > > > > > I attach the boot file and error message. > > > > What Click version are you using? > > Admitably, the support for newer Click releases is lagging behind. > > Could you try some of the following: > > > > * Use explicit interface configuration in the "interfaces" section > > instead of using the "default-system-config" statement; i.e., > > explicitly add the vif and IP address information to the > > XORP configuration. > > > > * Use the latest XORP code from anon. CVS: > > http://www.xorp.org/cvs.html > > > > * Use an older Click version. If I remember correctly, originally we > > had XORP working with Click-1.4.3 (and/or Click-1.4.2?). > > > > Regards, > > Pavlin > > > > > NW topology is organized with 2 routers and 2 end systems. 2 > > routers are > > > using xorp + click with RIP. > > > > > > Each router has two interfaces and each end system has one > > interface.> > > > Linking is source - r1 - r2 - sink > > > > > > > > > > > > Followings are the content of boot file; > > > > > > ----------------------------------------------------------------- > > ----------- > > > --- > > > > > > interfaces{ > > > > > > restore-original-config-on-shutdown: false > > > > > > interface eth2 { > > > > > > disable: false > > > > > > default-system-config > > > > > > } > > > > > > interface eth5 { > > > > > > disable: false > > > > > > default-system-config > > > > > > } > > > > > > } /* */ > > > > > > > > > > > > fea{ > > > > > > unicast-forwarding4 { > > > > > > disable: false > > > > > > } > > > > > > > > > > > > unicast-forwarding6 { > > > > > > disable: true > > > > > > } > > > > > > > > > > > > click { > > > > > > disable: false > > > > > > duplicate-routes-to-kernel: true > > > > > > > > > > > > kernel-click{ > > > > > > disable: true > > > > > > } > > > > > > > > > > > > user-click{ > > > > > > disable: false > > > > > > command-file: > > "/users/ssohn/click/bin/click"> > > > command-extra-arguments: "-R" > > > > > > command-execute-on-startup: true > > > > > > control-address: 127.0.0.1 > > > > > > control-socket-port: 13000 > > > > > > startup-config-file: "/dev/null" > > > > > > user-click-config-generator-file: > > > "/tmp/xorp-1.4/fea/xorp_fea_click_config_generator" <- no > > change in this > > > file > > > > > > } > > > > > > } > > > > > > > > > > > > } /* */ > > > > > > > > > > > > protocols { > > > > > > static { > > > > > > route 10.1.1.0/24 { > > > > > > next-hop: 10.1.1.2 > > > > > > metric: 1 > > > > > > } > > > > > > route 10.1.3.0/24 { > > > > > > next-hop: 10.1.1.2 > > > > > > metric: 1 > > > > > > } > > > > > > mrib-route 10.1.1.0/24 { > > > > > > next-hop: 10.1.1.2 > > > > > > metric: 1 > > > > > > } > > > > > > mrib-route 10.1.3.0/24 { > > > > > > next-hop: 10.1.1.2 > > > > > > metric: 1 > > > > > > } > > > > > > } > > > > > > } > > > > > > > > > > > > protocols { > > > > > > rip { > > > > > > export connected { > > > > > > metric: 0 > > > > > > tag: 0 > > > > > > } > > > > > > export static { > > > > > > metric: 1 > > > > > > tag: 0 > > > > > > } > > > > > > interface eth2 { > > > > > > vif eth2 { > > > > > > address 10.1.2.2 { > > > > > > disable: false > > > > > > } > > > > > > } > > > > > > } > > > > > > interface eth5 { > > > > > > vif eth5 { > > > > > > address 10.1.1.3 { > > > > > > disable: false > > > > > > } > > > > > > } > > > > > > } > > > > > > } > > > > > > } > > > > > > ----------------------------------------------------------------- > > ----------- > > > ------------------------------------- > > > > > > > > > > > > > > > > > > When I run this boot file, I got error message as follows; > > > > > > > > > > > > [ssohn at r2 ~/2routers]$ sudo /tmp/xorp-1.4/rtrmgr/xorp_rtrmgr -b > > > ~/2routers/R2.boot.rip > > > > > > [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +239 > > master_conf_tree.cc> execute ] Changed modules: interfaces, fea, > > rib, policy, rip, static_routes > > > > > > [ 2008/04/15 14:14:50 INFO xorp_rtrmgr:4310 RTRMGR +96 > > module_manager.cc> execute ] Executing module: interfaces > > (fea/xorp_fea)> > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled > > > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled > > > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started > > > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] MFEA enabled > > > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI enabled > > > > > > [ 2008/04/15 14:14:50 INFO xorp_fea MFEA ] CLI started > > > > > > [ 2008/04/15 14:14:52 INFO xorp_rtrmgr:4310 RTRMGR +96 > > module_manager.cc> execute ] Executing module: fea (fea/xorp_fea) > > > > > > [ 2008/04/15 14:14:57 ERROR xorp_fea:4312 FEA +777 > > ifconfig_set_click.cc> click_config_generator_done ] Failed to > > write the Click configuration: > > > User-level Click command error: 520-Write handler 'hotconfig' error: > > > > > > 520-:10: While configuring 'Print at 15 :: Print': > > > > > > 520- argument 1 takes string (label) > > > > > > 520-:17: While configuring 'Print at 27 :: Print': > > > > > > 520- argument 1 takes string (label) > > > > > > 520 Router could not be initialized! > > > > > > [ 2008/04/15 14:14:59 INFO xorp_rtrmgr:4310 RTRMGR +96 > > module_manager.cc> execute ] Executing module: rib (rib/xorp_rib) > > > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 > > > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing > > port number > > > for the Click forwarding table element to add entry net = > > 10.1.2.0/24> nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 > > metric = 0 admin_distance = > > > 0 xorp_route = true is_deleted = false is_unresolved = false > > > is_connected_route = true > > > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71 > > fti_transaction.cc> operation_result ] FTI transaction commit > > failed on AddEntry4: net = > > > 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 vifname = eth2 > > metric = 0 > > > admin_distance = 0 xorp_route = true is_deleted = false > > is_unresolved = > > > false is_connected_route = true > > > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 > > > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing > > port number > > > for the Click forwarding table element to add entry net = > > 10.1.1.0/24> nexthop = 10.1.1.3 ifname = eth5 vifname = eth5 > > metric = 0 admin_distance = > > > 0 xorp_route = true is_deleted = false is_unresolved = false > > > is_connected_route = true > > > > > > [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling > > method for > > > redist_transaction4/0.1/commit_transaction failed: XrlCmdError > > 102 Command > > > failed AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = > > eth2 vifname > > > = eth2 metric = 0 admin_distance = 0 xorp_route = true > > is_deleted = false > > > is_unresolved = false is_connected_route = true > > > > > > [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc > > > dispatch_complete ] Failed to commit transaction: 102 Command failed > > > AddEntry4: net = 10.1.2.0/24 nexthop = 10.1.2.2 ifname = eth2 > > vifname = eth2 > > > metric = 0 admin_distance = 0 xorp_route = true is_deleted = false > > > is_unresolved = false is_connected_route = true > > > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +301 > > > fticonfig_entry_set_click.cc add_entry ] Cannot find outgoing > > port number > > > for the Click forwarding table element to add entry net = > > fe80::/64 nexthop > > > = fe80::204:23ff:feb7:26dc ifname = eth2 vifname = eth2 metric = 0 > > > admin_distance = 0 xorp_route = true is_deleted = false > > is_unresolved = > > > false is_connected_route = true > > > > > > [ 2008/04/15 14:14:59 ERROR xorp_fea:4312 FEA +71 > > fti_transaction.cc> operation_result ] FTI transaction commit > > failed on AddEntry6: net = > > > fe80::/64 nexthop = fe80::204:23ff:feb7:26dc ifname = eth2 > > vifname = eth2 > > > metric = 0 admin_distance = 0 xorp_route = true is_deleted = false > > > is_unresolved = false is_connected_route = true > > > > > > [ 2008/04/15 14:14:59 WARNING xorp_fea XrlFeaTarget ] Handling > > method for > > > redist_transaction6/0.1/commit_transaction failed: XrlCmdError > > 102 Command > > > failed AddEntry6: net = fe80::/64 nexthop = > > fe80::204:23ff:feb7:26dc ifname > > > = eth2 vifname = eth2 metric = 0 admin_distance = 0 xorp_route = > > true> is_deleted = false is_unresolved = false is_connected_route > > = true > > > > > > [ 2008/04/15 14:14:59 ERROR xorp_rib:4316 RIB +910 redist_xrl.cc > > > dispatch_complete ] Failed to commit transaction: 102 Command failed > > > AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:feb7:26dc > > ifname = eth2 > > > vifname = eth2 metric = 0 admin_distance = 0 xorp_route = true > > is_deleted = > > > false is_unresolved = false is_connected_route = true > > > > > > [ 2008/04/15 14:15:01 INFO xorp_rtrmgr:4310 RTRMGR +96 > > module_manager.cc> execute ] Executing module: policy > > (policy/xorp_policy)> > > > [ 2008/04/15 14:15:03 INFO xorp_rtrmgr:4310 RTRMGR +96 > > module_manager.cc> execute ] Executing module: rip (rip/xorp_rip) > > > > > > [ 2008/04/15 14:15:05 WARNING xorp_policy:4317 XrlPolicyTarget +567 > > > policy_base.cc handle_policy_0_1_export ] Handling method for > > > policy/0.1/export failed: XrlCmdError 102 Command failed Export > > of rip > > > failed: ConfError from line 179 of configuration.cc: exports: > > Protocol rip > > > unknown > > > > > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +675 > > > master_conf_tree.cc commit_pass2_done ] Commit failed: 102 > > Command failed > > > Export of rip failed: ConfError from line 179 of > > configuration.cc: exports: > > > Protocol rip unknown > > > > > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +251 > > > master_conf_tree.cc config_done ] Configuration failed: 102 > > Command failed > > > Export of rip failed: ConfError from line 179 of > > configuration.cc: exports: > > > Protocol rip unknown > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +2228 > > task.cc run_task ] > > > No more tasks to run > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > > module_manager.cc> terminate ] Terminating module: fea > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > > module_manager.cc> terminate ] Terminating module: interfaces > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 > > module_manager.cc> terminate ] Killing module: interfaces > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > > module_manager.cc> terminate ] Terminating module: policy > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 > > module_manager.cc> terminate ] Killing module: policy > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > > module_manager.cc> terminate ] Terminating module: rib > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 > > module_manager.cc> terminate ] Killing module: rib > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +171 > > module_manager.cc> terminate ] Terminating module: rip > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +194 > > module_manager.cc> terminate ] Killing module: rip > > > > > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 > > module_manager.cc> done_cb ] Command "/tmp/xorp-1.4/rib/xorp_rib": > > terminated with signal 15. > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 > > module_manager.cc> module_exited ] Module killed during shutdown: rib > > > > > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 > > module_manager.cc> done_cb ] Command "/tmp/xorp- > > 1.4/policy/xorp_policy": terminated with signal > > > 15. > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 > > module_manager.cc> module_exited ] Module killed during shutdown: > > policy> > > > [ 2008/04/15 14:15:05 ERROR xorp_rtrmgr:4310 RTRMGR +747 > > module_manager.cc> done_cb ] Command "/tmp/xorp-1.4/rip/xorp_rip": > > terminated with signal 15. > > > > > > [ 2008/04/15 14:15:05 INFO xorp_rtrmgr:4310 RTRMGR +282 > > module_manager.cc> module_exited ] Module killed during shutdown: rip > > > > > > [ 2008/04/15 14:15:07 INFO xorp_rtrmgr:4310 RTRMGR +233 > > module_manager.cc> terminate_with_prejudice ] Killing module with > > prejudice: interfaces > > > > > > > > > > > > > > > > > > > > > > > > Plz plz help me out. > > > > > > > > > > > > > > > > > > Thank you in advance. > > > > > > > > > > > > Eric > > > > > > _______________________________________________ > > > Xorp-users mailing list > > > Xorp-users at xorp.org > > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > > > > > ------------------------------ > > > > _______________________________________________ > > Xorp-users mailing list > > Xorp-users at xorp.org > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > > > End of Xorp-users Digest, Vol 25, Issue 9 > > ***************************************** > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From info at cmd.nu Sun Apr 27 11:38:28 2008 From: info at cmd.nu (Christian Svensson) Date: Sun, 27 Apr 2008 20:38:28 +0200 Subject: [Xorp-users] OSPFv2 P2P still uses 224.0.0.5 In-Reply-To: References: Message-ID: Hello. My configuration looks like this: area 0.0.0.3 { area-type: "normal" interface "eth0" { link-type: "p2p" vif "eth0" { address 10.254.0.1 { priority: 128 hello-interval: 10 router-dead-interval: 40 interface-cost: 5 retransmit-interval: 5 transit-delay: 1 passive: false neighbor 10.254.0.2 { router-id: 10.254.0.2 } disable: false } } } } Looking at the packets that passes out of eth0, the only ones that seems to be OSPF-related are heading towards 224.0.0.5. My link between 10.254.0.1 and 10.254.0.2 strips some undocumented segments from packets and it does not handle multicast at all, thus I'm looking for a way of using unicast instead of multicast for inter-router communications. Looking at the OSPFv2 RFC and the P2P mode it appears that this is what I'm looking for but I could be wrong. Using Xorp 1.4. Greetings, -- Christian Svensson Command Systems From atanu at ICSI.Berkeley.EDU Sun Apr 27 20:01:02 2008 From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh) Date: Sun, 27 Apr 2008 20:01:02 -0700 Subject: [Xorp-users] OSPFv2 P2P still uses 224.0.0.5 In-Reply-To: Message from "Christian Svensson" of "Sun, 27 Apr 2008 20:38:28 +0200." Message-ID: <9595.1209351662@tigger.icir.org> Hi. The specification requires that the destination address for point-to-point networks is 225.0.0.5. RFC 2328 A.1 Encapsulation of OSPF packets ---------------------------------------- AllSPFRouters This multicast address has been assigned the value 224.0.0.5. All routers running OSPF should be prepared to receive packets sent to this address. Hello packets are always sent to this destination. Also, certain OSPF protocol packets are sent to this address during the flooding procedure. ---------------------------------------- RFC 2328 8.1. Sending protocol packets ---------------------------------------- The IP destination address for the packet is selected as follows. On physical point-to-point networks, the IP destination is always set to the address AllSPFRouters. On all other network types (including virtual links), the majority of OSPF packets are sent as unicasts, i.e., sent directly to the other end of the adjacency. In this case, the IP destination is just the Neighbor IP address associated with the other end of the adjacency (see Section 10). The only packets not sent as unicasts are on broadcast networks; on these networks Hello packets are sent to the multicast destination AllSPFRouters, the Designated Router and its Backup send both Link State Update Packets and Link State Acknowledgment Packets to the multicast address AllSPFRouters, while all other routers send both their Link State Update and Link State Acknowledgment Packets to the multicast address AllDRouters. ---------------------------------------- Atanu. >>>>> "Christian" == Christian Svensson writes: Christian> Hello. Christian> My configuration looks like this: Christian> area 0.0.0.3 { Christian> area-type: "normal" Christian> interface "eth0" { Christian> link-type: "p2p" Christian> vif "eth0" { Christian> address 10.254.0.1 { Christian> priority: 128 Christian> hello-interval: 10 Christian> router-dead-interval: 40 Christian> interface-cost: 5 Christian> retransmit-interval: 5 Christian> transit-delay: 1 Christian> passive: false Christian> neighbor 10.254.0.2 { Christian> router-id: 10.254.0.2 Christian> } Christian> disable: false Christian> } Christian> } Christian> } Christian> } Christian> Looking at the packets that passes out of eth0, the only ones that Christian> seems to be OSPF-related are heading towards 224.0.0.5. My link Christian> between 10.254.0.1 and 10.254.0.2 strips some undocumented segments Christian> from packets and it does not handle multicast at all, thus I'm looking Christian> for a way of using unicast instead of multicast for inter-router Christian> communications. Looking at the OSPFv2 RFC and the P2P mode it appears Christian> that this is what I'm looking for but I could be wrong. Christian> Using Xorp 1.4. Christian> Greetings, Christian> -- Christian> Christian Svensson Christian> Command Systems Christian> _______________________________________________ Christian> Xorp-users mailing list Christian> Xorp-users at xorp.org Christian> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From info at cmd.nu Sun Apr 27 22:46:05 2008 From: info at cmd.nu (Christian Svensson) Date: Mon, 28 Apr 2008 07:46:05 +0200 Subject: [Xorp-users] OSPFv2 P2P still uses 224.0.0.5 In-Reply-To: <9595.1209351662@tigger.icir.org> References: <9595.1209351662@tigger.icir.org> Message-ID: Hi, I see. I will look into using virtual links, maybe the solution for me lies there. Thanks! On Mon, Apr 28, 2008 at 5:01 AM, Atanu Ghosh wrote: > Hi. > > The specification requires that the destination address for > point-to-point networks is 225.0.0.5. > > RFC 2328 A.1 Encapsulation of OSPF packets > ---------------------------------------- > AllSPFRouters > This multicast address has been assigned the value > 224.0.0.5. All routers running OSPF should be prepared to > receive packets sent to this address. Hello packets are > always sent to this destination. Also, certain OSPF > protocol packets are sent to this address during the > flooding procedure. > ---------------------------------------- > > RFC 2328 8.1. Sending protocol packets > ---------------------------------------- > The IP destination address for the packet is selected as > follows. On physical point-to-point networks, the IP > destination is always set to the address AllSPFRouters. On all > other network types (including virtual links), the majority of > OSPF packets are sent as unicasts, i.e., sent directly to the > other end of the adjacency. In this case, the IP destination is > just the Neighbor IP address associated with the other end of > the adjacency (see Section 10). The only packets not sent as > unicasts are on broadcast networks; on these networks Hello > packets are sent to the multicast destination AllSPFRouters, the > Designated Router and its Backup send both Link State Update > Packets and Link State Acknowledgment Packets to the multicast > address AllSPFRouters, while all other routers send both their > Link State Update and Link State Acknowledgment Packets to the > multicast address AllDRouters. > ---------------------------------------- > > Atanu. > > >>>>> "Christian" == Christian Svensson writes: > > Christian> Hello. > Christian> My configuration looks like this: > > Christian> area 0.0.0.3 { > Christian> area-type: "normal" > Christian> interface "eth0" { > Christian> link-type: "p2p" > Christian> vif "eth0" { > Christian> address 10.254.0.1 { > Christian> priority: 128 > Christian> hello-interval: 10 > Christian> router-dead-interval: 40 > Christian> interface-cost: 5 > Christian> retransmit-interval: 5 > Christian> transit-delay: 1 > Christian> passive: false > Christian> neighbor 10.254.0.2 { > Christian> router-id: 10.254.0.2 > Christian> } > Christian> disable: false > Christian> } > Christian> } > Christian> } > Christian> } > > Christian> Looking at the packets that passes out of eth0, the only ones that > Christian> seems to be OSPF-related are heading towards 224.0.0.5. My link > Christian> between 10.254.0.1 and 10.254.0.2 strips some undocumented segments > Christian> from packets and it does not handle multicast at all, thus I'm looking > Christian> for a way of using unicast instead of multicast for inter-router > Christian> communications. Looking at the OSPFv2 RFC and the P2P mode it appears > Christian> that this is what I'm looking for but I could be wrong. > > Christian> Using Xorp 1.4. > > Christian> Greetings, > Christian> -- > Christian> Christian Svensson > Christian> Command Systems > > Christian> _______________________________________________ > Christian> Xorp-users mailing list > Christian> Xorp-users at xorp.org > Christian> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > -- Christian Svensson Command Systems From tsche at mitre.org Tue Apr 29 09:54:03 2008 From: tsche at mitre.org (Che, Ting-Shuo T.) Date: Tue, 29 Apr 2008 12:54:03 -0400 Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? Message-ID: <9FDF44CB3E9C9943B656E85501CF36FA022BF88F@IMCSRV1.MITRE.ORG> Started XORP on Linux Embedded System and connect that to a test equipment (emulating OSPFv3 neighbors). Test equipment added neighbors one-by-one and all of them enter "Full" state. After that, nothing in this setup is changed, for observation purposes. When there are more than 25 neighbors, the following error messages showed up through xorpsh after waiting for more than 30 minutes. root at 192.168.1.2 > [ 2008/04/15 18:59:29 ERROR xorp_rtrmgr:258 XRL +638 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out After this error message, all neighbors becomes "Down" state as shown at the test equipment side. On the xorpsh side, no more OSPFv3 console command could be accepted. root at 192.168.1.2 > show ospf6 neighbor | match Full | count [ 2008/04/15 19:11:42 WARNING xorp_rtrmgr:258 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ospfv3" does not exist or is not enabled. Count: 0 lines root at 192.168.1.2 > show ospf6 neighbor [ 2008/04/15 19:11:51 WARNING xorp_rtrmgr:258 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ospfv3" does not exist or is not enabled. ERROR: Command "/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited with exit status 255. Similar problems also happens for more neighbors (30, 35, 40, etc.). The only difference is the number (such as 252, 257, instead of 258) following xorp_rtrmgr: Any thought or tip on this is very much appreciated. Ting Che PS. What follows is the XORP configuration on the Linux Embedded System /*XORP Configuration File, v1.0*/ protocols { ospf6 0 { router-id: 192.168.0.102 ip-router-alert: false area 0.0.0.0 { area-type: "normal" interface eth1 { link-type: "broadcast" vif eth1 { priority: 128 hello-interval: 10 router-dead-interval: 40 interface-cost: 1 retransmit-interval: 5 transit-delay: 1 passive: false disable: false } } } } } fea { unicast-forwarding6 { disable: false } } interfaces { restore-original-config-on-shutdown: false interface eth1 { description: "" disable: false vif eth1 { disable: false address 192.168.2.4 { prefix-length: 24 disable: false } address 2000::2 { prefix-length: 64 disable: false } address fe80::210:ecff:fe80:fd { prefix-length: 64 disable: false } } } } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080429/a0e2fc87/attachment.html From atanu at ICSI.Berkeley.EDU Tue Apr 29 10:11:47 2008 From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh) Date: Tue, 29 Apr 2008 10:11:47 -0700 Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? In-Reply-To: Message from "Che, Ting-Shuo T." of "Tue, 29 Apr 2008 12:54:03 EDT." <9FDF44CB3E9C9943B656E85501CF36FA022BF88F@IMCSRV1.MITRE.ORG> Message-ID: <70195.1209489107@tigger.icir.org> Hi, Could you send the output generated by the the router manager? How many entries in the database? Atanu. >>>>> "Ting-Shuo" == Ting-Shuo T Che writes: Ting-Shuo> Started XORP on Linux Embedded System and connect that to a test Ting-Shuo> equipment (emulating Ting-Shuo> OSPFv3 neighbors). Test equipment added neighbors one-by-one and all Ting-Shuo> of them enter "Full" Ting-Shuo> state. After that, nothing in this setup is changed, for observation Ting-Shuo> purposes. Ting-Shuo> When there are more than 25 neighbors, the following error messages Ting-Shuo> showed up through Ting-Shuo> xorpsh after waiting for more than 30 minutes. Ting-Shuo> root at 192.168.1.2> [ 2008/04/15 18:59:29 ERROR xorp_rtrmgr:258 XRL Ting-Shuo> +638 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout Ting-Shuo> [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply Ting-Shuo> timed out Ting-Shuo> [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply Ting-Shuo> timed out Ting-Shuo> After this error message, all neighbors becomes "Down" state as shown Ting-Shuo> at the test equipment Ting-Shuo> side. On the xorpsh side, no more OSPFv3 console command could be Ting-Shuo> accepted. Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor | match Full | count Ting-Shuo> [ 2008/04/15 19:11:42 WARNING xorp_rtrmgr:258 XrlFinderTarget +406 Ting-Shuo> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled. Ting-Shuo> Count: 0 lines Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor Ting-Shuo> [ 2008/04/15 19:11:51 WARNING xorp_rtrmgr:258 XrlFinderTarget +406 Ting-Shuo> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled. Ting-Shuo> ERROR: Command Ting-Shuo> "/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited Ting-Shuo> with exit status 255. Ting-Shuo> Similar problems also happens for more neighbors (30, 35, 40, etc.). Ting-Shuo> The only difference is Ting-Shuo> the number (such as 252, 257, instead of 258) following xorp_rtrmgr: Ting-Shuo> Any thought or tip on this is very much appreciated. Ting-Shuo> Ting Che Ting-Shuo> PS. What follows is the XORP configuration on the Linux Embedded Ting-Shuo> System Ting-Shuo> /*XORP Configuration File, v1.0*/ Ting-Shuo> protocols { Ting-Shuo> ospf6 0 { Ting-Shuo> router-id: 192.168.0.102 Ting-Shuo> ip-router-alert: false Ting-Shuo> area 0.0.0.0 { Ting-Shuo> area-type: "normal" Ting-Shuo> interface eth1 { Ting-Shuo> link-type: "broadcast" Ting-Shuo> vif eth1 { Ting-Shuo> priority: 128 Ting-Shuo> hello-interval: 10 Ting-Shuo> router-dead-interval: 40 Ting-Shuo> interface-cost: 1 Ting-Shuo> retransmit-interval: 5 Ting-Shuo> transit-delay: 1 Ting-Shuo> passive: false Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> fea { Ting-Shuo> unicast-forwarding6 { Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> interfaces { Ting-Shuo> restore-original-config-on-shutdown: false Ting-Shuo> interface eth1 { Ting-Shuo> description: "" Ting-Shuo> disable: false Ting-Shuo> vif eth1 { Ting-Shuo> disable: false Ting-Shuo> address 192.168.2.4 { Ting-Shuo> prefix-length: 24 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> address 2000::2 { Ting-Shuo> prefix-length: 64 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> address fe80::210:ecff:fe80:fd { Ting-Shuo> prefix-length: 64 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> _______________________________________________ Ting-Shuo> Xorp-users mailing list Ting-Shuo> Xorp-users at xorp.org Ting-Shuo> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From greearb at candelatech.com Tue Apr 29 10:13:13 2008 From: greearb at candelatech.com (Ben Greear) Date: Tue, 29 Apr 2008 10:13:13 -0700 Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? In-Reply-To: <9FDF44CB3E9C9943B656E85501CF36FA022BF88F@IMCSRV1.MITRE.ORG> References: <9FDF44CB3E9C9943B656E85501CF36FA022BF88F@IMCSRV1.MITRE.ORG> Message-ID: <48175729.509@candelatech.com> Che, Ting-Shuo T. wrote: > Started XORP on Linux Embedded System and connect that to a test > equipment (emulating > OSPFv3 neighbors). Test equipment added neighbors one-by-one and all of > them enter "Full" > state. After that, nothing in this setup is changed, for observation > purposes. > > When there are more than 25 neighbors, the following error messages > showed up through > xorpsh after waiting for more than 30 minutes. Are you running all of these Xorps on the same machine? If so, might try digging through the archives for my performance improvement patch...it lets 30+ xorps work for me.... I'll generate a new patch sometime soon against the latest CVS and post it... Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From tsche at mitre.org Tue Apr 29 11:31:38 2008 From: tsche at mitre.org (Che, Ting-Shuo T.) Date: Tue, 29 Apr 2008 14:31:38 -0400 Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? In-Reply-To: <48175729.509@candelatech.com> References: <9FDF44CB3E9C9943B656E85501CF36FA022BF88F@IMCSRV1.MITRE.ORG> <48175729.509@candelatech.com> Message-ID: <9FDF44CB3E9C9943B656E85501CF36FA022BF896@IMCSRV1.MITRE.ORG> Hi Ben, No, I am running only one XORP on the embedded system "under test". It is connected to a test equipment that run 40 router instances. Nevertheless, is your "performance improvement patch" support 30+ XORP instances running on 1 machine, like the "test equipment"? If yes, that would be great for avoiding interoperability issue. Thank you very much for posting it to CVS. Ting -----Original Message----- From: Ben Greear [mailto:greearb at candelatech.com] Sent: Tuesday, April 29, 2008 1:13 PM To: Che, Ting-Shuo T. Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? Che, Ting-Shuo T. wrote: > Started XORP on Linux Embedded System and connect that to a test > equipment (emulating > OSPFv3 neighbors). Test equipment added neighbors one-by-one and all of > them enter "Full" > state. After that, nothing in this setup is changed, for observation > purposes. > > When there are more than 25 neighbors, the following error messages > showed up through > xorpsh after waiting for more than 30 minutes. Are you running all of these Xorps on the same machine? If so, might try digging through the archives for my performance improvement patch...it lets 30+ xorps work for me.... I'll generate a new patch sometime soon against the latest CVS and post it... Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From atanu at ICSI.Berkeley.EDU Tue Apr 29 12:01:54 2008 From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh) Date: Tue, 29 Apr 2008 12:01:54 -0700 Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? In-Reply-To: Message from "Che, Ting-Shuo T." of "Tue, 29 Apr 2008 14:14:50 EDT." <9FDF44CB3E9C9943B656E85501CF36FA022BF892@IMCSRV1.MITRE.ORG> Message-ID: <86609.1209495714@tigger.icir.org> Hi, The OSPF process seems to have exited, typically the XORP processes will print a message before exiting, it would be useful to see this message. Could you run the router manager in the background and capture the output, the following works for me with /bin/sh: # ./xorp_rtrmgr -b ./ipv6ospf.boot > log 2>&1 & If you are not already could you also try building from CVS so that you have all of the fixes. Atanu. >>>>> "Ting-Shuo" == Ting-Shuo T Che writes: Ting-Shuo> Hi Atanu, Ting-Shuo> I only have one shell to this embedded system. So I run router manager Ting-Shuo> process in the background (./xorp_rtrmgr -b ./ipv6ospf.boot &) and then Ting-Shuo> run XORP command shell in the foreground (./xorpsh) to check the number Ting-Shuo> of neighbors (show ospf6 neighbor) and database (show ospf6 database) Ting-Shuo> 1. Are you suggesting me to use other xorp_rtrmgr command options, or Ting-Shuo> just run it in the foreground (without xorpsh)? Any specific type of Ting-Shuo> error you are looking for? Ting-Shuo> 2. For 40 neighbors (192.168.2.5 ~ 192.168.2.44, 3 intra-area prefix Ting-Shuo> each, emulated by test equipment) in the same area 0.0.0.0 as embedded Ting-Shuo> system under test (192.168.0.102), "show ospf6 database" indicates 41 Ting-Shuo> Link LSAs, 41 Router LSAs, 1 Network LSAs, and 121 IntraArPfx LSAs. Ting-Shuo> Ting Ting-Shuo> PS. Attached is the detail screen dump FYI. Ting-Shuo> -----Original Message----- Ting-Shuo> From: atanu at icir.org [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh Ting-Shuo> Sent: Tuesday, April 29, 2008 1:12 PM Ting-Shuo> To: Che, Ting-Shuo T. Ting-Shuo> Cc: xorp-users at xorp.org Ting-Shuo> Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully Ting-Shuo> adjacent? Ting-Shuo> Hi, Ting-Shuo> Could you send the output generated by the the router manager? Ting-Shuo> How many entries in the database? Ting-Shuo> Atanu. >>>>> "Ting-Shuo" == Ting-Shuo T Che writes: Ting-Shuo> Started XORP on Linux Embedded System and connect that Ting-Shuo> to a test Ting-Shuo> equipment (emulating Ting-Shuo> OSPFv3 neighbors). Test equipment added neighbors Ting-Shuo> one-by-one and all Ting-Shuo> of them enter "Full" Ting-Shuo> state. After that, nothing in this setup is changed, for Ting-Shuo> observation Ting-Shuo> purposes. Ting-Shuo> When there are more than 25 neighbors, the following Ting-Shuo> error messages Ting-Shuo> showed up through Ting-Shuo> xorpsh after waiting for more than 30 minutes. Ting-Shuo> root at 192.168.1.2> [ 2008/04/15 18:59:29 ERROR Ting-Shuo> xorp_rtrmgr:258 XRL Ting-Shuo> +638 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Ting-Shuo> Keepalive timeout Ting-Shuo> [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response Ting-Shuo> 211 Reply Ting-Shuo> timed out Ting-Shuo> [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response Ting-Shuo> 211 Reply Ting-Shuo> timed out Ting-Shuo> After this error message, all neighbors becomes "Down" Ting-Shuo> state as shown Ting-Shuo> at the test equipment Ting-Shuo> side. On the xorpsh side, no more OSPFv3 console command Ting-Shuo> could be Ting-Shuo> accepted. Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor | match Full | Ting-Shuo> count Ting-Shuo> [ 2008/04/15 19:11:42 WARNING xorp_rtrmgr:258 Ting-Shuo> XrlFinderTarget +406 Ting-Shuo> ../xrl/targets/finder_base.cc Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError Ting-Shuo> 102 Command Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled. Ting-Shuo> Count: 0 lines Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor Ting-Shuo> [ 2008/04/15 19:11:51 WARNING xorp_rtrmgr:258 Ting-Shuo> XrlFinderTarget +406 Ting-Shuo> ../xrl/targets/finder_base.cc Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError Ting-Shuo> 102 Command Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled. Ting-Shuo> ERROR: Command Ting-Shuo> Ting-Shuo> "/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited Ting-Shuo> with exit status 255. Ting-Shuo> Similar problems also happens for more neighbors (30, Ting-Shuo> 35, 40, etc.). Ting-Shuo> The only difference is Ting-Shuo> the number (such as 252, 257, instead of 258) following Ting-Shuo> xorp_rtrmgr: Ting-Shuo> Any thought or tip on this is very much appreciated. Ting-Shuo> Ting Che Ting-Shuo> PS. What follows is the XORP configuration on the Linux Ting-Shuo> Embedded Ting-Shuo> System Ting-Shuo> /*XORP Configuration File, v1.0*/ Ting-Shuo> protocols { Ting-Shuo> ospf6 0 { Ting-Shuo> router-id: 192.168.0.102 Ting-Shuo> ip-router-alert: false Ting-Shuo> area 0.0.0.0 { Ting-Shuo> area-type: "normal" Ting-Shuo> interface eth1 { Ting-Shuo> link-type: "broadcast" Ting-Shuo> vif eth1 { Ting-Shuo> priority: 128 Ting-Shuo> hello-interval: 10 Ting-Shuo> router-dead-interval: 40 Ting-Shuo> interface-cost: 1 Ting-Shuo> retransmit-interval: 5 Ting-Shuo> transit-delay: 1 Ting-Shuo> passive: false Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> fea { Ting-Shuo> unicast-forwarding6 { Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> interfaces { Ting-Shuo> restore-original-config-on-shutdown: false Ting-Shuo> interface eth1 { Ting-Shuo> description: "" Ting-Shuo> disable: false Ting-Shuo> vif eth1 { Ting-Shuo> disable: false Ting-Shuo> address 192.168.2.4 { Ting-Shuo> prefix-length: 24 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> address 2000::2 { Ting-Shuo> prefix-length: 64 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> address fe80::210:ecff:fe80:fd { Ting-Shuo> prefix-length: 64 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> _______________________________________________ Ting-Shuo> Xorp-users mailing list Ting-Shuo> Xorp-users at xorp.org Ting-Shuo> Ting-Shuo> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From tsche at mitre.org Tue Apr 29 12:41:52 2008 From: tsche at mitre.org (Che, Ting-Shuo T.) Date: Tue, 29 Apr 2008 15:41:52 -0400 Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? In-Reply-To: <86609.1209495714@tigger.icir.org> References: Message from "Che, Ting-Shuo T." of "Tue, 29 Apr 2008 14:14:50 EDT." <9FDF44CB3E9C9943B656E85501CF36FA022BF892@IMCSRV1.MITRE.ORG> <86609.1209495714@tigger.icir.org> Message-ID: <9FDF44CB3E9C9943B656E85501CF36FA022BF89C@IMCSRV1.MITRE.ORG> Thanks a lot for the guidance. I will do it ASAP. Indeed the OSPFv3 process seems to "partially" exit and no longer functioning. What puzzled me was somehow "ps -ef" show xorp_ospfv3 still exists... Ting PS. root at 192.168.1.2> [ 2008/04/14 14:14:34 ERROR xorp_rtrmgr:252 XRL +638 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout [ 2008/04/14 14:14:48 ERROR xorp_rtrmgr:252 FINDER +85 finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out [ 2008/04/14 14:14:48 ERROR xorp_rtrmgr:252 FINDER +85 finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out root at 192.168.1.2> root at 192.168.1.2> show ospf6 neighbor | match Full | count [ 2008/04/14 14:15:15 WARNING xorp_rtrmgr:252 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ospfv3" does not exist or is not enabled. Count: 0 lines root at 192.168.1.2> show ospf6 neighbor [ 2008/04/14 14:15:36 WARNING xorp_rtrmgr:252 XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ospfv3" does not exist or is not enabled. ERROR: Command "/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited with exit status 255. root at 192.168.1.2> exit bash-3.00# date Mon Apr 14 14:15:50 MEST 2008 bash-3.00# ps -ef | grep xorp root 252 221 2 13:39 ? 00:01:01 ./xorp_rtrmgr -b ipv6ospf.boot root 254 252 2 13:39 ? 00:00:51 xorp_fea root 255 252 0 13:39 ? 00:00:03 xorp_rib root 256 252 0 13:39 ? 00:00:03 xorp_policy root 257 252 17 13:39 ? 00:06:26 xorp_ospfv3 root 24839 221 0 14:15 ? 00:00:00 grep xorp -----Original Message----- From: atanu at icir.org [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh Sent: Tuesday, April 29, 2008 3:02 PM To: Che, Ting-Shuo T. Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? Hi, The OSPF process seems to have exited, typically the XORP processes will print a message before exiting, it would be useful to see this message. Could you run the router manager in the background and capture the output, the following works for me with /bin/sh: # ./xorp_rtrmgr -b ./ipv6ospf.boot > log 2>&1 & If you are not already could you also try building from CVS so that you have all of the fixes. Atanu. >>>>> "Ting-Shuo" == Ting-Shuo T Che writes: Ting-Shuo> Hi Atanu, Ting-Shuo> I only have one shell to this embedded system. So I run router manager Ting-Shuo> process in the background (./xorp_rtrmgr -b ./ipv6ospf.boot &) and then Ting-Shuo> run XORP command shell in the foreground (./xorpsh) to check the number Ting-Shuo> of neighbors (show ospf6 neighbor) and database (show ospf6 database) Ting-Shuo> 1. Are you suggesting me to use other xorp_rtrmgr command options, or Ting-Shuo> just run it in the foreground (without xorpsh)? Any specific type of Ting-Shuo> error you are looking for? Ting-Shuo> 2. For 40 neighbors (192.168.2.5 ~ 192.168.2.44, 3 intra-area prefix Ting-Shuo> each, emulated by test equipment) in the same area 0.0.0.0 as embedded Ting-Shuo> system under test (192.168.0.102), "show ospf6 database" indicates 41 Ting-Shuo> Link LSAs, 41 Router LSAs, 1 Network LSAs, and 121 IntraArPfx LSAs. Ting-Shuo> Ting Ting-Shuo> PS. Attached is the detail screen dump FYI. Ting-Shuo> -----Original Message----- Ting-Shuo> From: atanu at icir.org [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh Ting-Shuo> Sent: Tuesday, April 29, 2008 1:12 PM Ting-Shuo> To: Che, Ting-Shuo T. Ting-Shuo> Cc: xorp-users at xorp.org Ting-Shuo> Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully Ting-Shuo> adjacent? Ting-Shuo> Hi, Ting-Shuo> Could you send the output generated by the the router manager? Ting-Shuo> How many entries in the database? Ting-Shuo> Atanu. >>>>> "Ting-Shuo" == Ting-Shuo T Che writes: Ting-Shuo> Started XORP on Linux Embedded System and connect that Ting-Shuo> to a test Ting-Shuo> equipment (emulating Ting-Shuo> OSPFv3 neighbors). Test equipment added neighbors Ting-Shuo> one-by-one and all Ting-Shuo> of them enter "Full" Ting-Shuo> state. After that, nothing in this setup is changed, for Ting-Shuo> observation Ting-Shuo> purposes. Ting-Shuo> When there are more than 25 neighbors, the following Ting-Shuo> error messages Ting-Shuo> showed up through Ting-Shuo> xorpsh after waiting for more than 30 minutes. Ting-Shuo> root at 192.168.1.2> [ 2008/04/15 18:59:29 ERROR Ting-Shuo> xorp_rtrmgr:258 XRL Ting-Shuo> +638 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Ting-Shuo> Keepalive timeout Ting-Shuo> [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response Ting-Shuo> 211 Reply Ting-Shuo> timed out Ting-Shuo> [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response Ting-Shuo> 211 Reply Ting-Shuo> timed out Ting-Shuo> After this error message, all neighbors becomes "Down" Ting-Shuo> state as shown Ting-Shuo> at the test equipment Ting-Shuo> side. On the xorpsh side, no more OSPFv3 console command Ting-Shuo> could be Ting-Shuo> accepted. Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor | match Full | Ting-Shuo> count Ting-Shuo> [ 2008/04/15 19:11:42 WARNING xorp_rtrmgr:258 Ting-Shuo> XrlFinderTarget +406 Ting-Shuo> ../xrl/targets/finder_base.cc Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError Ting-Shuo> 102 Command Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled. Ting-Shuo> Count: 0 lines Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor Ting-Shuo> [ 2008/04/15 19:11:51 WARNING xorp_rtrmgr:258 Ting-Shuo> XrlFinderTarget +406 Ting-Shuo> ../xrl/targets/finder_base.cc Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError Ting-Shuo> 102 Command Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled. Ting-Shuo> ERROR: Command Ting-Shuo> Ting-Shuo> "/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited Ting-Shuo> with exit status 255. Ting-Shuo> Similar problems also happens for more neighbors (30, Ting-Shuo> 35, 40, etc.). Ting-Shuo> The only difference is Ting-Shuo> the number (such as 252, 257, instead of 258) following Ting-Shuo> xorp_rtrmgr: Ting-Shuo> Any thought or tip on this is very much appreciated. Ting-Shuo> Ting Che Ting-Shuo> PS. What follows is the XORP configuration on the Linux Ting-Shuo> Embedded Ting-Shuo> System Ting-Shuo> /*XORP Configuration File, v1.0*/ Ting-Shuo> protocols { Ting-Shuo> ospf6 0 { Ting-Shuo> router-id: 192.168.0.102 Ting-Shuo> ip-router-alert: false Ting-Shuo> area 0.0.0.0 { Ting-Shuo> area-type: "normal" Ting-Shuo> interface eth1 { Ting-Shuo> link-type: "broadcast" Ting-Shuo> vif eth1 { Ting-Shuo> priority: 128 Ting-Shuo> hello-interval: 10 Ting-Shuo> router-dead-interval: 40 Ting-Shuo> interface-cost: 1 Ting-Shuo> retransmit-interval: 5 Ting-Shuo> transit-delay: 1 Ting-Shuo> passive: false Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> fea { Ting-Shuo> unicast-forwarding6 { Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> interfaces { Ting-Shuo> restore-original-config-on-shutdown: false Ting-Shuo> interface eth1 { Ting-Shuo> description: "" Ting-Shuo> disable: false Ting-Shuo> vif eth1 { Ting-Shuo> disable: false Ting-Shuo> address 192.168.2.4 { Ting-Shuo> prefix-length: 24 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> address 2000::2 { Ting-Shuo> prefix-length: 64 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> address fe80::210:ecff:fe80:fd { Ting-Shuo> prefix-length: 64 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> _______________________________________________ Ting-Shuo> Xorp-users mailing list Ting-Shuo> Xorp-users at xorp.org Ting-Shuo> Ting-Shuo> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From tsche at mitre.org Tue Apr 29 11:14:50 2008 From: tsche at mitre.org (Che, Ting-Shuo T.) Date: Tue, 29 Apr 2008 14:14:50 -0400 Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? In-Reply-To: <70195.1209489107@tigger.icir.org> References: Message from "Che, Ting-Shuo T." of "Tue, 29 Apr 2008 12:54:03 EDT." <9FDF44CB3E9C9943B656E85501CF36FA022BF88F@IMCSRV1.MITRE.ORG> <70195.1209489107@tigger.icir.org> Message-ID: <9FDF44CB3E9C9943B656E85501CF36FA022BF892@IMCSRV1.MITRE.ORG> Hi Atanu, I only have one shell to this embedded system. So I run router manager process in the background (./xorp_rtrmgr -b ./ipv6ospf.boot &) and then run XORP command shell in the foreground (./xorpsh) to check the number of neighbors (show ospf6 neighbor) and database (show ospf6 database) 1. Are you suggesting me to use other xorp_rtrmgr command options, or just run it in the foreground (without xorpsh)? Any specific type of error you are looking for? 2. For 40 neighbors (192.168.2.5 ~ 192.168.2.44, 3 intra-area prefix each, emulated by test equipment) in the same area 0.0.0.0 as embedded system under test (192.168.0.102), "show ospf6 database" indicates 41 Link LSAs, 41 Router LSAs, 1 Network LSAs, and 121 IntraArPfx LSAs. Ting PS. Attached is the detail screen dump FYI. -----Original Message----- From: atanu at icir.org [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh Sent: Tuesday, April 29, 2008 1:12 PM To: Che, Ting-Shuo T. Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent? Hi, Could you send the output generated by the the router manager? How many entries in the database? Atanu. >>>>> "Ting-Shuo" == Ting-Shuo T Che writes: Ting-Shuo> Started XORP on Linux Embedded System and connect that to a test Ting-Shuo> equipment (emulating Ting-Shuo> OSPFv3 neighbors). Test equipment added neighbors one-by-one and all Ting-Shuo> of them enter "Full" Ting-Shuo> state. After that, nothing in this setup is changed, for observation Ting-Shuo> purposes. Ting-Shuo> When there are more than 25 neighbors, the following error messages Ting-Shuo> showed up through Ting-Shuo> xorpsh after waiting for more than 30 minutes. Ting-Shuo> root at 192.168.1.2> [ 2008/04/15 18:59:29 ERROR xorp_rtrmgr:258 XRL Ting-Shuo> +638 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout Ting-Shuo> [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply Ting-Shuo> timed out Ting-Shuo> [ 2008/04/15 18:59:46 ERROR xorp_rtrmgr:258 FINDER +85 Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply Ting-Shuo> timed out Ting-Shuo> After this error message, all neighbors becomes "Down" state as shown Ting-Shuo> at the test equipment Ting-Shuo> side. On the xorpsh side, no more OSPFv3 console command could be Ting-Shuo> accepted. Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor | match Full | count Ting-Shuo> [ 2008/04/15 19:11:42 WARNING xorp_rtrmgr:258 XrlFinderTarget +406 Ting-Shuo> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled. Ting-Shuo> Count: 0 lines Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor Ting-Shuo> [ 2008/04/15 19:11:51 WARNING xorp_rtrmgr:258 XrlFinderTarget +406 Ting-Shuo> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled. Ting-Shuo> ERROR: Command Ting-Shuo> "/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited Ting-Shuo> with exit status 255. Ting-Shuo> Similar problems also happens for more neighbors (30, 35, 40, etc.). Ting-Shuo> The only difference is Ting-Shuo> the number (such as 252, 257, instead of 258) following xorp_rtrmgr: Ting-Shuo> Any thought or tip on this is very much appreciated. Ting-Shuo> Ting Che Ting-Shuo> PS. What follows is the XORP configuration on the Linux Embedded Ting-Shuo> System Ting-Shuo> /*XORP Configuration File, v1.0*/ Ting-Shuo> protocols { Ting-Shuo> ospf6 0 { Ting-Shuo> router-id: 192.168.0.102 Ting-Shuo> ip-router-alert: false Ting-Shuo> area 0.0.0.0 { Ting-Shuo> area-type: "normal" Ting-Shuo> interface eth1 { Ting-Shuo> link-type: "broadcast" Ting-Shuo> vif eth1 { Ting-Shuo> priority: 128 Ting-Shuo> hello-interval: 10 Ting-Shuo> router-dead-interval: 40 Ting-Shuo> interface-cost: 1 Ting-Shuo> retransmit-interval: 5 Ting-Shuo> transit-delay: 1 Ting-Shuo> passive: false Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> fea { Ting-Shuo> unicast-forwarding6 { Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> interfaces { Ting-Shuo> restore-original-config-on-shutdown: false Ting-Shuo> interface eth1 { Ting-Shuo> description: "" Ting-Shuo> disable: false Ting-Shuo> vif eth1 { Ting-Shuo> disable: false Ting-Shuo> address 192.168.2.4 { Ting-Shuo> prefix-length: 24 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> address 2000::2 { Ting-Shuo> prefix-length: 64 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> address fe80::210:ecff:fe80:fd { Ting-Shuo> prefix-length: 64 Ting-Shuo> disable: false Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> } Ting-Shuo> _______________________________________________ Ting-Shuo> Xorp-users mailing list Ting-Shuo> Xorp-users at xorp.org Ting-Shuo> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ErrorLog40Ospfv3Neighbors.txt Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080429/1c2271e5/attachment-0001.txt From yueli.m at gmail.com Wed Apr 30 16:54:48 2008 From: yueli.m at gmail.com (Yue Li) Date: Wed, 30 Apr 2008 19:54:48 -0400 Subject: [Xorp-users] BGP and Policy module shutdown Message-ID: <49567c360804301654w68903cb6t852f2a41e91d9cc@mail.gmail.com> Hi, All I am testing bgp and policies with 30 XORP instances. I got the following errors from one xorp instance, bgp and policy modules shutdown: [ 2008/04/30 19:07:08 ERROR xorp_rtrmgr:9832 RTRMGR +747 module_manager.cc done_cb ] Command "/local/xorp/bgp/xorp_bgp": terminated with signal 11. [ 2008/04/30 19:07:08 ERROR xorp_rtrmgr:9832 RTRMGR +747 module_manager.cc done_cb ] Command "/local/xorp/policy/xorp_policy": terminated with signal 6. [ 2008/04/30 19:07:08 ERROR xorp_policy:10139 XRL +635 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout [ 2008/04/30 19:07:08 ERROR xorp_policy:10139 LIBXORP +213 buffered_asyncio.cc io_event ] read error 104 [ 2008/04/30 19:07:08 ERROR xorp_policy:10139 XRL +782 xrl_pf_stcp.cc read_event ] Read failed (error = 104) [ 2008/04/30 19:07:08 ERROR xorp_policy:10139 XRL +635 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: read error [ 2008/04/30 19:07:08 INFO xorp_rib RIB ] Received death event for protocol bgp shutting down ------- OriginTable: ebgp EGP next table = Merged:(ebgp)+(ibgp) [ 2008/04/30 19:07:08 INFO xorp_rib RIB ] Received death event for protocol bgp shutting down ------- OriginTable: ebgp EGP next table = Merged:(ebgp)+(ibgp) [ 2008/04/30 19:07:08 INFO xorp_rib RIB ] Received death event for protocol bgp shutting down ------- OriginTable: ebgp EGP next table = Merged:(ebgp)+(ibgp) [ 2008/04/30 19:07:08 INFO xorp_rib RIB ] Received death event for protocol bgp shutting down ------- OriginTable: ebgp EGP next table = Merged:(ebgp)+(ibgp) [ 2008/04/30 19:07:08 FATAL xorp_policy:10139 XifRib +53 xorp_policy.cc main ] PolicyException: FMException from line 122 of filter_manager.cc: XRL policy_backend_cb() error: 210 Transport failed I have configured the import and export policies with about 4,000 terms on this router, most of them are like : policy-statement bgp_in { term 0 { from { neighbor: 10.0.1.81 } then { accept } } term 1 { from { neighbor: 10.0.1.62 network4: 199.253.246.0/24 } then { accept } ... term import_last { then { reject } } } policy-statement bgp_out { term 0 { from { protocol: "static" network4: 129.142.0.0/16 } to { neighbor: 10.0.1.141 } then { nexthop4: 10.0.1.142 accept } } ... term 209 { from { protocol: "bgp" network4: 146.75.0.0/16 } to { neighbor: 10.0.1.141 } then { accept } } ... term export_last { then { reject } } } bgp { bgp-id: 10.0.1.142 import: "bgp_in" export: "bgp_out" local-as: 1257 traceoptions { flag { all { disable: true } } } peer 10.0.1.141 { local-ip: 10.0.1.142 as: 286 next-hop: 10.0.1.142 ipv4-multicast: false ipv6-unicast: false ipv6-multicast: false } ... } Could anyone give some clues? Thanks! From agorski at mitre.org Wed Apr 30 22:28:53 2008 From: agorski at mitre.org (Gorski, Andrew J.) Date: Thu, 1 May 2008 01:28:53 -0400 Subject: [Xorp-users] SPF Calculations Message-ID: <9863411DEA890E458E57C11C5A1A18EAB8247C@IMCSRV7.MITRE.ORG> When using OSPF in XORP, is there anyway to see how many SPF calculations have been performed since the process began or since the counter was reset? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080501/559f311c/attachment.html