SDxCentral
Join Log In
SD-WAN 5G Edge 1 IoT SDN NFV Containers Cloud Security AI Data Center Storage APM/NPM Open Source

Log In to SDxCentral

Log in with your email? Forgot your password?
  • Newsletters
  • eBriefs
  • Podcasts
  • Webinars
  • Videos
  • Directory
  • White Papers
  • Resources
  • Use Cases
  • Support

Join SDxCentral and get information tailored to your particular interests everyday.

Join
Sponsored:
Dell EMC Citrix Riverbed

NFV Can Curb Those End-of-Life Woes

Vinyl Record
Craig Matsumoto
Craig MatsumotoMay 25, 2015
2:21 pm MT
Email LinkedIn Facebook Twitter Reddit Hacker News

Here’s a network functions virtualization (NFV) use case I hadn’t considered before: replacing equipment that’s reached obsolescence, more politely called end-of-life (EOL).

The idea came up during a Metaswitch Networks webinar last week on NFV and the telecom voice network. (Disclosure: SDxCentral helped promote this webinar, and I was a guest speaker on it.)

You won’t “EOL abatement” on the proof-of-concept roster assembled by ETSI, but the use case has come up with a customer, and Paul Drew, general manager of Metaswitch’s open source business unit.

A European incumbent operator is facing end-of-life treatment for the equipment it’s using in the voice network. This means the products will no longer be supported or sold by the vendor.

The software is still supported by the vendor; it’s just that the carrier is being forced onto a new hardware platform. And the carrier didn’t like that idea.

“Rather than just replace the hardware from their existing vendor, they wanted to go to an NFV-based deployment,” Drew said. “They did not want to get locked in by the next hardware revision.”

It also happened to be a cheaper option, he said. This particular carrier has been offering enterprise services through its own data center, so the organization is well versed in virtualization and has ready RackSpace for an NFV deployment.

But the main thing is that the carrier doesn’t have to face equipment obsolescence again. Or, more precisely: The carrier’s hardware becomes obsolete more often, but in a way that’s expected. Servers get replaced every few years, and replacements are easy to find and don’t have to come from the same vendor.

This, of course, as been one goal of NFV all along: Avoid vendor lock-in by moving network functions to commodity hardware. The mini-epiphany for me during this webinar was that any time equipment reaches end-of-life, it forces a new round of equipment shopping, which can create a natural transition point for NFV.

Metaswitch plans to more formally announce this use case soon, Drew said.

Related Articles

Fortinet Boosts Security Message for Carrier Push to 5G
Fortinet Boosts Security Message for Carrier Push to 5G
Ericsson, Intel Team Up on 5G Software-Defined Infrastructure
Ericsson, Intel Team Up on 5G Software-Defined Infrastructure
Orange-Business-Services-Is-Building-a-One-Stop-Shop-for-SD-WAN
Orange Business Services Builds ‘One-Stop Shop’ for SD-WAN
AT&T 5G Airship Plans Powered by Mirantis
AT&T 5G, Airship Plans Powered by Mirantis
Ericsson Turnaround Could Limit Growth Potential Says TBR
Ericsson Turnaround Could Limit Growth Potential, Says TBR
ONAP Casablanca Shows Up in ‘All the Gin Joints’
ONAP Casablanca Shows Up in ‘All the Gin Joints’
SDxCentral Daily News

Join your Peers! Subscribe to SDxCentral's Newsletter

Article Tags:

Breaking News Metaswitch Networks NFV

Craig Matsumoto

About Craig Matsumoto

Craig Matsumoto is managing editor at SDxCentral.com, responsible for the site's content and for covering news. He is a "veteran" of the SDN scene, having started covering it way back in 2010, and his background in technology journalism goes back to 1994. Craig is based in Silicon Valley. He can be reached at craig@sdxcentral.com.

Subscribe to Get the Daily News!

About SDxCentral

  • Newsletters
  • About Us
  • Contact Us
  • Work With Us
  • Editorial Team
  • Careers
  • Legal
  • Support

Engage With us

This material may not be copied, reproduced, or modified in whole or in part for any purpose except with express written permission from an authorized representative of SDxCentral, LLC. In addition to such written permission to copy, reproduce, or modify this document in whole or part, an acknowledgement of the authors of the document and all applicable portions of the copyright notice must be clearly referenced. All Rights Reserved.

© 2012-2019 SDxCentral, LLC, All Rights Reserved. SDNCentral™, the SDNCentral logo, SDxCentral™, SDxCentral logo, SDxNews™, SDxTech™, SDx™, the SDx logo, and DemoFriday™ are trademarks of SDxCentral, LLC in the U.S. and other countries.

  • Terms of Service
  • Privacy