This topic provides information about supported and unsupported scenarios that you can or cannot perform with this release of Windows Server 2016.
Важно
For all production scenarios, use the latest signed hardware drivers from your original equipment manufacturer (OEM) or independent hardware vendor (IHV).
Supported Networking Scenarios
This section includes information about the supported networking scenarios for Windows Server 2016, and includes the following scenario categories.
Deploy and use a software load balancer to distribute both northbound and southbound traffic.
Deploy and use a software load balancer to distribute eastbound and westbound traffic for virtual networks created with Hyper-V Network Virtualization.
Deploy and use a NAT software load balancer for virtual networks created with Hyper-V Network Virtualization.
Deploy and use a Layer 3 forwarding gateway
Deploy and use a virtual private network (VPN) gateway for site-to-site IPsec (IKEv2) tunnels
Deploy and use a Generic Routing Encapsulation (GRE) gateway.
Deploy and configure dynamic routing and transit routing between sites using Border Gateway Protocol (BGP).
Configure M+N redundancy for Layer 3 and site-to-site gateways, and for BGP routing.
Use Network Controller to specify ACLs on virtual networks and network interfaces.
For the scenarios in this section the Windows Server Networking team supports the use of any Windows Server 2016 certified driver. Please check with your network interface card (NIC) manufacturer to ensure you have the most recent driver updates.
The network platform scenarios allow you to:
Use a converged NIC to combine both RDMA and Ethernet traffic using a single network adapter.
Create a low-latency data path by using Packet Direct, enabled in the Hyper-V Virtual Switch, and a single network adapter.
Configure SET to spread SMB Direct and RDMA traffic flows between up to two network adapters.
Add network adapters to the NIC team in a supported configuration
Remove network adapters from the NIC team
Бележка
In Windows Server 2016, you can use NIC Teaming in Hyper-V, however in some cases Virtual Machine Queues (VMQ) might not automatically enable on the underlying network adapters when you create a NIC Team. If this occurs, you can use the following Windows PowerShell command to ensure that VMQ is enabled on the NIC team member adapters: Set-NetAdapterVmq -Name <NetworkAdapterName> -Enable
Switch Embedded Teaming (SET) scenarios
SET is an alternative NIC Teaming solution that you can use in environments that include Hyper-V and the Software Defined Networking (SDN) stack in Windows Server 2016. SET integrates some NIC Teaming functionality into the Hyper-V Virtual Switch.
Присъединете се към най-доброто виртуално събитие на Windows Server от 29 до 30 април за задълбочени технически сесии и въпроси и отговори на живо с инженери на Microsoft.
In this learning path, you’ll learn about Azure IaaS networking and identity. After completing the learning path, you’ll be able to implement IP addressing, manage DNS, and deploy and manage domain controllers in Azure.
This topic provides an overview of the Core Network Guide, which allows you to plan and deploy the core components required for a fully functioning network and a new Active Directory domain in a new forest with Windows Server 2016
This guide provides instructions on how to plan and deploy the core components required for a fully functioning network and a new Active Directory domain in a new forest with Windows Server 2016
You can use this topic to learn about Network Function Virtualization, which allows you to deploy virtual networking appliances like Datacenter Firewall, multitenant RAS Gateway, and Software Load Balancing (SLB) in Windows Server 2019 and 2016.
This topic provides instructions on using Windows PowerShell to deploy Network Controller on one or more computers or virtual machines (VMs) that are running Windows Server 2019 or 2016.