Get-CustomerRoute: Routing information
Get-PACAMapping: Mapping between PA and CA
Get-ProviderAddress: Information about provider addresses
Test-VirtualNetworkConnection: Perform a test to a virtual network.There are many others. Use (Get-Module HNVDiagnostics).ExportedCommands to see a
full list.
SYSTEM CENTER VIRTUAL MACHINE MANAGER
The core logical network, logical switch, VM network, and other fabric components are
all used for the SCVMM deployment of SDNv2, and they have a step-by-step guide for
the following:
Deployment of Network Controller and the basic virtual networks:
https://technet.microsoft.com/system-center-docs/vmm/Manage/Deploy-a-
Network-Controller-using-VMM
Deployment of SLB: https://technet.microsoft.com/en-us/system-center-
docs/vmm/manage/deploy-a-software-load-balancer-using-vmm:
Deployment of gateway: https://technet.microsoft.com/system-center-
docs/vmm/Manage/Deploy-a-RAS-Gateway-using-VMMYou need to provide a VM template, which should be Windows Server 2016
Datacenter, and can be either Server Core or Server with Desktop Experience. Where
possible, I recommend using Server Core.
These deployments are all facilitated through the use of service templates, which are
available for download from GitHub
(https://github.com/Microsoft/SDN/tree/master/VMM/Templates/NC) and require
only minimal configuration to have multi-instance deployments of all of the services
in your environment. As part of the deployment, additional logical networks are
created in addition to the management logical network that exists as a foundation to
provide connectivity between the hosts and the Network Controller. The additional
logical networks, documented in the deployment guide, are as follows:
HNV Provider Virtual Network Network used by hosts to communicate the
encapsulated virtual traffic. This network is enabled for VM networks to be created
using network virtualization. This requires an IP pool of PA addresses that will be
used by the Hyper-V hosts. Once created and deployed, VM networks will be
created using their own abstracted, isolated address spaces.
Transit Network Used by the SLB deployments, and it is used for BGP peering
and North/South traffic between the MUX and the upstream router (data plane).
This network is documented in the SLB deployment guide. It is possible to use the
management network if desired.
Private and Public VIP Networks Used for the frontend configuration of SLB