From: Donny MATEO (donny.mateo@sg.ca-indosuez.com)
Date: Fri Jul 04 2003 - 02:58:27 GMT-3
If I remember correctly there was an old thread discussing this. The conclusion is something like BGP need specific route to establish peering. Not sure if there is anymore information as to why and so on.
Donny
"Volkov, Dmitry
(IDS Canada)" To: "'ccielab@groupstudy.com'" <ccielab@groupstudy.com>
<dmitry_volkov@ca cc:
.ml.com> Subject: BGP peer establishment
Sent by:
nobody@groupstudy
.com
07/04/2003 06:22
AM
Please respond to
"Volkov, Dmitry
(IDS Canada)"
R5(172.50.50.5)---------(.1)pix(.10)--------(172.50.10.1)R1
R5 can ping R1; R5 uses default route to reach R1. R5 can not establish BGP
peering with R1
until I put static route - more specific than 0.0.0.0 0.0.0.0 - WHY ?
r5#sh ip bgp sum
BGP router identifier 60.5.5.5, local AS number 55
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
172.50.10.1 4 65 0 0 0 0 0 never Active
r5#sh ip ro
<snip>
R* 0.0.0.0/0 [120/1] via 172.50.50.1, 00:00:06, FastEthernet0/0
r5#conf t
Enter configuration commands, one per line. End with CNTL/Z.
r5(config)#ip route 172.50.10.1 255.255.255.255 172.50.50.1
00:55:02: %BGP-5-ADJCHANGE: neighbor 172.50.10.1 Up bgp ev
r5#sh ip bgp sum
BGP router identifier 60.5.5.5, local AS number 55
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
172.50.10.1 4 65 5 5 1 0 0 00:02:01 0
r5# sh ip ro
<snip>
S 172.50.10.1/32 [1/0] via 172.50.50.1
R* 0.0.0.0/0 [120/1] via 172.50.50.1, 00:00:13, FastEthernet0/0
r5#
router bgp 55
bgp log-neighbor-changes
neighbor 172.50.10.1 remote-as 65
neighbor 172.50.10.1 ebgp-multihop 2
r1#
router bgp 65
bgp log-neighbor-changes
neighbor 172.50.50.5 remote-as 55
neighbor 172.50.50.5 ebgp-multihop 2
Thank You,
Dmitry Volkov
CCIE # 10292
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:23 GMT-3