Merge pull request #50587 from MikeRayMSFT/20180830-UpdateTutorial

Update the load balancer tutorial to clarify WSFC IP address settings.

Author: rmca14

articles/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-availability-group-tutorial.md

@@ -42,7 +42,7 @@ The following table lists the prerequisites that you need to complete before sta
 |![Square](./media/virtual-machines-windows-portal-sql-availability-group-tutorial/square.png)| Windows Server | File share for cluster witness |  
 |![Square](./media/virtual-machines-windows-portal-sql-availability-group-tutorial/square.png)|SQL Server service account | Domain account |
 |![Square](./media/virtual-machines-windows-portal-sql-availability-group-tutorial/square.png)|SQL Server Agent service account | Domain account |  
-|![Square](./media/virtual-machines-windows-portal-sql-availability-group-tutorial/square.png)|Firewall ports open | - SQL Server: **1433** for default instance <br/> - Database mirroring endpoint: **5022** or any available port <br/> - Azure load balancer probe: **59999** or any available port |
+|![Square](./media/virtual-machines-windows-portal-sql-availability-group-tutorial/square.png)|Firewall ports open | - SQL Server: **1433** for default instance <br/> - Database mirroring endpoint: **5022** or any available port <br/> - Availability group load balancer IP address health probe: **59999** or any available port <br/> - Cluster core load balancer IP address health probe: **58888** or any available port |
 |![Square](./media/virtual-machines-windows-portal-sql-availability-group-tutorial/square.png)|Add Failover Clustering Feature | Both SQL Servers require this feature |
 |![Square](./media/virtual-machines-windows-portal-sql-availability-group-tutorial/square.png)|Installation domain account | - Local administrator on each SQL Server <br/> - Member of SQL Server sysadmin fixed server role for each instance of SQL Server  |
 
@@ -75,7 +75,7 @@ After the prerequisites are completed, the first step is to create a Windows Ser
    | Access Point for Administering the Cluster |Type a cluster name, for example **SQLAGCluster1** in **Cluster Name**.|
    | Confirmation |Use defaults unless you are using Storage Spaces. See the note following this table. |
 
-### Set the cluster IP address
+### Set the Windows server failover cluster IP address
 
 1. In **Failover Cluster Manager**, scroll down to **Cluster Core Resources** and expand the cluster details. You should see both the **Name** and the **IP Address** resources in the **Failed** state. The IP address resource cannot be brought online because the cluster is assigned the same IP address as the machine itself, therefore it is a duplicate address.
 
@@ -340,13 +340,15 @@ At this point, you have an Availability Group with replicas on two instances of
 
 On Azure virtual machines, a SQL Server Availability Group requires a load balancer. The load balancer holds the IP addresses for the Availability Group listeners and the Windows Server Failover Cluster. This section summarizes how to create the load balancer in the Azure portal.
 
