Tuesday, February 16, 2016

What true NFV means?

When talking about Network Function Virtualization, it is important to differentiate between true NFV solutions and traditional server-virtualisation techniques, where someone has to care for each virtualised server and their configurations. If the NFV concept is limited to managing a farm of virtual servers manually, many benefits of NFV are missed.

In a true NFV, such as any of the Radiator VNF solutions, VNF manager does the scaling and configuration of virtual servers automatically. For example, in our vAAA solution the VNF manager monitors the RADIUS and Diameter traffic distributed by load balancers and launches new AAA workers automatically to meet the workload. In addition to launching new workers,  all the new instances in the cloud are configured automatically by using the centralised configuration management service. Configuration management uses metadata services to automatically create configuration for the current cloud setup. External connection parameters can be pre-configured and/or configured via NETCONF by OSS/BSS.

Arch-Red-Radiator-A-True-NFV-Solution-Markerwizards-10.png

This kind of scaling is needed, for example, when all end user devices authenticate to the network at the same time. This may happen during rush hours, major public events or when things like sudden power failures happen. When the new AAA workers are not needed, the NFV manager shuts them down automatically – without any manual action or configuration.

Arch-Red-Radiator-A-True-NFV-Solution-Markerwizards-11.png

This automatic scaling and configuration is essential for network function virtualisation. It enables easier workload for your engineering staff – and gives you all the benefits of true NFV solutions. For more info, please see our NFV site or contact info@open.com.au

No comments:

Post a Comment