Re: [f-nsp] Where have all the MLX/XMR users gone to?

XMR life time has or will come very soon for DFZ routing, the MLXe (if 
you have one) is still a valid platform for DFZ and I am sure it is 
going to be supported at least till 2025/2026.

So configurations that still work:
- MLXE chassis with MR2-X-management cards

Modules:
- BR-MLX-100Gx2-CFP2-X2
	-> 2 x 100g
- BR-MLX-10GX20-X2 in its variants:
	-> BR-MLX-10Gx20-X2
		-> 20 x 1g/10g
	-> BR-MLX-10Gx10-X2
		-> 10 x 1g/10g, upgradeable to 20 1g/20g
	-> BR-MLX-1GX10-U10G-X2
		-> 20 x 1g, upgradeable to 20 1g/20g

Cam profiles:
- default (1424K mil ipv4, 416K ipv6)
- multiservice-6 ( 1120K ipv4, 768K ipv6)
- ipv4-ipv6-2 (2048K ipv4, 1024K ipv6, no VPN)
-> reference 
https://documentation.extremenetworks.com/netiron/SW/63x/6300a/netIron-6300a-managementguide.pdf

See also 
https://gtacknowledge.extremenetworks.com/articles/Q_A/How-to-enable-2-Million-routes-on-MLX-platform

If you buy new, SLX 9540/9640/9850 are valid targets but this leads the 
thread back to the beginning ;-).


On 22 Mar 2019, at 0:37, Jon Lewis wrote:

> On Fri, 15 Mar 2019, Dennis op de Weegh wrote:
>
>> The XMR and MLXe are limited to 786432 IPv4 routes and 65536 for IPv6 
>> (ipv4-ipv6-2 profile)
>> If you want more routes you need -X2 linecards.
>>
>> The IPv4 table and IPv6 tables are close to limit from the XMR/MLXe 
>> -x cards (+-757166 ipv4 and +-65239 ipv6)
>> That is why you get the cam profile warnings.
>
> It seems Brocade was even worse than Cisco (1M routes on the 3bxl), in 
> that their 1M route cards are really 1M routes - 2x v6 routes - about 
> 100000 TCAM slots for other misc uses, and you can't fine tune the 
> v4/v6 split.  I finally got a chance to do some messing around with a 
> lab XMR with full BGP feeds, and was I think I found is:
>
> system-max settings dealing with max numbers of ip[v6]-route/cache 
> affect what the router is willing/able to store in RIB, but the 
> cam-partition profile affects what can be stuffed in FIB, and other 
> than selecting between the various cam-partition profiles, the TCAM 
> carving between v4/v6 is not flexible (or if it is, that's a hidden 
> command).  So, for a full-table router, the only cam-partition profile 
> of any use is ipv4-ipv6-2, and that profile may or may not hold a 
> "full" table today depending on the exact size of your full table.
>
> Or in other words, the MLX/XMR is dead or very nearly there for anyone 
> needing full v4 & v6 tables.
>
> ----------------------------------------------------------------------
>  Jon Lewis, MCP :)           |  I route
>                              |  therefore you are
> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
> _______________________________________________
> foundry-nsp mailing list
> [email protected]
> http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp