[c-nsp] ASR1000 RP1 and BGP

CiscoNSP List cisconsp_list at hotmail.com
Fri Sep 6 02:14:53 EDT 2013


Thanks for the clarification - So RP1 will accept up to available ram in RIB (What happens when it exceeds available ram?), and then FIB will accept up to 1M prefixes(best path), which is currently ~460K....so on an RP1 you have an additional ~500k of prefixes(IPv4) that it will still accept?
 

> CC: cisco-nsp at puck.nether.net
> From: lukasz at bromirski.net
> Subject: Re: [c-nsp] ASR1000 RP1 and BGP
> Date: Fri, 6 Sep 2013 08:07:05 +0200
> To: cisconsp_list at hotmail.com
> 
> You're mistaking FIB for RIB. RIB will take whatever fits in available memory, usually way more than 1M of IPv4 routes. FIB is limited to 1M prefixes, but only bestpaths land here, so with number of full feeds you'll usually anyway land at around 460k of prefixes. Try to search in archives for a lot of details.
> 
> -- 
> ./
> 
> > On 6 wrz 2013, at 07:51, CiscoNSP List <cisconsp_list at hotmail.com> wrote:
> > 
> > 
> > Another question on the ASR1000 :)
> > 
> > RP1 supports 1M IPv4 routes i.e. ~2 full tables...If you bring on a third full table, will you see rib failure (memory) for all routes that exceed 1M? (Assume yes?)
> > 
> > How is the rib allocation calculated?  if you added(peered) 4 full tables (sequentially, one after the other), would the bgp sessions after the 1st and second be the ones that are rejected, and then it is based on route churn? (So would routes from peer 3 and 4 be added during churn?)
> > 
> > Cheers.                         
> > _______________________________________________
> > 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/
 		 	   		  


More information about the cisco-nsp mailing list