Thanks to all who responded. ebgp-multihop and update-source are both
present. Routes are set because we can ping between the two routers
even with setting the source IP address to the loopback interface.
I am going to substitute a test router and see if the same problem
presents itself.
Christian Koch wrote:
also ensure you have the update source set to loopback (neighbor
x.x.x.x update-source loopback0)
-christian
On Wed, Jun 25, 2008 at 6:13 PM, Tim Durack <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Do you have ebgp-multihop configured on the loopback session?
Tim:>
On Wed, Jun 25, 2008 at 8:58 PM, Roy <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> Hi,
>
> We are working with a new ISP for service. This one is via
metro ethernet.
> They require two BGP sessions. One goes between the ends of
the ethernet.
> The other BGP session is between a loopback interface on our
router and a
> loopback interface on one of the ISP's other routers.
>
> The first session comes up just fine but the second one using
loopback
> interfaces will not establish. I did some packet traces using a
Linux box
> and tcpdump and it would seem that the packets from our loopback
session go
> into the metro ethernet and disappear. When their router tries
to connect,
> the packets arrive and responses are sent but they too seem to
be ignored.
>
> The ISP blames us of course. I told them the packets seem to be
going out
> the switch port to the metro ethernet.
> Has anyone seem such a problem? Is there some strange magic
limit to the
> number of peers or something?
>
> Roy
> <http://puck.nether.net/pipermail/cisco-nsp/>
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
