Address fe80: : f5a2:a1db:d390:e4f5%15 IPv4 Address 192.168.200. 10 Subnet Mask 255.255. 255 0 Default Gateway 192.168.200 - 1 Ethernet adapter Management Connection-specific DNS Suffix ad.demo.com Link-local IPv6 Address fe80::6591:3b3d:669c:550cx14 IPv4 Address 172.28.0.101 Subnet Mask 255.255.0.0 Default Gateway 172.28.0.1 Ethernet adapter TenantNetworks: Connection-specific DNS Suffix Link-local IPv6 Address fe80::c45:790e:6d63:90a8%13 Autoconfiguration IPv4 Address 169.254.144.168 Subnet Mask 255.255.0.0 Default Gateway 50. Return to the VMM console, navigate to Fabric I Networking Network Service, and right-click on the HNVGateway1 entry. Click on Refresh. 51. Right-click on the HNVGateway1 entry again and click on Properties. Click on the new Connectivity option on the left. You will see that the names of the Ethernet adapters have changed, as shown in the following screenshot: Specify the configuration of each network connection and bandwidth that is available for tenants Connectivity Gateways have a front end that is connected to a traditional physical network and a back end that contains the network using network virtualization. Enable front end connection Front end network adapter: External External Front end network site: Management Enable back end connection TenantNetworks Back end network adapter: Back end network site: Host-Cluster_0 (Host-Cluster) Available bandwidth Select the amount of bandwidth that is available for tenants to use on this connection. This value can exceed the physical capabilities of the gateway if you expect the virtual networks to use less than they have requested. Limit bandwidth Available bandwidth (MBps): 10000 Creating the Gateway for Virtual Machine Communications 52. Check the Enable front end connection checkbox, and then set Front end network adapter to External and Front end network site to External (NAT)_0 (External (NAT)). 53. Check the Enable back end connection checkbox, and set the Back end network adapter to TenantNetworks and Back end network site to Provider 