New-SCVirtualNetwork

Syntax

New-SCVirtualNetwork
   -LogicalNetwork <LogicalNetwork[]>
   [-Name] <String>
   [-Description <String>]
   [-HostBoundVLanId <UInt16>]
   -JobGroup <Guid>
   [-BoundToVMHost <Boolean>]
   [-RunAsynchronously]
   [-PROTipID <Guid>]
   [-JobVariable <String>]
   [<CommonParameters>]

New-SCVirtualNetwork
   -VMHost <Host>
   [-Name] <String>
   [-Description <String>]
   [-HostBoundVLanId <UInt16>]
   [-JobGroup <Guid>]
   [-BoundToVMHost <Boolean>]
   [-VMHostNetworkAdapters <HostNetworkAdapter[]>]
   [-RunAsynchronously]
   [-PROTipID <Guid>]
   [-JobVariable <String>]
   [<CommonParameters>]

New-SCVirtualNetwork
   -VMHost <Host>
   [-ManagementAdapterName <String>]
   [-ManagementAdapterVLanId <UInt16>]
   [-ManagementAdapterVMNetwork <VMNetwork>]
   [-ManagementAdapterVMSubnet <VMSubnet>]
   [-ManagementAdapterPortClassification <PortClassification>]
   [-UseExplicitIPConfigurationForManagementAdapter <Boolean>]
   [-ManagementAdapterIPv4AddressType <EthernetAddressType>]
   [-ManagementAdapterIPv6AddressType <EthernetAddressType>]
   [-Description <String>]
   -LogicalSwitch <LogicalSwitch>
   [-JobGroup <Guid>]
   [-VMHostNetworkAdapters <HostNetworkAdapter[]>]
   [-CreateManagementAdapter]
   [-ManagementAdapterIPv4AddressPool <StaticIPAddressPool>]
   [-ManagementAdapterIPv6AddressPool <StaticIPAddressPool>]
   [-RunAsynchronously]
   [-PROTipID <Guid>]
   [-JobVariable <String>]
   [<CommonParameters>]

New-SCVirtualNetwork
   -VMHost <Host>
   [-Description <String>]
   -LogicalSwitch <LogicalSwitch>
   [-JobGroup <Guid>]
   [-VMHostNetworkAdapters <HostNetworkAdapter[]>]
   [-DeployVirtualNetworkAdapters]
   [-RunAsynchronously]
   [-PROTipID <Guid>]
   [-JobVariable <String>]
   [<CommonParameters>]

New-SCVirtualNetwork
   -VMHostCluster <HostCluster>
   -LogicalNetwork <LogicalNetwork[]>
   [-Name] <String>
   [-Description <String>]
   [-HostBoundVLanId <UInt16>]
   [-JobGroup <Guid>]
   [-BoundToVMHost <Boolean>]
   [-RunAsynchronously]
   [-PROTipID <Guid>]
   [-JobVariable <String>]
   [<CommonParameters>]

Description

The New-SCVirtualNetwork cmdlet creates a virtual network on a host managed by Virtual Machine Manager (VMM) over which virtual machines on that host can communicate.

System Center 2019 - VMM supports the use of virtual switches to implement virtual networking scenarios for Hyper-V and Citrix XenServer hosts. You can connect, or bind, virtual machines and hosts to a virtual network switch in a manner similar to the way that you connect physical computers to a physical network switch.

For Hyper-V hosts, and the virtual machines deployed on these hosts, VMM also supports the use of virtual switches to implement virtual local area networks (VLANs). A VLAN is an independent logical virtual network configured within a physical LAN. If you create multiple VLANs on a physical LAN, these separate logical segments cannot exchange data with each other.

For XenServer hosts, all virtual switches attached to a single network adapter on a XenServer host are represented as a single virtual network within VMM.

In VMM for System Center 2019 , you can easily move a virtual machine that is connected to a VLAN from one host to another host and (assuming that both hosts are connected to the same VLAN), the virtual machine in its new location is already configured to resume communicating over the VLAN without any additional administrator effort. Moving a virtual machine to a new location on a VLAN does not require software reconfiguration in the way that moving a physical computer to a new location on a physical network requires hardware reconfiguration.

VMM for System Center 2019 Networking Scenarios

The following three scenarios summarize VMM for System Center 2019 virtual networking configurations.

Scenario 1: External Virtual Network

In this scenario, virtual machines deployed on a host use a virtual network adapter to connect to a virtual switch on the host, and this virtual switch is, in turn, connected to a physical network adapter on the host. The host is connected through a physical switch to other computers on its network. This configuration gives the virtual machines access to the host itself, to the physical network to which the host is connected, and to other physical computers (or other physical devices) that are on the same physical network as the host.

The virtual network can support external access though a VLAN if the physical adapter on the host that it is bound to has been configured appropriately and if the virtual machines on that host are configured to use a VLAN. For more information, type Get-Help Add-SCVMHostNetworkAdapter -Detailed, or Get-Help New-SCVirtualNetworkAdapter -Detailed.

