Had a few queries from clients and colleagues who get confused on the workflow for creating a Logical Switch and Port Profile.
This quick post is to just run through that process. More info on the design decisions around Logical Network Definitions Host Groups etc. can be found here.
This walks through making a Port Profile, Creating a Logical Switch and defining Virtual Network Adapters to build a converged network adapter on your hosts.
In SCVMM we have to create an Hyper-V Port Profile
Select Uplink port profile
Select the logical network definitions available to the profile
Or use PoSH with out-gridview to select the Network Definitions you want to assign to the Port Profile
$definition = Get-SCLogicalNetworkDefinition | ogv –passthru New-SCNativeUplinkPortProfile -Name "Uplink-CNA" ` -Description "Demo uplink with SI" ` -LogicalNetworkDefinition $definition ` -EnableNetworkVirtualization $false ` -LBFOLoadBalancingAlgorithm "HyperVPort" ` -LBFOTeamMode "SwitchIndependent" -RunAsynchronously
Add the uplink profile to a Logical Switch or create a Logical Switch for it..
Name your switch and choose your uplink mode.
Here are the 3 choices we have here. For this demo we are using Embedded Team.
Add an existing Hyper-V Port Profile and build you vNICs.
Build the instance of a Logical Switch on a host and use the port profile
tip: Think of a Logical Switch in SCVMM as a vSwitch and/or Converged Network Adapter template
Select the Logical Switch you want to use.
Obviously in normal circumstances you would use more than 1 NIC for the team, but for the demo this will do.
Review the steps taken by VMM in the jobs log – I always recommend doing this for new SCVMM admins
When the job completes, review the new Virtual Switch settings of the host.
Any virtual NICs defined in the Logical Switch uplink will be created.
Log on to the host we can see the vNICs in sconfig
Or via PoSH – Get-NetAdapter
And last take a look using Get-VMNetworkAdapter –ManagementOS
Much more to consider but this should at least get you going..