BGP paths is what takes up most of the ram, you could potentially add 3
more full sessions and if that doesn't add much more paths then the ram
usage would not go up very much.
I have one with 6 full sessions, 58mb free.
If Cisco would implement some memory compression on these platforms it
would go a long way. I have a feature request for this but I doubt it
will go anywhere.. Maybe if other people submitted feature request for
the same thing (BGP path/attribute memory compression) they would do
it. Also TCAM compression.
Another way would be to use the SP to store data since it always has a
lot of RAM free.
On 3/11/2015 8:45 AM, Erik Klaassen wrote:
Hi all,
We use a 7600 with a sup720xl and we receive 3 full bgp tables, some partial
transit and some peering.
According to sh bgp sum bgp is using:
ipv4 ~250MB
ipv6 ~30MB
But the 1GB dram is almost full.
sh memory summary
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 46ABB9D0 894682672 785658748 109023924 54382492 48475720
Sh proc mem shows the bgp proces is using a lot more memory the ~300MB
PID TTY Allocated Freed Holding Getbufs Retbufs Process
496 0 799340392 180557004 517282488 0 0 BGP Router
how does this come and is this normal? I was expecting i could use some more
full tables on this router.
Thanks,
Erik
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
--
GloboTech Communications
Phone: 1-514-907-0050 x 215
Toll Free: 1-(888)-GTCOMM1
Fax: 1-(514)-907-0750
[email protected]
http://www.gtcomm.net
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
