Blade Server and virtualization for NFV are: Less complex standard hardware Use of lower CapEx Use of lower OpEx Increased flexibility Reduction in risk Availability of open market to software suppliers Less power consumption Testing of new apps Reduced TTM NFV Practices and Recommendations for Network Services Virtualization Though virtualization of network services has featured a lot of advantages, they give rise to some major concerns regarding NFV practices and recommendations as listed below: NFV orchestration evaluates the degradation of individual services/functions resulted due to the introduction of the Ohypervisor and multiple virtualized services on the same physical hardware. It also supervises the hypervisor and host resources to troubleshoot, and hereby resolving the contention of physical resources. Figure 7. NFV using Blade Server and virtualization All Functions in common X86 Architecture All Functions in common X86 Architecture Media Media Router Switch Router Switch Firewall Firewall Server Server Balancer Server Server Balancer Virtual Virtual Virtual Virtual Virtual Virtual Machine Machine Machine Machine Machine Machine Metal Metal Metal Metal Metal Metal Hypervisor Metal X86 Using Blade Server Using Virtualization Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Virtualizing Network Functions in Software-Defined Networks An introduction of hypervisor results into a Single Point of Failure (SPOF) which may affect the working of virtual machines on a host and other defined chains of network services. Hypervisor comprising a virtual switch has the ability to control traffic in order to avoid application failure while serving multiple vNICs of various virtual machines. The hypervisor also provisions the feature of management awareness that distributes and isolate the applications when the failure of a physical machine state like NIC port takes place. Moreover, the management awareness by hypervisor is bridged by SDN controller and Orchestration cooperation.