From: Omer Ansari (omer@xxxxxxxxxx)
Date: Wed Jul 03 2002 - 19:46:27 GMT-3
Gyori, you can see this as an example:
http://www.cisco.com/warp/public/459/36.html
Just make sure R1 and R2 both are in private ASes because:
http://www.cisco.com/warp/public/459/32.html
If the AS_PATH includes both private and public AS numbers, BGP doesn't
remove the private AS numbers. This situation is considered a
configuration error.
the solution is clean, but doesnt it pose restriction and possible
configuration on R1 and R2?
On Wed, 3 Jul 2002 chwarren@cox.net wrote:
> Private AS numbers are in the range of 64512 to 65535.
> > > or, another scenario is that you can put AS1 as a private AS
> > > number and use
> > > the "neighbor as4-router remote-as x remove-private-as" which
> > > will remove
> > > the private-as number from the update that went through r1 to
> > > r2 to r3 and
> > > the as-path attribute the the networkA when it gets to R4
> > > will have r3's AS
> > > number as the originator.
> > >
> >
> > It is the solution I am looking for. The only thing I don't know, how to ma
rk
> > AS1 as private AS.
> > >
> > > Hi !
> > >
> > > Here is an othe problem:
> > >
> > > AS1 AS2 AS3 AS4
> > > R1 ---- R2 --- R3 ---- R4
> > >
> > > R1 is advertising network A towards R4.
> > > The task is to solve that AS4 see network A with AS path does
> > > not contain
> > > AS1.
> > > Configuration has to be done on R3 with the least
> > > configuration statements.
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:18 GMT-3