Merge pull request #178127 from rishjai-msft/multiIP

Separation of Compute and Network Blades, Multi-IP Support

Author: Court72

articles/site-recovery/azure-stack-site-recovery.md

@@ -254,7 +254,7 @@ Before you run a test failover, verify the machine properties, and make sure tha
 
 1. In **Protected Items**, click **Replicated Items** > VM.
 2. In the **Replicated item** pane, there's a summary of VM information, health status, and the latest available recovery points. Click **Properties** to view more details.
-3. In **Compute and Network**, modify settings as needed.
+3. In **Compute** and **Network** settings, modify settings as needed.
 
     - You can modify the Azure VM name, resource group, target size, [availability set](../virtual-machines/windows/tutorial-availability-sets.md), and managed disk settings.
     - You can also view and modify network settings. These include the network/subnet to which the Azure VM is joined after failover, and the IP address that will be assigned to the VM.

articles/site-recovery/azure-to-azure-customize-networking.md

@@ -2,12 +2,12 @@
 title: Customize networking configurations for a failover VM  | Microsoft Docs
 description: Provides an overview of customize networking configurations for a failover VM in the replication of Azure VMs using Azure Site Recovery.
 services: site-recovery
-author: sideeksh
-manager: rochakm
+author: rishjai-msft
+manager: gaggupta
 ms.service: site-recovery
 ms.topic: article
-ms.date: 10/21/2019
-ms.author: sideeksh
+ms.date: 10/01/2021
+ms.author: rishjai
 
 ---
 # Customize networking configurations of the target Azure VM
