Shulou(Shulou.com)06/02 Report--

In Windows Server 2016 and Virtual Machine Manager, the end-to-end network virtualization solution provided by Microsoft. There are five main components that make up Microsoft's network virtualization solution:

Windows Azure Windows Server's package provides the creation of a virtual network facing the portal and the management of the portal to manage virtual network tenants.

A centralized management network structure provided by the Virtual Machine Manager (VMM).

Microsoft network controllers provide centralized, programmable point automation to manage, configure, monitor, and resolve the virtual and physical network infrastructure in your data center.

HYPER-V network virtualization provides the infrastructure needed to virtualize network traffic.

The HYPER-V Network Virtualization Gateway provides connectivity between virtual and physical networks.

Function description

Virtual machines are similar to how server virtualization (hypervisors) provides the operating system with "virtual machines" HYPER-V network virtualization to make "virtual networks" (called VM networks). Network virtualization separates virtual networks from the physical network infrastructure and removes VLAN and hierarchical IP address allocation constraints on virtual machine provisioning. This flexibility makes it easy for customers to move to IaaS Yunxia efficient hosts and datacenter administrators to manage their infrastructure while maintaining the necessary multi-tenant isolation, security requirements, and support for overlapping virtual machine IP addresses.

Customers want to seamlessly extend their data centers in the cloud. Such seamless hybrid cloud architectures are currently under way to address technical challenges. One of the major obstacles to customers' faces is to reuse their existing network topologies (individual subnets, IP addresses, network services, etc.). In the cloud and bridge between its local resources and its cloud resources HYPER-V network virtualization provides the concept of basic physical network-independent VM networks. Using one or more virtual subnets on this VM network, the concept separates the exact location of the virtual machine connected to the physical network in the virtual network from the virtual network topology. In this way, customers can easily switch their virtual subnets to the cloud while keeping existing IP addresses and topologies in the cloud so that existing services continue to run on subnets that do not know the physical location. In other words, HYPER-V network virtualization allows you to seamlessly mix clouds.

In addition to hybrid clouds, many organizations have merged their data centers and created dedicated cloud internals to gain the efficiency and scalability benefits of the cloud architecture. HYPER-V network virtualization allows greater flexibility and efficiency for dedicated clouds by separating the enterprise unit (by making virtual) the actual physical network topology from. In this way, business devices are easily shared away from the internal private cloud and the existing network topology continues. Operations data center teams have the flexibility to deploy and dynamically move servers that do not provide better operational efficiency by interrupting datacenter and overall more efficient workloads anywhere in the data center.

A key advantage for workload owners is that they can now move their workload "topology" to the cloud without changing their IP addresses or rewriting their applications. For example, a typical three-tier LOB application consists of the front-end business logic layer and the database layer. Through policy, HYPER-V network virtualization allows customers to load all or part of the three layers of content into the cloud to build, while routing topology and IP address services (that is, virtual machine IP addresses) without the need to change the application.

Greater flexibility in the location of infrastructure owner virtual machines allows workloads to move anywhere in the data center without changing virtual machines or reconfiguring the network. For example, HYPER-V network virtualization enables real-time migration of cross-networks, so that virtual machines can migrate anywhere in real time without service interruption of datacenter. Real-time migration was previously limited to the same subnet virtual machine location limit. Cross-subnet real-time migration allows administrators to consolidate workloads based on dynamic resource requirements, energy increases efficiency, and infrastructure maintenance of workloads that accommodate customer uptime without disrupting them.

Practical application

For the success of virtualized data centers, IT departments and bearer providers (providers also exist or physical server leases) have begun to provide a more flexible virtualized infrastructure to make it easier for them to provide on-demand server instances to their customers. Such new services are called infrastructure as a service (IaaS). Windows Server 2016 provides all the necessary platform features to enable enterprise customers to immediately dedicate Yunxia and convert to an IT as a version of the service operation model. Windows Server 2016 also hosts public clouds and provides IaaS solutions for its customers. When used in conjunction with the virtual machine manager and the Windows Azure package to manage HYPER-V network virtualization strategy, Microsoft will provide a powerful solution in the cloud.

Windows Server 2016 HYPER-V network virtualization provides policy-based, software-controlled network virtualization, reducing the number of companies flying overhead when they deploy a dedicated IaaS cape, and providing cloud hosts with better flexibility and scalability to manage virtual machines to achieve higher versions of resource utilization management.

Virtual machine IaaS scenarios that have been separated from different organizations (private cloud) or different customer (managed cloud) need to be securely isolated. Today's solution, Virtual Local Network (Vlan), can show the larger disadvantages of this solution.

Vlan

Currently, Vlan is used by most organizations to support address space reuse tenant isolation mechanism. VLAN uses explicit tags (VLAN ID) in its Ethernet frame header and it relies on Ethernet switches to enforce isolation and restrict traffic to the same VLAN ID network node with the main disadvantages of Vlan as follows:

Increases the risk of unintentionally interrupting switching due to production hassles when switching virtual machines or isolating restrictions on movement in dynamic data centers.

In terms of scalability limitations, because 4094 Vlan is the most, typical switches support no more than 1000 VLAN Id.

The number of single VLAN nodes in the limit, and the physical location on the virtual machine is based on the location of a single IP child constraint. Even if the Vlan can be extended at the site, the entire VLAN must have the same subnet.

IP address assignment

Vlan has disadvantages, except that there are problems with virtual machine IP address allocation, including:

The physical location of the data center network infrastructure determines the virtual machine IP address. As a result, moving to the cloud usually requires changing the IP address of the service workload.

