Skip to content

Commit 65fcb7e

Browse files
author
Ankita Dutta
committed
removing blockers
1 parent c6bcdea commit 65fcb7e

File tree

4 files changed

+14
-14
lines changed

4 files changed

+14
-14
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,12 +39,12 @@ You can provide the following key resource configurations for the failover VM wh
3939
2. Select the desired Azure VM.
4040
3. Select **Network** and select **Edit**. Notice that the NIC configuration settings include the corresponding resources at the source.
4141

42-
:::image type="content" source="./media/azure-to-azure-customize-networking/edit-networking-properties.png" alt-text="Image showing how to Customize the failover networking configurations." lightbox="./media/azure-to-azure-customize-networking/edit-networking-properties.png":::
42+
:::image type="content" source="./media/azure-to-azure-customize-networking/edit-networking-properties.png" alt-text="Screenshot of how to Customize the failover networking configurations." lightbox="./media/azure-to-azure-customize-networking/edit-networking-properties.png":::
4343

4444
4. Select a test failover virtual network.
4545
5. Select the NIC tab you want to configure. Now, select the corresponding pre-created resources in the test failover and failover location.
4646

47-
:::image type="content" source="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png" alt-text="Image showing how to Edit the NIC configuration." lightbox="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png":::
47+
:::image type="content" source="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png" alt-text="Screenshot of Edit the NIC configuration." lightbox="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png":::
4848

4949
6. Select **OK**.
5050

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,14 +27,14 @@ Map networks as follows:
2727

2828
1. In **Site Recovery Infrastructure**, click **+Network Mapping**.
2929

30-
:::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png" alt-text="Image showing how to Create a network mapping." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png":::
30+
:::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png" alt-text="Screenshot of Create a network mapping." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png":::
3131

3232
3. In **Add network mapping**, select the source and target locations. In our example, the source VM is running in the East Asia region, and replicates to the Southeast Asia region.
3333

34-
:::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png" alt-text="Image showing how to Select source and target." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png":::
34+
:::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png" alt-text="Screenshot of Select source and target." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png":::
3535
3. Now create a network mapping in the opposite direction. In our example, the source will now be Southeast Asia, and the target will be East Asia.
3636

37-
:::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png" alt-text="Image showing how to Add network mapping pane - Select source and target locations for the target network." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png":::
37+
:::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png" alt-text="Screenshot of Add network mapping pane - Select source and target locations for the target network." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png":::
3838

3939

4040
## Map networks when you enable replication
@@ -59,7 +59,7 @@ The subnet of the target VM is selected based on the name of the subnet of the s
5959
- 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.
6060
- You can modify the target subnet in the **Network** settings for the VM.
6161

62-
:::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png" alt-text="Image showing how to Network compute properties window" lightbox="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png":::
62+
:::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png" alt-text="Screenshot of Network compute properties window" lightbox="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png":::
6363

6464
## Set up IP addressing for target VMs
6565

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.custom: engagement-fy23
1616

1717
Accelerated Networking enables single root I/O virtualization (SR-IOV) to a VM, greatly improving its networking performance. This high-performance path bypasses the host from the datapath, reducing latency, jitter, and CPU utilization, for use with the most demanding network workloads on supported VM types. The following picture shows communication between two VMs with and without accelerated networking:
1818

19-
:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png" alt-text="Image showing Comparison." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png":::
19+
:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png" alt-text="Screenshot of difference between accelerated and non-accelerated networking." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png":::
2020

2121
Azure Site Recovery enables you to utilize the benefits of Accelerated Networking, for Azure virtual machines that are failed over to a different Azure region. This article describes how you can enable Accelerated Networking for Azure virtual machines replicated with Azure Site Recovery.
2222

@@ -70,7 +70,7 @@ When you [enable replication](azure-to-azure-tutorial-enable-replication.md) for
7070

7171
The status of Accelerated Networking can be verified under the respective NIC's Tab in the **Network** settings for the replicated virtual machine.
7272

73-
:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png" alt-text="Image showing the Accelerated Networking setting." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png":::
73+
:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png" alt-text="Screenshot of Accelerated Networking setting." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png":::
7474

7575

7676

@@ -79,7 +79,7 @@ If you have enabled Accelerated Networking on the source virtual machine after e
7979
2. Click on the name of the network interface under the **Network interfaces** section
8080
3. Select **Enabled** from the dropdown for Accelerated Networking under the **Target** column
8181

82-
:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png" alt-text="Image showing how to Enable Accelerated Networking." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png":::
82+
:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png" alt-text="Screenshot of Enable Accelerated Networking." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png":::
8383

8484

8585
The above process should also be followed for existing replicated virtual machines, that did not previously have Accelerated Networking enabled automatically by Site Recovery.

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,24 +25,24 @@ Site Recovery automatically configures the failover of your Primary IP Configura
2525

2626
1. Navigate to the **Network** blade on the Replicated Items page.
2727

28-
:::image type="content" source="./media/concepts-multiple-ip-address-failover/network-tab.png" alt-text="Image showing Replicated Items Blade.":::
28+
:::image type="content" source="./media/concepts-multiple-ip-address-failover/network-tab.png" alt-text="Screenshot of Replicated Items Blade.":::
2929

3030

3131
2. You will see the following highlighted text. Click on **Edit** to modify it.
3232

33-
:::image type="content" source="./media/concepts-multiple-ip-address-failover/network-edit.png" alt-text="Image showing Network Tab Edit Mode." lightbox="./media/concepts-multiple-ip-address-failover/network-edit-expanded.png":::
33+
:::image type="content" source="./media/concepts-multiple-ip-address-failover/network-edit.png" alt-text="Screenshot of Network Tab Edit Mode." lightbox="./media/concepts-multiple-ip-address-failover/network-edit-expanded.png":::
3434

3535
3. Click on "+ IP Configurations". You will see two options, Either add all IP Configurations, or selectively add IP Configurations.
3636

37-
:::image type="content" source="./media/concepts-multiple-ip-address-failover/add-ip-configurations.png" alt-text="Image showing how to Add IP Configurations.":::
37+
:::image type="content" source="./media/concepts-multiple-ip-address-failover/add-ip-configurations.png" alt-text="Screenshot of Add IP Configurations.":::
3838

3939
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.
4040

41-
:::image type="content" source="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations.png" alt-text="Image showing how to add All IP Configurations." lightbox="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations-expanded.png":::
41+
:::image type="content" source="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations.png" alt-text="Screenshot of All IP Configurations." lightbox="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations-expanded.png":::
4242

4343
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.
4444

45-
:::image type="content" source="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png" alt-text="Image showing how to Select and Add IP Configurations." lightbox="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png":::
45+
:::image type="content" source="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png" alt-text="Screenshot of Select and Add IP Configurations." lightbox="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png":::
4646

4747
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.
4848

0 commit comments

Comments
 (0)