[c-nsp] ASR-1001 bgp memory usage

[Mack McBride]

You do get multiple processes.  The IOS CLI portion is fairly monolithic but even on the old 6500s you
can restart the BGP process (you have to remove all configured peers to do it though :( )
They are working on streamlining XE to provide better isolation of the CLI and underlying driver code.
And don't disparage the redundant processes, it isn't a bad design.
Of course full modularity is something of a myth.
If the underlying OS has issues then all of the processes are going to have issues.

Having said all of that, yes they can do a better job of modularizing things.

Mack

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Gert Doering
Sent: Wednesday, September 21, 2011 2:24 PM
To: Christian Kratzer
Cc: Gert Doering; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] ASR-1001 bgp memory usage

Hi,

On Wed, Sep 21, 2011 at 10:01:58PM +0200, Christian Kratzer wrote:
> >Could someone explain to me again what's so great about IOS XE, and 
> >why IOS XR or NX-OS or anything else halfway decent is not used on 
> >these platforms, except "because another business unit made it"?
> 
> it runs Lunix and it's a PC:

Yes...  with a single non-modular IOS process on top of it, and serious memory management issues.

Try again?

(Oh yes, you can have two single non-modular IOS processes for redundancy, I forgot)

gert
--
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de