The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-Jan> msg00081



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Re: Aggregate routes Import & export within VRF's on the same PE's

  • From: "Shailendra Gupta" <shailendra.gupta@estelcom.com>
  • Date: Wed, 28 Jan 2004 16:50:32 +0530
  • Resent-Date: Wed, 28 Jan 2004 06:59:21 -0500
  • To: "Spice Sylvia" <falsesylvia@yahoo.co.uk>, "Piotr Marecki" <piotr.marecki@tdcinternet.pl>, <mpls-ops@mplsrc.com>
  • X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
  • X-AntiAbuse: Primary Hostname - cpanel.people-connect.com
  • X-AntiAbuse: Original Domain - mplsrc.com
  • X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
  • X-AntiAbuse: Sender Address Domain - estelcom.com

Dear Spice
 
I guess some typo mistake which creates some confusion, as segment 192.168.1.0/16 seems to be invalid and /16 routes can not be aggregated into /17.
 
Shailendra
 
 
 
----- Original Message -----
Sent: Wednesday, January 28, 2004 12:44 PM
Subject: Re: [MPLS-OPS]: Aggregate routes Import & export within VRF's on the same PE's

I guess the example given by M. Elk was a bad one (the specifics are a subset of the aggregate but not a complete set).
 
I guess if I could rephrase the question, based on what I understood from the reply he sent:
 
Assume we have 192.168.0.0/16 and 192.168.1.0/16 in VRF Green
 
This can be aggregated to 192.168.0.0/17.
 
Now when we propogate the routes using export and import RT, how are the routes propogated to VRF Red on the same PE?
 
Will the interface routes also be advertised in this case?
 
My guess is yes as the most specific would be advertised.
 
In this particular case above, my guess is the aggregate would never be advertised.
 
Is this correct?
 
(Incase one was to not bother about most specific but only about protocol metrics, then maybe even the aggregate could be advertised, but that could be avoided by pulling up the cost associated with the next-hop null0/or using a policy map which sends only aggregate to remote PE routers.)
M.Elk, was this what you wanted to clarify?

Piotr Marecki <piotr.marecki@tdcinternet.pl> wrote:

>
> 2- Specific to cisco implementation .
> guess the above as configured is not workable ,ie: 10.9/16 will not
show
> in VRF red
> neither 10.10/16 in VRF green , is it correct ?

Actually all aggregates will appear in other vrf with next-hop null0.Of
course
more specific , ie static routes will also appear in other vrf with next-hop
of
proper vrf intf. Moreover , on others PE ( MP_BGP ) you 'll also see other
agregate ( with proper
route-target import) . PE LFIB will contain Aggregate as an action connected
with every aggregated prefix.

regards

Piotr Marecki



-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplssrc.com/mpls-ops_archive.shtml


BT Yahoo! Broadband - Free modem offer, sign up online today and save £80