@@ -23,7 +23,8 @@ Learn how Site Recovery provides disaster recovery for [this scenario](azure-to-
 You can provide the following key resource configurations for the failover VM while replicating Azure VMs:
 
 - [Internal load balancer](../load-balancer/load-balancer-overview.md)
-- [Public IP](../virtual-network/ip-services/public-ip-addresses.md)
+- [Public IP](../virtual-network/public-ip-addresses.md)
+- [Secondary IP](../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.md)
 - [Network security group](../virtual-network/manage-network-security-group.md) both for the subnet and for the NIC
 
 ## Prerequisites
@@ -35,14 +36,14 @@ You can provide the following key resource configurations for the failover VM wh
 
 1. Go to **Replicated Items**. 
 2. Select the desired Azure VM.
-3. Select **Compute and Network** and select **Edit**. Notice that the NIC configuration settings include the corresponding resources at the source. 
+3. Select **Network** and select **Edit**. Notice that the NIC configuration settings include the corresponding resources at the source. 
 
-     ![Customize the failover networking configurations](media/azure-to-azure-customize-networking/edit-networking-properties.png)
+    :::image type="content" source="./media/azure-to-azure-customize-networking/edit-networking-properties.png" alt-text="Customize the failover networking configurations" lightbox="./media/azure-to-azure-customize-networking/edit-networking-properties-expanded.png":::
 
 4. Select a test failover virtual network.
-5. Failover network is Select **Edit** near the NIC you want to configure. In the next blade that opens, select the corresponding pre-created resources in the test failover and failover location.
+5. Select the NIC tab you want to configure. Now, select the corresponding pre-created resources in the test failover and failover location.
 
-    ![Edit the NIC configuration](media/azure-to-azure-customize-networking/nic-drilldown.png) 
+    :::image type="content" source="./media/azure-to-azure-customize-networking/nic-drilldown.png" alt-text="Edit the NIC configuration" lightbox="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png":::
 
 6. Select **OK**.
 

articles/site-recovery/azure-to-azure-network-mapping.md

@@ -48,17 +48,17 @@ If you haven't prepared network mapping before you configure disaster recovery f
 
 >[!NOTE]
 >* Modifying the network mapping only changes the defaults for new VM replications. It does not impact the target virtual network selections for existing replications.
->* If you wish to modify the target network for an existing replication, go to Compute and Network Settings of the replicated item.
+>* If you wish to modify the target network for an existing replication, go to **Network** Settings of the replicated item.
 
 ## Specify a subnet
 
 The subnet of the target VM is selected based on the name of the subnet of the source VM.
 
 - If a subnet with the same name as the source VM subnet is available in the target network, that subnet is set for the target VM.
 - If a subnet with the same name doesn't exist in the target network, the first subnet in the alphabetical order is set as the target subnet.
-- You can modify the target subnet in the **Compute and Network** settings for the VM.
+- You can modify the target subnet in the **Network** settings for the VM.
 
-    ![Compute and Network compute properties window](./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png)
+    ![Network compute properties window](./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png)
 
 
 ## Set up IP addressing for target VMs
@@ -68,6 +68,7 @@ The IP address for each NIC on a target virtual machine is configured as follows
 - **DHCP**: If the NIC of the source VM uses DHCP, the NIC of the target VM is also set to use DHCP.
 - **Static IP address**: If the NIC of the source VM uses static IP addressing, the target VM NIC will also use a static IP address.
 
+The same holds for the Secondary IP Configurations as well.
 
 ## IP address assignment during failover
 
@@ -87,7 +88,7 @@ Target network isn't the failover VNet | - Target IP address will be static with
 
 - The failover VNet is the target network that you select when you set up disaster recovery.
 - We recommend that you always use a non-production network for test failover.
-- You can modify the target IP address in the **Compute and Network** settings of the VM.
+- You can modify the target IP address in the **Network** settings of the VM.
 
 
 ## Next steps

articles/site-recovery/azure-to-azure-support-matrix.md

@@ -323,9 +323,9 @@ Internal Load balancer | Supported | Associate the preconfigured load balancer u
 Public IP address | Supported | Associate an existing public IP address with the NIC. Or, create a public IP address and associate it with the NIC using an Azure Automation script in a recovery plan.
 NSG on NIC | Supported | Associate the NSG with the NIC using an Azure Automation script in a recovery plan.
 NSG on subnet | Supported | Associate the NSG with the subnet using an Azure Automation script in a recovery plan.
-Reserved (static) IP address | Supported | If the NIC on the source VM has a static IP address, and the target subnet has the same IP address available, it's assigned to the failed over VM.<br/><br/> If the target subnet doesn't have the same IP address available, one of the available IP addresses in the subnet is reserved for the VM.<br/><br/> You can also specify a fixed IP address and subnet in **Replicated items** > **Settings** > **Compute and Network** > **Network interfaces**.
+Reserved (static) IP address | Supported | If the NIC on the source VM has a static IP address, and the target subnet has the same IP address available, it's assigned to the failed over VM.<br/><br/> If the target subnet doesn't have the same IP address available, one of the available IP addresses in the subnet is reserved for the VM.<br/><br/> You can also specify a fixed IP address and subnet in **Replicated items** > **Settings** > **Network** > **Network interfaces**.
 Dynamic IP address | Supported | If the NIC on the source has dynamic IP addressing, the NIC on the failed over VM is also dynamic by default.<br/><br/> You can modify this to a fixed IP address if required.
-Multiple IP addresses | Not supported | When you fail over a VM that has a NIC with multiple IP addresses, only the primary IP address of the NIC in the source region is kept. To assign multiple IP addresses, you can add VMs to a [recovery plan](recovery-plan-overview.md) and attach a script to assign additional IP addresses to the plan, or you can make the change manually or with a script after failover.
+Multiple IP addresses | Supported | When you fail over a VM that has a NIC with multiple IP addresses, only the primary IP address of the NIC in the source region is kept by default. To failover Secondary IP Configurations, go to the **Network** blade and configure them.
 Traffic Manager     | Supported | You can preconfigure Traffic Manager so that traffic is routed to the endpoint in the source region on a regular basis, and to the endpoint in the target region in case of failover.
 Azure DNS | Supported |
 Custom DNS    | Supported |

articles/site-recovery/azure-vm-disaster-recovery-with-accelerated-networking.md

@@ -3,12 +3,12 @@ title: Enable accelerated networking for Azure VM disaster recovery with Azure S
 description: Describes how to enable Accelerated Networking with Azure Site Recovery for Azure virtual machine disaster recovery
 services: site-recovery
 documentationcenter: ''
-author: Harsha-CS
-manager: rochakm
+author: rishjai-msft
+manager: gaggupta
 ms.service: site-recovery
 ms.topic: conceptual
 ms.date: 04/08/2019
-ms.author: harshacs
+ms.author: rishjai
 
 ---
 # Accelerated Networking with Azure virtual machine disaster recovery
@@ -67,12 +67,12 @@ For more information on VM instances, see [Linux VM sizes](../virtual-machines/s
 
 When you [enable replication](azure-to-azure-tutorial-enable-replication.md) for Azure virtual machines, Site Recovery will automatically detect whether the virtual machine network interfaces have Accelerated Networking enabled. If Accelerated Networking is already enabled, Site Recovery will automatically configure Accelerated Networking on the network interfaces of the replicated virtual machine.
 
-The status of Accelerated Networking can be verified under the **Network interfaces** section of the **Compute and Network** settings for the replicated virtual machine.
+The status of Accelerated Networking can be verified under the respective NIC's Tab in the **Network** settings for the replicated virtual machine.
 
 ![Accelerated Networking setting](./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png)
 
 If you have enabled Accelerated Networking on the source virtual machine after enabling replication, you can enable Accelerated Networking for the replicated virtual machine's network interfaces by the following process:
-1. Open **Compute and Network** settings for the replicated virtual machine
+1. Open **Network** settings for the replicated virtual machine
 2. Click on the name of the network interface under the **Network interfaces** section
 3. Select **Enabled** from the dropdown for Accelerated Networking under the **Target** column
 

articles/site-recovery/concepts-multiple-ip-address-failover.md

@@ -0,0 +1,51 @@
+---
+title: Configure failover of multiple IP addresses with Azure Site Recovery
+description: Describes how to configure the failover of secondary IP configs for Azure VMs
+services: site-recovery
+author: rishjai-msft
+manager: gaggupta
+ms.service: site-recovery
+ms.topic: conceptual
+ms.date: 11/01/2021
+ms.author: rishjai
+
+---
+# Configure failover of multiple IP addresses with Azure Site Recovery
+
+Every NIC attached to a VM has one or more IP configurations associated to it. Each configuration is assigned one static or dynamic private IP address. Each configuration may also have one public IP address resource associated to it. A public IP address resource has either a dynamic or static public IP address assigned to it. To learn more about [IP addresses in Azure](../virtual-network/ip-services/public-ip-addresses.md), read the IP addresses in Azure article.
+
+Today, Site Recovery automatically configures the failover of the Primary IP Configuration. This article describes how you can configure failover of Secondary IP Configs with Site Recovery. Please note that this is supported only for Azure VMs.
+
+## Configure Secondary IP Address Failover via Azure portal
+
+Site Recovery automatically configures the failover of your Primary IP Configuration when you Enable Replication for the VM. Secondary IP Configurations need to be manually configured after the Enable Replication completes. For this you need a protected VM that has one or more Secondary IP Configurations.
+
+Follow the steps as outlined:
+1. Navigate to the **Network** blade on the Replicated Items page.
+
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-tab.png" alt-text="Replicated Items Blade":::
+    
+
+2. You will see the following highlighted text.  Click on **Edit** to modify it.
+ 
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-edit.png" alt-text="Network Tab Edit Mode" lightbox="./media/concepts-multiple-ip-address-failover/network-edit-expanded.png":::    
+
+3. Click on "+ IP Configurations". You will see two options, Either add all IP Configurations, or selectively add IP Configurations.
+
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-ip-configurations.png" alt-text="Add IP Configurations":::
+
+4. On clicking **Add all secondary IP Configurations**, all of them will appear in the grid below, and then you can configure them as you like.
+
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations.png" alt-text="Add All IP Configurations" lightbox="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations-expanded.png":::    
+
+5. Alternatively, on clicking **Select and add secondary IP Configurations**, a blade will open where you can pick and add IP Configurations you'd like to configure for failover.
+
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png" alt-text="Select and Add IP Configurations":::
+
+Now, for each IP Configuration that you've added, you can configure the values for Private IP, Public IP, and Backend Pool for Failover and Test Failover separately. After you've done it all, don't forget to Save changes.
+
+
+## Next steps
+- Learn more about [Traffic Manager with Azure Site Recovery](../site-recovery/concepts-traffic-manager-with-site-recovery.md)
+- Learn more about Traffic Manager [routing methods](../traffic-manager/traffic-manager-routing-methods.md).
+- Learn more about [recovery plans](site-recovery-create-recovery-plans.md) to automate application failover.

articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md

@@ -62,7 +62,7 @@ To select a proximity placement group in the DR region while enabling replicatio
 You can easily update your selection of a proximity placement group in the DR region after replication has been enabled for the VM:
 
 1. Go to the virtual machine. On the left pane, under **Operations**, select **Disaster Recovery**.
-2. Go to the **Compute and Network** pane and select **Edit**.
+2. Go to the **Compute** pane and select **Edit**.
 3. You can see the options to edit multiple target settings, including the target proximity placement group. Choose the proximity placement group that you want the VM to fail over into, and then select **Save**.
 
 ### VMware to Azure