> neighbor $slowjoe {
> remote-as xxxx
> descr "slowjoe"
> set localpref 100
> set weight 45
> announce self
> announce IPv6 none
> tcp md5sig passwd xxxxxxxxx
> prepend-self 2
> }
>
> ... right ?
>
>
> And while I'm at it:
> - if I wan't to make sure that $slowjoe is chosen as a last resort,
how
> many times (0-9) should I prepend ?
See the combined explanation below...
> - in short, how will the 'prepend-[self|neighbor]' attributes affect
the
> 'localpref' and/or 'weight' ?
It's my understanding that prepending excludes the 'weight'
decision-making so long as the paths being compared are no longer of
equal as-path length... so to answer your question 'how many times
should I prepend' I'd answer... 'as many times until the $slowjoe
as-path appears longer than the other carrier as-paths.' Keep checking a
looking glass (preferably $slowjoe's if they have one) for $slowjoe's
announcements of your blocks to be sure.
> - In contrast to 'prepend-self' when should the 'prepend-neighbor'
> attribute be used ?
It's also my understanding that if you are looking to make $slowjoe your
backup peer, then you could use 'prepend-self' for your outgoing
announcements, and 'prepend-neighbor' for their incoming announcements.
The former would make reachability to you via $slowjoe less attractive
than via other carriers you have, and the latter makes the routes you
receive from $slowjoe less attractive than routes you received from
other carriers... so imho, use both.
>
> Thank you in advance.
>
> /per
> [EMAIL PROTECTED]
If I'm wrong about these statements, please let me know...
