Hi All,
Just trying to get my head around why BGP prefers a certain route over
others in my example below. I've read up on how BGP makes it's path
selection decision but I can't follow why it hasn't chosen a route with
a higher local preferences.
Here's my example...
Edge-Router#sh ip bgp
Hi,
On Tue, Sep 09, 2008 at 11:44:45PM -0400, Gregory Boehnlein wrote:
3356, (aggregated by 3356 4.69.130.12)
4.53.194.5 from 4.53.194.5 (4.69.181.195)
Origin IGP, metric 1000, localpref 100, valid, external,
atomic-aggregate
Community: 3356:0 3356:3 3356:100 3356:123
You could fix it with a route-map and as-path.
ip as-path access-list 98 permit ^3356$
route-map as-3356-inbound permit 5
match as-path 98
set local-preference 200
Then in the router bgp section, add this:
neighbour 4.53.194.5 route-map as-3356-inbound in
This will solve the problem for the
Cisco RSP4+ (R5000) processor with 262144K/2072K bytes of memory. Slave in
slot 3 is running Cisco IOS Software, RSP Software (RSP-IK91SV-M), Version
12.2(25)S12, RELEASE SOFTWARE (fc1)
Hello,
I'm bringing up a new BGP peer and am working at tweaking our BGP
routing configuration. In
On Wednesday 10 September 2008 11:44:45 Gregory Boehnlein
wrote:
Can someone explain
to me the reason why Path #3 is being chosen over the
lower AS-Path #1 and #2 routing choices?
Path 3 is the best because it has a higher LOCAL_PREF value
(150) vs. that from paths 1 and 2.
Cheers,
Mark.
: Gert Doering [mailto:[EMAIL PROTECTED]
Sent: giovedì 29 maggio 2008 22.20
To: Brian Turnbow
Cc: Gary Roberton; Pete Templin; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] BGP Route selection
Hi,
On Fri, May 23, 2008 at 05:08:58PM +0200, Brian Turnbow wrote:
Setting the metric is not going
Hi,
On Fri, May 23, 2008 at 03:08:54PM +0100, Gary Roberton wrote:
Router A BGP table entry is shown here;
* 90.0.0.0 10.40.1.6 50 0 64604 1000 i
* 10.40.1.2 0 64603 1000 i
Ah. Different next-hop ASes.
You
Hi,
On Fri, May 23, 2008 at 05:08:58PM +0200, Brian Turnbow wrote:
Setting the metric is not going to affect your BGP route selection.
Read up on the BGP decision algorithm :-)
gert
--
USENET is *not* the non-clickable part of WWW!
Hi,
On Fri, May 23, 2008 at 10:53:24AM -0500, Pete Templin wrote:
You should tweak a different knob to achieve the desired results.
Origin code comes to mind as an easy twiddle. Or, have the remote
routers send a community to request a particular local preference (as
someone else
Gert Doering wrote:
On Fri, May 23, 2008 at 05:08:58PM +0200, Brian Turnbow wrote:
Setting the metric is not going to affect your BGP route selection.
Read up on the BGP decision algorithm :-)
Your can be singular or plural, specific or general. In this case,
specifically, it is not
Hi,
On Thu, May 29, 2008 at 03:44:58PM -0500, Pete Templin wrote:
Gert Doering wrote:
On Fri, May 23, 2008 at 05:08:58PM +0200, Brian Turnbow wrote:
Setting the metric is not going to affect your BGP route selection.
Read up on the BGP decision algorithm :-)
Your can be singular or
Hi All
I have router A receiving network 80.0.0.0 from router 1 and router 2.
Router 2 weights its metric so that it is less favourable.
In router A's BGP table I can see both routes and the route from Router 1 is
placed in the global routing table. Fine.
When you turn off Router1, Router A
On Fri, May 23, 2008 at 10:21 AM, Gary Roberton
[EMAIL PROTECTED] wrote:
Hi All
I have router A receiving network 80.0.0.0 from router 1 and router 2.
Router 2 weights its metric so that it is less favourable.
In router A's BGP table I can see both routes and the route from Router 1 is
Gary Roberton wrote:
I have router A receiving network 80.0.0.0 from router 1 and router 2.
Router 2 weights its metric so that it is less favourable.
Are routers 1 and 2 in your AS, or in another AS? Also, please clarify
'weights its metric' - do you mean it adjusts weight, it adjusts
All
The network in question is actually 90.0.0.0. All routers are in their own
separate AS. The route in question is a connected network not
redistributed.
To make it clearer;
Router X has network 90.0.0.0 connected
Router X advertises to both Router1 and Router2.
Router 1 sends it on to
On how BGP selects paths
Regards
Brian
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gary Roberton
Sent: venerdì 23 maggio 2008 16.09
To: Pete Templin
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] BGP Route selection
All
The network in question
Gary Roberton wrote:
Router A BGP table entry is shown here;
* 90.0.0.0 http://90.0.0.0 10.40.1.6
http://10.40.1.6 50 0 64604 1000 i
* 10.40.1.2
http://10.40.1.2 0 64603 1000 i
Paths come from different
Pete
To clarify - if I just adjust the local preference on the receiving router,
that should do it?
But if I didn't have an admin control of the receiving router I would do it
on the advertising router by requesting a community.
Just sanity checking...
On Fri, May 23, 2008 at 4:53 PM, Pete
Update - used local preference set on the receiving router and got the
behaviour I wanted. Thanks to all for help and suggestions. I did it using
set local-pref on a route map of the receiving router.
Cheers
Have a good weekend.
Gary
On Fri, May 23, 2008 at 4:58 PM, Gary Roberton [EMAIL
10:09 AM
To: Pete Templin
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] BGP Route selection
All
The network in question is actually 90.0.0.0. All routers are in their own
separate AS. The route in question is a connected network not
redistributed.
To make it clearer;
Router X
20 matches
Mail list logo
