Download Implementing a Software-Defined Datacenter.70-745.Prep4Sure.2018-11-09.30q.tqb

References:https://blogs.technet.microsoft.com/larryexchange/2016/05/31/step-by-step-for-deploying-a-sdnv2-using-vmm-part-3/

When you install VMM you need to configure the VMM service to use either the Local System account or a domain account. If you specify a domain account, the account must be a member of the local Administrators group on the computer. References:https://docs.microsoft.com/en-us/system-center/vmm/plan-install?view=sc-vmm-1801#account-and-domain-requirements

To create a logical network 1. Open the Fabric workspace. 2. On the Home tab, in the Show group, click Fabric Resources. 3. In the Fabric pane, expand Networking, and then click Logical Networks. 4. On the Home tab, in the Create group, click Create Logical Network. The Create Logical Network Wizard opens. 5. On the Name page, do the following:* Enter a name and optional description for the logical network. For example, enter the name BACKEND, with the description Corporate network. Use for internal servers such as application and database servers. * If you have System Center 2012 SP1 or System Center 2012 R2, select check boxes as appropriate by using the table that follows. Otherwise, skip to the next numbered step in this procedure. Select one or more check boxes based on how you intend to use the VM networks that will be configured on top of this logical network. The following table provides guidelines:6. Click Next. 7. On the Network Site page, take the following steps. Note For guidelines for configuring network sites, see “Network sites” in Configuring Logical Networking in VMM Overview. If you do not need to configure network sites, on the Network Site page, click Next, and then click Finish to complete the wizard. 1. To create a network site, click Add. VMM automatically generates a site name that consists of the logical network name, followed by an underscore and a number. 2. Review the network site name and ensure that it is no longer than 64 characters. To change the default name, in the Network site name box, enter a new name for the network site. For example, enter the name BACKEND - Seattle. 3. Under Host groups that can use this network site, select the check box next to each host group to which you want to make the logical network available. For example, to make the BACKEND logical network available to the Seattle host group and all its child host groups, select the check box next to Seattle. 4. Under Associated VLANs and IP subnets, enter the VLANs and IP subnets that you want to assign to the network site. To enter VLAN and IP subnet information, click Insert row, click the field under VLAN or IP subnet, depending on what you want to configure, and then enter a VLAN, an IP subnet, or a subnet/VLAN pair. You can insert multiple rows. For example, add the IP subnet/VLAN pair that makes up the example BACKEND network in Seattle, as shown in the following table. Important In your test environment, make sure that you use VLANs and IP subnets that are available in your network. 5. Optionally, create additional network sites by clicking Add and repeating the process. 6. When you complete this step, click Next. 8. On the Summary page, review the settings, and then click Finish. The Jobs dialog box appears. Make sure the job has a status of Completed, and then close the dialog box. 9. Verify that the logical network appears in the Logical Networks and IP Pools pane. Also, if you added network sites, right-click the logical network, click Properties, click the Network Site tab, and verify that the intended network sites appear on the tab. References:https://technet.microsoft.com/en-us/library/gg610588(v=sc.12).aspx

References:https://docs.microsoft.com/en-us/system-center/vmm/hyper-v-rolling-upgrade?view=sc-vmm-1807

You can use System Center to deploy SLB MUXs and to install SLB Host Agents on computers that are running Windows Server 2016 Technical Preview and Hyper-V. When you deploy SLB, you must use System Center, Windows PowerShell, or another management application to deploy the SLB Host Agent on every Hyper-V host computer. References:https://technet.microsoft.com/en-US/library/mt632286.aspx

An HTTP health probe should return a response code of 200 to indicate a healthy status. References:https://docs.microsoft.com/en-us/windows-server/networking/sdn/manage/configure-slb-and-nat

References:https://docs.microsoft.com/en-us/windows-server/networking/sdn/manage/configure-slb-and-nat

A Hyper-V extensible switch filtering extension can inspect, modify, and insert packets into the extensible switch data path. Based on extensible switch port and switch policy settings, the extension can drop a packet or exclude its delivery to one or more destination ports. A forwarding extension has the same capabilities as a filtering extension, but is responsible for performing the core packet forwarding and filtering tasks of the extensible switch. References:https://docs.microsoft.com/en-us/windows-hardware/drivers/network/overview-of-the-hyper-v-extensible-switch

You can view reports in the Reporting workspace in System Center Operations Manager, or by using a web browser and entering this address: http://ReportingServerName:port/reports.References:https://docs.microsoft.com/en-us/system-center/vmm/monitor?view=sc-vmm-1801