Table of contents
TOC
Collapse the table of content
Expand the table of content

Network Function Virtualization

Vic Horne|Last Updated: 1/25/2017
|
5 Contributors

Applies To: Windows Server 2016

You can use this topic to learn about Network Function Virtualization, which allows you to deploy virtual networking appliances such as Datacenter Firewall, multitenant RAS Gateway, and Software Load Balancing (SLB) multiplexer (MUX).

Note

In addition to this topic, the following Network Function Virtualization documentation is available.

In today's software defined datacenters, network functions that are being performed by hardware appliances (such as load balancers, firewalls, routers, switches, and so on) are increasingly being virtualized as virtual appliances. This "network function virtualization" is a natural progression of server virtualization and network virtualization. Virtual appliances are quickly emerging and creating a brand new market. They continue to generate interest and gain momentum in both virtualization platforms and cloud services.

Microsoft included a standalone gateway as a virtual appliance starting with Windows Server 2012 R2 . For more information, see Windows Server Gateway. Now with Windows Server 2016 Microsoft continues to expand and invest in the network function virtualization market.

Virtual appliance benefits

A virtual appliance is dynamic and easy to change because it is a pre-built, customized virtual machine. It can be one or more virtual machines packaged, updated, and maintained as a unit. Together with software defined networking (SDN), you get the agility and flexibility needed in today's cloud-based infrastructure. For example:

  • SDN presents the network as a pooled and dynamic resource.

  • SDN facilitates tenant isolation.

  • SDN maximizes scale and performance.

  • Virtual appliances enable seamless capacity expansion and workload mobility.

  • Virtual appliances minimize operational complexity.

  • Virtual appliances let customers easily acquire, deploy, and manage pre-integrated solutions.

    • Customers can easily move the virtual appliance anywhere in the cloud.

    • Customers can scale virtual appliances up or down dynamically based on demand.

For more information about Microsoft SDN see Software Defined Networking.

What network functions are being virtualized?

The marketplace for virtualized network functions is growing quickly. The following network functions are being virtualized:

  • Security

    • Firewall

    • Antivirus

    • DDoS (Distributed Denial of Service)

    • IPS/IDS (Intrusion Prevention System/Intrusion Detection System)

  • Application/WAN optimizers

  • Edge

    • Site-to-site gateway

    • L3 gateways

    • Routers

    • Switches

    • NAT

    • Load balancers (not necessarily at the edge)

    • HTTP proxy

Why Microsoft is a great platform for virtual appliances

Virtual network stack

The Microsoft platform has been engineered to be a great platform to build and deploy virtual appliances. Here's why:

  • Microsoft provides key virtualized network functions with Windows Server 2016.

  • You can deploy a virtual appliance from the vendor of your choice.

  • You can deploy, configure, and manage your virtual appliances with the Microsoft Network Controller which comes with Windows Server 2016. For more information about the Network Controller, see Network Controller.

  • Hyper-V can host the top guest operating systems that you need.

Network function virtualization in Windows Server 2016

Virtual appliances functions provided by Microsoft

The following virtual appliances are provided with Windows Server 2016:

Software load balancer

A layer-4 load balancer operating at datacenter scale. This is a similar version of Azure's load balancer that has been deployed at scale in the Azure environment. For more information about the Microsoft Software Load Balancer, see Software Load Balancing (SLB) for SDN. For more information about Microsoft Azure Load Balancing Services, see Microsoft Azure Load Balancing Services.

Gateway. RAS Gateway provides all combinations of the following gateway functions.

  • Site-to-Site gateway

    RAS Gateway provides a Border Gateway Protocol (BGP)-capable, multitenant gateway that allows your tenants to access and manage their resources over site-to-site VPN connections from remote sites, and that allows network traffic flow between virtual resources in the cloud and tenant physical networks. For more information about the RAS Gateway, see RAS Gateway High Availability and RAS Gateway.

  • Forwarding gateway

    RAS Gateway routes traffic between virtual networks and the hosting provider physical network. For example, if tenants create one or more virtual networks, and need access to shared resources on the physical network at the hosting provider, the forwarding gateway can route traffic between the virtual network and the physical network to provide users working on the virtual network with the services that they need. For more information, see RAS Gateway High Availability and RAS Gateway.

  • GRE tunnel gateways

    GRE based tunnels enable connectivity between tenant virtual networks and external networks. Since the GRE protocol is lightweight and support for GRE is available on most network devices, it becomes an ideal choice for tunneling where data encryption is not required. GRE support in Site to Site (S2S) tunnels solves the problem of forwarding between tenant virtual networks and tenant external networks using a multi-tenant gateway. For more information about GRE tunnels, see GRE Tunneling in Windows Server 2016.

Routing control plane with BGP

Hyper-V Network Virtualization (HNV) Routing Control is the logical, centralized entity in the control plane, which carries all the Customer Address plane routes and dynamically learns and then updates the distributed RAS Gateway routers in the virtual network. For more information, see RAS Gateway High Availability and RAS Gateway.

Distributed multi-tenant firewall

The firewall protects the network layer of virtual networks. The policies are enforced at the SDN-vSwitch port of each tenant VM. It protects all traffic flows: east-west and north-south. The policies are pushed through the tenant portal and the Network Controller distributes them to all applicable hosts. For more information about the distributed multi-tenant firewall, see Datacenter Firewall Overview.

© 2017 Microsoft