[f-nsp] Current Total Free Memory [...] is below 5 percent of Installed Memory.

[Franz Georg Köhler]

Am 17.12.11 13:47, schrieb Valeri Streltsov:
> Hi
> 
> CAM profile are affecting to IPv4, IPv6, ACL(v4&v6), vrf, mpls sizes of 
> allocated partitions.
> 
> In you case there is no solution to increase amount of partitions 
> because "ipv6-ipv6-2" profile.
> 
> Try to decrease ACL usage or look for migrating to MLXe modules.
> 
> Information about profile differs are located in configuration guide in 
> chapter "CAM partition profiles" (from 2622 page in 5.2 manual)

Hello,

Table 524 in the manual was helpful. It contains the size values for
every profile.

I have a CAM related question:

Currently I am running on this MLX:

cam-partition profile multi-service-2
cam-partition logging 90% 30
enable-acl-cam-sharing
cam-mode ipv6 dynamic
cam-mode ipvpn dynamic
cam-mode ip dynamic

I have high CPU utilization on the first line card.
My impression is that this is related to cam memory exhaustion, which
causes the packets to be switched to the line card CPU:

LP-1#show cpu

... Usage average in the last 1 second  - 39 ...
last 1 second  utilization = 39
last 5 seconds utilization = 39
last 1 minute  utilization = 41
last 5 minutes utilization = 41
LP-1#show task
  Task Name    Pri  State  PC        Stack       Size  CPU Usage(%)
task vid
  -----------  ---  -----  --------  --------  ------  ------------
--------
  con           27  wait   00059054  04090dc8   32768             0  0
  mon           31  wait   00059054  0416bf10    8192             0  0
  flash         20  wait   00059054  04177f48    8192             0  0
  dbg           30  wait   00059054  04171ec0   16384             0  0
  main           3  ready  20917a18  235adef8  262144            95  101
  i2c_task       3  wait   00059054  2dca9ee8    4096             0  101
  stats_colle    3  ready  00059054  2dcabf70    4096             0  101


#show cam-p u

CAM partitioning profile: multi-service-2

Slot 1 XPP20SP 0:
            [IP] 458752(size),  306881(free), 33.10%(used)
        :SNet 0:   2048(size),       0(free), 100.00%(used)
        :SNet 1: 418219(size),  269046(free), 35.66%(used)
        :SNet 2:  32668(size),   32103(free), 01.72%(used)
        :SNet 3:   4497(size),    4423(free), 01.64%(used)
        :SNet 4:    680(size),     670(free), 01.47%(used)
        :SNet 5:    128(size),     127(free), 00.78%(used)
[...]

My Questions are:
- What is "SNet 0"? Do those different SNets hold different classes of
networks?
If I know what information is stored within "SNet 0" I might be able to
free up some space....

- Since in this case "Snet 0" seems to be fully used while there is
still avaiable memory in the other SNets: Is it possible to use the
available space for "SNet 0"?

As far as I can see (I have only limited possibility to test all CAM
profiles) the different CAM profiles all have a SNet 0 size of 2048
(this is another MLX router with ipv4-ipv6-2 profile):

Slot 1 XPP20SP 0:
            [IP] 491520(size),  491444(free), 00.01%(used)
        :SNet 0:   2048(size),    1978(free), 03.41%(used)
        :SNet 1: 448283(size),  448278(free), 00.00%(used)
        :SNet 2:  35001(size),   35000(free), 00.00%(used)
        :SNet 3:   4819(size),    4819(free), 00.00%(used)
        :SNet 4:    729(size),     729(free), 00.00%(used)
        :SNet 5:    128(size),     128(free), 00.00%(used)



Best regards,

Franz Georg Köhler