Slashdot Mirror


Opinions on Alternatives to Cisco Routers?

An anonymous reader asks: "I'm currently working on a project that is 'partnered' with Cisco. Despite that they make good routers, the company's relatively large size does not appear to be willing to meeting unique, customized, requirements. So what are your opinions of the alternatives: 3com, Juniper, etc? Anyone had bad/good experience with these companies? Are all their routers really essentially the same? How about comparative performance with totally customized routing solutions via Linux+Zebra or some other open solution?"

26 of 67 comments (clear)

  1. my question.... by Anonymous Coward · · Score: 4, Interesting

    what could you possibly require that you need cisco to customize their stuff for you? with all the software/hardware coming out of that company, how's it possible that something doesnt quite entirely cover everything you need?

  2. Cisco partner, cisco equipment by greywar · · Score: 5, Insightful

    Don't for a instant use some elses-cisco WILL take it as a slap in the face. If you need something custom-goto someone on their end in charge, and request either the equipment, or someone whom they approve that WILL do what you want. I've dealt with Cisco before.

  3. Will your customers accept non-Cisco equipment ? by MerlynEmrys67 · · Score: 4, Insightful
    I know of several IT shops that will not allow non Cisco equipment into their infrastructure. Would make it hard (if not impossible) to qualify for those accounts.

    That said - what kind of customization are you looking for... Cisco is the gold standard on most things IP infrastructure these days.

    --
    I have mod points and I am not afraid to use them
  4. My experience by jgaynor · · Score: 4, Informative

    In my experience, Cisco can meet basically any NEED you have. A good sales engineer can fulfill almost any scenario and guarantee that it will work. The biggest downside with Cisco is, undeniably, price.

    Matching the featureset of a cisco installation with zebra? easy.

    Matching the performance of a cisco box with Linux and Zebra? uh-uh. Not gonna happen. For a small installations maybe, but not when performance or load is involved.

    Why? Cisco does everything in hardware (ASICS). You can't meet performance like that with a PCI nic and the various bottlenecks associated with standard PC-based architecture. Juniper realized this and made a business model out of it. The took some open-source OS (which I can't remember right now - BSD?) and added support for network-task specific hardware. They can match cisco on performance and load-capability if not on product line. And they do it for ALOT less. My suggestion - take a look at juniper, then throw the juni quote back in your Cisco reps face. See if you can get him to bend a little :).

    1. Re:My experience by Urgoll · · Score: 5, Informative

      You're talking about the PIX - Cisco's firewall product line. Those are software only, and if you pirate the software you can easily clone it.

      But the real iron does everything in hardware (except error handling).

    2. Re:My experience by Triumph+The+Insult+C · · Score: 2, Informative

      Why? Cisco does everything in hardware (ASICS).

      on the high end, maybe. on the low end, that can't be further from the truth. on the low end, it's very cheap hardware, made up with better software

      sangoma has made t1/e1 cards for some time now with drivers for *bsd and linux. they have just been recently merged into openbsd-current and will get maintained by the openbsd peeps there.

      between carp, pf, pfsync, the soon-to-be-a-reality ifstated, and now the sangoma drivers, the question becomes more, why cisco?

      besides, you shouldn't support cisco to begin with. they are an evil, non-oss friendly, non-free/open standard, company

      --
      vodka, straight up, thank you!
    3. Re:My experience by ebrandsberg · · Score: 4, Interesting

      Methinks you haven't looked at what can be done with a PC these days. I work for a company that provides hardware that front-ends the largest websites in the world, and it's Intel hardware with PCI-X bus support, and PCI-X NIC's. These boxes can drive over 4Gb/s of traffic. How many networks drive that much traffic? The point is that with the right software, the hardware can fly. The hard part is the software. If you do the math, a 33mhz 32 bit PCI bus can handle about 1Gb/s, which if run equal xmit and receive, comes to 512Mb/s. A 64 bit 66mhz comes to about 4Gb/s. A 133Mhz 64 bit PCI bus does 8Gb/s, and gig cards now support this. So, even if you drive four Gig cards at wire speed, you are just reaching the top capacity of a single 133Mhz 64 bit PCI bus. Now consider that higher-end motherboards now have more than one PCI bus that can run at this speed, and a PC can make a very good alternative to a router. Again, the key is the software...

    4. Re:My experience by PurpleFloyd · · Score: 3, Informative
      Well, the "better quality" Ciscos are certainly computers in the Turing machine sense - they're just not very similar to your desktop machine. Rather, they use extremely specialized high-speed buses and processors to shuffle data around at amazing speed. Simply put, there's no way a 32-bit/33 MHz PCI bus will keep up with an OC-48's worth of data coming in constantly; a high-end Cisco will handle it easily. IOS (Cisco's proprietary OS) won't run on anything but Cisco hardware, either - the hardware and software are tuned to take advantage of each other's capabilities and thus do use hardware acceleration.

      While a Linux box or similar commodity hardware can do a good job in non-demanding situations, you start running into bus-bandwidth issues when you get into really high-speed networking. The only real reasons to use a Cisco router on a small, low-throughput internal network are consistency and Cisco's support, which is truly excellent.

      The one Cisco product line that does use standard off-the-shelf hardware is their firewall line. There, the fact that firewalls need to be able to cope with complex rule sets means that tuning the hardware for one set of circumstances will probably result poorly. Thus, the extensible and customizable nature of the PC architecture wins out over the highly specialized router architecture. Also, it means that it's possible to pirate the software and run it on other PCs - something Cisco certainly doesn't like and will probably come down hard on, legally speaking. I would imagine that has something to do with the incident you're thinking of, where their software was "warez'd;" the latest version of IOS is not hard to obtain, since Cisco makes most of their money on hardware and support contracts.

      --

      That's it. I'm no longer part of Team Sanity.
    5. Re:My experience by pyite · · Score: 5, Insightful

      Can I slap an OC-48 card in a PC? Unlikely. OC-192? How about 10GigE? Again, unlikely. For some of us, PCs can't compete with dedicated routing hardware. Even PCs that can handle large amounts of traffic can't switch at wirespeed. The key is programmable ASICs, pure and simple. If it's hitting the CPU too often (which all switching/routing on a PC must do) then we have a problem.

      --

      "Nature doesn't care how smart you are. You can still be wrong." - Richard Feynman

    6. Re:My experience by jgaynor · · Score: 3, Informative

      didn't they get quite mad at some guys cloning their hardware

      The incident you're referring to is the frankenpix project. It used the fact that one of the original PIX product line was a 300Mhz PII on an intel OEM chipset to create a clone using commodity parts combined with a PCI flash card (the only expensive part). Cisco took a cue from this, however, and changed it's business model accordingly. Newer pixes now come in the form of non-X86 standalone boxes or blades that interface directly with the switch-fabric of their higher end chassis (how the hell do you write chassis plural?).

      The comment above about PIX licensing is also correct. The base PIXos is still downloadable from Cisco's software repository for free with a valid CCO login, but add-on features are activated via 'product keys' which are a bit harder to come by.

    7. Re:My experience by jgaynor · · Score: 2, Informative

      4Gb/s Bus bandwidth != $Gb/s routing throughput.

      If your traffic was nothing but orderly, GIANT flows of data that went one for minutes at a time then maybe you could get some use out of that bus. Traditional traffic will squash the processor before the bus even gets up to a jogging pace. Giant backplanes or busses are very good for non-policy work (read: switching) but won't help when individual attention must be paid to each packet or frame.

      Its the policy involved with routing that will squash a PC-based router. Each packet has to be checked against ACLs, Quality of Service policies, line subscription rates, etc, etc. Big iron handles this by flow switching, IE applying policy to the first packet in each flow and then switching the rest based on that initial policy decision. There simply is no PC equivalent without specialized hardware.

      Even then, flow switching fails when viral traffic or network scans are thrown into the mix. Millions of ip threads per second, all with different destinations addresses and ports will bring even the hardiest of PCs to it's knees.

    8. Re:My experience by jgaynor · · Score: 3, Funny

      sangoma has made t1/e1 cards for some time now with drivers for *bsd and linux. they have just been recently merged into openbsd-current and will get maintained by the openbsd peeps there.

      between carp, pf, pfsync, the soon-to-be-a-reality ifstated, and now the sangoma drivers, the question becomes more, why cisco?


      Because we're talking about routing today, not routing in 1998. T1 speed traffic can probably be routed without loss by an apple newton that's simultaneously trying to OCR a hand-written journal entry by Christopher Reeve. Throw in virulent windows boxes at full-duplex GigE speeds and you're going to need ASICs for the policy and routing decisions.

    9. Re:My experience by forged · · Score: 2, Informative
      The key is programmable ASICs, pure and simple.

      You've got it. And the most common such ASIC in Cisco's middle range is called PXF for Parallel Express Forwarding.

      PXF is basically a programmable ASIC using a custom assembly language (think of it as a FPGA) where packets come in one side and are pushed through columns. Each PXF is one grid of 4 rows x 4 colums (16 CPU in total), and packets stay in each column for 128 cycles. Each column is responsible for one task, rarely two. What one PXF does includes IP decapsultaion and encapsulation, sanity checks (ttl, etc.), netflow accounting, NAT, L2TP, Policing/CAR, MAC rewrite, WRED, WFQ, LLQ, traffic shaping, L2TP LNS. This was 2 years ago on the c7200 and c7400 platform; now they're using two PFX processors in serial on newer platforms to do even more features.

      PXF is found on the c7200 platform (NSE-1), c7304, c7401, OSM line cards for the Cat6K/c7600, ESR 10k and uBR 10K where two PXF are working in serial, 10720, and probably more.

      So the PXF basically does the features described above in hardware. When the c7304 was introduced it was the quickest NAT box that Cisco had with 2Mpps switching performance with NAT. The main router CPU was hovering at 0% utilization, obviously. Not too shaby.. I'd like to see a PC do that but I don't think it's gonna happen any time soon :)

    10. Re:My experience by sql*kitten · · Score: 2, Insightful

      The biggest downside with Cisco is, undeniably, price.

      Well, you aren't paying for the kit, you're paying for the support infrastructure they have in place. Sure it's expensive upfront, but if something goes wrong, you'll be glad you did.

    11. Re:My experience by dublin · · Score: 3, Interesting

      Now consider that higher-end motherboards now have more than one PCI bus that can run at this speed, and a PC can make a very good alternative to a router. Again, the key is the software...

      Not entirely. Host-based routing is undoubtedly more do-able now than it was a few years ago, since Moore's law is finally delivering hardware that's "fast enough" for most such applications.

      The real problems aren't all in the software either. Linux in particular has serious performance problems in such applications. I'm not Linux-bashing here, it's just fact: If you want to do serious host-based network processing, you'll find that only Sun and IBM can really keep up with wire speeds.

      There are two reasons for this: First, the superior networking performance of those OSes (which is why *really* big firewalls like the one NASA uses to move *all* of its satellite tlemetry through always run on big IAX boxes); and Second, their markedly superior internal bus architectures. Almost all non-IBM x86 boxes have serious choke points in their buses or buscontrollers. (Seriously, check out the way IBM's x-series servers provide higher I/O cpacities, and you'll realize that if you're planning to really the crank I/O, Dell and HPaq aren't even in this game.

      Then, of course, there is the application software, which you correctly point out is often hard to come by (except commercially).

      Finally, pay attention to the NICs - they are definitely NOT all created equal. In general, the 3Coms, Intels, and such are trash from a serious performance point of view, and you're generally *way* better off with something designed by a company that haas a clue about protocol and system i/o performance, like Syskonnect.

      If you do your homework correctly, you can build a host-based router that will do the job in most cases, but it isn't easy. Especially if you're pushing the limits and don't have the serious multidisciplinary skills required to pull off putting together such a system (I'd estimate fewer than 1 sysadmin in 500 does), you're better off staying with the canned router solutions...

      --
      "The future's good and the present is nothing to sneeze at." - Roblimo's last ./ post
  5. "OpenBSD will soon rule the router world!" by Pegasus · · Score: 4, Interesting

    Or at least that's what some would want :) Which would be interesting to see ...

    Anyway, they already have good failover support for their firewall, nice bgpd, support for T1 hardware was recently merged into -current ... Theo himself is looking into replacing ciscos with OpenBSD.

    Something good will come out of it, i'm sure ...

  6. Back in my days... by psyconaut · · Score: 3, Interesting

    ...at a relatively large telco, we had Cisco pretty much rewrite one of their software products for us. We didn't scream or shout, just pointed out that the product was flawed in some areas and that we really would like to use a complete Cisco solutions. They were even flying guys up from CA on a weekly basis at one point.

    Yes, it did reinforce millions of dollars worth of equipment sales. But they also probably wouldn't have lost the sales if they refused.

    -psy

  7. Why ask this? by bluGill · · Score: 3, Insightful

    There are plenty of router companies. Cisco is most popular, but that is the only thing you can easily see. Any other advantage needs to be tested in the real world (or in a lab).

    Plenty of companies are as good or better, but until you define your requirements (to the point that few of us are qualified to comment) nobody can say which is really better.

    IP is standard. There isn't much that someone can do different and still be correct. Firewalls, speed, and some max capacity. IPv6 would be nice too. Figure your needs and then ask who will meet them.

    I've worked with and around several companies trying to knock Cisco off. It is hard because even when you have a technical advantage Cisco dominates. Sort of like how Microsoft dominates, but not as extreme, and Cisco has never been accused of being quite that evil.

  8. Do you REALLY need it? by bigsteve@dstc · · Score: 3, Insightful
    Before you go too far down this path, ask yourself if your company really needs a "unique, customized solution". If they do, expect to pay a "unique, customized" price for it. Not just up-front costs, but also in on-going costs. For example, you may have to pay premium maintainance costs, or you customizations may be tied to a particular vendor product limiting your future upgrade options.

    And beware of slick salesman who will promise you any feature you ask for in order to get a sale.

  9. If you can't go cisco... by shaitand · · Score: 2, Insightful

    don't listen to the other guy saying cisco will take it personal. First they won't even know, second we are a cisco partner and it's actually a pretty rare experience to even talk to someone at cisco (unless your techs are idiots and have to call them left and right).

    If you have to go with something other than cisco you may as well be using your own linux solution (since they are basically all using embedded linux ANYWAY). Go with something like a via mini-itx board/case (rather nice solid case on caseoutlet.com that I use alot) or a ppc board.

    Either way the main thing your looking for is something that can be passively cooled. I recommend having a case with a fan even if the chip is supposedly passively cooled. That way if the fan dies on you it's not a big deal. You also want solid state storage and enough ram to run the OS out of it. The general idea is to eliminate moving parts. Once you are running completely out of memory, and have no essential moving parts... you've got dedicated hardware devices matched at least equaled in this respect. And a 1ghz c3 at the very least equals 200mhz specialty chip (which are quite rare in practice despite everyone citing them to defend said routers).

    Nope, the biggest concern your going to have is bus speed. I'd keep it in mind.

    1. Re:If you can't go cisco... by pyite · · Score: 3, Interesting
      a pretty rare experience to even talk to someone at cisco

      Someone's Cisco rep doesn't like them. But seriously, if you're not in constant communication with Cisco, then you don't have a real big deployment. Heck, our Cisco rep comes to our department picnics and foots the bill for happy hour every now and then.

      don't listen to the other guy saying cisco will take it personal. First they won't even know

      Again, I find that highly unlikely. Let's put it this way, my department is entirely Cisco based. There just so happens to be another department in my organization that has some Foundry ServerIrons for their own use. I was talking with the Foundry guys at CeBit in New York this year and when I made the comment "We're an all Cisco shop." They immediately rebutted with, "No, I know for a fact you guys have some ServerIrons in your machine room." If Cisco's competition knows what kind of hardware we're running, you better believe that every time Cisco sets foot in a customer's machine room, they're taking note of any competitor's equipment that is in there. Use that fact to your advantage. That's all I'll say.

      --

      "Nature doesn't care how smart you are. You can still be wrong." - Richard Feynman

  10. unique custom solution? by kasper37 · · Score: 2, Insightful

    Your problem seems paradoxical. If your company isn't that big, I don't see how you would need any customization beyond what anyone off the street could get from Cisco. On the flip side, if you are that big, Cisco (as well as other companies) will do quite a bit to make sure you're happy.

  11. Really depends on your needs by dtfinch · · Score: 2, Interesting

    Though I wouldn't recommend it, I've seen 30 systems all accessing the internet behind a $30 linksys router (appears to belong in a home network) with zero complaints. It was configured to work as a NAT and also provided port forwarding and log streaming. Though I doubt it could handle much more, it worked well for the given workload and setup needs.

    So I don't think a cisco router is necessary for every network. For small networks, cheaper solutions work fine. Just remember that if you underestimate your future needs, it can cost you dearly later. But I've heard even cisco zealots talk about the routers crashing under load, which obviously should be unacceptable for any hardware of "enterprise" quality, but I haven't been around them long enough to see it for myself.

    Search google for 'cisco "lawful interception"' if you like a good scare. Also, the fact that their IOS source code was recently stolen is another thing to be concerned about.

    But what do I know? My experience with cisco routers is limited to a single class on network security. They're very flexible and featureful routers, certainly top quality even if not bug free, but whether you need one is highly dependent on what you'd want it to do for you.

  12. Suggestions by noah_fense · · Score: 2, Informative


    Core Network:
    Juniper

    Layer 2/3 routers: (Can still perform all router functions, but are cheaper per-port)
    Riverstone Networks
    Extreme Networks

    I wouldn't recommend anyone else. Alcatel, Foundry, and 3COM haven't really impressed me.

    Interestng note, Qwest uses Juniper M20/40s in their core OC28 network. Juniper, IMHO, is the only real Cisco competitor for a network backbone. And, Juniper uses a BSD OS on their routers.

    I've had good experience with riverstone support.

    I work in an environment where we see many different router vendors every month. Riverstone seems to be the ones who stick around. Also, you might not have heard of them because they sell mostly MAN (Metro area networks) which are most deployed abroad.

    -n

  13. Re:Will your customers accept non-Cisco equipment by dublin · · Score: 4, Interesting

    I know of several IT shops that will not allow non Cisco equipment into their infrastructure. Would make it hard (if not impossible) to qualify for those accounts.

    Cisco is good, but they're by no means in a class all their own from a performance or capability point of view. Personally, I've found Extreme Networks can often offer considerably higher performance at a price that's a bit lower than Cisco's - and the care and feeding of Extreme's gear is *way* easier than Cisco's, too, which is a cost that you should NOT ignore...

    I have nothing against Cisco, but Extreme "gets" performance far more than Cisco - for instance, Extreme's gigabit switches have deeper buffers than Cisco's which is irrelevant for most networking tasks, but shows up big-time when you try to do something serious like, say, storage-over-IP, or a cable head-end: it's just way too easy to overrun Cisco's buffers and wind up with your data all over the floor. Of course, if you ever have to retransmit anything because of this, the huge latency involved in that obliterates any chance of good performance. Extreme's engineers know this, and design their gear accordingly.

    I'd suggest giving them a chance as an alternative vendor. (I have no relationship with Extreme, either, except as one pleasantly surprised by the company on several occasions.)

    --
    "The future's good and the present is nothing to sneeze at." - Roblimo's last ./ post
  14. Opinions from a network engineer (for a living) by cantstoptherock · · Score: 3, Insightful

    Okay, so I do network engineering for a living. I've been doing it for about eight years, so I think I have some insight for you. First off, ebrandsberg's +5 moderated statement (#9567080) is a little bogus.

    While the math on the hardware is straight, he fails to comprehend that the routing engines of Linux and FreeBSD are completely not designed for rapid routing and forwarding lookups. While there is some progress being made in this area, it is incredibly slow work. The Linux and FreeBSD IP stacks are not designed for packet forwarding and rapid cut-through switching; they're designed for dealing with an entirely separate problem, and the code is pretty ugly compared to the rest of the large body of network code. BSD has a leg up on Linux, but 2.6 is catching up fast in this regard.

    I don't understand what you think you're not getting from Cisco. From an innovation perspective, Cisco has pretty much every feature in real-world networks deployed that people need, with some minor exceptions in the MPLS world. While Juniper beats them on lookup and engine performance, the Juniper backplane has some distance to go when coupled with large amounts of traffic. Your own description of your problem isn't sufficient data for me to really speak to your requirements, but I have to go on record here and say I think your statement about Cisco not able to provide unique, customized needs is a little off-kilter. I question what your unique and customized needs really are, because the reality of network engineering is you find a set of features, you find a box that meets your performance requirements, and you roll out. Cisco has a feature/performance mix for every network from A to FF, including yours.

    If your sales team isn't working well, then find a different one. This is standard business practice, and not unique to Cisco.

    Please do not take the advice of other trolls in this thread who suggest that they can recommend you a vendor without knowing intimate details of your application. They are snakeoil salesmen. People who suggest Juniper, Extreme, Riverstone, may all have good recommendations, and they may be sound for your application, but I wouldn't make that judgement call without being absolutely certain that they knew all your requirements. For example, I do over 5Gb/s outbound to the Internet on Foundry Networks gear, and while it works, I can't honestly say that i'm happy with it for the features that I need. We gave Juniper a shot and they didn't have the right cost-per-port/density that we needed, so we ended up heading in Cisco's direction. This decision took me about a month and a half in comparing all the options, and doing a feature matrix that was weighted towards what I needed.

    This may all seem like stupidity or busywork to you, but I assure you it is not. Any network design requires this much attention, and your company will thank you for it. Do not try to do things cheaply - the PC router road is a worn one, mostly because people come back down the same path they took to get there and go off in another direction.

    If you are insistent on using "open-source" using Zebra, GateD, or Click under FreeBSD, Linux, or something else, I would advise you to wait for some time unless your traffic needs are under a couple of megs a second.