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 trou
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 hav
On 27 aug 2008, at 14:16, Steve Bertrand wrote:
The only reason I use loopbacks for eBGP multihop is so that if one
of my physical interfaces goes down taking a transit link with it,
these particular sessions will attempt to re-establish via another
path.
Actually they should stay up.
Wo
Iljitsch van Beijnum wrote:
On 27 aug 2008, at 7:58, Paul Wall wrote:
- single loopback/single IP for all peers, or;
- each peer with its own loopback/IP?
You should use caution when using loopback IP addresses and building
external multihop BGP sessions. By permitting external devices to
tr
On 27 aug 2008, at 7:58, Paul Wall wrote:
- single loopback/single IP for all peers, or;
- each peer with its own loopback/IP?
You should use caution when using loopback IP addresses and building
external multihop BGP sessions. By permitting external devices to
transmit packets to your loopba
On Tue, Aug 26, 2008 at 7:48 PM, Steve Bertrand <[EMAIL PROTECTED]> wrote:
> There are a few benefits to doing it this way (IMHO), but I see obvious
> benefits of using a single loopback interface and single IP for ALL of these
> multihop peers. Before I state good/bad, or get any wrong idea in my
Steve,
You ask a very good question because I have seen some providers embark
on the multiple loopback approach for numerous reasons. I suggest a
single loopback per routing-instance whenever possible. The cost
savings in OSS and integration in routing configurations with a single
repeata
Hi everyone,
This question comes after likely overlooking an IETF document or BCP
that describes what I'm after. Given that I am looking for advice from
someone who is more experienced operationally in this regard than me,
and that this technically is an implementation-neutral question, I
wan
8 matches
Mail list logo