Scenario 2: Internal Virtual Network

In this scenario, virtual machines deployed on a host use a virtual network adapter to connect to a virtual switch on the host. In this scenario, the virtual network is bound to the host but the virtual machines do not connect via the virtual switch to a physical network adapter on the host. This configuration establishes an internal virtual network that enables virtual machines connected to that virtual switch to communicate with each other and with services and applications on the host, but not with other computers connected to the host's physical network.

If you want to to configure an internal network that is separated into two or more VLANs, you must set the VLAN IDs on a virtual network adapter configured on the virtual machine object. For more information, type Get-Help New-SCVirtualNetworkAdapter -Detailed, Get-Help Set-SCVirtualNetworkAdapter -Detailed, or Get-Help Set-SCVMHostNetworkAdapter -Detailed.

Scenario 3: Private Virtual Network

In this scenario, virtual machines deployed on a host use a virtual network adapter to connect to a virtual switch on the host. As in scenario 2, a virtual machine does not connect via that virtual switch to a physical network adapter on the host. Unlike scenario 2, the virtual network is not bound to the host. This configuration establishes a private virtual network that virtual machines on the same host can use to communicate with each other, but, in this case, they cannot communicate with services or applications on the host or with any physical computers connected to the host's physical network.

Examples

Example 1: Create an external virtual network on a host

PS C:\> $VMHost = Get-SCVMHost -ComputerName "VMHost01.Contoso.com"
PS C:\> $HostAdapter = Get-SCVMHostNetworkAdapter -VMHost $VMHost -Name "HostLANAdapter01"
PS C:\> New-SCVirtualNetwork -Name "ExternalVirtualNetwork01" -VMHost $VMHost -VMHostNetworkAdapter $HostAdapter

The first command gets the host object named VMHost01 and stores the object in the $VMHost variable.

The second command gets the physical host network adapter object named HostLANAdapter01 on VMHost01 and stores the object in the $HostAdapter variable.

The third command creates a virtual network on VMHost01 named ExternalVirtualNetwork01, and connects the new virtual network to the host network adapter HostLANAdapter01.

This virtual network is an external virtual network. It is attached to the physical network adapter on the host and can therefore access the LAN that the host is attached to as if it were another physical computer on that LAN.

Example 2: Create an internal host-bound virtual network

PS C:\> $VMHost = Get-SCVMHost -ComputerName "VMHost01.Contoso.com"
PS C:\> New-SCVirtualNetwork -VMHost $VMHost -Name "InternalVNet01" -Description "Internal Host-Bound Virtual Network" -BoundToVMHost $True

The first command gets the host object VMHost01 and stores the object in the $VMHost variable.

The second command creates a virtual network on VMHost01, names it InternalVNet01, specifies a description and tag, and binds the virtual network to the physical host.

This virtual network is an internal, host-bound virtual network. Because it is not attached to a physical network adapter on the host, it cannot access networks external to the host. Virtual machines that are connected to this internal virtual network on this host can communicate only with each other. Because the network is bound to the host, network communication from virtual machines to the host is also possible.

Example 3: Create a private virtual network that is not bound to the host

PS C:\> $VMHost = Get-SCVMHost -ComputerName "VMHost01.Contoso.com"
PS C:\> New-SCVirtualNetwork -Name "UnboundVirtualNetwork01" -VMHost $VMHost

The first command gets the host object named VMHost01 and stores the object in the $VMHost variable.

The second command creates a virtual network on VMHost01 named UnboundVirtualNetwork01.

Because the network is not attached to a physical network adapter on the host, it cannot access networks external to the host. Virtual machines that are connected to this internal virtual network on this host can communicate only with each other. Because the virtual network is not bound to the host, network communication to the host is not possible.

Parameters

-BoundToVMHost

-CreateManagementAdapter

-DeployVirtualNetworkAdapters

-Description

-HostBoundVLanId

-JobGroup

-JobVariable

-LogicalNetwork

-LogicalSwitch

-ManagementAdapterIPv4AddressPool

-ManagementAdapterIPv4AddressType

-ManagementAdapterIPv6AddressPool

-ManagementAdapterIPv6AddressType

-ManagementAdapterName

-ManagementAdapterPortClassification

-ManagementAdapterVLanId

-ManagementAdapterVMNetwork

-ManagementAdapterVMSubnet

-Name

-PROTipID

-RunAsynchronously

-UseExplicitIPConfigurationForManagementAdapter

-VMHost

-VMHostCluster

-VMHostNetworkAdapters

Outputs

VirtualNetwork

This cmdlet returns a VirtualNetwork object.

Related Links

• Get-SCVirtualNetwork
• Get-SCVMHost
• Get-SCVMHostNetworkAdapter
• Remove-SCVirtualNetwork
• Repair-SCVirtualNetwork
• Set-SCVirtualNetwork