From: Brian McGahan (brian@xxxxxxxxxxxxxxx)
Date: Thu Aug 29 2002 - 20:35:04 GMT-3
Omer,
You will never route traffic to a locally generated aggregate,
since the outgoing interface is null. Besides, if the local router is
doing the aggregation, it should always have a longer match to the
destination network in the first place. This is the reason the null
route is used, to in fact prevent the local router from routing traffic
for which the longest match is your locally generated aggregate.
HTH
Brian McGahan, CCIE #8593
Director of Design and Implementation
brian@cyscoexpert.com
CyscoExpert Corporation
Internetwork Consulting & Training
http://www.cyscoexpert.com
Voice: 847.674.3392
Fax: 847.674.2625
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Omer Ansari
> Sent: Thursday, August 29, 2002 3:39 AM
> To: ccielab@groupstudy.com
> Subject: how does as-set change the bgp best path selection?
>
> All,
>
> we know that local routes from the bgp router are 3rd in the selection
> list:
> http://www.cisco.com/warp/public/459/25.shtml
>
> this includes bgp routes generated using the aggregrate-address
command.
>
> however if the as-set option is used, does that route still qualify as
a
> locally generated route and if not, does that drop this route further
down
> in the bgp path selection list?
>
> thanks
> Omer
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:42 GMT-3