The policy is closely related to IP addresses, such as firewall rule resource discovery and directory services, and so on. To change the IP address, all associated policies need to be updated.

Virtual machine deployment and traffic isolation depend on the topology.

When data center network administrators plan the physical layout of the datacenter, they must decide where the subnets will be physically placed and routed. These decisions are based on IP and Ethernet technologies that affect a given server or are connected to a specific rack data center where knife-edge running virtual machines allow potential IP addresses. When a virtual machine is preconfigured and placed in the data center, it must comply with these options and restrictions on IP addresses. Therefore, the typical result is the datacenter administrator, assigning the new IP address to the virtual machine.

The problem with this requirement is that there is no semantic IP address and associated information except the current address. For example, a subnet may contain a given service, or it may be in a different physical location. Firewall rules, access control policies, and IPsec security associations are typically associated with the IP address of the program. Changing the IP address forces the virtual machine owner to adjust all policies that are based on the original IP address. When this renumbering flies overhead, many enterprises choose to deploy to the cloud to build, as long as the only new service that leaves the old application is too high.

HYPER-V network virtualization will separate the virtual network of customer virtual machines from the physical network infrastructure. Therefore, it allows the customer virtual machine to maintain its original IP address while allowing the datacenter administrator to preconfigure anywhere in the customer virtual machine data center that does not need to reconfigure the physical IP address or VLAN Id configuration. The next part summarizes the main functions.

Important function

The following is a list of key features, benefits, and features in HYPER-V Network Virtualization Windows Server 2016:

Flexible network isolation of workload locations and reuse of IP addresses without the need for Vlan

HYPER-V network virtualization will separate from the physical network infrastructure host to provide the corresponding free workload in the center of the customer virtual network. The workload location of virtual machines is no longer restricted by IP address allocation or physical network VLAN isolation requirements because it is implemented within the HYPER-V host according to the software definition, tenant virtualization policy.

Virtual machines from overlapping IP addresses and different customers can now be deployed on the same master server without troubling VLAN configuration or violating the IP address hierarchy. This optimizes the migration of customers to shared IaaS hosting providers, enabling customers to maintain these workloads without modification, including virtual machine IP addresses. Hosting service providers that support many customers who want to extend their existing network address space to sharing IaaS datacenter are configured and maintained for each customer to ensure that the potential overlapping address space coexists with independent Vlan complex exercises. Addresses that overlap with HYPER-V network virtualization support become easier to network and require fewer network bearer providers to be reconfigured.

In addition, it does not cause the time under the customer workload to complete the physical infrastructure maintenance and upgrade. "with HYPER-V network virtualization, virtual machines can be migrated on specific hosts, racks, individual subnets, VLAN, or the entire cluster without changing physical IP addresses or major reconfiguration."

Enable a shared IaaS cloud with easy access to workloads

IP addresses and configuration virtual machines remain the same with HYPER-V network virtualization. This makes it easier to move workloads from their data centers to shared IaaS hosting businesses that provide minimal rework of workloads or infrastructure tools and policies IT. In cases where the two data centers are connected, IT administrators can continue to use their tools without having to reconfigure them.

Enable real-time migration between subnets

Virtual machine workload real-time migration tradition changes the IP address of the virtual machine because it has been limited to the guest operating system of the virtual machine required by the same IP child or VLAN cross-network. This address change breaks existing communications and disrupts services running on the virtual machine. Using HYPER-V network virtualization workloads can be migrated to servers in real time without changing the subnets of the workload IP address different subnets running Windows Server 2016 a subnet on a server running Windows Server 2016. HYPER-V network virtualization ensures that virtual machines are updated and synchronized between hosts with continuous communication with the migrated virtual machine due to the location of the live migration.

Make it easier to manage separate servers and network management

The underlying physical network configuration of the migration and workload location simplifies the workload location of the server independently. Server administrators can focus on managing servers, and service and network administrators can focus on the infrastructure and traffic management of the entire network. This enables datacenter server administrators to deploy and migrate virtual machines without changing the IP address of the virtual machines. It reduces overhead when flying overhead because HYPER-V network virtualization allows the location of virtual machines to separate network topologies that can reduce network administrators' exposure to possible changes in isolation limits.

Simplified the network and improved the usage of network resources in the server

The location correlation between the Vlan hardness and the physical network infrastructure on the virtual machine results in overconfiguration and inadequacy. By breaking dependencies, increased flexibility in the workload location of virtual machines can simplify network management and improve server and network resource usage. Note that Vlan is supported in the context of HYPER-V network virtualization physical datacenter. For example, datacenter might want to virtualize traffic for all HYPER-V networks on a particular VLAN.

Existing infrastructure and emerging technologies and compatibility

HYPER-V network virtualization can be deployed in today's datacenter but compatible with emerging datacenter "direct network" technologies.

For example, the Windows Server 2016 HNV supports VXLAN encapsulation format and opens vSwitch Database Management Protocol (OVSDB) as a SouthBound interface (SBI)..

Provides interoperability and ecosystem preparation

HYPER-V network virtualization cross-premise connections, storage area networks (saints), non-virtualized resource access, etc., such as supporting communication in multiple configurations using existing resources. Microsoft is committed to working with ecosystem partners to support and enhance the experience of HYPER-V network virtualization performance, scalability, and manageability.

Policy-based configuration

Configure the network virtualization policy in Windows Server 2016 through the Microsoft network controller. The network controller has rest style northbound API and Windows PowerShell interface configuration strategy.

Software requirements

Using the Microsoft network controller HYPER-V network virtualization requires the Windows Server 2016 and HYPER-V roles.

Welcome to the official account of Wechat: Xiao Wen study Society.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.