[f-nsp] auto-shutdown new BGP-neighbors in 3.7 on MLX / reasons for upgrading: cam-exhaustion

[Ryan Harden]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We have several MLXs (in static cam mode) across the state for transit
between the Campuses as well as ISP and Research Network connectivity.
There are two full tables from different ISPs, a session with
Internet2-CPS, as well as a few Research and Bilateral sessions. One of
the ISP sessions is what they call "Summary" view, where they aggregate
if they can, so I expect my table size to be slightly smaller than what
others are seeing.

As of a couple weeks ago 'sh ip route summ' had the following output:
IP Routing Table - 238551 entries:
  6 connected, 2 static, 0 RIP, 42 OSPF, 238501 BGP, 0 ISIS
  Number of prefixes:
  /8: 18 /9: 9 /10: 15 /11: 40 /12: 135 /13: 275
  /14: 492 /15: 975 /16: 9744 /17: 4225 /18: 6887
  /19: 14901 /20: 17100 /21: 16183 /22: 20219
  /23: 21282 /24: 126003 /29: 8 /30: 30 /32: 10

A snippit of our cam-partition utilization looked as follows:
CAM partitioning profile: default

Slot 1 XPP20SP 0:
Slot 1 XPP20SP 0:
            [IP]262144(size),  23592(free), 91.00%(used)
        :SNet 0: 12288(size),  12263(free), 00.20%(used)
        :SNet 1:227590(size),   9723(free), 95.72%(used)
        :SNet 2: 18552(size),   1152(free), 93.79%(used)
        :SNet 3:  2709(size),      6(free), 99.77%(used)
        :SNet 4:   459(size),      2(free), 99.56%(used)
        :SNet 5:    82(size),      1(free), 98.78%(used)
        :SNet 6:    16(size),      2(free), 87.50%(used)
        :SNet 7:    32(size),     29(free), 09.37%(used)
        :SNet 8:    32(size),     31(free), 03.12%(used)

I had to shut down one of our ISP sessions last night due to unrelated
instabilities or I'd give up to the minute output.

Obviously this is alarming and we've been running in eyes wide open mode
since the cam filled up. We've expedited our 3.7.00 roll-out plan and
will be moving in the next couple weeks.

/Ryan

Gunther Stammwitz wrote:
> Hey Erich,
>  
> that's great news, thanks for the hint.
> Let's hope that foundry is going to provide a solution for the MRP-problem too.
> 
> 
> We are still running code <= version 3.6 on most machines but this sounds like
> we should start upgrading...
> Oh by the way: everyone who is using foundry direct routing (FDR) which equals
> the static cam mode should update *soon* as the global bgp routing table is
> growing and growing and there is a limit of about 256k routes in older code
> versions.
> One can also circumvent this problem by using the dynamic cam mode although this
> will increase the cpu utilization - but hey: a M4-jetcore-module is capable of
> handling this so the MLX shouldn't suffer from any cpu problems, right???
> 
> Is anyone actually using the static cam mode on a peering router with lots of
> peers, maybe at an IXP???
> 
> 
> Gunther
> 
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Erich Hohermuth [mailto:eh at solnet.ch] 
>> Gesendet: Donnerstag, 3. Januar 2008 15:24
>> An: Peter Olsen
>> Cc: Gunther Stammwitz; goverton at nwi.net; foundry-nsp at puck.nether.net
>> Betreff: Re: [f-nsp] What is the prefered way to add a vlan 
>> to a topo-group
>>
>> Hi 
>>
>> This feature is now implemented on MLX and XMR ;-)
>>
>> Section: Auto Shutdown Beginning with release 03.7.00, you can use the
>> new of BGP Neighbors on Initial global auto-shutdown-new-neighbors
>> command Configuration the router bgp configuration to disable
>> establishment of the BGP connection with a remote peer when 
>> the peer is
>> first configured.
>>
>> Regards
>> 	Erich
> 
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

- --
Ryan M. Harden, BS, KC9IHX		Office: 217-265-5192
CITES - Network Engineering		Cell:  	630-363-0365
2130 Digital Computer Lab		Fax:    217-244-7089
1304 W. Springfield	 		email:  hardenrm at uiuc.edu
Urbana, IL  61801 			

	 University of Illinois at Urbana/Champaign
		University of Illinois - ICCN
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFHfPoctuPckBBbXboRApIQAKCaN7dXjrvpZNG3lGvBywra7ohM+ACdEvNy
fJuynCOJzvQNCCKwPrTe2y8=
=lY2Q
-----END PGP SIGNATURE-----