[c-nsp] Dreaded FIB Exception on Sup2

[Rick Kunkel]

Well, I've hit the dreaded error message on my Sup2:

%MLSCEF-SP-7-FIB_EXCEPTION: FIB TCAM exception, Some entries will be 
software switched

I've done a lot of reading on this (cisco.com, this list, etc.), with the 
conclusion that this supervisor engine is likely just at the end of its 
useful lifetime, but I figured I'd double check I wasn't missing anything.

This happened when I started getting a full routing table from a provider 
today.  We're connected to one peering point and another aggregation-style 
provider, and are in the process of adding a Cogent connection (hold 
any tempting comments on that one, please).

Is there a "show" command I can use to find the usage in the TCAM?  I 
can't seem to find a good one.  SOme useful ones I've found for the Sup3 
don't work on the Sup2 apparently.

Some ones I've used to deduce what's going on though:

ROUTER#show ip route sum
IP routing table name is Default-IP-Routing-Table(0)
Route Source    Networks    Subnets     Overhead    Memory (bytes)
connected       1           6           448         1120
static          8           1           576         1440
eigrp           11          57          4352        10880
bgp             130170      133117      16850368    42131020
   External: 263287 Internal: 0 Local: 0
internal        3190                                3764200
Total           133380      133181      16855744    45908660

ROUTER#show ip cef sum
IP Distributed CEF with switching (Table Version 641214), flags=0x0
   263458 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 2992
   263458 leaves, 14567 nodes, 50979968 bytes, 640846 inserts, 377388 
invalidations
   0 load sharing elements, 0 bytes, 0 references
   universal per-destination load sharing algorithm, id EB4814E6
   3(0) CEF resets, 3 revisions of existing leaves
   Resolution Timer: Exponential (currently 1s, peak 2s)
   3 in-place/0 aborted modifications
   refcounts:  4241756 leaf, 3729408 node

   Table epoch: 0 (263458 entries at this epoch)

Adjacency Table has 71 adjacencies

ROUTER#show mls cef sum

Total CEF switched packets:  0000271471473221
Total CEF switched bytes:    0182929990663338
Total routes:                261865
     IP unicast routes:       261865
     IPX routes:              0
     IP multicast routes:     0

Any thoughts?  Am I simply SOL without a new Sup?  I've heard tell of 
optimizing TCAM memory, but it would appear that maybe that wouldn't even 
cut the mustard with the amount of routes I'm dealing with maybe...(?)

If I get full routes from two providers and a thousand or so routes form 
the peering point, AND have a 0.0.0.0/0 route out a preferred provider, 
could that cover my bases?

One more thing.  My show ver:

ROUTER#show ver
Cisco Internetwork Operating System Software
IOS (tm) c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(26)E8, RELEASE 
SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by cisco Systems, Inc.
Compiled Fri 29-Dec-06 06:42 by hqluong
Image text-base: 0x40008F90, data-base: 0x41856000

ROM: System Bootstrap, Version 12.2(17r)S1, RELEASE SOFTWARE (fc1)
BOOTLDR: c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(26)E8, RELEASE 
SOFTWARE (fc1)

ROUTER uptime is 37 weeks, 4 days, 6 hours, 54 minutes
Time since ROUTER switched to active is 37 weeks, 4 days, 6 hours, 54 
minutes
System returned to ROM by power-on (SP by power-on)
System restarted at 03:01:49 PST Sat Dec 15 2007
System image file is "sup-bootflash:c6sup22-psv-mz.121-26.E8.bin"

cisco WS-C6509 (R7000) processor (revision 3.0) with 458752K/65536K bytes 
of memory.
Processor board ID SAL0730H93F
R7000 CPU at 300Mhz, Implementation 39, Rev 3.3, 256KB L2, 1024KB L3 Cache
Last reset from power-on
X.25 software, Version 3.0.0.
Bridging software.
2 Virtual Ethernet/IEEE 802.3  interface(s)
48 FastEthernet/IEEE 802.3 interface(s)
10 Gigabit Ethernet/IEEE 802.3 interface(s)
381K bytes of non-volatile configuration memory.

32768K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102

Thanks much!

Rick Kunkel