Solved

MLX cam partition issue

  • 25 April 2019
  • 4 replies
  • 444 views

Hello 🙂 I have a warning in log about cam partition free space. Now profile is ipv4-ipv6-2 and table is almost full
[ip] 786432(size), 39005(free), 095.04%(used)
[IPV6] 65536(size), 6250(free), 090.46%(used)

There are other profiles but i couldn't find any documentation about exact values. Could you please help me?
icon

Best answer by Steve Worrall 25 April 2019, 15:01

Hello,

The details of the profiles can be found in the management guide. If you do a search for cam-partition then it should get you to the appropriate section. There are quite a few tables that show the amount of resource that is available for each of the profiles.

Steve
View original

4 replies

Userlevel 1
Hello,

The details of the profiles can be found in the management guide. If you do a search for cam-partition then it should get you to the appropriate section. There are quite a few tables that show the amount of resource that is available for each of the profiles.

Steve
Hi Steve,
Thanks a lot 🙂
Userlevel 1
The profile also depends which line cards you got installed. For a DFZ BGP table you need to upgrade to X2 cards for more IPv4/IPv6 route space, else you need to build up some prefix filters, because we are reaching the 768k limit soon.

Valid modules:
code:
- 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 10g/20g
-> BR-MLX-1GX10-U10G-X2
-> 20 x 1g, upgradeable to 20 10g/20g




Valid cam-profiles (limits apply only with modules from above, else other limits apply)
code:
- default (1424K mil ipv4, 416K ipv6)
- multiservice-6 ( 1120K ipv4, 768K ipv6)
- ipv4-ipv6-2 (2048K ipv4, 1024K ipv6, no VPN)




Also see:
https://gtacknowledge.extremenetworks.com/articles/Q_A/How-to-enable-2-Million-routes-on-MLX-platform
https://documentation.extremenetworks.com/netiron/SW/63x/6300a/netIron-6300a-managementguide.pdf

I built
https://github.com/ipcjk/asnbuilder
to block some routes from regions, that I am not interested in, e.g. LACNIC.

Hi joergkost,
you are absolutely right, bgp table grows quick and for MLXs it is a problem
Thanks a lot for a tip 🙂

Reply