NetIron MLX/XMR
From FoundryWiki
The Foundry NetIron MLX/XMR line is a layer 3 switch/router.
Contents |
[edit] Main purpose
[edit] Available models
[edit] MLX
[edit] XMR
[edit] Available line cards
[edit] Non-blocking
- MLX/XMR-10Gx4 - 4 ports 10GbE (XFP)
- MLX/XMR-10Gx2 - 2 ports 10GbE (XFP)
- MLX/XMR-1Gx20-SFP - 20 ports FE/GE (SFP)
- MLX/XMR-1Gx20-GC - 20 ports FE/GE (Copper)
- MLX-1Gx48-T - 48 ports FE/GE MRJ21 (Copper)
- X-OC192x2 - 2 ports SONET OC-192/STM-64 (XFP)
- X-OC192x1 - 1 port SONET OC-192/STM-64 (XFP)
- X-OC48x8 - 8 ports SONET OC-12/48/STM-4/16 (XFP)
- X-OC48x4 - 4 ports SONET OC-12/48/STM-4/16 (XFP)
- X-OC48x2 - 2 ports SONET OC-12/48/STM-4/16 (XFP)
[edit] Overbooked
[edit] Architecture
[edit] Limitations
[edit] Layer 2
- Maximum of 16 ports in an aggregated link (32 as of software version 3.8.00)
- Maximum of 8 VSRP trackports
[edit] Layer 3
- Maximum CAM size for IPv4: 1M/512K (XMR/MLX)
- Maximum CAM size for IPv6: 240K/112K (XMR/MLX)
NOTE: Actual available CAM size may be less, depending on chosen CAM partitioning profile
[edit] Configuration tips
Some hints aimed at an IX point perspective
cam-partition profile ipv4-ipv6-2 system-max vlan 4095 system-max rstp 128 system-max ip-cache 524288 system-max ip-route 524288 system-max virtual-interface 4095 system-max receive-cam 8192 cpu-usage on # enabled CPU monitoring in SNMP note: setting the system-max vlan and virtual-interface to 4095 will have a big memory usage impact (over 80MB extra usage)
