Some comments inline.
> Also, put in your BGP configuration
> no synchronization - This will allow BGP to establish before EIGRP
finishes.
The synchronization rule only applies to IBGP neighbors. In this case,
these are EBGP neighbors and synchronization does not apply. As long as
routes are in the BGP table and routing table of A, it will pass them along
to B.
Also, synchronization applies to routes learned via IBGP. The prefixes he
is advertising via the network command are directly attached, which
automatically places them in the routing table.
Regards,
John
> no auto-summary
>
> Also, if you want to use the Loopback interface as the IP address to be
> referenced by the neighbors then use the following command....
>
> ie
> neighbor 1.1.1.1 remote-as 400
> neighbor 1.1.1.1 update-source Loopback0 (Or whatever Loopback you want
to
> use)
You can do this, but I believe it's not often used in EBGP. EBGP neighbors
are generally directly connected and one hop away. If you use loopbacks as
your update-source on each side, then each side also has to have the ebgp
multihop command in place because the peer is now seen to be two hops away.
_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
