• United States

The search for the optimum network: Don’t let IT vendors sell you on lock-in

Sep 28, 20216 mins
Network Management SoftwareNetworking

Credit: Bigstock

How should an enterprise pick products to build its network? Do they look for the best of each product category, knowing this will increase both integration issues and finger-pointing? Do they select the best vendor overall, knowing that this will invite vendor lock-in and compromises in each product category?

This issue is as old as networking, and we’ve still not resolved it. How do enterprises decide when to add a vendor in hopes of getting the best technology, and protect themselves from the consequences?

Every network vendor wants to be your only vendor. No network vendor wants to accept responsibility for problems, and most don’t even want to work hard to find out who’s causing them. Big network-equipment vendors have not only fallen behind on innovation, they work to actively stifle it, fearing it could damage their incumbent position. These are the views of enterprises, whether they favor single-vendor networks or best-of-breed.

The risk of your vendor going out of business is significant unless you buy from a giant. Startups are one-trick ponies that have seized on a niche problem and solved it but will never do anything else useful. No vendors really support standard interfaces or practices, so integrating vendors is an unsolvable problem. The total cost of integration and support for multi-vendor networks will exceed the cost of the hardware. These are also enterprise views, and again from both sides of the debate.

You can see from these points why managed network services are getting more popular, but even there, enterprises say that it’s nearly impossible to find a managed service provider that will take responsibility for LAN and WAN, and early reports on those that do suggest that the MSPs themselves are falling into the single-vendor-or-best-of-breed pit, too.  We can’t forego networks, so what do we do?  Fortunately, the two sides of the debate agree on some points.

Don’t simply reject single-vendor networking

The first point they agree on is that insisting on multiple vendors just to avoid depending on a single vendor is a mistake. You don’t really gain leverage over them, and you multiply your integration and problem-resolution challenges. The only valid reason for a multi-vendor network is that there’s a significant cost, performance, or feature benefit to the decision. Don’t use intangibles to justify “best-of-breed” network additions. Demand real financial quantification of each potential benefit. The fewer vendors you already have, the greater the savings you should demand. Enterprises are mixed on a specific number, but most say that unless you can show quantifiable financial benefits of between 15% (if you already have multiple vendors) and 30% (if you only have one vendor now), it’s almost certainly not worth adding another vendor or technology. 

“Almost certainly” isn’t a sure thing, of course. Many best-of-breed advocates say that their primary vendors drive them to a multi-vendor approach one little step at a time by employing tactics aimed at locking them in. They say that there are warning signs that you should look for, signs that your vendor is taking you in the wrong direction:

  • Improved features or performance are available only in new products, new software, and at extra costs. You can’t stay the course.
  • Your operations costs are increasing year over year because of increased complexity in the vendor’s management requirements.
  • Features you need are not available from your vendor until well after they’re offered by other vendors.
  • Your problem response times are lengthening, and your problem escalation procedures don’t seem to get your vendor’s attention any longer.
  • Your vendor is suddenly reluctant to make any pricing or terms concessions during negotiations for new equipment, or during a refresh of old technology.

Indications that your vendor is taking you in the wrong direction doesn’t mean that you couldn’t make things even worse. Suppose you either see a clear, quantifiable, justification for a best-of-breed vendor addition to your network, or that you’re seeing some of these warning signs. Is it possible to avoid all the risks of multiple vendors and still gain best-of-breed benefits? Probably.

Enterprises that successfully navigate that tightrope say that the first step is to think enclaves. If you have multiple vendors, keep them in contained areas and connect those enclaves with the simplest and most mature interfaces available. Most networks aren’t vast mixtures of devices creating a single ecosystem, they’re made up of collections of devices performing a common function. One router vendor in core, another at the edge.  One data-center switch vendor and another in workgroups or the WAN. Treat each enclave as a discrete network.

Enterprises already often use different vendors for different enclaves, picking vendors whose cost and features are optimum for each mission. Many vendors focus on specific missions, and that’s what often creates “best of breed” options in the first place. The interactions of devices within each of these enclaves is typically more complex than the interactions across enclave boundaries, so having a single vendor and even a single class of device within an enclave is more important. Intermingling vendors within an enclave network invites all the classic finger-pointing and integration problems. It will also likely prevent you from realizing any best-of-breed benefits, because special capabilities will be short-stopped by devices that don’t support them.

Another useful strategy is to focus on monitoring the interfaces between your enclaves and develop fault-isolation procedures designed to identify which side of the interface isn’t performing. While a single management system across an entire network may seem helpful, it’s often not even useful. Data-center networks are managed differently than branch networks or VPNs. It’s better to focus any special monitoring tools at the enclave boundaries. If you can isolate problems at the boundary points, you can then use specialized management tools to correct the enclave that is broken.

Even if you don’t have different vendors in different enclaves, this kind of management partitioning often improves operations efficiency. It also keeps the door open for introducing a best-of-breed solution in an enclave with minimal disruption of your operations processes.

The final strategy is to accept reality. Despite the debate over single-vendor versus best-of-breed, almost every enterprise ends up with multi-vendor networks, and say that adopting the latter approach in some cases is the right answer. Enterprises don’t want a single-vendor or best-of-breed network; they want an optimum network.  The fact that there are so few enterprises that have really settled on a single supplier of network gear says it all. That’s why it’s smart to declare that best-of-breed has won, and focus on how to justify, integrate, and manage the resulting multi-vendor environment. If enterprise experience is a guide, that will get you the optimum network you want.


Tom Nolle is founder and principal analyst at Andover Intel, a unique consulting and analysis firm that looks at evolving technologies and applications first from the perspective of the buyer and the buyers’ needs. Tom is a programmer, software architect, and manager of large software and network products by background, and he has been providing consulting services and technology analysis for decades. He’s a regular author of articles on networking, software development, and cloud computing, as well as emerging technologies like IoT, AI, and the metaverse.

More from this author