Page 1 / 13   >   >>
opticalPassion 12/5/2012 | 3:23:38 AM
re: Foundry Strikes at the Core I feel happy to see the arrogant monopoly CSCO get beaten up eventually!
tsat 12/5/2012 | 3:23:38 AM
re: Foundry Strikes at the Core
Does not appear to support SONET interfaces, is
this correct?

materialgirl 12/5/2012 | 3:23:38 AM
re: Foundry Strikes at the Core If routes are decided 100% in hardware, how does the system adapt to change, either in the network or in services provided, say different MPLS standards or something of that ilk?
tsat 12/5/2012 | 3:23:37 AM
re: Foundry Strikes at the Core
Software manages the hardware routing tables.

What this means is that hardware determines the
route of each individual packet without going
though a time-consuming software routine.

materialgirl 12/5/2012 | 3:23:36 AM
re: Foundry Strikes at the Core tdat,
That is where I am confused. I do not see what is done in hardware that is new. If the routing function is done in hardware, it seems to me that no software or routing tables would need to exist. If the speed and cost advantage come from doing route decisions in hardware, the price you pay is manual control adaptation to change over time. It seems that you pay now or pay later somehow.
reoptic 12/5/2012 | 3:23:36 AM
re: Foundry Strikes at the Core Carrier business relationships and carrier class experience mean a lot and does Foundry have that? What about support for millions of routes and protocols like V6? Isn't an all ethernet core really after the market that Force10 is after?
dadofamunky 12/5/2012 | 3:23:36 AM
re: Foundry Strikes at the Core I think this is exciting. Just from the price point alone they're bound to get some more attention. Whether that translates into exponentially greater sales in that segment is another question.
light-headed 12/5/2012 | 3:23:35 AM
re: Foundry Strikes at the Core No News... Re-badge existing enterprise gear and do some feature locking based on EEPROM. 3com wrote the book on this years ago. The federal space must be drying up and they are getting desperate.

Limited selection of real router interfaces and features. YAAAAAAAAAAAWWWWWWWWWWWWN...

Foundry Networks... NO CORE for YOU!


(the Router Nazi has spoken - apologies to Seinfeld)
beowulf888 12/5/2012 | 3:23:35 AM
re: Foundry Strikes at the Core Are they OSMINE compliant/certified? If not, what's their roadmap for this. Cheap is good, but Telco's won't be buying this equipment if they can't integrate it into their network management systems...

blackstar 12/5/2012 | 3:23:34 AM
re: Foundry Strikes at the Core materialgirl,

there is nothing new/unique here that is done in hardware. all performace-oriented routers on sale today do as much as is feasible of the packet forwarding role in hardware, usually meaning firmware running on custom chips, for performance reasons.
Packet forwarding always needs a way to figure out where to send a packet, hence the tables. All routers have tables that control where to send traffic, though these tables may be implemented in suprisingly dissimilar ways, and might be nothing like a table in the conventional sense.

Routing protocols are never implemented in hardware since routing protocols are much too complex, buggy, and subject to change to be burned into silicon (other issues there too).

You are correct that a trade-off exists here. For example, a company might sell line cards that whose chips will never be able to support, say, IPv6, because the chips were designed only for very fast IPv4 processing. Such a company would need to sell completely new line cards to support IPv6 or for certain new features (this can make customers unhappy).

Other vendors' line cards are more programmable, and wouldn't have such a severe issue, though the flexibility sometimes at the expense of performace, e.g. can't do line rate with particular combinations of features enabled.

Most vendors that I'm familiar with are going with something more like the more flexible approach, because development on a flexible platform is cheaper in the long run and because customers don't like buying all new hardware every time they want to implement a new protocol or feature.
Page 1 / 13   >   >>
Sign In