 
                    
                The idea of network functions virtualization originated with service providers that wanted to make it easier to deploy new network services. Typically, they would have to introduce a wide range of new physical devices for routing, switching, security, WAN optimization, and more just to offer new solutions.
With NFV, you consolidate network functions typically deployed with black boxes onto industry-
standard commercial-off-the-shelf (COTS) servers. We know that it’s getting increasingly 
difficult to introduce new appliances to your physical architecture, so being able to decouple 
network functions from dedicated hardware will become more of a necessity than a luxury 
soon.
At first glance, this might just seem like a small piece of the software-defined networking promise. However, you can start to deploy NFV as a standalone strategy without actually approaching SDN at first.
The key difference is that SDN focuses on separating the data plane from network control logic 
for centralized, automated control over traffic. Network functions virtualization focuses less on 
abstraction and more on the data plane itself, leveraging virtual machines and open source 
software.

Because there is still debate over open source SDN controller technology, NFV may seem more 
approachable as you lay the groundwork for a future 40G/100G data center. Here are just a few 
of the possible use cases for virtualized network functions:
If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool. 
If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link. 
While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline. 
Some of you may have noticed a flaw in the logic behind this solution!  You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.
Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.
Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.
Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.