From: Abe Mounce (Amounce@xxxxxxxxxxxxxxxxx)
Date: Thu Nov 01 2001 - 18:47:02 GMT-3
Hmmm.... This scenario seems very familar to me. Wait, i vaguely recall
some VERY similar issues appearing on [DELETED DUE TO NDA REQUIREMENTS]
;) BTW, distribute-list or route map will do, allowing only internal
nets out, summarized or no...
-----Original Message-----
From: Juan Villamil [mailto:juan.villamil@earthling.net]
Sent: Thursday, November 01, 2001 3:31 AM
To: 'Bryan Ginman'
Cc: 'CCIE Group Study'
Subject: RE: Non-transit AS
Why not tag all routes into your AS with community local-AS and send
that community to your local AS peers...
Regards,
Juan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Bryan Ginman
Sent: 31 October 2001 23:52
To: Jason Sinclair; Jonathan Chin Kah Fi; Chua, Parry
Cc: CCIE Group Study
Subject: RE: Non-transit AS
It definitely is a type of problem that is resolved to the particular
situation. Usually you are given summarizable blocks and if you are
doing
private hopefully you've addressed correctly to provide summarization
;oP.
If not you can tag and pull, it's a little more work but both work.
Regards,
Bryan
-----Original Message-----
From: Jason Sinclair [mailto:sinclairj@powertel.com.au]
Sent: Wednesday, October 31, 2001 7:20 PM
To: 'Bryan Ginman'; Jonathan Chin Kah Fi; Chua, Parry
Cc: CCIE Group Study
Subject: RE: Non-transit AS
Bryan,
This will work, however what if you have a large number of routes? This
means that u would have a very large
prefix-list/distribute-list/filter-list. If you tag the incoming routes
with
community say AS:100, you can easily match the community and deny it and
allow all else (which would match your internal routes). That said, your
solution will definitely work, I am just thinking of time constraints.
Hope this helps,
Regards,
Jason Sinclair
Network Support Manager
POWERTEL Limited
Level 11, 55 Clarence Street, SYDNEY
Phone: 61-2-8264-3820
Fax: 61-2-9279-2604
Mobile: 0416 105 858
jasons@powertel.net.au
-----Original Message-----
From: Bryan Ginman [mailto:ginmanb@westnet.com]
Sent: Thursday, 1 November 2001 02:16
To: Jonathan Chin Kah Fi; Chua, Parry
Cc: CCIE Group Study
Subject: RE: Non-transit AS
This is very simple just set up a route-map on both
routers
to the external
AS's advertising only your internal networks that you
want
known, this is
the same thing as ip as-path access-list perm ^$
-----Original Message-----
From: nobody@groupstudy.com
[mailto:nobody@groupstudy.com]On
Behalf Of
Jonathan Chin Kah Fi
Sent: Wednesday, October 31, 2001 3:56 AM
To: Chua, Parry
Cc: CCIE Group Study
Subject: Re: Non-transit AS
I have thought of a way to do it...not sure if it works.
I will have two EBGP peers peering with the two ISP AS.
For
each EBGP in
my own AS, I will have something like this :
router bgp my_as
neighbor ISP_AS route-map set_no_export in
neighbor my_as_other_EBGP send-community
route-map set_no_export permit 10
set no-export
This will also be configured on the other EBGP peer in
my
own AS.
This way, all routes from ISP will be tagged with
"no-export". The tagged
routes
will be send to the EBGP peer in my own AS and he will
not
advertise it out
to
the other ISP.
"Chua, Parry" wrote:
> I think you could set community from Ebgp peers update
and
do not
advertise
> or export out
> of other ibgp peers.
>
> > Parry Chua
> >
>
> -----Original Message-----
> From: Jonathan Chin Kah Fi [mailto:kachin@cisco.com]
> Sent: Wednesday, October 31, 2001 4:18 PM
> To: CCIE Group Study
> Subject: Non-transit AS
>
> Hi,
>
> I have a question here.
>
> Supposing you have your own AS peered with two ISP AS.
How
do you
> configure
> your own AS such that it will become a Non-Transit AS?
To
make things
> more
> complicated, ip as-path access-list is not allowed to
be
used.
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:00 GMT-3