From: Calton, Doug (Doug.Calton@getronics.com)
Date: Fri Jan 23 2004 - 22:24:58 GMT-3
Yes - the ebg-multihop tells bgp to expect to have to traverse more hops
in that direction to reach the neighbor. Normally (for Ebgp), the
expectation is that the peer is directly connected to the network, and
will fail to establish the TCP connection when the specified neighbor
address is not found.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
alsontra@hotmail.com
Sent: Friday, January 23, 2004 7:03 PM
To: ccielab@groupstudy.com
Subject: BGP MultiHop
If your using loopback to source BGP sessions in a single direction, do
you have to specify "neighbor/ebgp-multihop " on both bgp peers? Or do
you have to use the "neighbor\ebgp-multihop" command on both peer
involved in the peer relationship?
For example:
(assuming that IGPs or statics are in place and life is good)
(Lo1-1.1.1)--R1-------------R2
R1 neighbors statements:
neighbor 4.4.4.4 remote-as (100)
R2 neighbor statements
neighbor 1.1.1.1 remote-as 200
neighbor 1.1.1.1 update-source-loopback Lo0
neighbor 1.1.1.1 ebgp-multihop 255
I suspect that you only need to use the "neighbor/ebgp-multihop"
statement on the bgp peer peering with a host using an ip address on a
non-connected network.
Thanks,
Alsontra
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:49 GMT-3