take a period of time because providers & enterprises are not going to decommission their existing Infrastructure and replace everything by virtualized Individual components as this will be too expensive then. DOI: 10.4018/978-1-5225-3640-6.ch008 Copyright © 2018, IGI Global. Copying or distributing in print or electronic forms without written permission of IGI Global is prohibited. Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 NFV Practical Implementation Figure 1. Changes with NFV with VNFs POWER SUPPLIES PROCESSOR SWITCH FABRIC FAN MODULE FOR EVERY INDIVIDUAL COMPONENTS FIREWALL LOAD BALANCER SWITCHES ROUTERS NO LONGER PHYSICAL TRADITIONAL NETWORK ARCHITECTURE LIMITATIONS Scalability Limitations. Vendor dependent predefined hardware & software components. High operational cost due to the management of Individual hardware within datacenters. More Space & Power Requirements. Individual Hardware management Issues. Huge Capital Expenditure. Limitation in rapidly offering services to the users due to the time to build the infrastructure. Additional hardware to deploy for High Availability. NFV BENEFITS Service Elasticity. Operational Efficiency. Automated Network Operations. Capital Expenditure Reduction. Vendor agnostic. Downloaded 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 NFV Practical Implementation Software Oriented Innovation. Rapid Service Delivery Reduced Space & Power Consumption. Hardware Flexibility Scalability & Multi-tenancy. Reduction of number of network devices management. 12. Reduced complexity for HA (High Availability). 13. Reduction of network elements for deployment and management. NFV ARCHITECTURE AND FRAMEWORK The relevance of NFV framework is to ensure standardization & compatibility between different vendor software pieces of share hardware resources. Virtualized Network Function (VNF) - A software component that replaces the vendor specific hardware to perform the same function on share hardware, eventually reducing t