From: Marvin Greenlee (marvingreenlee@yahoo.com)
Date: Mon Nov 27 2006 - 12:50:36 ART
...
'no-prepend' prevents the 'local-as' AS from being
added to the path, but only for peerings "behind" the
'local-as' peering. From the outside, you will always
see the 'local-as'.
****
R1(AS1)--R2(AS23)--R3(AS23)--R4(AS4)--R5(AS5)
Network XX on R1, Network YY on R5.
Assuming that R3's peering to R4 includes local-as 100
R1(AS1)--R2(AS23)--R3(AS23)--local-AS100))-R4(AS4)--R5(AS5)
R1 sees network YY with path 23 100 4 5.
with no-prepend on R3's peering to R4, R1 would see 23
4 5.
R5 sees network XX with path 4 100 23 1.
with no-prepend on R3's peering to R4, R5 still sees
the path as 4 100 23 1.
****
In this case, R1 and R2 are "behind the 'local-as'",
and may or not see the local-as in the path depending
on whether or not the no-prepend keyword is used. R4
and R5 are "outside the 'local-as'", and will always
see local-as, regardless of whether or not R3 is
configured with the 'no-prepend' keyword.
Thanks,
Marvin Greenlee
CCIE #12237, MCSE, JNCIA-M
--- Yoshe Rionando <Rionando@swadharma.com> wrote:
> There is an effect to configure :
> neighbor xx.xx.xx..xx local-as AA no-prepend
>
> I think it not append the AS to the list.
> I try this, but no effect appear.
>
>
> Yoshe Rionando Y.
> PT. Swadharma Duta Data
> Network & System Engineering Dept.
> Senior Network Engineer
> phone : 62 21 8318881
> fax : 62 21 8297293
> mobile : 62 8159084895
>
>
This archive was generated by hypermail 2.1.4 : Fri Dec 01 2006 - 08:05:48 ART