Oh the 6500. I run a small service provider network and run the 6500 as a PE router. Worst decision of my life. (That was an embellished statement, but you get my point.)
I run full BGP routes in a VRF and have experienced a lot of problem surrounding this.
You're example is not very surprising. As Daniel said in his post there is an LFIB entry for each VRF prefix as well as a VPNv4 entry. This can be changed by adding the command
mpls label mode vrf Internet protocol all-afs per-vrf as was stated; however, this does not get you out of the woods. If you change to per VRF prefixes it does remove the LFIB entry (yay!) but adds an entry for every single prefix into the Adjacency table (wait, what?!). Since the 6500 forwarding hardware is shared between L2 and L3 forwarding this doesn't change your hardware memory usage at all. If anything it makes the problem harder to find.
If you look at your usage once you've changed to per VRF usage (using
show platform hardware cef resource-level) it looks as though you've fixed the issue. However if you use the command
show platform hardware cef adjacencies resource-level it reveals the problem has just moved to a different location.
Below are the outputs from one of my 6500's resource-level and adjacency usage. Outlining what I'm talking about.
Global watermarks: apply to Fib shared area only.
Protocol watermarks: apply to protocols with non-default max-routes
Fib-size: 1024k (1048576), shared-size: 1016k (1040384), shared-usage: 458k(469769)
Red_WM: 95%, Greem_WM: 80%, Current usage: 45%
Protocol Red_WM(%) Green_WM(%) Current(%)
-------- --------- ---------- ----------
IPV4 -- -- 42% (of shared)
IPV4-MCAST -- -- 0 % (of shared)
IPV6 -- -- 2 % (of shared)
IPV6-MCAST -- -- 0 % (of shared)
MPLS -- -- 0 % (of shared)
EoMPLS -- -- 0 % (of shared)
VPLS-IPV4-MCAST -- -- 0 % (of shared)
VPLS-IPV6-MCAST -- -- 0 % (of shared)
Watermarks apply to regions available for allocation and not pre-reserved
Stats region size for alloc: 444160
Non-stats region size for alloc: 376832
Adjacency Mgr watermarks:
Type Red_WM(%) Green_WM(%) Current usage(%)
---- --------- ---------- ----------------
Stats_WM 95% 80% 97%
Non-Stats_WM 95% 80% 14%
Ivan's post on this was base on my findings here. I am currently working with Cisco to attempt to fix this issue, but unfortunately right now there is no way to fix this.
Your milage may vary since you've got no MPLS adjacencies. Would be interested to see your adjacency usage now that you've made the change.