From: Pink, Paul (Paul.Pink@mtvstaff.com)
Date: Fri Dec 02 2005 - 15:36:59 GMT-3
First show ip bgp should tell you what the next hop is. The next hop
should be fine as you are able to establish a peer.
Second there are two tables you should be concerned with - The IGP and
the BGP routing tables.
If the two are not "synchronized" you will not be able to route.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Chula Bandara
Sent: Friday, December 02, 2005 1:20 PM
To: jslauer@hotmail.com; ongdes@singnet.com.sg; ccielab@groupstudy.com
Subject: Re: iBGP
if you can peer you already have a route to R1. can't you simply use
next-hop-self.
--------------------------------------------------------------------
From: "joshua lauer" <jslauer@hotmail.com>
Reply-To: "joshua lauer" <jslauer@hotmail.com>
To: "Des" <ongdes@singnet.com.sg>, <ccielab@groupstudy.com>
Subject: Re: iBGP
Date: Fri, 2 Dec 2005 13:08:15 -0500
Try policy routing in the middle or creating a GRE tunnel since R2 is
not running BGP.
JL
----- Original Message ----- From: "Des" <ongdes@singnet.com.sg>
To: <ccielab@groupstudy.com>
Sent: Friday, December 02, 2005 12:57 PM
Subject: iBGP
>Hi there,
>
>I have the following scenerios.
>
>
>R1(AS100)------R2(non-bgp)-----R3(AS100)
>
>I am peering with R3 with ibgp. I can receive all the routes from
>R1.
>But however, I cannot ping R1 advertised networks. I need to have a
>static route at R2 for those network advertised by R1. Is there any
>way
>without adding static routes?
>
>Tks!
>
>Des
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Jan 09 2006 - 07:07:50 GMT-3