Top considerations in transitioning to NFV

July 17, 2015

Network Functions Virtualization (NFV) is a network architecture that implements virtualization of network functions to deliver communication services efficiently. It offers the potential for enhancing service delivery and reducing capital expenditure for service providers offering business, residential and mobile services. Some of other benefits that drive networking stakeholders to adopt NFV include – significant reduction in operational costs and time to market, elimination of vendor lock-in, ability to offer flexible and competitive service delivery.
NFV derives these benefits by utilizing virtualization and cloud computing capabilities in order to accommodate network appliance in software. Thus, while the aforementioned benefits of NFV are alluring, the following challenges that co-exist must be considered before adoption.

Performance

While the software-based network paves a range of opportunities to innovative services, it could hamper performance. In several scenarios, the performance levels of dedicated hardware cannot be achieved by a single virtual network function (VNF). Hence the number of instances of VNF, need to be scaled-up to achieve the same. During dynamic provisioning, this introduces a management overhead, when the load of each VNF has to be determined. This in turn deteriorates the performance levels delivered by NFV.

Furthermore, as network functions are moved from dedicated hardware to cloud infrastructure, additional performance impact is introduced in network services. Besides this, service providers need to verify that the level of impact of their SLA metrics due to NFV transition.

Security

While embracing an evolving architecture one cannot ignore the associated security challenges. Newer capabilities and components in the network also mean fresh and unexpected prospects for security attacks. Further distribution of VNFs across datacenters and frequent migration for resource optimization introduces practical difficulties of defining and enforcing the security policies.

Reliability

Service providers typically have demanded five-nines reliability. While the proprietary hardware based legacy networks have the ability to adhere to this standard, a hybrid environment which encompasses COTS hardware capabilities (both virtualized and non-virtualized) adhering to the five-nines is a challenge. The dependencies on multiple components and utilization of commodity hardware introduce complexities expecting resiliencies to be built into the software component than the hardware.

Interoperability / Compatibility

An NFV deployment involves hypervisor, hardware and software solutions from various vendors, which could introduce compatibility issues. When a migration of VNFs from such an environment is attempted this could yet again lead to compatibility challenges. As a result consistent performance cannot be assured.

Troubleshooting

Troubleshooting in a next generation network involves correlation of information across various cloud resources. This increases operational costs and makes it challenging for the administrator to correlate information across heterogeneous entities and determine the root cause. For instance, in an NFV deployment while determining the end to end latency could be feasible, the root cause could be the VNF, the platform hosting the VNF or any other component across the network. To narrow down and determine the actual root cause of latency in such an environment could be a challenge.

Service Provisioning

Traditional service provisioning was restricted to the network elements. However in the current scenario service provisioning also extends to VNFs in the cloud. With the different functionalities being spread across both hardware and cloud, service provisioning management system has becomes complex and requires to be overcome with intelligent systems.

NFV provides flexibility in migration of VNF components and this in turn increases the need for service re-provisioning. This is induced not due to changes in service parameters but due to increase in migration across cloud services.

The aforementioned factors mandate specialized monitoring and diagnostics of networks which support NFV capabilities. The diagnostics capabilities should be enabled on-demand during both validation and live deployment. Further, gaining visibility into the network and awareness of the performance levels is of paramount importance. These capabilities ensure that the rising expectations of varied NFV stakeholders are met in a consistent manner. Therefore a solution that is able to monitor and diagnose network service performance across the service lifecycle could be key in facilitating quicker adoption of NFV-based infrastructure.

Veryx’s Solution

Veryx SAMTEST enables service providers to measure various performance metrics, utilizing a combination of physical and virtual probes, diagnose / troubleshoot network issues and provide in-depth visibility into network.

Learn more about Veryx SAMTEST.

About Author

Charanya Balasubramanian is the Product Manager at Veryx Technologies. Charanya handles product management efforts for SDN and emerging technologies at Veryx. She has over five years of experience in the Information and Communication Technologies (ICT) industry spanning across several technologies including virtualization and cloud computing. She holds a Master’s degree in Strategy and Marketing from XLRI, Jamshedpur, India and Bachelor’s Degree in Computer Science and Engineering from Anna University, Chennai, India. Charanya can be reached at charanya.balasubramanian@veryxtech.com.