From: Prashant Shukla (shukla_cisco@yahoo.co.in)
Date: Wed Sep 12 2007 - 10:48:54 ART
Ashok,
It seems you are using the loopback to peer with your I/E-BGP peers and the configs do not mention the "update-source" cmd.
By default , if the update-source is not mentioned the peering is done using the outgoing interface's IP .
Here it seems in the BGP peering the routers are expecting the source of the BGP TCP connection to be interface IPs rather that loop backs. (default).
Would recommend using update-source with peers and Im sure the peering will be up.
Have burnt my hands in the past with same.
Shukla.
Cisco Systems.
Scott Morris <swm@emanon.com> wrote: Take a look at "debug ip packet" perhaps and you may find that the packets
are coming from an IP address that the other side doesn't have listed in its
neighbor table. (e.g. update-source)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Ashok CCIE
Sent: Wednesday, September 12, 2007 7:27 AM
To: ccielab@groupstudy.com
Subject: BGP over Frame-relay
Hi Team,
I am configuring IBGP b/w loopback interfaces of two interfaces which are
over Frame-relay. But my routers are not making any neighbor relationship.
Why so?
Config is here..
R1
router bgp 100
no synchronization
bgp router-id 2.2.2.1
bgp log-neighbor-changes
network 1.1.1.0 mask 255.255.255.0
network 2.2.2.1 mask 255.255.255.255
neighbor 2.2.2.2 remote-as 100
neighbor 2.2.2.2 next-hop-self
neighbor 2.2.2.3 remote-as 100
neighbor 2.2.2.3 next-hop-self
no auto-summary
R2
router bgp 100
no synchronization
bgp router-id 2.2.2.2
bgp log-neighbor-changes
network 1.1.1.0 mask 255.255.255.0
network 2.2.2.2 mask 255.255.255.255
neighbor 2.2.2.1 remote-as 100
neighbor 2.2.2.1 ebgp-multihop 255
no auto-summary
Could you please help?
Thanks,
Ashok
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:11 ART