Merge pull request MicrosoftDocs#2446 from MikeRayMSFT/20170713_DistributedAG_IP_ALL

Fix items mentioned in PR 2426

Author: PRMerger7

docs/database-engine/availability-groups/windows/configure-distributed-availability-groups.md

@@ -1,5 +1,5 @@
 ---
-title: "Configure distributed Availability Groups (Always On Availability Groups) | Microsoft Docs"
+title: "Configure distributed availability group (Always On Availability Group) | Microsoft Docs"
 ms.custom: ""
 ms.date: "07/12/2017"
 ms.prod: "sql-server-2016"
@@ -18,15 +18,17 @@ manager: "jhubbard"
 
 # Configure distributed availability group  
 
-To create a distributed availability group, you must create an availability group and listener on each WSFC. You then combine these into a distributed availability group. The following steps provide a basic example in Transact-SQL. This example does not cover all of the details of creating availability groups and listeners; instead, it focuses on highlighting the key requirements. 
+To create a distributed availability group, you must create an availability group and listener on each Windows Server Failover Cluster (WSFC). You then combine these into a distributed availability group. The following steps provide a basic example in Transact-SQL. This example does not cover all of the details of creating availability groups and listeners; instead, it focuses on highlighting the key requirements. 
 
-For a technical overview of distributed availability groups, see [Distributed Availability Groups](distributed-availability-groups.md).   
+For a technical overview of distributed availability groups, see [Distributed availability groups](distributed-availability-groups.md).   
 
-## Set the endpoint listeners to listen to all IP addresses
+## Prerequisites
 
-On each server that will host a replica in the distributed availability group, configure the listener to `LISTENER_IP = ALL`. The listeners on each server cannot listen to a specific IP address because the endpoint listener must listen to traffic coming over the server IP address as well as the listener IP address.  
+### Set the endpoint listeners to listen to all IP addresses
 
-### Create a listener to listen to all IP addresses
+Make sure the endpoints can communicate between the different availability groups in the distributed availability group. If one availability group is set to a specific network on the endpoint, the distributed AG will not work properly. On each server that will host a replica in the distributed availability group, configure the listener to `LISTENER_IP = ALL`. 
+
+#### Create a listener to listen to all IP addresses
 
 For example, the following script creates a listener endpoint on TCP port 5022 that listens on all IP addresses.  
 
