Gadgets
How to Migrate VMware to Hyper-V (7): Plan SCVMM Networking
[ad_1]
SCVMM networking is relatively complex. Starting with Logical Networks, in this section, we’ll plan the deployment of the various elements of a VMM network.
Task 1: Plan SCVMM Logical Networks
In VMM, a logical network is auto-created for all Hyper-V Virtual Switches. However, Network sites and IP Pools are not added automatically.
It is important to mention that VM Networks are also added for every logical network. VM networks are used to connect VMs to the network.
In part 8, we will delete all auto-created VM Networks, except the Mgt-vSwitch (the only network we need to connect our VMs to the primary network with access to the internet).
| Logical Network | Network Site | Host Groups | Associated IP Subnet | VLAN |
|---|---|---|---|---|
| Mgt-vSwitch | Mgt-vSwitch_0 | Hyper-V | 192.168.0.0/24 | NA* |
| Lmg-vSwitch | Lmg-vSwitch_0 | Hyper-V | 192.168.1.0/24 | NA |
| Clu-vSwitch | Mgt-vSwitch_0*** | Hyper-V | 192.168.0.0/24 | NA |
*If you’re deploying this in production, add the VLAN IDs in the VLAN column
**Only the Mgt-vSwitch VMs use requires a network site to be added. By adding a network site, the switch will be listed when we create an uplink port profile
***If the cluster and management (VM Networks) are on the same subnet, use the Mgt-vSwitch_0 Network Site for the cluster, as you cannot create two network sites with the same IP subnet.
Task 2: Plan Virtual Network Adapter Port Profiles
Use the default Virtual Network Adapter Port Profiles created for Live Migration and Cluster Workloads.
| Virtual Port Profile Name | Offload Settings | Security Settings | Bandwidth Settings |
|---|---|---|---|
| Live Migration | Enable Virtual Machine Queue Enable IPSec Task Offloading |
None | Minimum Bandwidth (Mbps): 0 Maximum Bandwidth (Mbps): 0 Minimum Bandwidth (Weight): 40 |
| Cluster | Enable Virtual Machine Queue Enable IPSec Task Offloading |
None | Minimum Bandwidth (Mbps): 0 Maximum Bandwidth (Mbps): 0 Minimum Bandwidth (Weight): 10 |
Task 3: Plan Uplink Port Profiles
We need one uplink port profile that connects the Mgt-vSwitch (used by VMs) to the network. Live Migration and Cluster nets DO NOT require an uplink.
| Uplink Port Profile | Load Balancing Algorithm* | Teaming Mode | Network Configuration |
|---|---|---|---|
| Mgt-vSwitch-uplink | Host Default | Switch Independent | Mgt-vSwitch_0 |
| Lmg-vSwitch-uplink | Host Default | Switch Independent | Lmg-vSwitch_0 |
| Clu-vSwitch-uplink | Host Default | Switch Independent | Mgt-vSwitch_0** |
*Using Host Default allows VMM to use the LBA configured in the Hyper-V Switch – Windows Server 2012 does not support Dynamic Teaming Mode, so using Host Default creates a PP that is compatible with Windows Server 2012 VMs (if we still have them).
**Used the same network switch as the Mgt-vSwitch-uplink for the Clu-vSwitch-uplink if the management (VM traffic) and Cluster traffic workload are on the same VLAN IP subnet
Task 4: Plan Port Classification
Use the default classifications created by VMM “Live Migration Workload,” and “Host Cluster Workload.” These will be used in combination with the Virtual Network Adapter Port Profiles.
| Port Classification | Description |
|---|---|
| Live migration workload | Port classification to be used for host live migration workloads. |
| Host Cluster Workload | Port classification for host cluster workloads. |
Task 5: Plan Logical Switch
The Logical Switch MUST have the same name as the Hyper-V Virtual Switch to allow conversion of the Virtual Switch to a VMM Logical Switch on the Hyper-V hosts.
Beyond that, the Teaming mode and other settings like SR-IOV must also match the Hyper-V SET configuration.
| Logical Switch | Uplink Mode | Settings | Extensions | Virtual Port | Uplinks |
|---|---|---|---|---|---|
| Mgt-vSwitch | Embedded Team | Minimum Bandwidth: None Enable Single Root I/O Virtualization (SR-IOV): checked |
None* | None** | Mgt-vSwitch-uplink |
| Clu-vSwitch | Embedded Team | Minimum Bandwidth: Weight Enable Single Root I/O Virtualization (SR-IOV): unchecked** |
None | Port Classification: Host Cluster Workload Virtual Port Profile: |
Clu-vSwitch-uplink |
| Lmg-vSwitch | Embedded Team | Minimum Bandwidth: Weight Enable Single Root I/O Virtualization (SR-IOV): unchecked** |
None | Port Classification: Live Migration Workload Virtual Port Profile: |
Clu-vSwitch-uplink |
*Extension not required for most configurations
**I am using the Virtual ports to configure the Cluster and Live Migration virtual switches
SR-IOV is not recommended in Cluster and LM switches, which is why it is not enabled in the Clu and LM Hyper-V vSwitches and the table above.
Congratulations! You have completed the VMM networking configuration planning. Before you proceed to part 8 – Setup VMM Networking – ensure you’ve completed the tasks above.
[ad_2]
Victor Ashiedu
Source link
