ebgp-multi-hop connection

[wgranada1]

Hi everyone how are things? I have a quick quesiton here. I'm trying to create a ebgp-multihop connection but the problem is it never establishes. I don't have any access-list on the interface so it is wide open, I've been looking at this for a while now so everything looks ok to me. I know I'm missing something but anyways here is my config:

router bgp 60301

neighbor 192.168.50.50 remote-as 64637

neighbor 192.168.50.50 ebgp-multihop 5

neighbor 192.168.50.50 update-source FastEthernet1/15

neighbor 192.168.50.50 version 4

neighbor 192.168.50.50 soft-reconfiguration inbound

neighbor 192.168.50.50 prefix-list from-interim in

neighbor 192.168.50.50 prefix-list to-interm out

when I do a sh ip bgp neigh 192.168.50.50 I see the bgp state as active but not established. I've done a soft clear and clear but nothing as of yet. Thank you in advance!!

[wgranada1]

I appreciate the help...sorry guys I was trying to keep my ip private but I think I'm doing more harm than help so here is it is with the real IPs

MY SIDE:

router bgp 64821

no synchronization

bgp router-id 172.19.103.45

bgp log-neighbor-changes

neighbor 10.128.184.105 remote-as 64637

neighbor 10.128.184.105 ebgp-multihop 5

neighbor 10.128.184.105 update-source FastEthernet1/15

neighbor 10.128.184.105 version 4

neighbor 10.128.184.105 soft-reconfiguration inbound

neighbor 10.128.184.105 prefix-list from-interim in

neighbor 10.128.184.105 prefix-list to-interm out

His side:

router bgp 64637

no synchronization

neighbor 172.19.103.45 remote-as 64821

neighbor 172.19.103.45 ebgp-multihop 5

neighbor 172.19.103.45 update-source Loopback1

neighbor 172.19.103.45 soft-reconfiguration inbound

neighbor 172.19.103.45 prefix-list Routes-from-Futures in

neighbor 172.19.103.45 prefix-list Routes-to-Futures out

no auto-summary

now he told me I'm suppose to be peering with his 10.128.184.105 and inorder for me to get to that peer I need to go through the ethernet connection

My side

interface FastEthernet1/15

ip address 172.19.80.9 255.255.255.252

His side

interface gigethernet 0/1

ip address 172.19.80.10 255.255.255.252

I have routes to his 10.128.184.105

sfschirt4#sh ip route 10.128.184.105

Routing entry for 10.128.184.105/32

Known via "static", distance 1, metric 0

Redistributing via ospf 1

Routing Descriptor Blocks:

* 172.19.80.10

Route metric is 0, traffic share count is 1

and can source ping

sfschirt4#ping 10.128.184.105 source 172.19.80.9

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.128.184.105, timeout is 2 seconds:

Packet sent with a source address of 172.19.80.9

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

sorry guys about that

[wgranada1]

Also when I did run a debug I see the following:

Mar 28 15:29:17.315 UTC: BGP: 10.128.184.105 passive open to 172.19.103.45

*Mar 28 15:29:17.315 UTC: BGP: 10.128.184.105 passive open failed - 172.19.103.45 is not update-source FastEthernet1/15's address (172.19.80.9)

*Mar 28 15:29:17.315 UTC: BGP: 10.128.184.105 remote connection attempt failed, local address 172.19.103.45

*Mar 28 15:29:37.195 UTC: BGP: 10.128.184.105 open active, local address 172.19.80.9

*Mar 28 15:29:37.195 UTC: BGP: 10.128.184.105 open failed: Connection refused by remote host, open active delayed 25365ms (35000ms max, 28% jitter)

[Harold Ritter]

Warren,

172.19.103.45 is the address your peer uses. Make sure you use the interface that matches that address as your update-source on your side.

Regards,

[Martin Parry]

Hi Warran

The 172.19.103.45 address is not assigned to your F1/15 interface. You need to make sure that you have the interface assigned to this address as your update source for this peering.

Martin

[wgranada1]

I was looking over the config and noticed that I have an internal peering as well that is also using the loopback address as well if I source from the new connection as suggested will that affect what is already there?

router bgp 64821

no synchronization

bgp router-id 172.19.103.45

bgp log-neighbor-changes

redistribute ospf 1 match internal external 1 external 2 route-map to-VNET

neighbor VNET peer-group

neighbor VNET remote-as 64820

neighbor VNET update-source FastEthernet1/0

neighbor VNET version 4

neighbor VNET soft-reconfiguration inbound

neighbor VNET prefix-list from-VNET in

neighbor VNET prefix-list to-VNET out

neighbor VNET route-map from-VNET-LOCALPREF in

neighbor VNET route-map to-VNET-PREPEND out

neighbor VNET filter-list 17 out

neighbor SFS-INTERNAL peer-group

neighbor SFS-INTERNAL remote-as 64821

neighbor SFS-INTERNAL update-source Loopback0<-- Already being used

neighbor 10.128.184.105 remote-as 64637

neighbor 10.128.184.105 ebgp-multihop 5

neighbor 10.128.184.105 update-source FastEthernet1/15

neighbor 10.128.184.105 version 4

neighbor 10.128.184.105 soft-reconfiguration inbound

neighbor 10.128.184.105 prefix-list from-interim in

neighbor 10.128.184.105 prefix-list to-interm out

neighbor 172.19.98.50 peer-group VNET

neighbor 172.19.103.30 peer-group SFS-INTERNAL

no auto-summary

[Harold Ritter · Accepted solution]

Warren,

You can use the loopback interface as the update-source for the eBGP and iBGP session.

Regards,

[wgranada1]

YOU GUYS ROCK!!!!! thank you all for helping out sorry about the confusion in the beginning

I see that neighor relationship has been established:

sfschirt4#sh ip bgp neigh 10.128.184.105

BGP neighbor is 10.128.184.105, remote AS 64637, external link

BGP version 4, remote router ID 10.128.184.105

BGP state = Established, up for 00:00:10

YEAH!!!!! thank you agian!!!!!

[Martin Parry]

No Problem Warren

Glad you have it all working now.

[Martin Parry]

The update-source is specific only to that neighbor. It will not affect any other update-source interfaces you have configured under this AS.