http://www.brocade.com/downloads/documents/html_product_manuals/NI_05400a_CFG/CAM_part.82.2.html
2012/10/3 Darren O'Connor <[email protected]> > Greg. > > Out of interest, what will my XMR hold for both? I've been told 1 million > IPv4. so if I wanted to split this into IPv4 and IPv6 does that give me > 750K IPv4 and 62.5K IPv6? > > Thanks > > > Date: Wed, 3 Oct 2012 12:50:23 -0400 > > From: [email protected] > > To: [email protected] > > Subject: Re: [f-nsp] CER FIB capacity > > > > Hi Rob, the CER routers use SRAM for the IPv4/v6 FIB instead of CAM, so > > for the CES/CER/CER-RT platforms the scalability is dynamic for all IP > > routes in the FIB (vs the MLX CAM architecture where we have to choose > > fixed partition sizes which can support a maximum number). > > > > Scalability depends on how the memory is used by IPv4 and IPv6 routes. > > There is no easy formula to calculate the utilization, so we have tested > > certain combinations which are officially supported maximums. While a > > different number of routes might work, it will not be a supported or > > tested combination. > > > > For CER: > > 256K IPv4 routes + 128K IPv6 > > 448K IPv4 + 64K IPv6 > > 512K IPv4 + 0 IPv6 > > > > For CER-RT: > > 1.5M IPv4 + 512K IPv6 > > > > "Internet route mix" is used to indicate that we are using a mix of > prefix > > lengths. No compression is being used. > > > > Greg > > (works for Brocade) > > > > -- > > Greg Hankins <[email protected]> > > > > -----Original Message----- > > Date: Wed, 3 Oct 2012 16:54:45 +0200 > > From: Robert Hass <[email protected]> > > To: [email protected] > > Subject: [f-nsp] CER FIB capacity > > > > Hi > > I know that CER (non-RT version) have FIB for 512K IPv4 / 128K IPv6. > > My question is CAM is split between IPv4 and IPv6 - I mean if I have > > 128K IPv6 routes in FIB then I cannot have 512K IPv4 routes at same > > time. > > > > Rob > > _______________________________________________ > > foundry-nsp mailing list > > [email protected] > > http://puck.nether.net/mailman/listinfo/foundry-nsp > > _______________________________________________ > > foundry-nsp mailing list > > [email protected] > > http://puck.nether.net/mailman/listinfo/foundry-nsp > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp >
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
