Virtual Machine Manager 2012 R2 basic network configuration steps 1/2

This blog post describes how to configure basic fabric network to Virtual Machine Manager 2012 R2. We are going to create two different host group. One for Management cluster and one for Tenant cluster. 
Both groups will be have Hyper-V cluster which will be managed by VMM.

In this case we will have Management network as native and all other networks as trunk.

Let´s first do some basic modifications to VMM. Start VMM console and login

Go to Settings -> Network -> unticle “create logical Networks automatically”. It´s better to manage logical networks manually.

Let´s create Host Groups for Management and Tenant. Go to Fabric -> Servers -> Create Host Group (and create needed host groups)


Next we will start to create logical networks. We will have own logical networks for following purposes:

Management (for management network) VLAN 0
Cluster (for cluster communication) VLAN 10
Live-Migration (for VM live-migrations) VLAN 11
PA (For provider Address network which is used on network virtualization if needed) VLAN 300
(and if you are using SMB storage, create one for that too)

Go to Fabric -> Networking -> Logical Networks and choose “Create Logical Network”

Let´s start from Management network. Choose One Connected network and “Create a VM network..” (of course you can create VM network manually if you want)



Then create site for Management and add network details. I will choose both host groups, because Tenant host clusters are going to use same management network

And we are done for creating Management logical network. Repeat same steps for Live-Migration and Cluster network

Next move on to PA network. As we are using this for Provider Address network we need to enable network virtualization (we don´t need VM network for this one)


Now we have all needed networks for Windows Azure Pack installation.
We need to create IP Pool at least for PA network

Add name and ensure that correct logical network is selected

Use earlier created site

Add IP range

All other settings you can leave empty when creating PA IP pool.

Now we have all needed logical networks and IP Pool for PA network. I suggest to configure IP Pool at least Cluster and Live-Migration networks. It´s much more easier to configure Hyper-V hosts when VMM handles IP addresses of those networks.

In next blog post I will show how to configure Switches, port profiles and virtual networks.


Common question is also how to add your own networks if you are not using network virtualisation for all VMs and it´s quite simple too. Let me give a example.
We will have VLAN 101 and VLAN 102 for production.
We are going to run VMs on Tenant cluster, because Management cluster is for WAP and other Management VMs.

Let´s create Logical network Production. We need to use VLAN-Based settings, because we are using different VLANs from this logical network


Then we create Site for Production networks and add them there. If you want to create different sites per for example Infra and SAP you can do it easily too.


Now we are also able to use basic VLANs from tenant host group. Only thing which is needed is virtual networks for both VLANs. This is described on next post.

Next blogpost can be found HERE



4 thoughts on “Virtual Machine Manager 2012 R2 basic network configuration steps 1/2

  1. Thanks Tomi for this very useful walk through. Hoping to see your part 2 of the post with VLAN config. Thanks.

    — Badar

  2. Hi,
    Great article and simple to follow. Just a few questions as im new to VMM.

    Do i use the management network for host domain traffic?

Leave a Reply

Your email address will not be published. Required fields are marked *