<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'><style>p { margin: 0; }</style><div style="font-family: Times New Roman; font-size: 12pt; color: rgb(0, 0, 0);">Excellent information! Thanks alot.<br><br>Do you recommend i use the cam-partition command you gave me?<br><br>cam-partition l2 7 l3 68 l4 25<br><br><br><br>----- Original Message -----<br>From: "Jeroen Wunnink" <jeroen@easyhosting.nl><br>To: "Brendan Mannella" <bmannella@teraswitch.com>, foundry-nsp@puck.nether.net<br>Sent: Monday, July 14, 2008 11:41:49 AM GMT -05:00 US/Canada Eastern<br>Subject: Re: [f-nsp] BigIron 4k with JetCore<br><br>Hi Brendan,<br><br>The first 4 ports on slot 3 look fairly loaded:<br><br>Layer 3 sw index range:<br> L3 L3 1 - 2047 (0x00001 - 0x007ff), free 1964 (0x007ac)<br> L3 L2 2048 - 4095 (0x00800 - 0x00fff), free 1118 (0x0045e)<br> L3 4096 - 32767 (0x01000 - 0x07fff), free 13172 (0x03374)<br><br>Is this a snapshot of peak-time or at low usage ?, if there's a <br>sudden surge with for example a synflood which makes a ton of <br>connections, those 13000 remaining free L3 entries can run out pretty <br>fast resulting in the router throwing the L3 routing part over the <br>CPU (that's when the domino effect starts happening on connections <br>getting lost once the CPU maxes out)<br><br>Some ideas:<br>You could set the cam-partition on slot 3 to allocate more space to <br>layer 3 (L3) and less to layer 2 (L2) if you don't use it much for <br>switching. The minimum for L4 is a mandatory 25% though.<br><br>enable the quick-aging option with the cpu-protection feature, which <br>cuts the cam expire timer in half if the CPU or CAM load is over a <br>certain threshold. (you can set some conditions and actions here)<br><br>Devide the busiest uplinks between more port groups<br><br>I've seen our L3 CAM space run out very fast once the maximum <br>ip-cache hit it's limit, check if the system-max is set to 400000 for <br>the ip-cache<br><br>note: You'll need to reload the device once you re-partitioned the <br>cam or increased the system-max settings<br><br>We've had our fair share of CPU spikes and CAM exhaust issues in the <br>past on our Irconcore and Jetcore BI4k equipment , these were the <br>main issues and solutions that solved it for us with some help from <br>Foundry TAC and NLNOG'ers (Dutch network admins)<br><br><br>At 16:36 14-7-2008, Brendan Mannella wrote:<br>>Here is a copy and paste of the "sh cam-part det". Does it look exhausted?<br>>[snip..]<br><br><br><br>Met vriendelijke groet,<br><br>Jeroen Wunnink,<br>EasyHosting B.V. Systeembeheerder<br>systeembeheer@easyhosting.nl<br><br>telefoon:+31 (035) 6285455 Postbus 48<br>fax: +31 (035) 6838242 3755 ZG Eemnes<br><br>http://www.easyhosting.nl<br>http://www.easycolocate.nl<br><br><br></div></div></body></html>