BGP/OSPF ID mismatch - new thoughts

From: tang bing (tang_bing@xxxxxxxxx)
Date: Sat Feb 16 2002 - 01:35:56 GMT-3


   
          r1---1.1.1.1
           |
          | |
         | |
        | |
2.2.2.2 r2 r3 3.3.3.3
               |
               10.10.10.0/24

suppose in the beginning ,
r1-r2-r3 is hub-spoke OSPF , ospf router-id is as
showed .
r1 is route-reflector for r2/r3 , bgp router-id is the
same as ospf router-id , sync is on of course .

now, in r2 you found the route 10.10.10.0 in not sync.
because router-id mismatch .
If you want solve this problem with changing r1's bgp
router-id to 3.3.3.3 , then r2 will see this route
from the same originater , sounds good ?
BUT, now r1 and r3 are using the same bgp-router-id
which cause BGP never form neighbor .
OK, let's change r3's bgp router-id to something else
, now in r1 , the route 10.10.10.0 will come from r3
with different source ( router-id mismatch again ) ,
the route will not sync agian and thus will not send
to r2 at all .

Is this logic right ?
If so , confederation is the only choice .

Ben



This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:24 GMT-3