SAP HANA standby with scale out on SLES - changes for network configuration.

Author: rdeltcheva

articles/virtual-machines/workloads/sap/sap-hana-scale-out-standby-netapp-files-suse.md

@@ -98,16 +98,16 @@ One method for achieving HANA high availability is by configuring host auto fail
 
 In the preceding diagram, which follows SAP HANA network recommendations, three subnets are represented within one Azure virtual network: 
 * For client communication
-* For internal HANA inter-node communication
 * For communication with the storage system
+* For internal HANA inter-node communication
 
 The Azure NetApp volumes are in separate subnet, [delegated to Azure NetApp Files](https://docs.microsoft.com/azure/azure-netapp-files/azure-netapp-files-delegate-subnet).  
 
 For this example configuration, the subnets are:  
 
   - `client` 10.23.0.0/24  
-  - `hana` 10.23.3.0/24  
   - `storage` 10.23.2.0/24  
+  - `hana` 10.23.3.0/24  
   - `anf` 10.23.1.0/26  
 
 ## Set up the Azure NetApp Files infrastructure 
@@ -138,7 +138,7 @@ The following instructions assume that you've already deployed your [Azure virtu
 
    As you're deploying the volumes, be sure to select the **NFSv4.1** version. Currently, access to NFSv4.1 requires additional whitelisting. Deploy the volumes in the designated Azure NetApp Files [subnet](https://docs.microsoft.com/rest/api/virtualnetwork/subnets). 
 
-   Keep in mind that the Azure NetApp Files resources and the Azure VMs must be in the same Azure virtual network or in peered Azure virtual networks. For example, **HN1**-data-mnt00001, **HN1**-log-mnt00001, and so on are the volume names and nfs://10.23.1.5/**HN1**-data-mnt00001, nfs://10.23.1.4/**HN1**-log-mnt00001, and so on are the file paths for the Azure NetApp Files volumes.  
+   Keep in mind that the Azure NetApp Files resources and the Azure VMs must be in the same Azure virtual network or in peered Azure virtual networks. For example, **HN1**-data-mnt00001, **HN1**-log-mnt00001, and so on, are the volume names and nfs://10.23.1.5/**HN1**-data-mnt00001, nfs://10.23.1.4/**HN1**-log-mnt00001, and so on, are the file paths for the Azure NetApp Files volumes.  
 
    * volume **HN1**-data-mnt00001 (nfs://10.23.1.5/**HN1**-data-mnt00001)
    * volume **HN1**-data-mnt00002 (nfs://10.23.1.6/**HN1**-data-mnt00002)
@@ -207,26 +207,26 @@ The SAP HANA configuration for the layout that's presented in this article, usin
 
 ## Deploy Linux virtual machines via the Azure portal
 
-First you need to create the Azure NetApp Files volumes. Then do the following:
+First you need to create the Azure NetApp Files volumes. Then do the following steps:
 1. Create the [Azure virtual network subnets](https://docs.microsoft.com/azure/virtual-network/virtual-network-manage-subnet) in your [Azure virtual network](https://docs.microsoft.com/azure/virtual-network/virtual-networks-overview). 
 1. Deploy the VMs. 
 1. Create the additional network interfaces, and attach the network interfaces to the corresponding VMs.  
 
-   Each virtual machine has three network interfaces, which correspond to the three Azure virtual network subnets (`client`, `hana` and`storage`). 
+   Each virtual machine has three network interfaces, which correspond to the three Azure virtual network subnets (`client`, `storage` and `hana`). 
 
    For more information, see [Create a Linux virtual machine in Azure with multiple network interface cards](https://docs.microsoft.com/azure/virtual-machines/linux/multiple-nics).  
 
 > [!IMPORTANT]
 > For SAP HANA workloads, low latency is critical. To achieve low latency, work with your Microsoft representative to ensure that the virtual machines and the Azure NetApp Files volumes are deployed in close proximity. When you're [onboarding new SAP HANA system](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRxjSlHBUxkJBjmARn57skvdUQlJaV0ZBOE1PUkhOVk40WjZZQVJXRzI2RC4u) that's using SAP HANA Azure NetApp Files, submit the necessary information. 
  
-The next instructions assume that you've already created the resource group, the Azure virtual network, and the three Azure virtual network subnets: `client`, `hana` and `storage`. When you deploy the VMs, select the client subnet, so that the client network interface is the primary interface on the VMs. You will also need to configure an explicit route to the Azure NetApp Files delegated subnet via the storage subnet gateway. 
+The next instructions assume that you've already created the resource group, the Azure virtual network, and the three Azure virtual network subnets: `client`, `storage` and `hana`. When you deploy the VMs, select the client subnet, so that the client network interface is the primary interface on the VMs. You will also need to configure an explicit route to the Azure NetApp Files delegated subnet via the storage subnet gateway. 
 
 > [!IMPORTANT]
 > Make sure that the OS you select is SAP-certified for SAP HANA on the specific VM types you're using. For a list of SAP HANA certified VM types and OS releases for those types, go to the [SAP HANA certified IaaS platforms](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/iaas.html#categories=Microsoft%20Azure) site. Click into the details of the listed VM type to get the complete list of SAP HANA-supported OS releases for that type.  
 
 1. Create an availability set for SAP HANA. Make sure to set the max update domain.  
 
-2. Create three virtual machines (**hanadb1**, **hanadb2**, **hanadb3**) by doing the following:  
+2. Create three virtual machines (**hanadb1**, **hanadb2**, **hanadb3**) by doing the following steps:  
 
    a. Use a SLES4SAP image in the Azure gallery that's supported for SAP HANA. We used a SLES4SAP 12 SP4 image in this example.  
 
@@ -236,11 +236,11 @@ The next instructions assume that you've already created the resource group, the
 
    When you deploy the virtual machines, the network interface name is automatically generated. In these instructions for simplicity we'll refer to the automatically generated network interfaces, which are attached to the client Azure virtual network subnet, as **hanadb1-client**, **hanadb2-client**, and **hanadb3-client**. 
 
-3. Create three network interfaces, one for each virtual machine, for the `hana`  virtual network subnet (in this example, **hanadb1-hana**, **hanadb2-hana**, and **hanadb3-hana**).  
+3. Create three network interfaces, one for each virtual machine, for the `storage` virtual network subnet (in this example, **hanadb1-storage**, **hanadb2-storage**, and **hanadb3-storage**).  
 
-4. Create three network interfaces, one for each virtual machine, for the `storage` virtual network subnet (in this example, **hanadb1-storage**, **hanadb2-storage**, and **hanadb3-storage**).  
+4. Create three network interfaces, one for each virtual machine, for the `hana`  virtual network subnet (in this example, **hanadb1-hana**, **hanadb2-hana**, and **hanadb3-hana**).  
 
-5. Attach the newly created virtual network interfaces to the corresponding virtual machines by doing the following:  
+5. Attach the newly created virtual network interfaces to the corresponding virtual machines by doing the following steps:  
 
     a. Go to the virtual machine in the [Azure portal](https://portal.azure.com/#home).  
 
@@ -256,7 +256,7 @@ The next instructions assume that you've already created the resource group, the
 
     g. Leave the virtual machines in stopped state for now. Next, we'll enable [accelerated networking](https://docs.microsoft.com/azure/virtual-network/create-vm-accelerated-networking-cli) for all newly attached network interfaces.  
 
-6. Enable accelerated networking for the additional network interfaces for the `storage` and `hana` subnets by doing the following:  
+6. Enable accelerated networking for the additional network interfaces for the `storage` and `hana` subnets by doing the following steps:  
 
     a. Open [Azure Cloud Shell](https://azure.microsoft.com/features/cloud-shell/) in the [Azure portal](https://portal.azure.com/#home).  
 
@@ -273,7 +273,7 @@ The next instructions assume that you've already created the resource group, the
 
     </code></pre>
 
-7. Start the virtual machines by doing the following:  
+7. Start the virtual machines by doing the following steps:  
 
     a. In the left pane, select **Virtual Machines**. Filter on the virtual machine name (for example, **hanadb1**), and then select it.  
 
@@ -287,7 +287,7 @@ The instructions in the next sections are prefixed with one of the following:
 * **[2]**: Applicable only to node 2
 * **[3]**: Applicable only to node 3
 
-Configure and prepare your OS by doing the following:
+Configure and prepare your OS by doing the following steps:
 
 1. **[A]** Maintain the host files on the virtual machines. Include entries for all subnets. The following entries were added to `/etc/hosts` for this example.  
 
@@ -308,19 +308,19 @@ Configure and prepare your OS by doing the following:
 
 2. **[A]** Change DHCP and cloud config settings for the network interface for storage to avoid unintended hostname changes.  
 
-The following instructions assume that the storage network interface is `eth1`. 
+    The following instructions assume that the storage network interface is `eth1`. 
 
     <pre><code>
     vi /etc/sysconfig/network/dhcp
-    #Change the following DHCP setting to "no"
+    # Change the following DHCP setting to "no"
     DHCLIENT_SET_HOSTNAME="no"
     vi /etc/sysconfig/network/ifcfg-<b>eth1</b>
     # Edit ifcfg-eth1 
     #Change CLOUD_NETCONFIG_MANAGE='yes' to "no"
     CLOUD_NETCONFIG_MANAGE='no'
     </code></pre>
 
-2. **[A]** Add a network route, so that the communication to the Azure Netapp Files goes via the storage network interface.  
+2. **[A]** Add a network route, so that the communication to the Azure NetApp Files goes via the storage network interface.  
 
 The following instructions assume that the storage network interface is `eth1`. 
 
@@ -333,7 +333,7 @@ The following instructions assume that the storage network interface is `eth1`.
     <b>10.23.1.0/26</b> <b>10.23.2.1</b> - -
     </code></pre>
 
-Reboot the VM to activate the changes.  
+    Reboot the VM to activate the changes.  
 
 3. **[A]** Prepare the OS for running SAP HANA on NetApp Systems with NFS, as described in [SAP HANA on NetApp AFF Systems with NFS configuration guide](https://www.netapp.com/us/media/tr-4435.pdf). Create configuration file */etc/sysctl.d/netapp-hana.conf* for the NetApp configuration settings.