Hello, I am very sorry but i still have the problem.
It's working fine until router Vyatta-A sees its BGP peers and then the BGP process crashs. I have no problem on Vyatta-B because there is no protocol redistribution. Case study: openmaniak.com/vyatta_case4.php REgards TRoopy ---------- Original Message ---------------------------------- From: "Troopy ." <[EMAIL PROTECTED]> Reply-To: <[EMAIL PROTECTED]> Date: Wed, 21 Nov 2007 08:26:42 +0100 > > >Hello, > >I changed BGP to OSPF4 in the policy statement and rebooted, the BGP is now >stable. > >So i don't know is it was becasue of the mistake in the policy statement or >the reboot. >but i have the feeling it was because of the mistake in the policy statement > >Thanks > >Troopy > > >---------- Original Message ---------------------------------- >From: "Troopy ." <[EMAIL PROTECTED]> >Reply-To: <[EMAIL PROTECTED]> >Date: Tue, 20 Nov 2007 20:17:21 +0100 > >> >>Hello, >> >>Thank you for your help >> >>That's right there is a mistake in the "to-BGP" statement where "bgp" should >>be replaced by "ospf4" of course, i am sorry. >> >>The goal is to redistribute ospf into bgp and the contrary. >> >>I have only about 10 to 20 routes. >> >>I will change "bgp" to "ospf4" in the config tomoworow and let you informed >>but it's not the reason why the BGP routes suddenly disappear after some >>seconds, something crashed inside the router. >> >>Do you mean that the ospf to BGP redistribution is bugged? >> >>Thanks again >> >>I would really like to finish my BGP tutorial >>http://openmaniak.com/vyatta_case4.php >> >>Troopy >> >> >> >>---------- Original Message ---------------------------------- >>From: Arthur Xiong <[EMAIL PROTECTED]> >>Date: Tue, 20 Nov 2007 07:40:22 -0800 (PST) >> >>> >>>1. How many BGP routes would be there on the router? >>> >>>2. >>>" >>> policy-statement "to-BGP" { >>> term 1 { >>> from { >>> protocol: "connected" >>> } >>> then { >>> action: "accept" >>> } >>> } >>> term 2 { >>> from { >>> protocol: "bgp" >>> } >>> then { >>> action: "accept" >>> } >>> } >>> } >>>" >>>Assuming there is no manipulation for the bgp routes to be advertised to the >>>peers, term 2 is not necessary. >>> >>>3. >>>" >>> policy-statement "to-BGP" { >>> term 1 { >>> from { >>> protocol: "connected" >>> } >>> then { >>> action: "accept" >>> } >>> } >>> term 2 { >>> from { >>> protocol: "bgp" >>> } >>> then { >>> action: "accept" >>> } >>> } >>> } >>>" >>>Term 2 might not be tested for OSPF yet. >>> >>> >>>--Arthur >>> >>>----- Original Message ----- >>>From: "Troopy ." <[EMAIL PROTECTED]> >>>To: vyatta-users@mailman.vyatta.com >>>Sent: Tuesday, November 20, 2007 2:13:02 AM (GMT-0800) America/Los_Angeles >>>Subject: Re: [Vyatta-users] BGP problems >>> >>> >>>HEllo, >>> >>>That's sad but i have the feeling there is still the same BGP problem on VC >>>3.0. >>> >>>Case study: openmaniak.com/vyatta_case4.php >>>Live CD 3.0 + floppy disk >>> >>> >>>Below the router config. >>>When the router is loaded the BGP appears correctly for >>> some seconds and then disappear. >>> >>>And after show bgp routes, i have: >>> >>>"BGP is not configured" >>> >>> >>> Troopy >>> >>> >>>[EMAIL PROTECTED] show >>> protocols { >>> bgp { >>> bgp-id: 50.0.1.2 >>> local-as: 65001 >>> export: "to-BGP" >>> peer "10.0.1.1" { >>> local-ip: 10.0.2.2 >>> as: 65001 >>> next-hop: 10.0.2.2 >>> } >>> peer "100.0.2.4" { >>> import: "LocalPref" >>> local-ip: 100.0.2.2 >>> as: 65004 >>> next-hop: 100.0.2.2 >>> } >>> } >>> ospf4 { >>> router-id: 50.0.1.2 >>> area 0.0.0.0 { >>> interface eth0 { >>> address 10.0.2.2 { >>> } >>> } >>> } >>> export: "to-OSPF" >>> } >>> } >>> policy { >>> policy-statement "to-OSPF" { >>> term 1 { >>> from { >>> protocol: "connected" >>> } >>> then { >>> metric: 2000 >>> action: "accept" >>> } >>> } >>> term 2 { >>> from { >>> protocol: "bgp" >>> } >>> then { >>> metric: 2000 >>> action: "accept" >>> } >>> } >>> } >>> policy-statement "to-BGP" { >>> term 1 { >>> from { >>> protocol: "connected" >>> } >>> then { >>> action: "accept" >>> } >>> } >>> term 2 { >>> from { >>> protocol: "bgp" >>> } >>> then { >>> action: "accept" >>> } >>> } >>> } >>> policy-statement LocalPref { >>> term 1 { >>> then { >>> localpref: 222 >>> action: "accept" >>> } >>> } >>> } >>> } >>> interfaces { >>> loopback lo { >>> address 50.0.1.2 { >>> prefix-length: 32 >>> } >>> } >>> ethernet eth0 { >>> hw-id: xxxxx >>> address 10.0.2.2 { >>> prefix-length: 24 >>> } >>> } >>> ethernet eth1 { >>> hw-id: xxxxx >>> address 100.0.2.2 { >>> prefix-length: 24 >>> } >>> } >>> } >>> service { >>> >>> >>>______________________________________________________ >>>Désirez vous une adresse éléctronique @suisse.com? >>>Visitez la Suisse virtuelle sur http://www.suisse.com >>> >>>_______________________________________________ >>>Vyatta-users mailing list >>>Vyatta-users@mailman.vyatta.com >>>http://mailman.vyatta.com/mailman/listinfo/vyatta-users >>> >>> >> >> >> >>______________________________________________________ >>Désirez vous une adresse éléctronique @suisse.com? >>Visitez la Suisse virtuelle sur http://www.suisse.com >> >> > > > >______________________________________________________ >Désirez vous une adresse éléctronique @suisse.com? >Visitez la Suisse virtuelle sur http://www.suisse.com > > ______________________________________________________ Désirez vous une adresse éléctronique @suisse.com? Visitez la Suisse virtuelle sur http://www.suisse.com _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
