From: RSiddappa@xxxxxxxxxx
Date: Sat Feb 02 2002 - 16:05:10 GMT-3
John,
Thanks.
But I guess when I am using RR, changing the router ID will not make any
differnce right.
R.
-----Original Message-----
From: John Neiberger [mailto:neiby@ureach.com]
Sent: Saturday, February 02, 2002 10:40 AM
To: Siddappa, Rajeev; ccielab@groupstudy.com
Subject: Re: RE: BGP Sync
Depending on the exact scenario and its requirements, you have
at least five options:
1. Use a full iBGP mesh
2. Use confederations instead of route reflectors
3. Alter the BGP or OSPF ID manually by using the
commands 'ospf router-id' and/or 'bgp router-id'
4. Move your redistribution point to a different router
5. Break up your iBGP mesh over different OSPF areas
HTH,
John
---- On Sat, 2 Feb 2002, RSiddappa@NECBNS.com
(RSiddappa@NECBNS.com) wrote:
>
>
> John,
>
> Looks like no one has the solution yet. If u ahev the
previosu mails pls
> post it agin.
>
> I could not find it.
>
> R.
>
> -----Original Message-----
> From: John Neiberger [mailto:neiby@ureach.com]
> Sent: Friday, February 01, 2002 12:29 PM
> To: Bob Sinclair; ccielab@groupstudy.com
> Subject: Re: BGP Sync
>
>
> It appears that you're running into the very BGP/OSPF issue
> that we've been discussing a *lot* lately. The problem is
that
> R2 is learning iBGP routes from one router and the OSPF
routes
> from another.
>
> When you use OSPF as your IGP there is an additional
> synchronization rule: the router ID of the router
advertising
> the iBGP routes must match the router ID of the router
> advertising the OSPF routes.
>
> To verify the issue, do "show ip bgp 140.10.2.0" followed
> by "show ip ospf database". You'll probably see that the
> advertising router IDs do not match.
>
> Check the recent archives. I believe we've had at least
three
> threads on this in the last three or four weeks. There are
> some good ideas in there about how to resolve this issue, or
at
> least work around it.
>
> HTH,
> John
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:10 GMT-3