Mailing List Archive

On Wed, Feb 18, 2004 at 04:48:36AM -0800, Martin Robinson wrote:
> Trying to spec up a juniper m5/m10/m40, main requiremnt is that we
> need to hold a full bgp routing table, is there a mimimum spec of
> routing engine we should be looking at.

No, even RE-2.0 comes with at least 256M RAM (upgradable to 768M).
Current REs being delivered for M5/M10/M40e are probabably RE-3.0
with at least 512M, upgradable to 2G or so. Anyway, 256M is enough
for the usage you described briefly.

This is not Cisco. :-)


Regards,
Daniel

On Wed, 18 Feb 2004, Daniel Roesen wrote:

> No, even RE-2.0 comes with at least 256M RAM (upgradable to 768M).
> Current REs being delivered for M5/M10/M40e are probabably RE-3.0 with
> at least 512M, upgradable to 2G or so. Anyway, 256M is enough for the
> usage you described briefly.

Depends on how many peers/transits you have. You may find with reasonable
numbers of both (2 x transit, 100 peers) that 256Mb RAM won't be
enough.

> This is not Cisco. :-)

Agreed, but Junipers have their limitations too.

Rich

> Trying to spec up a juniper m5/m10/m40, main requiremnt is that we need to
> hold a full bgp routing table, is there a mimimum spec of routing engine
> we should be looking at.

if not 500 views of the full table, any will do it

> > Trying to spec up a juniper m5/m10/m40, main requiremnt is that we need to
> > hold a full bgp routing table, is there a mimimum spec of routing engine
> > we should be looking at.
>
> if not 500 views of the full table, any will do it

Not true. We have just three full BGP views and with 256MB RAM on a M5 the box
started swapping heavily, to the point that a "commit" took 2 minutes and a
BGP route change took 5 minutes to be seen in the "show route" output. But at
least the box survived because it swapped, a Cisco can not swap :-)

In any case where a machine is supposed to take on full table and an X
amount of peers 512MB is always the safest choice, especially if you're
planning on expanding peers/full views in the future.

Cheers,

Erik

On Wed, 2004-02-18 at 20:10, Blaz Zupan wrote:
> > > Trying to spec up a juniper m5/m10/m40, main requiremnt is that we need to
> > > hold a full bgp routing table, is there a mimimum spec of routing engine
> > > we should be looking at.
> >
> > if not 500 views of the full table, any will do it
>
> Not true. We have just three full BGP views and with 256MB RAM on a M5 the box
> started swapping heavily, to the point that a "commit" took 2 minutes and a
> BGP route change took 5 minutes to be seen in the "show route" output. But at
> least the box survived because it swapped, a Cisco can not swap :-)
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
--
---
Erik Haagsman
Network Architect
We Dare BV
tel: +31.10.7507008
fax: +31.10.7507005
http://www.we-dare.nl

I think it will be depending on your configuration
along with other features.
256MB will be enough for one full BGP routing table.
But I want to go with max memory if you wants to use this as important.
Memory usage will be different based on lots of reason or events.

Frequent flapping of connections
IBGP/EBGP peering numbers
other features or functions from router

From Juniper M20 with one external BGP peering - full BGP routing - and a
coupel of IBGP session, I saw it uses 180MB, but occasionally it uses up to 213MB.

If you use more than physical memory, it should be swapped, and that will give
slow response time from routing-engine.

I think you can use PC memory for memory expansion,
but I think Juniper did a good job to make reliable router,
so I bought memory from them at expensive price for them
to stay in the market as long as we use Juniper router. ^.^




Martin Robinson wrote:

> Hi,
>
> Trying to spec up a juniper m5/m10/m40, main requiremnt is that we need to hold a full bgp routing table, is there a mimimum spec of routing engine we should be looking at.
>
> Martin.
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
>