A simple confederaton seems to be the way to do this..the as-set command will not change the origin AS. In fact its purpose it to include the as path information in the summary announcement.
See below... On Sun, 4 Nov 2001, Baety Wayne A1C 18 CS/SCBX wrote: > > However, to satisfy the question you can use BGP aggregation on R3 which was > specifically designed for this purpose... > > router bgp 64512 > aggregate-address 200.200.200.1 255.255.255.0 summary-only as-set > http://www.cisco.com/warp/public/459/aggregation.html Using the as-set argument, the path information in the BGP table for the aggregate route changes to include a set from 300 {200,100}. This indicates that the aggregate actually summarizes routes that have passed through AS-200 and AS-100. The as-set information becomes important in avoiding routing loops because it records where the route has been. > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 05, 2001 2:53 AM > To: [EMAIL PROTECTED] > Subject: Re: BGP question [7:25130] > > Hi > > what I am trying to achieve is as follow > > AS 100 is connected to AS 200. > AS 200 is connected to AS 300 > > AS 100 has route from AS 300. So the AS-PATH List is: 200, 300, i > The task is: AS 100 should see all the route from AS 300 as if they came > from AS 100 directly the path will look like 200, i If AS 200 and AS 300 were in a confederation using 200 as the identifier this would be the result.. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=25246&t=25130 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