@@ -42,7 +44,7 @@ FOR DATA_MIRRORING (
 GO
 ```
 
-### Alter a listener to listen to all IP addresses
+#### Alter a listener to listen to all IP addresses
 
 For example, the following script changes a listener endpoint to listen on all IP addresses.  
 
@@ -52,8 +54,9 @@ ALTER ENDPOINT [aodns-hadr]
 GO
 ```
 
+## Create first availability group
 
-## Create the primary availability group on the first cluster  
+### Create the primary availability group on the first cluster  
 Create an availability group on the first WSFC.   In this example, the availability group is named `ag1` for the database `db1`.      
 
 ```tsql  
@@ -77,7 +80,7 @@ GO
 
 Note that this example uses direct seeding, where **SEEDING_MODE** is set to **AUTOMATIC** for both the replicas and the distributed availability group. This means that once established, the secondary replicas and secondary availability group will be automatically populated without requiring a manual backup and restore of primary database.  
 
-## Join the secondary replicas to the primary availability group  
+### Join the secondary replicas to the primary availability group  
 Any secondary replicas must be joined to the availability group with **ALTER AVAILABILITY GROUP** with the **JOIN** option. Because direct seeding is used in this example, you must also call  **ALTER AVAILABILITY GROUP** with the **GRANT CREATE ANY DATABASE** option. This allows the availability group to create the database and begin seeding it automatically from the primary replica.  
 
 In this example, the following commands are run on the secondary replica, `server2`, to join the `ag1` availability group. The availability group is then permitted to create databases on the secondary.  
@@ -88,7 +91,7 @@ ALTER AVAILABILITY GROUP [ag1] GRANT CREATE ANY DATABASE
 GO  
 ```  
 
-## Create a listener for the primary availability group  
+### Create a listener for the primary availability group  
 
 Next add a listener for the primary availability group on the first WSFC. In this example, the listener is named `ag1-listener`. For detailed instructions on creating a listener, see [Create or Configure an Availability Group Listener (SQL Server)](../../../database-engine/availability-groups/windows/create-or-configure-an-availability-group-listener-sql-server.md).  
 
@@ -98,7 +101,8 @@ ALTER AVAILABILITY GROUP [ag1]
 GO  
 ```  
 
-## Create the secondary availability group on the second cluster  
+
+## Create second availability group  
  Then on the second WSFC, create a second availability group, `ag2`. In this case, the database is not specified, because it will be automatically seeded from the primary availability group.  
 
 ```tsql  
@@ -122,7 +126,7 @@ GO
 > [!NOTE]  
 >  Note that the secondary availability group must use the same database mirroring endpoint (in this example port 5022). Otherwise, replication will stop after a local failover.  
   
-## Join the secondary replicas to the secondary availability group  
+### Join the secondary replicas to the secondary availability group  
  In this example, the following  commands are run on the secondary replica, `server4`, to join the `ag2` availability group. The availability group is then permitted to create databases on the secondary to support direct seeding.  
 
 ```tsql  
@@ -131,7 +135,7 @@ ALTER AVAILABILITY GROUP [ag2] GRANT CREATE ANY DATABASE
 GO  
 ```  
 
-## Create a listener for  the secondary availability group  
+### Create a listener for  the secondary availability group  
  Next add a listener for the secondary availability group on the second WSFC. In this example, the listener is named `ag2-listener`. For detailed instructions on creating a listener, see [Create or Configure an Availability Group Listener (SQL Server)](../../../database-engine/availability-groups/windows/create-or-configure-an-availability-group-listener-sql-server.md).  
 
 ```  
@@ -140,7 +144,7 @@ ALTER AVAILABILITY GROUP [ag2]
 GO  
 ```  
 
-## Create the distributed availability group on the first cluster  
+## Create distributed availability group on first cluster  
  On the first WSFC, create a distributed availability group (named `distributedag` in this example). Use the **CREATE AVAILABILITY GROUP** command with the **DISTRIBUTED** option. The **AVAILABILITY GROUP ON** parameter specifies the member availability groups, `ag1` and `ag2`.  
 
 ```tsql  
@@ -167,7 +171,7 @@ GO
 > [!NOTE]  
 >  The **LISTENER_URL** specifies the listener for each availability group along with the database mirroring endpoint of the availability group. In this example, that is port `5022` (not port `60173` used to create the listener).  
   
-### Join the distributed availability group on the second cluster  
+## Join distributed availability group on second cluster  
  Then join the distributed availability group on the second WSFC.  
 
 ```tsql  
@@ -241,9 +245,10 @@ Only manual failover is supported at this time. The following Transact-SQL state
       ALTER AVAILABILITY GROUP distributedag SET (ROLE = SECONDARY); 
       ```  
 
-    Note: at this point, the distributed availability group is not available.
+   >[NOTE!]
+   >At this point, the distributed availability group is not available.
 
-1. Test the failover readiness. Run the following quey:
+1. Test the failover readiness. Run the following query:
 
       ```tsql
       SELECT ag.name, 
@@ -262,7 +267,9 @@ Only manual failover is supported at this time. The following Transact-SQL state
       ```tsql
       ALTER AVAILABILITY GROUP distributedag FORCE_FAILOVER_ALLOW_DATA_LOSS; 
       ```  
-      Note: After this step, the distributed availability group is available.
+
+   >[NOTE!]
+   >After this step, the distributed availability group is available.
       
 After completing the steps above, the distributed availability group fails over without any data loss. Microsoft recommends changing the availability mode back to ASYNCHRONOUS_COMMIT if the availability groups are across a geographical distance that causes latency. 
   
@@ -273,7 +280,7 @@ After completing the steps above, the distributed availability group fails over
 DROP AVAILABILITY GROUP [distributedag]  
 ```  
 
-## Create a Distributed Availability Group with Failover Cluster Instances
+## Create distributed availability group on failover cluster instances
 
 You can create a distributed availability group using an availability group on a failover cluster instance (FCI). In this case, you don't need an availability group listener. Use the virtual network name (VNN) for the primary replica of the FCI instance. The following example shows a distributed availability group called SQLFCIDAG. One availability group is SQLFCIAG. SQLFCIAG has 2 FCI replicas. The VNN for the primary FCI replica is SQLFCIAG-1, and the VNN for the secondary FCI replica is SQLFCIAG-2. The distributed availability group also includes SQLAG-DR, for disaster recovery.
 
@@ -303,11 +310,12 @@ CREATE AVAILABILITY GROUP [SQLFCIDAG]
       );   
 ```  
 
-Note that the listener URL is the VNN of the primary FCI instance.
+>[NOTE!]
+>The listener URL is the VNN of the primary FCI instance.
 
-## Manually Failover FCI in Distributed Availability Group
+## Manually fail over FCI in distributed availability group
 
-To manually failover the FCI availability group, update the distributed availability group to reflect the change of listener URL. For example, run the following DDL on both the primary AG and the secondary AG of SQLFCIAG:
+To manually fail over the FCI availability group, update the distributed availability group to reflect the change of listener URL. For example, run the following DDL on both the primary AG and the secondary AG of SQLFCIAG:
 
 ```tsql  
 ALTER AVAILABILITY GROUP [SQLFCIDAG]  
@@ -318,7 +326,8 @@ ALTER AVAILABILITY GROUP [SQLFCIDAG]
     )
 ```  
 
-## See Also  
+## Next steps
+
  [CREATE AVAILABILITY GROUP (Transact-SQL)](../../../t-sql/statements/create-availability-group-transact-sql.md)   
  [ALTER AVAILABILITY GROUP (Transact-SQL)](../../../t-sql/statements/alter-availability-group-transact-sql.md)