Hi Tony,
The FIB TCAM is already dynamically allocated as of 4.2 (ie, no
static/fixed allocation, blocks of various width entries grow/shrink
as necessary). At the control plane, you can control the max prefixes
for each, which naturally limits the h/w consumption to those numbers as well.
Hope that helps,
Tim
At 11:28 AM 3/9/2010, Tony Varriale clamored:
<snip>
And I believe you are going to allow configurable allocation between ipv4
and ipv6 space.
tv
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
<https://puck.nether.net/mailman/listinfo/cisco-nsp>https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at
<http://puck.nether.net/pipermail/cisco-nsp/>http://puck.nether.net/pipermail/cisco-nsp/
Tim Stevenson, tstev...@cisco.com
Routing & Switching CCIE #5561
Technical Marketing Engineer, Cisco Nexus 7000
Cisco - http://www.cisco.com
IP Phone: 408-526-6759
********************************************************
The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