+An Azure Load Balancer can be either a Standard Load Balancer or a Basic Load Balancer. Standard Load Balancer has more features than the Basic Load Balancer. For an availability group, the Standard Load Balancer is required if you use an Availability Zone (instead of an Availability Set). For details on the difference between the load balancer types, see [Load Balancer SKU comparison](../../../load-balancer/load-balancer-overview.md#skus).
+
 1. In the Azure portal, go to the resource group where your SQL Servers are and click **+ Add**.
-2. Search for **Load Balancer**. Choose the load balancer published by Microsoft.
+1. Search for **Load Balancer**. Choose the load balancer published by Microsoft.
 
    ![AG in Failover Cluster Manager](./media/virtual-machines-windows-portal-sql-availability-group-tutorial/82-azureloadbalancer.png)
 
-1.  Click **Create**.
-3. Configure the following parameters for the load balancer.
+1. Click **Create**.
+1. Configure the following parameters for the load balancer.
 
    | Setting | Field |
    | --- | --- |
@@ -355,7 +357,7 @@ On Azure virtual machines, a SQL Server Availability Group requires a load balan
    | **Virtual network** |Use the name of the Azure virtual network. |
    | **Subnet** |Use the name of the subnet that the virtual machine is in.  |
    | **IP address assignment** |Static |
-   | **IP address** |Use an available address from subnet. Note that this is different from your cluster IP address |
+   | **IP address** |Use an available address from subnet. Use this address for your availability group listener. Note that this is different from your cluster IP address.  |
    | **Subscription** |Use the same subscription as the virtual machine. |
    | **Location** |Use the same location as the virtual machine. |
 
@@ -373,7 +375,9 @@ To configure the load balancer, you need to create a backend pool, a probe, and
 
    ![Find Load Balancer in Resource Group](./media/virtual-machines-windows-portal-sql-availability-group-tutorial/86-findloadbalancer.png)
 
-1. Click the load balancer, click **Backend pools**, and click **+Add**. 
+1. Click the load balancer, click **Backend pools**, and click **+Add**.
+
+1. Type a name for the backend pool.
 
 1. Associate the backend pool with the availability set that contains the VMs.
 
@@ -388,7 +392,7 @@ To configure the load balancer, you need to create a backend pool, a probe, and
 
 1. Click the load balancer, click **Health probes**, and click **+Add**.
 
-1. Set the health probe as follows:
+1. Set the listener health probe as follows:
 
    | Setting | Description | Example
    | --- | --- |---
@@ -404,14 +408,14 @@ To configure the load balancer, you need to create a backend pool, a probe, and
 
 1. Click the load balancer, click **Load balancing rules**, and click **+Add**.
 
-1. Set the load balancing rules as follows.
+1. Set the listener load balancing rules as follows.
    | Setting | Description | Example
    | --- | --- |---
    | **Name** | Text | SQLAlwaysOnEndPointListener |
    | **Frontend IP address** | Choose an address |Use the address that you created when you created the load balancer. |
    | **Protocol** | Choose TCP |TCP |
-   | **Port** | Use the port for the availability group listener | 1435 |
-   | **Backend Port** | This field is not used when Floating IP is set for direct server return | 1435 |
+   | **Port** | Use the port for the availability group listener | 1433 |
+   | **Backend Port** | This field is not used when Floating IP is set for direct server return | 1433 |
    | **Probe** |The name you specified for the probe | SQLAlwaysOnEndPointProbe |
    | **Session Persistence** | Drop down list | **None** |
    | **Idle Timeout** | Minutes to keep a TCP connection open | 4 |
@@ -420,17 +424,17 @@ To configure the load balancer, you need to create a backend pool, a probe, and
    > [!WARNING]
    > Direct server return is set during creation. It cannot be changed.
 
-1. Click **OK** to set the load balancing rules.
+1. Click **OK** to set the listener load balancing rules.
 
-### Add the front end IP address for the WSFC
+### Add the cluster core IP address for the Windows Server Failover Cluster (WSFC)
 
 The WSFC IP address also needs to be on the load balancer.
 
-1. In the portal, add a new Frontend IP configuration for the WSFC. Use the IP Address you configured for the WSFC in the cluster core resources. Set the IP address as static.
+1. In the portal, on the same Azure load balancer, click **Frontend IP configuration** and click **+Add**. Use the IP Address you configured for the WSFC in the cluster core resources. Set the IP address as static.
 
-1. Click the load balancer, click **Health probes**, and click **+Add**.
+1. On the load balancer, click **Health probes**, and click **+Add**.
 
-1. Set the health probe as follows:
+1. Set the WSFC cluster core IP address health probe as follows:
 
    | Setting | Description | Example
    | --- | --- |---
@@ -444,13 +448,13 @@ The WSFC IP address also needs to be on the load balancer.
 
 1. Set the load balancing rules. Click **Load balancing rules**, and click **+Add**.
 
-1. Set the load balancing rules as follows.
+1. Set the cluster core IP address load balancing rules as follows.
    | Setting | Description | Example
    | --- | --- |---
-   | **Name** | Text | WSFCEndPointListener |
-   | **Frontend IP address** | Choose an address |Use the address that you created when you configured the WSFC IP address. |
+   | **Name** | Text | WSFCEndPoint |
+   | **Frontend IP address** | Choose an address |Use the address that you created when you configured the WSFC IP address. This is different from the listener IP address |
    | **Protocol** | Choose TCP |TCP |
-   | **Port** | Use the port for the availability group listener | 58888 |
+   | **Port** | Use the port for the cluster IP address. This is an available port that is not used for the listener probe port. | 58888 |
    | **Backend Port** | This field is not used when Floating IP is set for direct server return | 58888 |
    | **Probe** |The name you specified for the probe | WSFCEndPointProbe |
    | **Session Persistence** | Drop down list | **None** |
@@ -483,7 +487,7 @@ In SQL Server Management Studio, set the listener port.
 
 1. You should now see the listener name that you created in Failover Cluster Manager. Right-click the listener name and click **Properties**.
 
-1. In the **Port** box, specify the port number for the Availability Group listener by using the $EndpointPort you used earlier (1433 was the default), then click **OK**.
+1. In the **Port** box, specify the port number for the Availability Group listener. 1433 is the default, then click **OK**.
 
 You now have a SQL Server Availability Group in Azure virtual machines running in Resource Manager mode.
 

includes/virtual-machines-ag-listener-configure.md

@@ -10,7 +10,7 @@ The availability group listener is an IP address and network name that the SQL S
 
    ![Cluster Network Name](./media/virtual-machines-ag-listener-configure/90-clusternetworkname.png)
 
-2. <a name="addcap"></a>Add the client access point.  
+1. <a name="addcap"></a>Add the client access point.  
     The client access point is the network name that applications use to connect to the databases in an availability group. Create the client access point in Failover Cluster Manager.
 
     a. Expand the cluster name, and then click **Roles**.
@@ -24,7 +24,9 @@ The availability group listener is an IP address and network name that the SQL S
 
     d. To finish creating the listener, click **Next** twice, and then click **Finish**. Do not bring the listener or resource online at this point.
 
-3. <a name="congroup"></a>Configure the IP resource for the availability group.
+1. Take the availability group cluster role offline. In **Failover Cluster Manager** under **Roles**, right-click the role, and select **Stop Role**.
+
+1. <a name="congroup"></a>Configure the IP resource for the availability group.
 
     a. Click the **Resources** tab, and then expand the client access point you created.  
     The client access point is offline.
@@ -41,7 +43,7 @@ The availability group listener is an IP address and network name that the SQL S
     1. Disable NetBIOS for this address and click **OK**. Repeat this step for each IP resource if your solution spans multiple Azure VNets. 
     ------------------------->
 
-4. <a name = "dependencyGroup"></a>Make the SQL Server availability group resource dependent on the client access point.
+1. <a name = "dependencyGroup"></a>Make the SQL Server availability group resource dependent on the client access point.
 
     a. In Failover Cluster Manager, click **Roles**, and then click your availability group.
 
@@ -53,7 +55,7 @@ The availability group listener is an IP address and network name that the SQL S
 
     d. Click **OK**.
 
-5. <a name="listname"></a>Make the client access point resource dependent on the IP address.
+1. <a name="listname"></a>Make the client access point resource dependent on the IP address.
 
     a. In Failover Cluster Manager, click **Roles**, and then click your availability group. 
 
@@ -65,34 +67,37 @@ The availability group listener is an IP address and network name that the SQL S
 
    ![IP Resource](./media/virtual-machines-ag-listener-configure/98-propertiesdependencies.png) 
 
-    d. Right-click the listener name, and then click **Bring Online**. 
-
     >[!TIP]
     >You can validate that the dependencies are correctly configured. In Failover Cluster Manager, go to Roles, right-click the availability group, click **More Actions**, and then click  **Show Dependency Report**. When the dependencies are correctly configured, the availability group is dependent on the network name, and the network name is dependent on the IP address. 
 
 
-6. <a name="setparam"></a>Set the cluster parameters in PowerShell.
+1. <a name="setparam"></a>Set the cluster parameters in PowerShell.
 
   a. Copy the following PowerShell script to one of your SQL Server instances. Update the variables for your environment.
 
-  - `$ILBIP` is the IP address that you created on the Azure load balancer for the availability group listener.
+  - `$ListenerILBIP` is the IP address that you created on the Azure load balancer for the availability group listener.
 
-  - `$ProbePort` is the port you configured on the Azure load balancer for the availability group listener.
+  - `$ListenerProbePort` is the port you configured on the Azure load balancer for the availability group listener.
 
   ```PowerShell
   $ClusterNetworkName = "<MyClusterNetworkName>" # the cluster network name (Use Get-ClusterNetwork on Windows Server 2012 of higher to find the name)
   $IPResourceName = "<IPResourceName>" # the IP Address resource name
-  $ILBIP = "<n.n.n.n>" # the IP Address of the Internal Load Balancer (ILB). This is the static IP address for the load balancer you configured in the Azure portal.
-  [int]$ProbePort = <nnnnn>
+  $ListenerILBIP = "<n.n.n.n>" # the IP Address of the Internal Load Balancer (ILB). This is the static IP address for the load balancer you configured in the Azure portal.
+  [int]$ListenerProbePort = <nnnnn>
   
   Import-Module FailoverClusters
 
-  Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$ILBIP";"ProbePort"=$ProbePort;"SubnetMask"="255.255.255.255";"Network"="$ClusterNetworkName";"EnableDhcp"=0}
+  Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$ListenerILBIP";"ProbePort"=$ListenerProbePort;"SubnetMask"="255.255.255.255";"Network"="$ClusterNetworkName";"EnableDhcp"=0}
   ```
 
   b. Set the cluster parameters by running the PowerShell script on one of the cluster nodes.  
 
-Repeat the steps above to set the cluster parameters for the WSFC cluster IP address.
+  > [!NOTE]
+  > If your SQL Server instances are in separate regions, you need to run the PowerShell script twice. The first time, use the `$ListenerILBIP` and `$ListenerProbePort` from the first region. The second time, use the `$ListenerILBIP` and `$ListenerProbePort` from the second region. The cluster network name and the cluster IP resource name are also different for each region.
+
+1. Bring the availability group cluster role online. In **Failover Cluster Manager** under **Roles**, right click the role, and select **Start Role**.
+
+If necessary, repeat the steps above to set the cluster parameters for the WSFC cluster IP address.
 
 1. Get the IP address name of the WSFC Cluster IP address. In **Failover Cluster Manager** under **Cluster Core Resources**, locate **Server Name**.
 
@@ -104,22 +109,22 @@ Repeat the steps above to set the cluster parameters for the WSFC cluster IP add
 
   a. Copy the following PowerShell script to one of your SQL Server instances. Update the variables for your environment.
 
-  - `$ILBIP` is the IP address that you created on the Azure load balancer for the WSFC core cluster resource. It is different from the IP address for the availability group listener.
+  - `$ClusterCoreIP` is the IP address that you created on the Azure load balancer for the WSFC core cluster resource. It is different from the IP address for the availability group listener.
 
-  - `$ProbePort` is the port you configured on the Azure load balancer for the WSFC health probe. It is different from the probe for the availability group listener.
+  - `$ClusterProbePort` is the port you configured on the Azure load balancer for the WSFC health probe. It is different from the probe for the availability group listener.
 
   ```PowerShell
   $ClusterNetworkName = "<MyClusterNetworkName>" # the cluster network name (Use Get-ClusterNetwork on Windows Server 2012 of higher to find the name)
   $IPResourceName = "<ClusterIPResourceName>" # the IP Address resource name
-  $ILBIP = "<n.n.n.n>" # the IP Address of the Cluster IP resource. This is the static IP address for the load balancer you configured in the Azure portal.
-  [int]$ProbePort = <nnnnn> # The probe port from the WSFCEndPointprobe in the Azure portal. This port must be different from the probe port for the availability grouop listener probe port.
+  $ClusterCoreIP = "<n.n.n.n>" # the IP Address of the Cluster IP resource. This is the static IP address for the load balancer you configured in the Azure portal.
+  [int]$ClusterProbePort = <nnnnn> # The probe port from the WSFCEndPointprobe in the Azure portal. This port must be different from the probe port for the availability grouop listener probe port.
   
   Import-Module FailoverClusters
   
-  Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$ILBIP";"ProbePort"=$ProbePort;"SubnetMask"="255.255.255.255";"Network"="$ClusterNetworkName";"EnableDhcp"=0}
+  Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{"Address"="$ClusterCoreIP";"ProbePort"=$ClusterProbePort;"SubnetMask"="255.255.255.255";"Network"="$ClusterNetworkName";"EnableDhcp"=0}
   ```
 
   b. Set the cluster parameters by running the PowerShell script on one of the cluster nodes.  
 
-  > [!NOTE]
-  > If your SQL Server instances are in separate regions, you need to run the PowerShell script twice. The first time, use the `$ILBIP` and `$ProbePort` from the first region. The second time, use the `$ILBIP` and `$ProbePort` from the second region. The cluster network name and the cluster IP resource name are the same.
+>[!WARNING]
+>The availability group listener health probe port has to be different from the cluster core IP address health probe port. In these examples, the listener port is 59999 and the cluster core IP address is 58888. Both ports require an allow inbound firewall rule.