Check network virtualization addresses and routing
View network virtualization information and check connectivity between hosts.
November 6, 2015
Q. How can I check the provider address and policy tables when using Network Virtualization on Hyper-V?
A. When using Network Virtualization each node that hosts a VM in a virtual network has a provider address which is used to actually transfer network virtualized traffic. Each node also maintains a policy table which lists the VMs in virtual networks, the VM customer addresses (the IP address in the virtual network of the VM) and the provider address to be used to communicate with the right target host (to then relay the traffic to the VM). All of this detail can be viewed.
To view the provider addresses for a host run the following command:
PS C:> Get-NetVirtualizationProviderAddressProviderAddress : 172.1.1.6InterfaceIndex : 44PrefixLength : 0VlanID : 173AddressState : PreferredMACAddress : 001dd8b71c08ManagedByCluster : FalseProviderAddress : 172.1.1.3InterfaceIndex : 44PrefixLength : 0VlanID : 173AddressState : PreferredMACAddress : 001dd8b71c03ManagedByCluster : False
Note in the above there are two provider addresses for the host because the host is hosting VMs on two different virtual networks. To test connectivity between hosts using the provider addresses use ping -p .
To view the policy table (lookup/routing) use the following:
PS C:> Get-NetVirtualizationLookupRecord | Sort-Object VMName | Format-Table CustomerAddress,VirtualSubnetID,ProviderAddress,VMName -AutoSize CustomerAddress VirtualSubnetID ProviderAddress VMName --------------- --------------- --------------- ------ 192.168.10.4 6864375 172.1.1.3 Blue-VM-1 192.168.10.5 6864375 172.1.1.4 Blue-VM-2 192.168.11.2 6836310 172.1.1.3 Blue-VM-3 192.0.2.253 16200119 172.1.1.6 DHCPExt.sys192.0.2.253 6864375 172.1.1.3 DHCPExt.sys192.0.2.253 6836310 172.1.1.3 DHCPExt.sys192.168.10.1 16200119 1.1.1.1 GW 192.168.11.1 6836310 1.1.1.1 GW 192.168.10.1 6864375 1.1.1.1 GW 192.168.10.2 16200119 172.1.1.6 Red-VM-1
To view all the routing domains (virtual networks) and the subnets in the virtual networks use Get-NetVirtualizationCustomerRoute.
About the Author
You May Also Like