From: Devecchio Turner (devecchio.turner@charter.net)
Date: Mon Mar 06 2006 - 00:20:16 GMT-3
Just finished a lab with the same scenario and I didn't notice i was running
12.0 on one of the routers....which by default has synchonization
on.....turned it off and all was fine..there went 20 minutes I can never
regain but, when i see that again i'll never forget :o)
----- Original Message -----
From: "Godswill Oletu" <oletu@inbox.lv>
To: "David Vasek" <dvasek@satx.rr.com>; <ccielab@groupstudy.com>
Sent: Sunday, March 05, 2006 8:36 PM
Subject: Re: BGP Neighbor Inaccessible
> did u try..
> no synchronization
> neighbor ...... next-hop-self
>
> no need for route reflector if you have a fully mesh ibgp.
>
> HTH.
>
>
> ----- Original Message -----
> From: "David Vasek" <dvasek@satx.rr.com>
> To: <ccielab@groupstudy.com>
> Sent: Sunday, March 05, 2006 9:11 PM
> Subject: BGP Neighbor Inaccessible
>
>
>> Hello Everyone,
>> What are some ways to get around an inaccessible BGP neighbor? I have
> a
>> full IBGP mesh between 3 routers. Two of the routers have EBGP peers in
> the
>> same AS. One of the IGBP routers has the network for the EGBP peer
> included
>> in it's IGP protocol, the other router does not. The second router uses
> the
>> network that is not included in it's IGP as the next hop that it
> advertises
>> to the IBGP peers. I have tried several ways to influence the next hop
>> but
>> none of them seem to work right. I am trying to do this without using
> route
>> reflectors. Any ideas?
>> Thanks,
>> -DV
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:38 GMT-3