1 ACCEPTED SOLUTION
Do you want to replace the MLXe chassis with another chassis solution like the SLX-9850 or would you like to go to the pizza box? What is the current use case for the MLXe?
Just asking, because the SLX is more like a concept and an OS, that comes bundled with different devices. Also I don't think there is a ready-to-use "why this is better"-for you presentation in this case.
The SLX series was once meant to supersede the CER/MLX slowly and is of course a much younger platform than the MLX. E.g. MLX uses a lot of power-hungry PPCs and older Broadcom chips, while the SLX-series is almost state of the art (...depending on the device...).
Because of Brocades failed strategy on "The New IP" (Brocades "SDN" predecessor), the Brocade <-> Broadcom sale and the delay in the Extreme acquisitions by the CFIUS, the original release and engineering schedule was ruptured heavily and the MLX still exists (for good, I love it).
So, but still some reasons to switch slowly from MLX to SLX and not to another vendor:
- Keep your original vendor
and keep the network world diverse
- built on Broadcom newest commodity ASICs (much more powerful in theory)
- The CLI/CONF syntax is similar to MLX (with a bit of VDX), less training
- lot of the code comes from MLX/VDX, so a lot of features are stable, e.g. MCT works the same way
- better density, saving cooling capacity and rack capacity
- pricing is reasonable
- all the new features (VXLAN, EVPN) and will get all the newest features
- SDN features (see the SDN configuration guide)
- "Insight" features, e.g. spin up VMs on the management board
- lot of EXTREME VALIDATED DESIGNs available with setups between MLX and SLX (smoother transition)
- comes in different hardware version for your requirements (e.g. the 9640 as full DFZ internet router or the 9850 as chassis version for core routing) but it is always the same OS underlying (one OS strategy)
Dear bro,
thank you very much for your detailed explanation
Yes, the customer want to replace the MLXe chassis with another chassis solution. We want them to keep using Extreme products.
I fully agree with you. your comments is very helpful. we will collect these key points and discuss with customer.
thanks again~~
Do you want to replace the MLXe chassis with another chassis solution like the SLX-9850 or would you like to go to the pizza box? What is the current use case for the MLXe?
Just asking, because the SLX is more like a concept and an OS, that comes bundled with different devices. Also I don't think there is a ready-to-use "why this is better"-for you presentation in this case.
The SLX series was once meant to supersede the CER/MLX slowly and is of course a much younger platform than the MLX. E.g. MLX uses a lot of power-hungry PPCs and older Broadcom chips, while the SLX-series is almost state of the art (...depending on the device...).
Because of Brocades failed strategy on "The New IP" (Brocades "SDN" predecessor), the Brocade <-> Broadcom sale and the delay in the Extreme acquisitions by the CFIUS, the original release and engineering schedule was ruptured heavily and the MLX still exists (for good, I love it).
So, but still some reasons to switch slowly from MLX to SLX and not to another vendor:
- Keep your original vendor
- built on Broadcom newest commodity ASICs (much more powerful in theory)
- The CLI/CONF syntax is similar to MLX (with a bit of VDX), less training
- lot of the code comes from MLX/VDX, so a lot of features are stable, e.g. MCT works the same way
- better density, saving cooling capacity and rack capacity
- pricing is reasonable
- all the new features (VXLAN, EVPN) and will get all the newest features
- SDN features (see the SDN configuration guide)
- "Insight" features, e.g. spin up VMs on the management board
- lot of EXTREME VALIDATED DESIGNs available with setups between MLX and SLX (smoother transition)
- comes in different hardware version for your requirements (e.g. the 9640 as full DFZ internet router or the 9850 as chassis version for core routing) but it is always the same OS underlying (one OS strategy)
