[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zebra
Subject:    [zebra 18100] Re: bgp connect failed between two hosts,  Active
From:       Jack Lin <jacklin () andrew ! cmu ! edu>
Date:       2003-02-28 22:07:46
[Download RAW message or body]

Hi,
1) the two hosts are able to ping each other.  
2) they can not telnet each other to the bgp port (179?)
3) This is what's in the log files for them.
2003/02/26 17:25:49 BGP: 128.2.76.251 [Event] Connect start to
128.2.76.251 fd 11
2003/02/26 17:25:49 BGP: 128.2.76.251 [Event] Connect failed (Operation
now in progress)

4) i think if the ebgp-multihop line by itself defaults to at most 255,
so that should not be a problem. ( i can tell this by the "show ip bgp
neighbor" command)

Anyone has any ideas why i am not able to connect those two hosts?  my
options are exhausting...  

Thanks.

jack





On Thu, 2003-02-27 at 04:05, Stephane Bortzmeyer wrote:
> On Wed, Feb 26, 2003 at 07:06:21PM -0500,
>  Jack Lin <jacklin@andrew.cmu.edu> wrote 
>  a message of 70 lines which said:
> 
> > mine, but i'm having trouble connecting to another one of my hosts.  The
> > router id are both 0.0.0.0 when i query "show ip bgp neighbors".    I
> > have zebra runnning on both machine as well.  
> 
> OK, test the following:
> 
> * can they ping each other?
> * can they 'telnet remote-router bgp' each other (not sufficient,
>   because of eBGP multihop, but necessary),
> * what is in the log files?
> 
> Zebra does not log (unfortunately) all the possible problems. tcpdump
> often reveals them. For instance, if the problem is an AS mismatch,
> tcpdump shows it:
> 
> 192.134.7.241.179 > 192.134.7.245.46151: P 1:24(23) ack 46 win 17520:\
>       BGP (NOTIFICATION: error OPEN Message Error, subcode Bad Peer AS) [ttl 1]
> 
> >   neighbor 128.2.76.251 ebgp-multihop
> 
> You can try to set up explicitely a hop count at the end of the above
> line.
> 


[prev in list] [next in list] [prev in thread] [next in thread]