etwork Site Enter IP subnets using CIDR notation, for example: 192.168.1.0/24, FD4A:29CD:184F:3A2C::/64. Remove VLAN Testing_ 0 Host groups that can use this network site: All Hosts Hosts Gateway 20. You will see that the Tenant A Subnet 1 - IP Pool is only linked to the VM Network, which allows subnets to be created within the VM Network without having to change the underlying Logical Network, Logical Network Sites, and provider IP pool. This is software-defined networking. Tenant A Subnet 1 IP Pool Create IP Pool Main Network Properties Host-Management Delete Host-LiveMigration View Dependent Resources Host-Cluster External (NAT) Implementing Network Isolation in Hyper-V Any Virtual Machines created in the VMN-VLAN-Testing_0-150 or VMN-VLAN- Testing_0-151 VM Networks are isolated in that VLAN. Any traffic between those VLANs must traverse the default gateway for those VLANs, which would more than likely be a physical router away from the Hyper-V environment. To add this VLAN to the Standard Uplink Port Profile, which controls the Logical Switches, perform the following steps: 21. Navigate to the Fabric workspace and then click on Port Profiles. Right-click on the Standard UPLINK PORT PROFILE and click on Network Configuration. 22. Click on VLAN-Testing_0 and then click on OK. Select the network sites supported by this uplink port profile Network sites: Network Site Logical Network External (NAT)_0 External (NAT) Host-Cluster_0 Host-Cluster Host-LiveMigration_0 Host-LiveMigration Host-Management_0 Host-Management Provider Address_0 Provider Address VLAN Testing_0 VLAN Testing 23. This tells VMM that the VLANs are now available wherever this uplink port profile is used. 24. To test whether the VLANs are available navigate to the Library workspace; click on VM Templates; right-click on your default VM template, in this case, Windows Server 2012 R2 Standard; and then click on Create Virtual Machine. 25. Navigate through the Create Virtual Machine wizard giving the appropriate information. Use a suitable name, in th