From: Dan C (cdan2154@gmail.com)
Date: Mon Feb 25 2008 - 03:35:00 ARST
Hi Matt,
Check your ip addressing in R2 under bgp process: instead of nei 1.1.1.2 it
should be 1.1.1.2 ....
Cheers,
Dan
On Sun, Feb 24, 2008 at 2:54 AM, Matt Bentley <mattdbentley@gmail.com>
wrote:
> I thought I had a really good understanding of this, but it seems I am
> wrong.
>
> I have a BGP neighbor relationship between two devices
>
> R1 (1.1.1.1) -------------> R2 (1.1.1.2)
> R1 Fa0/1 connects to R2 Fa0/1
>
> Underlying protocol for BGP transport is EIGRP
>
>
> R1 Config:
> router bgp 1
> bgp router-id 1.1.1.1
> neighbor 1.1.1.2 remote-as 2
> neighbor 1.1.1.2 update-source l0
> neighbor 1.1.1.2 ebgp-multihop
> !
> int l0
> ip add 11.11.11.11 255.255.255.0
>
> R2:
> router bgp 2
> bgp router-id 2.2.2.2
> neighbor 1.1.1.1 remote-as 1
> neighbor 1.1.1.1 update-source l0
> neighbor 1.1.1.2 ebgp-multihop
> !
> ip add 12.12.12.12 255.255.255.0
> !
>
> I can ping both the IP addresses as well as the loopback addresses. If I
> bring the neighbor relationship up first, and then issue the update-source
> option, it doesn't kill the neighbor relatinoship, however, if I bounce
> the
> interfaces, it gives the following debug. What am I missing?
>
>
> *Mar 1 00:03:43.819: BGP: 1.1.1.1 open active, local address 12.12.12.12
> *Mar 1 00:03:43.819: BGP: 1.1.1.1 read request no-op
> *Mar 1 00:03:43.819: BGP: 1.1.1.1 open failed: Connection refused by
> remote
> host, open active delayed 14770ms (35000ms max, 60% jitter)
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2008 - 16:54:49 ARST