NFV — Network Function Virtualization

Overview

NFV decouples network functions (firewalls, load balancers, routers) from dedicated hardware appliances, running them as software on commodity servers. This reduces costs, increases flexibility, and enables rapid service deployment.

Traditional vs NFV Architecture

graph TD
    subgraph "Traditional (Hardware)"
        T1[Firewall Appliance]
        T2[Load Balancer Appliance]
        T3[Router Appliance]
        T4[WAN Optimizer Appliance]
    end
    subgraph "NFV (Software on Commodity Hardware)"
        H[Commodity Server / x86]
        V1[Virtual Firewall]
        V2[Virtual Load Balancer]
        V3[Virtual Router]
        V4[Virtual WAN Optimizer]
        H --> V1
        H --> V2
        H --> V3
        H --> V4
    end

NFV Architecture (ETSI Framework)

graph TD
    subgraph "OSS/BSS"
        OSS[Operations Support]
    end
    subgraph "NFV Management & Orchestration (MANO)"
        NFVO[NFV Orchestrator]
        VNFManager[VNF Manager]
        VIM[VIM<br>Virtual Infrastructure Manager]
    end
    subgraph "NFV Infrastructure (NFVI)"
        Compute[Compute]
        Storage[Storage]
        Network[Network]
        Hypervisor[Hypervisor / Container Runtime]
    end
    subgraph "Virtual Network Functions (VNFs)"
        VNF1[vFirewall]
        VNF2[vLoadBalancer]
        VNF3[vRouter]
    end
    OSS --> NFVO
    NFVO --> VNFManager
    NFVO --> VIM
    VNFManager --> VNF1
    VNFManager --> VNF2
    VNFManager --> VNF3
    VIM --> Compute
    VIM --> Storage
    VIM --> Network
    VNF1 --> Hypervisor
    VNF2 --> Hypervisor
    VNF3 --> Hypervisor

NFV Components

VNF (Virtual Network Function)

A VNF is a software implementation of a network function:

graph LR
    subgraph "Traditional Hardware"
        FW[Physical Firewall<br>$50,000]
        LB[Physical LB<br>$30,000]
        R[Physical Router<br>$20,000]
    end
    subgraph "VNFs on x86 Server"
        VFW[vFirewall<br>Software]
        VLB[vLoadBalancer<br>Software]
        VR[vRouter<br>Software]
    end

Common VNFs

Service Function Chaining (SFC)

NFV enables dynamic service chains — ordered sequences of VNFs:

graph LR
    IN[Traffic In] --> FW[vFirewall]
    FW --> LB[vLoad Balancer]
    LB --> IDS[vIDS]
    IDS --> WAF[vWAF]
    WAF --> APP[Application]

Traditional: Traffic must pass through physical appliances in a fixed order. NFV: Service chains are defined in software and can be changed dynamically.

NFV vs SDN

graph TD
    SDN[SDN<br>Centralized Control] --> NFV[NFV<br>Virtualized Functions]
    SDN -->|Controls| SWITCHES[Physical Switches]
    NFV -->|Runs on| SERVERS[Commodity Servers]
    SDN -->|Programs| NFV

NFV Benefits

NFV Challenges

Containerized Network Functions (CNF)

Modern NFV is moving from VMs to containers:

graph TD
    subgraph "Traditional VNF"
        VM[Virtual Machine]
        VNF1[VNF Application]
        GuestOS[Guest OS]
        VM --> GuestOS --> VNF1
    end
    subgraph "Cloud-Native CNF"
        POD[Kubernetes Pod]
        CNF[CNF Application]
        POD --> CNF
    end

Interview Questions

1. Q: What is NFV? A: Network Function Virtualization runs network functions (firewalls, load balancers, routers) as software on commodity hardware instead of dedicated appliances. Benefits: cost reduction, rapid deployment, scalability, vendor independence.

2. Q: What is a VNF? A: A Virtual Network Function — a software implementation of a network function running on NFVI. Examples: vFirewall, vLoadBalancer, vRouter. Multiple VNFs can run on the same server.

3. Q: What’s the difference between NFV and SDN? A: NFV virtualizes network functions (runs them as software). SDN separates control and data planes (centralized control). They’re complementary: SDN can control the network that NFV functions run on.

4. Q: What is MANO in NFV? A: Management and Orchestration — the ETSI framework for managing NFV. Components: NFVO (orchestration), VNFM (VNF lifecycle), VIM (infrastructure management). Handles deployment, scaling, healing, and termination of VNFs.

5. Q: What is service function chaining? A: An ordered sequence of network functions that traffic must traverse. Example: firewall → load balancer → WAF → application. NFV enables dynamic chaining in software, rather than fixed physical appliance order.

6. Q: What are CNFs? A: Containerized Network Functions — VNFs running in containers instead of VMs. They start faster (seconds vs minutes), use less resources, and integrate with Kubernetes for orchestration. The evolution of NFV toward cloud-native.

Common Mistakes

• Confusing NFV (virtualize functions) with SDN (separate control/data plane)
• Assuming NFV means no hardware (you still need servers)
• Not understanding the MANO framework
• Forgetting that VNFs can have performance overhead vs dedicated hardware
• Not considering that containerized NFVs (CNFs) are the modern approach

Summary

NFV virtualizes network functions, running them as software on commodity hardware. The ETSI MANO framework manages VNFs. Service function chaining enables dynamic traffic paths. CNFs (containerized) are the modern evolution. NFV and SDN are complementary technologies.

Cross-References

• Wireless Overview
• SDN — Complementary technology
• 5G — 5G core uses NFV
• Firewalls — vFirewall example
• Load Balancing — vLoadBalancer example

Cross References

• SDN
• Cloud Virtualization
• Distributed Microservices