The MPLS-OPS Archive
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index]
Fwd: Re: Fwd: Cisco
-
From: Roger Clark Williams <rogerw@nordlink.com>
-
Date: Thu, 27 Mar 2003 07:23:50 -0800
-
Resent-Date: Thu, 27 Mar 2003 09:34:08 -0500
-
To: MPLS-ops Mailing List <mpls-ops@mplsrc.com>
-
X-Sender: rogerw@together.net@pop.mindspring.com
Perhaps I was being too general in my comment. What I meant was that,
since routes are cached once the first packet to the route goes through,
or tables of various sorts are built as required (FIB, LIB, LFIB, VRF,
ARP), a certain amount of memory is required to store these tables so
that the router isn't left process-switching everything or having a
process that simply doesn't work. By example, for MPLS to work on a Cisco
router, CEF must be running, and this will build the FIB table which has
to be stored somewhere. Beyond my comment on memory of various sorts,
others have mentioned that the memory isn't the only factor to consider
as well. So it boils down to this: The straight statement about a
platform supporting X routes is not the only factor to consider, and even
a platform that could support X routes many not if not properly
built up. It may not do so right out of the box. It is simply one other
thing to consider beyond the printed specifications. Perhaps this is
obvious, but I thought I should mention it.
Roger Williams
Resent-Date: Thu, 27 Mar 2003
06:20:07 -0500
X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender
to mpls-ops-request@mplsrc.com using -f
Date: Thu, 27 Mar 2003 16:58:35 +0530 (IST)
Subject: Re: Fwd: [MPLS-OPS]: Cisco
From: "Alok Dube" <alok.dube@apara.com>
To: <rogerw@nordlink.com>
Importance: Normal
Cc: <mpls-ops@mplsrc.com>
Reply-To: alok.dube@apara.com
X-Mailer: SquirrelMail (version 1.2.6)
Resent-From: mpls-ops@mplsrc.com
X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/5496
X-Loop: mpls-ops@mplsrc.com
Resent-Sender: mpls-ops-request@mplsrc.com
wud appreciate if someone could clarify...
How does RAM size effect forwarding table capacity?
does FT use RAM?
> Be a bit careful of straight statements you may read. Much of
any
> platform capability is based on the level of RAM, flash or
whatever.
> For example, perhaps a router can hold 100,000 routes, but it
may take
> 50mb memory to do so...
>
> Roger Williams
>
>
>>Resent-Date: Wed, 26 Mar 2003 16:37:21 -0500
>>X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set
sender
>>to mpls-ops-request@mplsrc.com using -f
>>X-Originating-IP: [155.245.41.182]
>>X-Originating-Email: [frasker@hotmail.com]
>>From: "Fat Bouy" <frasker@hotmail.com>
>>To: mpls-ops@mplsrc.com
>>Date: Wed, 26 Mar 2003 21:20:13 +0000
>>X-OriginalArrivalTime: 26 Mar 2003 21:20:13.0364 (UTC)
>>FILETIME=[7D336F40:01C2F3DD]
>>Subject: [MPLS-OPS]: Cisco
>>Resent-From: mpls-ops@mplsrc.com
>>X-Mailing-List: <mpls-ops@mplsrc.com>
archive/latest/5489
>>X-Loop: mpls-ops@mplsrc.com
>>Resent-Sender: mpls-ops-request@mplsrc.com
>>
>>Hi,
>>
>>cisco documented that its routers are capable of having up to 1
million
>>IP entries in their forwarding tables. Is this feature
available to
>>all its products?
>>
>>
>>
>>
>>_________________________________________________________________
Are
>>you in love? Find a date on MSN Personals
http://match.msn.com.my/
>>
>>-------
>>The MPLS-OPS Mailing List
>>Subscribe/Unsubscribe:
http://www.mplsrc.com/mplsops.shtml
>>Archive:
http://www.mplsrc.com/mpls-ops_archive.shtml
>
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:
http://www.mplsrc.com/mplsops.shtml
> Archive:
http://www.mplsrc.com/mpls-ops_archive.shtml
-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:
http://www.mplsrc.com/mplsops.shtml
Archive:
http://www.mplsrc.com/mpls-ops_archive.shtml
-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
| |
|