[isp-bgp] Re: iBGP routing issues...

["Chris Hale" <chale@...>]

**On Tue, Aug 24, 2004 at 08:37:22AM -0400, Chris Hale wrote:
**> Scenario:
**>
**> Internet A --- > EBGP -- > Router1 --- > RIPv2 --- > Router 2 --- >
**RIPv2
**> --- > Router 3 --- > EBGP --- > Internet B
**
**Are you redistributing internet bgp routes into router 2? otherwise
**router2
**won't know where to go, or can cause routing loops. reocmmendation is to
**run
**ibgp on router2 as well. redistribution is usually a bad idea.
**

[Chris Hale] No, currently router 2 does not support BGP.

**>
**> Internet A feed is DS-3, getting full routes to Router 1.  Internet B
**feed
**> is dual T-1, getting default only to Router 3.  Router 1 and Router 3
**are
**> meshed with iBGP.
**>
**> Issues:  We?re getting full routes at Router 3 via iBGP from Router 1,
**but
**> they?re getting installed into the routing tables as directly connected
**
**not sure if i follow that part..

[Chris Hale] If I do a show ip route on router 3, most of the BGP routes
received from router 1 by router 3 show a next hop of 94.1, and shows
"possibly down".  If I do a show ip route 66.203.94.1, it shows a route in
the tables, but a metric of a million or some absurd number.  There is a
routing loop between router 3 and router 2.  I tried to use RIPv2 to inject
an automatic metric of 3 for all advertised routes from router 3, but router
2 is still taking the default route from router 3 when it should be getting
a better, lower cost route from router 1.

**
**> routes, with a next hop of the /30 from Router 1.  Next hop is
**inaccessible:
**
**probably b/c nexthop is not reachable

[Chris Hale] 
 [Chris Hale] No, nexthop is pingable and reachable.

We had to drop the iBGP and BGP sessions on router 3 to get things working
this morning.  I'll just see if I can get a BGP-capable router to replace
router 2.

**
**do a 'sh ip bgp x.x.x.x' where x.x.x.x is anything out on the internet
**(e.g. 3.0.0.0)
**and what is the nexthop ? 66.203.94.x? and also do sh ip route on the next
**hop address
**as well.. that should help debug.
**
**-J
**
**--
**James Jun                                            TowardEX
**Technologies, Inc.
**Technical Lead                        Network Design, Consulting, IT
**Outsourcing
**james@...                  Boston-based Colocation & Bandwidth
**Services
**cell: 1(978)-394-2867           web: http://www.towardex.com , noc:
**www.twdx.net
**
**
**_______________ 

 ______________



**
**To unsubscribe via postal mail, please contact us at:
**Jupitermedia Corp.
**Attn: Discussion List Management
**475 Park Avenue South
**New York, NY 10016
**
**Please include the email address which you have been contacted with.










To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.