Hyper-V Network Virtualization (HNV)
Server virtualization enables multiple server instances to run concurrently on a single physical host. Each virtual machine essentially operates as if it is the only server running on the physical computer.
Network virtualization provides a similar capability, in which multiple virtual networks (potentially with overlapping IP addresses) run on the same physical network infrastructure and each virtual network operates as if it is the only virtual network running on the shared network infrastructure.
virtualization rules also define routing topology between the networks
- Customer Address Rule (New-NetVirtualizationLookupRecord):
This rule defines the mapping for a VM (CA). For each VM CA (defined by VirtualSubnetID, CA, and MAC), the corresponding PA and virtualization mechanism are specified by the rule.
- Customer Route (Net-VirtualizationCustomerRoute):
It defines the customer VM subnet topology and forwarding rules. For each customer destination prefix (defined by VirtualSubnetID, RoutingDomainID, and destination prefix), the rule specifies the corresponding next hop gateway address — The RoutingDomainID specifies the subnets that are routable/reachable from each other. Each VirtualSubnetID MUST belong to one and only one RoutingDomainID. Each RoutingDomainID can contain one or more VirtualSubnetIDs.
- Provider Address Rule (Net-VirtualizationProviderAddress):
This rule defines the Provider Addresses (hyper-V host) assigned on the corresponding host for VM CA’s. If a VM on a host is mapped to PA-1, PA-1 MUST be assigned on the SDN module using this rule. This rule tells the virtualization module that a specific PA is assigned on the host, and the virtualization module can use the PA to send packets, and MUST receive packets destined to the PA.
- Provider Route Rule (Net-VirtualizationProviderRoute):Defines the PA forwarding rules and next hop gateways so the virtualization module knows how to send PA packets