[107148] in North American Network Operators' Group
Re: BGP, ebgp-multihop and multiple peers
daemon@ATHENA.MIT.EDU (Rick Ernst)
Wed Aug 27 12:00:39 2008
In-Reply-To: <48B54AEE.40007@ibctech.ca>
Date: Wed, 27 Aug 2008 09:00:21 -0700 (PDT)
From: "Rick Ernst" <ernst@easystreet.com>
To: "Steve Bertrand" <steve@ibctech.ca>
Cc: NANOG list <nanog@merit.edu>
Reply-To: ernst@easystreet.com
Errors-To: nanog-bounces@nanog.org
If you keep a separate peering/loopback-IP for each peer, you can move
individual peering sessions to other devices if needed.
On Wed, August 27, 2008 05:39, Steve Bertrand wrote:
> Iljitsch van Beijnum wrote:
>
>> The advantage of a separate loopback address is that if you ever have
>> any trouble, you can simply remove that address and the trouble is gone,
>> too. This wouldn't work for the loopback address you also use for iBGP
>> or a physical interface.
>
> Ok. It probably would have made much more sense in my original post to
> clarify that each eBGP multihop peer session is configured on separate
> loopback interfaces, apart from the ones I use internally.
>
> Generally, I leave lo0 as-is, lo1 for internal, then configure each eBGP
> multihop peer on an incremental loopback basis thereafter.
>
> So, in essence, I'll continue to use a loopback (separate from internal
> functions) for ebgp-multihop peers, but instead of each session having
> its own interface/IP, I'll share one for all of them.
>
> Thanks everyone!
>
> Steve
>
