[50630] in North American Network Operators' Group
RE: Deaggregating for emergency purposes
daemon@ATHENA.MIT.EDU (Phil Rosenthal)
Tue Aug 6 13:53:17 2002
Reply-To: <pr@isprime.com>
From: "Phil Rosenthal" <pr@isprime.com>
To: <nanog@merit.edu>
Date: Tue, 6 Aug 2002 13:52:44 -0400
In-Reply-To: <20020806173829.GA8521@puck.nether.net>
Errors-To: owner-nanog-outgoing@merit.edu
Speaking of that, anyone know of the config mem size on a Cisco 6509, a
Foundry Bigiron, a Juniper M40 for example?
--Phil
-----Original Message-----
From: Jared Mauch [mailto:jared@puck.nether.net]
Sent: Tuesday, August 06, 2002 1:38 PM
To: Phil Rosenthal
Cc: 'Omachonu Ogali'; nanog@merit.edu
Subject: Re: Deaggregating for emergency purposes
You should check that your upstream router vendor can handle the
increased config size.
You are lucky to have as much as 512k config mem on a router let
alone 2M+ as is necessary for some people that do IRR based filtering.
This is something everyone should keep in mind doing vendor
selection these days...
- Jared
On Tue, Aug 06, 2002 at 01:29:58PM -0400, Phil Rosenthal wrote:
>
> Most ISPs that build off of the IRR's do it nightly. I am talking
> about 10 /24's out of /19, and I'm not announcing any of the /24's --
> and wont unless there is an emergency, and only then would it be
> temporary.
>
--
Jared Mauch | pgp key available via finger from jared@puck.nether.net
clue++; | http://puck.nether.net/~jared/ My statements are only
mine.
