From: Herbert Maosa (asawilunda@googlemail.com)
Date: Sat Oct 20 2007 - 09:47:53 ART
Very basic single hop eBGP neighbors using Loopback Interfaces, connected
through a point to point HDLC Link. I was expecting myself to configure
neighbor ebgp-multihop 2 or neighbor disable-connected-check before the
peering could come up, but this peering is coming up before I configure
either command.
I am GUESSING this is happening because I have configured the loopbacks to
be reachable through the point to point interfaces, but I am wondering iof
anyone has links to any documentation that explains this behaviour.
Configs below.
*Router2 Config*
router bgp 25
no synchronization
bgp router-id 150.150.2.2
bgp log-neighbor-changes
neighbor 150.150.5.5 remote-as 25
neighbor 150.150.5.5 update-source Loopback0
no auto-summary
!
ip classless
ip route 150.150.5.0 255.255.255.0 Serial0/2/0
*Router5 Config*
**
router bgp 25
no synchronization
bgp router-id 150.150.5.5
bgp log-neighbor-changes
neighbor 150.150.2.2 remote-as 25
neighbor 150.150.2.2 update-source Loopback0
no auto-summary
!
ip classless
ip route 150.150.2.0 255.255.255.0 Serial0/2/0
*Rack1R2#*sh ip bgp sum
BGP router identifier 150.150.2.2, local AS number 25
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
150.150.5.5 4 25 23 23 1 0 0 00:19:12 0
Rack1R2#
*Rack1R5#sh* ip bgp sum
BGP router identifier 150.150.5.5, local AS number 25
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
150.150.2.2 4 25 23 23 1 0 0 00:19:56 0
Rack1R5#
Herbert.
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:17 ART