[c-nsp] BGP memory on a 6500
Francois Corthésy
fc at deckpoint.com
Thu Sep 28 02:40:32 EDT 2006
Well, I'm no 6500 Guru, but my understanding of the TCAM is that it is
used for *every* route, which in tunrs means that your internal routing
table/ARP count/BGP table all have to share the ~239'000 limit that the
TCAM has.
Francois
Rick Kunkel wrote:
> Sakes alive, there's a snarl at every turn. I appreciate every piece of
> info though.
>
> Is the TCAM used for BGP? Things I've read seem to indicate they're used
> for ACLs. Obviously, I'm bound to use some ACLs for BGP, but are there
> other elements that the TCAM would be used for that woudl be limiting to
> BGP?
>
> On another note, I've heard that the 7600 and 6500 are now almost
> identical with the Sup720. Is this true?
>
> Thanks much!
>
> Rick
>
> On Wed, 27 Sep 2006, Francois Corthésy wrote:
>
>
>> Hi Rick,
>>
>> Might I point to this earlier discution :
>> https://puck.nether.net/pipermail/cisco-nsp/2006-August/032822.html
>>
>> Essentially, If you plan on using anything else than a Sup720-3BXL for
>> Full BGP routing on a 6500 for more than 1 or 2 years you are stuck.
>>
>> Francois
>>
>> Rick Kunkel wrote:
>>
>>> Hello all,
>>>
>>> I'm considering a 6500, and am trying to assemble a list of required
>>> components. I'm looking at the Sup2 with PSC2 and MSCF2. You can get the
>>> MSFC with 512MB of RAM. Is THIS the RAM that the BGP routing table would
>>> be used, or is that stored elsewhere? If elsewhere, then where?
>>>
>>> THanks,
>>>
>>> Rick Kunkel
>>>
>>>
>>> _______________________________________________
>>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>
>>>
>>>
>>>
>>
>
>
>
More information about the cisco-nsp
mailing list