[c-nsp] aggregate lfib entry - what is the actual prefix ?

[Adam Vitkovsky]

Lukas is right,
Think of it this way:
Consider data-plane perspective: 
When a packet arrives on the PE destined to a 192.168.1.1 IP address -it's not going to be switched to where the 192.168.0.0/16 points to as it would get dropped. 
Instead an additional FIB lookup in the VRF is needed to find out which interface to use in order to forward the packet.
  
adam
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
> Lukas Tribus
> Sent: 13 February 2015 15:03
> To: Aaron; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] aggregate lfib entry - what is the actual prefix ?
> 
> > Are you sure it doesn't map to a particular prefix ? I just found this.
> > This seems to be what it maps to...the aggregate route that I config'd
> > within bgp vrf test.
> 
> Aggregate routes will point to *the* aggregate vrf label, yes. But you can
> have many aggregates and they all will point to the very same label.
> 
> The aggregate label may only have been created because of your aggregate
> route, but that doesn't mean its per aggregate prefix. Its per vrf, really.
> 
> 
> Lukas
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
---------------------------------------------------------------------------------------
 This email has been scanned for email related threats and delivered safely by Mimecast.
 For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------