x
Optical/IP

Foundry vs Nexus

9:30 AM -- You'll surely recall this table, from January, showing Cisco Systems Inc. (Nasdaq: CSCO) ostensibly taking the lead in 10-Gbit/s Ethernet density with the Nexus 7000. (Or, just read the story: Cisco's Nexus Targets Data Center's Future.)

Today, Foundry Networks Inc. (Nasdaq: FDRY) is bringing out a new, 16-port 10-Gbit/s Ethernet module for its BigIron RX that will bring it to density parity with Cisco. Each company will have a chassis capable of holding 512 10-Gbit/s Ethernet ports.

Of course, all this is just on paper. Foundry's module won't ship until August, and the 18-slot Nexus that would provide those 512 ports is expected to arrive by July. And the folks at Woven Systems Inc. will still talk your ear off about their ability to mesh systems together.

— Craig Matsumoto, West Coast Editor, Light Reading

Page 1 / 3   >   >>
idafmool 12/5/2012 | 3:42:14 PM
re: Foundry vs Nexus According to a personal interview with Joe... X Cisco / http://www.networkworld.com/co...

The Cisco Nexus is a rebranded/over-upgraded 6509.

Do you really think that Foundry has overcome the SW stability issues??

Pete Baldwin 12/5/2012 | 3:42:12 PM
re: Foundry vs Nexus Thanks for the link. I don't see a spot where Ammirato directly makes the 6509 comparison -- is that your own conclusion?

Regarding the software stability question -- I'm not sure I know what you're referring to. (And might not have known the answer anyway; I haven't spoken to Foundry about the announcement.) Care to elaborate?
idafmool 12/5/2012 | 3:42:10 PM
re: Foundry vs Nexus Sure. I've met Joe personally and he told me in confidence that the product was a flop. Haven't had my hands on it though.

Foundry... anytime you rely on merchant silicon
you end up with a diverse code base to support your product set. Some products overlap but will have their own train of code. The only way it truly gets baked in is by using the customer as an experiment. It ends up as an engineering and support nightmare. In addition, there has historically been issues with lack of egress ACL capabilities, egress rate limiting, ability to modify ACL's on the fly, small buffers, the small amount of 802.3ad groups per switch and ports per bundle, inefficient 802.3ad hashing mechanisms(source and destination MAC vs 5 tuple), and the number of vlans they support is typically not as advertised.

So, who will buy Force10 this year??
Pete Baldwin 12/5/2012 | 3:41:32 PM
re: Foundry vs Nexus >Sure. I've met Joe personally...

OHHH, I see. Sorry. I misunderstood "personal interview" to mean "interview done by the person who wrote that article in the link" -- I didn't interpret the phrase literally enough.

Well, great point then, and thanks for the input. Thanks also for the details on the shortcomings of merchant silicon.

I gotta agree with NorthernRights about Force10 though. It's too pricey to get bought, and AFAIK all the obvious candidates don't have much need to buy them... unless you're seeing an angle I'm not .......
NorthernRights 12/5/2012 | 3:41:32 PM
re: Foundry vs Nexus idafmool...interesting...on Force10...i don't think anyone will pay the big bucks the VCs want for Force10...i'm a wall street analyst...just my two cents...
Soupafly 12/5/2012 | 3:41:29 PM
re: Foundry vs Nexus Agreed with craig although I am hardly a Force10 expert. As for Foundry they are interesting but an interesting niche way.

Whats going to be fascinating is if the traditional datacomms only model can survive. By that I mean Juniper, Foundry, Force10, etc.

With the way the market is moving the need to consolidate, integrate & virtualise the functionality these players deliver into higher utility platforms I see it as an interesting future. (Higher utility been Routing, Switching, BRAS, etc..)

There will still be a need for specialists, just a llot less of them! Only 1 or 2 of the current crop have +5 year longevity for me.

What are your thoughts, folks? Am I way off?
core11 12/5/2012 | 3:41:22 PM
re: Foundry vs Nexus 1) Nexus GĒō from their web 64 ports wire-speed per box; BigIron GĒō 128 ports wire-speed (RX and MLX)per box
2) Oversubscribed configurations: both use 4:1 => nexus-256, BigIron-512.

@ idafmool

I happen to know the FDRY box
- several things stated are wrong
- if you look for bigger ACL look at MLX
- both switches has big buffers (min 512Mb per 10G)
- Merchant silicon GĒō Non-factor (Cisco and Juniper use them as well)

Looking at FDRY financials, you got to admit product is a big success. Cisco Nexus looks promising as well and it does not seem to an upgrade of 6509
idafmool 12/5/2012 | 3:41:21 PM
re: Foundry vs Nexus Well... in your opinion what was stated wrong? If you've had your hands on the RX you'd know the limitations. You shouldn't consider the MLX for an RX application. Foundry will tell you that.

Just so we are on the same page:
Cisco Nexus:
- Nexus Targets the Data Center
- Brand New OS (NX-OS) based on MDS SAN OS
- Virtual Ouput Queues (LOL - not again)
- 10GE Card is 4:1 Oversubscribed. (Big Buffers won't help!!)
- Only 64 Line Rate 10GE Ports
- 6000 Watt PS (not going green with that)

Foundry RX
- The RX uses Marvel Chipset (ooohh boy)
- See limitations in original email. All have been tested.
- High density is all they give you

** Yes there are limitations in merchant silicon. Cisco is good @ virtualizing queues and buffers to compensate for the short comings.
mboltin 12/5/2012 | 3:41:17 PM
re: Foundry vs Nexus "If you've had your hands on the RX you'd know the limitations. You shouldn't consider the MLX for an RX application. Foundry will tell you that. "

I think you are a bit misinformed here. Foundry will tell you just the opposite: If you have need for outbound ACL's, egress RL, scalability numbers, etc., then you should get the MLX.

And by the way, the latest MLX code supports multiple enhanced hash algorithms and up to 32 ports in a LAG. Do you need more?
idafmool 12/5/2012 | 3:41:16 PM
re: Foundry vs Nexus Too funny. If you read closely (See Subject)... it was Nexus vs the Big Iron... Not the NetIron MLX or XMR series.

They are positioned at the SP edge. I seriously don't think Foundry will put the MLX in the Data Center?? Silly man You!

http://www.foundrynet.com/prod...

Anyway... explain the hash algo's. Show me the merchant silicon that can do 5 or 7 tuple hashing!


Page 1 / 3   >   >>
HOME
Sign In
SEARCH
CLOSE
MORE
CLOSE